Integrations
Connects to your PBX, your messaging channels, your website and your own systems. Connections are managed centrally; secrets are stored encrypted and never returned in responses.
PBX
Asterisk, 3CX, Twilio or no PBX
The call center isn't tied to a PBX brand. Agents place calls from the browser (WebRTC); only the central administrator connects the PBX.
Asterisk
Asterisk-based PBXs, including FreePBX and Issabel.
3CX
3CX PBX driver.
Twilio
Calling through Twilio.
Manual (no PBX)
The default flow. Calls are logged in the panel and placed from the agent's own phone; a PBX can be connected centrally later.
Website
A live chat widget with one line
The script goes on your page; the button and widget open in an iframe from our own address. Your site's CSS doesn't touch the widget, and the widget's CSS doesn't touch your site.
The install script is unique to your company; copy it ready-made from Live Chat → Widget → Install in the app.
Live Chat moduleHelpdesk's request widget is added with its own line, separate from live chat. Your site signs the logged-in user with a secret key (HMAC-SHA256) and passes them to the widget; the user sees their own tickets on every device without logging in again.
Helpdesk moduleThe Analytics tracking script is one line too: by default it measures without cookies, is under 6 KB compressed and runs independently of the chat and ticket widgets.
Analytics moduleWebhooks
Send chat events to your own systems
The events you choose are sent to your https address as JSON. Every request is signed; the receiver signs the body with its own key and compares.
- conversation.started
- Chat started
- conversation.assigned
- Chat assigned to an agent
- conversation.closed
- Chat closed
- conversation.rated
- Visitor rated the chat
- offline_message.created
- Offline message left
- Signature: the body's HMAC-SHA256 value in the X-Voltr-Signature header; the key is shown only once, when it's created.
- The delivery ID stays the same across retries so the receiver can drop duplicates. A failed delivery is attempted 5 times in total.
- Delivery log in the panel: status, response code and body; any delivery can be resent with one click.
- https only; nothing is sent to internal network addresses (SSRF check) and redirects aren't followed.
POST https://example.com/voltr-webhook
Content-Type: application/json
X-Voltr-Event: conversation.closed
X-Voltr-Delivery: 5f0c…-…-…
X-Voltr-Signature: sha256=9b1f…Channels and data
Messaging channels, AI and links between modules
WhatsApp and Telegram connect to their own inboxes, reports can be exported as files, and modules link to each other on the same record.
WhatsApp Business
Meta's official Cloud API: you enter your number's Meta details, and VOLTR subscribes the app and registers the number. Webhook events whose signature doesn't verify are never processed.
Telegram
All you need is the bot token; VOLTR sets up the webhook with a secret token. If you connect your account to the bot with Chat Automation (no Premium needed), messages to that account land in the same inbox.
Claude AI (optional)
If you want, Live Chat's AI assistant writes answers with Claude, and the agent helper runs on Claude; you don't need a key of your own. The default VOLTR matcher doesn't connect to any outside service.
CSV export
Live chat and CRM reports download as CSV for the date range you choose.
CRM records from chats
An agent opens a support ticket or a lead from a chat; the record is linked to the chat and an internal note is added to it.
Activities from calls
A CRM activity can be linked to a company, a deal and a call at the same time, so the full history with a company reads in one place.
Accounts and CRM
An ERP account can be linked to a CRM company, so sales and finance see the same customer.
Chat transcript email
A chat transcript is only sent to the visitor's own email address; the sender name and reply-to address are set in the panel.
Offline messages
When no agent is available the visitor leaves an offline message; it shows among the conversations in the panel and is also sent by webhook.
FAQ
Integration questions
Our PBX is Asterisk-based — can it connect?
Yes. Asterisk-based PBXs including FreePBX and Issabel are supported, and there are drivers for 3CX and Twilio too. You can start with the manual flow and connect the PBX centrally later.
How do we add the chat widget to our site?
Copy your company's script from the panel's Widget tab and add it to your site's pages. The look and texts are edited in the panel; the widget opens in an iframe, so it doesn't affect your site's design.
How do we connect WhatsApp and Telegram?
For WhatsApp you enter your number's Meta details; the app subscription and number registration are done in the panel. For Telegram you enter the bot token you got from @BotFather, and VOLTR sets up the webhook. Details are on the Messaging channels page.
How do we verify a webhook request really came from you?
Every request carries the body's HMAC-SHA256 signature in the X-Voltr-Signature header. Before parsing the body, sign it with your own key and compare in constant time.
Can we export reports?
Yes. Live chat and CRM reports download as CSV for the date range you choose.