Integrations
Connect Astervis to your CRM and messaging channels.
Astervis is most useful when it sits next to the tools your team already lives in. Connect a CRM and your call data stops being a separate report — every call links itself to the right deal, contact, and operator. Connect a messaging channel and your agents handle chats from the same console they take calls in.
Everything here runs on your own server, alongside the rest of Astervis. There's no middleware in the cloud: webhooks travel between your PBX and your CRM directly, and your call recordings never leave the machine.
Pick an integration
Bitrix24
Two-way sync of leads, deals, contacts, companies and pipeline stages.
Custom fields
Track your Bitrix24 UF_ fields and chart them like any built-in metric.
amoCRM
Click-to-call, incoming-call pop-ups and automatic call logging with recordings.
Open Lines
One operator console for chats from Telegram and WhatsApp.
Telegram
Connect a BotFather bot to a queue and answer customers in chat.
What each one does
Pick by where your customer data and conversations already live.
| Integration | What it gives you |
|---|---|
| Bitrix24 | Deep two-way sync — departments, employees, categories, pipeline stages, leads, deals, deal-stage history, contacts and companies. Inbound webhook + token for the initial pull and backfill; outbound webhooks keep things live. Deal data feeds the sales dashboards. |
| Custom fields | Bitrix24 UF_ custom fields, picked field-by-field. Astervis discovers them via crm.deal.userfield.list, you choose which to track, and the values become first-class columns you can filter and chart. |
| amoCRM | A full OAuth marketplace widget: click-to-call from the contact card, an incoming-call pop-up with the caller's name, automatic call logging, recordings playable inside amoCRM, a callback task on missed calls, and auto-created contacts/deals for unknown numbers. |
| Open Lines | An omnichannel inbox. Telegram and WhatsApp conversations land in one operator console with supervisor monitoring, bots, sessions and quick replies. |
| Telegram | The simplest channel to start with — a single BotFather bot wired to a queue, with a welcome message, commands and media support. |
Bitrix24, Custom fields and Open Lines are configured in the Astervis admin under Settings → Integrations. amoCRM is installed the other way around — from the amoCRM marketplace — because it ships as a widget inside amoCRM itself.
Messaging channels
Open Lines is the omnichannel layer. It turns inbound chats into the same queued, operator-assigned sessions your phone calls already use, so a supervisor watches chat and voice side by side. Two channels are supported today:
Create a bot with @BotFather, then paste its token into Astervis and assign the bot to a queue. From there you can set a welcome message, register commands, and let operators send and receive media. Telegram is the quickest channel to bring online and a good first test of Open Lines.
See Telegram for the step-by-step setup.
Open Lines currently supports Telegram and WhatsApp (Cloud API) only. There is no Instagram channel — if a guide elsewhere mentions one, it's out of date.
How call ↔ CRM linking works
The point of a CRM integration is that a call and a CRM record find each other on their own. Here's the shape of it, regardless of which CRM you use.
A call happens on your PBX
Asterisk writes the Call Detail Record (CDR), and — if the call was recorded —
a recording file in /var/spool/asterisk/monitor. Astervis replicates the CDR
into its local TimescaleDB store as usual.
The number is matched to a CRM record
Astervis looks up the other party's phone number against the contacts, leads and deals it has synced from your CRM. A match attaches the call to that record; an unknown number can auto-create a new contact (and deal) so nothing falls through.
The call is logged back into the CRM
The integration writes the call into the matched record — direction, duration,
operator, and a link to the recording. In amoCRM the recording plays right inside
the contact card; the playback URL is HMAC-signed (via RECORDING_SIGN_SECRET) so
only authorised links resolve. A missed call can spawn a callback task automatically.
Both sides stay in sync
Outbound webhooks from your CRM tell Astervis when a deal moves stage, a contact changes, or a record is created — so dashboards and the operator console reflect reality without anyone re-keying data.
Because deals and their stages are synced, your sales dashboards are driven by real CRM data: deal counts, average sale price and top-performing numbers all come from the CRM you connected — no separate report to maintain.
Recordings and privacy
Call recordings are mounted read-only from your PBX and stay on your server. When a CRM widget plays a recording, it streams from your machine through a signed, time-limited URL — the audio is never copied to a third party. The only thing that can leave the server is what you explicitly opt into: AI analysis, which sends a finished call's audio to Google Gemini. See AI & privacy for exactly what does and doesn't leave the box.
Next steps
Last updated on