With Binotel CRM integration, Elbuz handles calls: one-click calls from the card, and calls with recordings go to the log and customer history automatically.
When you need this:
- The manager doesn't know who's calling — before pickup, Binotel shows the Elbuz customer name on the phone and can route the call to their manager.
- Dialing by hand — “Call” in the card: Binotel connects the manager, then the customer.
- Missed calls get lost — each becomes a “Call back” task in “Pulse”.
- No one answers — after 20 seconds the call goes to an AI employee.
Where to start: ask Binotel support for REST API keys (what to ask for).
What Elbuz can do with Binotel
- The customer's name on the manager's phone before the call is answered — plus routing to the personal manager (name on the phone).
- One-click call from the customer card — from the line number you choose (extensions).
- Call log and recordings — incoming and outgoing, with the “New customer” flag (what reaches Elbuz).
- Incoming and missed call card — name, recent orders, a “Call back” task (call card).
- Call summary in the customer's history — AI analysis and the next step (AI call analysis).
- AI employee on incoming calls — answers if managers don't pick up (voice AI).
What you need from Binotel
REST API keys — a “key + secret” pair — are issued by Binotel itself: Binotel's API document says the customer's developer “will get a key from us”. Binotel's official materials don't describe any place in the account where you can generate them yourself.
- Ask Binotel support for REST API keys (support@binotel.ua). Ask specifically for REST API: Binotel's WebSocket keys are separate, look exactly the same, and Elbuz won't work with them.
- Later, in the same email thread, you'll send the event address (step three) — support will set it up on their side.
- An employee's extension is shown in the My.Business account: «Параметри» (Settings) → the «Співробітники» (Employees) tab → the «Внутрішня лінія» (Extension) column.
The Binotel account paths come from the operator's official documentation. If a menu item is named differently, go by these pages or ask Binotel support:
How to connect Binotel to Elbuz
Three steps in order: keys, extensions and the event address. Without extensions, the “Call” button doesn't work. Without the event address, the log is filled only by the hourly reconciliation, and the customer's name doesn't appear on the phone.
Step one: Binotel keys
Open the Binotel row in the “Telephony” group. The “Active” toggle is already on — leave it that way. Fields you fill in:
| Form field | What to enter |
|---|---|
| “API key” | the REST API key from Binotel |
| “Secret” | the REST API secret from the same pair |
| “Line for outgoing calls” | your Binotel number to call customers from; leave it empty and the PBX picks one itself |
1
Link to the guide2
Active switch3
API key field4
Secret field5
Line for outgoing calls6
Check connection button- The “Where exactly — step by step in the guide for your operator” link leads to this page.
- The “Active” switch — the integration is turned on.
- The “API key” field — the Binotel REST API key, not the WebSocket one.
- The “Secret” field — the REST API secret of the same pair.
- The “Line for outgoing calls” field — the number Binotel calls the customer from.
- The “Check connection” button — a read-only request to the operator, nothing changes in the account.
The form saves itself about a second after each edit: “Saving...” shows at the bottom, then “Saved”. There is no “Save” button.
Finally, click “Test connection”. The reply is “Connected to the PBX. Employees in the PBX: ‹count›”. Elbuz reads the list of Binotel employees with their names, emails and extensions. The “PBX extensions without an Elbuz employee” line shows which Binotel numbers don't match any employee card in Elbuz yet.
Step two: extensions
When a manager clicks “Call”, Binotel first rings their extension and only after they answer dials the customer. The same number links calls in the log to the manager.
Where: employee card (“Users”) → the “Internal phone” field.
Binotel sometimes sends the number together with the group route — for example, “801 > 205”. Elbuz takes the last part after “>”, that is, the line the conversation actually happened on. Enter exactly this final number in the card — 205.
Below the connection form there is an “Employee extensions” card — a “Manager” / “Extension” table for all active employees. Rows with a dash are the ones whose number hasn't been entered yet.
Step three: the event address for Binotel
The form has a “PBX webhook address” card with the address and a “Copy” button. Binotel's official materials don't describe a self-service setting for it: send the address to Binotel support and ask them to set up two events on it — API CALL SETTINGS and API CALL COMPLETED (what they do).
1
Address for the operator2
Copy button- The address you give to the operator; the secret key at the end is masked in the frame.
- The “Copy” button — puts the address on the clipboard.
The address contains a 32-character secret key and the host you opened the form from. If you changed the domain or re-created the service in the list, the address is now different, and you need to send it to Binotel again.
To get Binotel working with Elbuz
What reaches Elbuz
Everything below has been checked against the Binotel integration module in Elbuz.
| Feature | How it works with Binotel |
|---|---|
| Calling from the card and the log (“Call”) | yes: Binotel first rings the manager's extension, then the customer once the manager answers. “Line for outgoing calls” sets which number the call is made from |
| Incoming and outgoing calls in the log | yes, from the call completed event (API CALL COMPLETED) |
| The customer's name on the phone screen | yes: in reply to API CALL SETTINGS, Elbuz returns the name from the card (up to 43 characters) and a link to the card |
| Personal manager | yes: if the contact has a manager assigned, Elbuz sends that manager's email, and Binotel can route the call to them |
| Call recording | yes: Elbuz requests the link from Binotel when you click “Play recording”; the link is valid for 15 minutes |
| “New customer” flag | yes, Binotel sends it — a hidden column in the log is filled in |
| Hourly log reconciliation | yes, at minute 25 of every hour, covering the past 24 hours |
| Hanging up from the incoming call card | yes: the “Hang up” button in the “Incoming call” card |
| Voice AI employee | incoming — yes, via forwarding to a SIP address (set up by Binotel support); outgoing — no (see below) |
Two events Binotel sends to the Elbuz address:
- API CALL SETTINGS — arrives as the call comes in. Elbuz looks up the customer by number and replies with the name and a link to the card; Binotel shows them on the manager's phone and in its Chrome extension.
- API CALL COMPLETED — arrives after the call ends. It puts the call into the log and the customer's feed. If Elbuz doesn't reply “success”, Binotel retries delivery up to seven times.
Binotel specifics
Events are accepted only from Binotel addresses
Binotel events aren't signed, so Elbuz accepts them only from 26 Binotel server addresses and rejects requests from any other address. If Binotel changes its addresses, events will stop arriving without any error on screen — the log will be filled only by the hourly reconciliation.
Customer name on the phone and personal manager
In reply to API CALL SETTINGS, Elbuz sends Binotel the customer's name, a card link and, if set, the personal manager's email. The name is cut to 43 characters — the Binotel extension fits no more. For a company's contact person, the name reads “Company / Contact”. An unknown number gets no name, just a link to the contact list.
Call recordings
Binotel issues a recording link for only 15 minutes, so Elbuz doesn't store it and requests it each time you click “Play recording”. You can listen to a recording for as long as Binotel keeps it.
Hourly reconciliation
Binotel returns call history for no more than 24 hours per request and allows five such requests per minute without a pause. Elbuz splits the period into one-day chunks and, starting from the sixth request, waits 10 seconds between them. The regular hourly reconciliation covers one day — a single request.
How a call from the button works
Elbuz asks Binotel to connect the manager's extension with the customer's number and doesn't wait for the manager to pick up: Binotel replies right away and starts the call on its own. If Binotel doesn't reply within 15 seconds, you'll see a timeout message — the call may already have started anyway.
Voice AI employee on a Binotel number
An Elbuz AI employee can answer calls and call customers on its own. The conversation is handled not by your PBX but by the Elbuz voice platform, so the number has to be routed to it. Settings for the “Voice on the phone” section are in the Voice AI employee article.
Incoming calls: how to route the number to AI
Binotel support confirmed (20.10.2026): a call can be transferred to an external SIP address, the caller's number is preserved, and incoming calls to a SIP address aren't billed separately. Binotel support sets up the forwarding in the call flow itself.
- In the “Voice on the phone” section, enter the Binotel number AI should answer, choose “Other operator” under “Operator” and turn on “Answer calls”. You can leave “Operator addresses” empty — Elbuz will then accept calls from any address. To restrict it, ask Binotel support which addresses these calls come from.
- Copy the SIP address from the section — it looks like
380XXXXXXXXX@<domain>— and add “+” before the number:+380XXXXXXXXX@<domain>. Binotel accepts an external SIP address only in this form: a number with “+” on the left, not a login. Elbuz accepts a call to the number with or without “+”. - Ask Binotel support to set up forwarding to this SIP address in the call flow. It can be for all calls or as a fallback: “if managers haven't answered within 20 seconds, transfer to the SIP address”.
- Call the number and check that AI answers and the caller's number is shown in the call log.
Outgoing AI calls through Binotel
Not available yet. Binotel allows outgoing calls only via a registered SIP trunk, but the Elbuz voice platform runs in a cloud abroad and can't register on a PBX. Also, under Ukrainian law Binotel blocks outgoing calls from Ukrainian numbers via foreign IPs. This needs a Ukrainian SIP gateway, which Elbuz doesn't have yet. Incoming AI calls aren't affected.
Scenarios
The manager sees who's calling before answering
- Send the event address to Binotel support (step three).
- Assign a personal manager to customers in the contact card.
- A customer calls — Binotel shows their name on the phone and can route the call to their manager. The “Incoming call” card pops up on the Elbuz screen.
AI picks up when managers are busy
- Turn on “Answer calls” in the “Voice on the phone” section and copy the SIP address (incoming calls to AI).
- Ask Binotel support: “if managers haven't answered within 20 seconds, transfer to the SIP address”.
- AI gives the order status by the caller's number, answers questions about delivery and payment, and takes down the request.
A missed call doesn't get lost
The manager didn't pick up — a “Missed call” card pops up, and a “Call back” task appears in “Pulse”. The manager clicks “Call”, Binotel connects them to the customer from the “Line for outgoing calls”, and the task closes by itself. More: missed calls.
What to do when Binotel doesn't work with Elbuz
General telephony problems — no call button, an empty log, no recording — are covered in Telephony in Elbuz. Here is what's specific to Binotel.
| What you see | Why | What to do |
|---|---|---|
| There's no “Call” button in the contact list or in the card | The keys aren't entered or the “Active” toggle is off — then call buttons aren't shown at all | Check the fields and the toggle in the connection form (step one) |
| “Your employee card has no extension number” | The “Internal phone” field in your card is empty: the PBX has nowhere to call first | Enter the number in the employee card (step two) |
| “Test connection” returns an error even though the keys are entered | Most often, WebSocket keys were pasted instead of REST API keys — they look the same | Ask Binotel specifically for REST API keys and re-enter both fields |
| The customer's name doesn't show on the manager's phone, and calls appear in the log up to an hour late | Binotel events aren't arriving: the address isn't set up for API CALL SETTINGS / API CALL COMPLETED, or it has the old domain | Copy the address from the “PBX webhook address” card and send it to Binotel again |
| The “Manager” column in the log is empty | The employee's extension in Elbuz doesn't match the final Binotel line | Enter in “Internal phone” the number shown in the “PBX extensions without an Elbuz employee” line |
| “The PBX did not answer in time. If the call did start, it will show up in the call log — check it before dialing again” | The operator didn't reply within 15 seconds. The request may still have been accepted — then your phone will ring a bit later | Don't dial again right away: wait a minute. If the PBX accepted the request, your phone will ring, and after the conversation the call will appear in the log |
FAQ
How do I get Binotel API keys for Elbuz?
Ask Binotel support (support@binotel.ua): the official materials don't describe a place in the account to generate them. You need a “key + secret” pair specifically for REST API — WebSocket keys won't work with Elbuz.
What are API CALL SETTINGS and API CALL COMPLETED?
Two Binotel events. The first arrives as the call comes in, and Elbuz replies with the customer's name. The second arrives after the conversation and puts the call into the log. Both are set up to go to the address from the “PBX webhook address” card.
Will the manager see the customer's name on the phone?
Yes, if the number is in your contacts and Binotel sends API CALL SETTINGS to the Elbuz address. The name is taken from the card and cut to 43 characters.
Can I listen to a Binotel call recording?
Yes. The “Play recording” button in the log requests a fresh link from Binotel each time — it's valid for 15 minutes, so Elbuz doesn't store it.
Why did Binotel events stop arriving without any error?
Elbuz accepts events only from 26 Binotel server addresses and with a valid key in the address. If the domain changed, the service was re-created or Binotel changed its addresses, events are rejected. The log is then filled only by the hourly reconciliation.
Can I call a contact's second number from the card?
No. The “Call” button in the card uses the contact's main phone number.
Can I connect voice AI to a Binotel number?
Yes, for incoming calls: send the SIP address from the “Voice on the phone” section, with “+” before the number, to Binotel support for forwarding (step by step). Outgoing AI calls through Binotel aren't available yet.
Where to find it and who has access
The Binotel connection sits with the other integrations, not in the call log. The window that opens from the operator row is called “API access settings for external services”.
- Menu
- Account → System settings → “Other settings” → “External services and integrations” → “Telephony” → Binotel
- Other ways in
- “Call log” → window menu → “Telephony connection”
- Access right
- system settings and the “Call log” window; you don't need any rights just to make calls
- Prepare
- the Binotel key and secret, employees' extensions
Without the right to “Call log”, “Test connection”, the webhook address and the settings file don't work.
Related topics
- If you need the overall picture of telephony and a comparison of operators — Telephony in Elbuz.
- If the call is already in the log and you need to understand the columns or “Result” — Call log.
- If you want AI to answer and call customers on its own — Voice AI employee.
- If calls aren't linked to a manager — Users, the “Internal phone” field.
- If you need to find a conversation in the customer's history — Contact card.
