Elbuz connects to the Phonet PBX: managers call customers from the card in one click; calls with recordings land in the log and customer history.
When you need this:
- Unknown caller — Phonet shows the customer's Elbuz name on the phone before answering and can route the call to their personal manager.
- Manual dialing — “Call” in the card: Phonet connects the manager, then the customer.
- Lost missed calls — each becomes a “Call back” task in “Pulse”.
- Managers too busy — an AI employee answers.
Where to start: enter the PBX address and API key from your Phonet account (where exactly) in the Phonet row under “Telephony”.
What Elbuz does with Phonet
- The customer's name on the manager's phone before answering — and routing to the personal manager (webhook).
- One-click calls from the customer card — no need to dial the number (extensions).
- Call log and recordings — incoming and outgoing, with playback after the call (what arrives).
- Incoming and missed call card — name, latest 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 Phonet
Phonet shows both values for Elbuz in one place (according to Phonet's help):
- Phonet account → “Налаштування” (Settings) → the “Інтеграції” (Integrations) tab.
- Scroll to the “Інша CRM система” (Other CRM system) widget and click “ДОДАТИ” (Add).
- The “API сервер” (API server) field is the “PBX address” in Elbuz (a domain like
mycompany.phonet.com.ua); the “API ключ” (API key) field is the “API key”.
Keep the integration page open — in step three you paste an address from Elbuz into it. Elbuz signs in with the PBX domain and uses the same domain to fetch history and recordings.
The paths in the Phonet account are taken from the operator's official documentation. If an item is named differently, use these pages or ask Phonet support:
How to connect Phonet to Elbuz
Three steps in order: keys, extensions and the . Without extensions the “Call” button doesn't work. Without the webhook the log is filled only by the hourly sync, and the customer's name doesn't appear on the phone.
Step one: Phonet keys
Open the Phonet row in the “Telephony” group. The “Active” toggle is already on — leave it that way. Fields to fill in:
| Form field | What to enter |
|---|---|
| “PBX address” | the value of the “API server” field from Phonet, for example mycompany.phonet.com.ua; “https://” and a trailing slash are removed automatically |
| “API key” | the value of the “API key” field from Phonet |
1
Link to the guide2
“Active” switch3
“PBX address” field4
“API key” field5
“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 on.
- The “PBX address” field — the “API server” value from Phonet.
- The “API key” field — the “API key” value from Phonet.
- The “Check connection” button — a read-only request to the operator, changes nothing in the account.
The form saves itself about a second after each change: you see “Saving...” at the bottom, then “Saved”. There is no “Save” button.
Finally, click “Test connection”. The app replies “Connected to the PBX. Employees in the PBX: ‹count›”. Elbuz reads the list of Phonet PBX users with their names, emails and extensions. The “PBX extensions without an Elbuz employee” line shows who doesn't have a number in Elbuz yet.
Step two: extensions
When a manager clicks “Call”, Phonet first rings their extension and dials the customer only after they answer. The same number links calls in the log to the manager.
Where: employee card (“Users”) → the “Internal phone” field.
Below the connection form there's an “Employee extensions” card — a “Manager” / “Extension” table for all active employees. Rows with a dash are employees who don't have a number yet.
Step three: webhook for other CRM systems
The form has a “PBX webhook address” card with the address and a “Copy” button. Paste it into the webhook fields of the same “Other CRM system” integration in your Phonet account and save. Phonet's help doesn't give the names of these fields in text, so if it's unclear which field is for what, check with Phonet support.
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 into the clipboard.
To get Phonet working with Elbuz
What arrives in Elbuz
Everything below has been checked against the Phonet integration module in Elbuz, built on the operator's HTTPS 4.1 documentation.
| Feature | How it works with Phonet |
|---|---|
| Calling from the card and the log (“Call”) | yes: Phonet rings the manager's extension, then the customer |
| Incoming and outgoing calls in the log | yes, on the call-ended event; internal calls aren't recorded |
| Customer's name on the phone screen | yes: when Phonet asks before the call, Elbuz replies with the name and a link to the card |
| Personal manager | yes: Elbuz passes the extension and email of the contact's personal manager |
| Incoming call card | yes, from a dialing or connected event that contains an extension |
| Call recording | yes, at a permanent address on your PBX; available after the call ends |
| Hourly log sync | 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 transfer to a SIP address; outgoing — not confirmed by Phonet, check with a test call (below) |
Events Elbuz handles from the Phonet webhook:
- call.settings — a request for the customer's name before the call. Elbuz replies with the name, a link to the card, a new-contact flag and the personal manager.
- call.dial and call.bridge — the call is being dialed and connected: the incoming call card pops up.
- call.hangup — the call has ended: it goes to the log.
Phonet specifics
The name on the phone updates with a delay
Phonet caches the name reply: up to a minute for new contacts, up to five minutes for existing ones. If you've just added a customer or changed a name, it may not show on the phone right away.
Events are accepted only from Phonet addresses
Phonet events carry no signature, so besides the key in the address, Elbuz checks the sender's address: it accepts only the six Phonet server addresses listed in the operator's documentation. If Phonet changes them, events will stop arriving without any notice. Phonet events can be duplicated — the log records a call once.
Session authorization
Phonet doesn't accept the key in every request: Elbuz first signs in with the PBX address and key, gets a session and works with it. When the session expires, Elbuz signs in again and repeats the request. If the key or the PBX domain has changed, the connection test returns an error.
Call recordings
Phonet builds the recording address from a template: your PBX domain followed by the call ID. A recording is available only after the call ends. Elbuz puts this address in the log if the call lasted at least a second.
Hourly sync
Phonet returns history in batches of 50 calls, and Elbuz pages through them until it has everything for the past 24 hours. The sync skips internal calls — only incoming and outgoing.
Voice AI employee on a Phonet 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 of the “Voice on the phone” section are covered in AI employee on the phone.
Incoming: how to route the number to AI
In the “Operator” field of the “Voice on the phone” section, select “Other operator”. In “Operator addresses”, enter your PBX domain — mycompany.phonet.com.ua, the same as in the integration's “PBX address” field.
Per Phonet support (20.10.2026), calls to an external SIP address come from the of your own PBX, so Phonet has no shared address list. Elbuz resolves the domain to an IP when the section is saved. If the PBX IP changes, edit any field there to re-save. Empty field — Elbuz accepts calls from any address.
The section shows an address like <number>@<domain>. Phonet support confirmed that a call can be transferred to an external SIP address at no extra charge. Here's how:
- In your Phonet account, create a separate user for AI and enter the SIP address from the “Voice on the phone” section in its contact numbers — exactly, with no spaces.
- In the call scenario, add a transfer to this user. This way you can also set up “AI if managers don't answer”: the managers' group first, then a transfer to the AI user.
- Transport — UDP or TCP; don't turn on TLS encryption: Elbuz accepts the call without it, and TLS is enabled separately in Phonet. Voice uses the G.711 codecs (A-law and μ-law).
- Call the number and check that AI answers and the caller's number shows in the call log. Phonet passes it in +380 format — leave it as is so AI can find the customer by number.
Outgoing: a SIP line for AI calls
An administrator can see a user's phone registration details like this (according to Phonet's help):
- Phonet account → “Налаштування” (Settings) → “Конфігурація телефонії” (Telephony configuration).
- Select the user AI will work under and open the “Інший телефон” (Other phone) option: it has the domain, username and password.
Domain goes into “SIP server”, username into “Line login”, password into “Line password”. In Phonet the device password is separate from the personal account password. It's best to create a separate user for AI.
Phonet support hasn't confirmed that these details can be used to call from the Elbuz voice platform: Elbuz calls via a SIP login without registering a phone. Check with a test call (“Test call” in the “Voice on the phone” section). If the call doesn't go through, outgoing AI calls via Phonet aren't available yet — incoming calls still work.
Outgoing calls work only when “Answer calls” is on; otherwise the test call replies “Outgoing calls are not set up: enter the line login and password and turn on answering calls”. By default AI calls from 9 to 20 in the account's time — the “Call during hours” field.
Scenarios
The manager sees who is calling before answering
- Paste the webhook address into the “Other CRM system” integration (step three).
- Set customers' personal manager in the contact card.
- A customer calls — Phonet 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
- Create a user for AI in Phonet with the SIP address from the “Voice on the phone” section (incoming to AI).
- In the call scenario: the managers' group first, then a transfer to the AI user.
- AI gives the order status by the caller's number and records the request; the conversation goes to the log.
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”, Phonet connects them with the customer, and the task closes on its own. More: missed calls.
What to do when Phonet doesn't work with Elbuz
General telephony problems — no call button, empty log, no recording — are covered in Telephony in Elbuz. This section is about Phonet.
| 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 in the first step | Enter the number in the employee card (step two) |
| “Test connection” returns an authorization error | The API key is wrong or “PBX address” has the wrong domain | Check the PBX domain in your Phonet account and re-enter the key |
| No customer name on the phone, calls appear up to an hour late | The webhook isn't set up or the address has an old Elbuz domain | Copy the address from the “PBX webhook address” card and replace it in the Phonet integration |
| The phone shows the customer's old name, though the card already has the new one | Phonet caches the reply for up to five minutes | Wait a few minutes |
| “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 answer within 15 seconds. The request may still have been accepted — then your phone will ring a bit later | Don't redial right away: wait a minute. If the PBX accepted the request, your phone will ring, and the call will show up in the log after the conversation |
| In the “Voice on the phone” section: “Could not resolve the addresses in “Operator addresses” — check the PBX domain or IP” | The domain in “Operator addresses” wasn't found — most often a typo. To avoid accepting calls from any address, Elbuz doesn't set up call reception | Enter the domain from the integration's “PBX address” field (mycompany.phonet.com.ua) and edit the field again (incoming to AI) |
| Incoming calls to AI work, but “Test call” doesn't go through | Phonet hasn't confirmed calls via a SIP login without registering a phone | Check the user's login, password and domain; if that doesn't help, outgoing AI calls via Phonet aren't available yet (outgoing) |
FAQ
What do I enter in the “PBX address” field for Phonet?
The value of the “API server” field from the “Other CRM system” integration in your Phonet account — your PBX domain, for example mycompany.phonet.com.ua. Elbuz removes the https:// prefix and a trailing slash itself.
Where do I get the API key in Phonet and where do I enter the Elbuz address?
In your Phonet account: Settings → Integrations → “Other CRM system” → Add. That's where the “API server” and “API key” fields are, and also the webhook fields for the address from the “PBX webhook address” card.
Can I listen to a Phonet call recording from Elbuz?
Yes, after the call ends. The recording address is built from your PBX domain, so there's no separate request to Phonet when you play it.
Why do Phonet events arrive twice?
Phonet may duplicate events — its documentation says so. Elbuz records the call in the log once: a repeat with the same call ID doesn't create a new row.
Can I choose the number Phonet calls the customer from?
No. Phonet's call API doesn't accept a line number, so the Phonet form has no “Line for outgoing calls” field.
Do internal calls between employees go to the log?
No. The log is about conversations with customers: Elbuz records only incoming and outgoing Phonet calls.
Can I connect voice AI to a Phonet number?
Yes, for incoming calls: a user for AI in Phonet with the SIP address from the “Voice on the phone” section and a transfer to it in the scenario (step by step). Check outgoing AI calls with a test call.
Where it is and who has access
The Phonet connection lives among 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” → Phonet
- Other ways in
- “Call log” → window menu → “Telephony connection”
- Access right
- system settings and the “Call log” window; no rights are needed to make calls
- Prepare
- the Phonet PBX address, the API key, employee extensions
Without the right to “Call log”, “Test connection”, the webhook address and the configuration file don't work.
Related topics
- For the overall telephony picture 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 — AI employee on the phone.
- If calls aren't linked to a manager — Users, the “Internal phone” field.
- To find a conversation in the customer's history — Contact card.
