Through a Twilio SIP trunk, Elbuz hands your Twilio number to the voice AI employee: it answers customers when managers are busy and calls customers itself from processes.
When you need this:
- Calls come in after hours — the AI gives the order status and explains delivery and payment.
- A customer wants to order or complain — the AI records the request, and a callback request goes to “Pulse”.
- A new order arrives — the AI calls to confirm it.
- The order has shipped — the AI calls and reads out the tracking number.
Where to start: create a SIP trunk in the Twilio Console.
What the AI can do on a Twilio number
It works through Elastic Trunking in the Twilio Console. In Twilio you create a trunk with the Elbuz address for incoming calls and a username and password for outgoing ones; in Elbuz you enter the number, the Twilio operator and the trunk address. What the AI says and how processes start calls: AI employee on the phone.
- Answers calls. Gives the order status by the caller's number, explains delivery and payment based on the store's articles, and tells the price and availability of a product (incoming).
- Takes requests. Records the name, number and what it's about; a callback request goes to “Pulse” for the person responsible for the customer.
- Leaves a transcript and summary. Elbuz adds a new customer to the by their number, and the summary goes to the feed of their card (what you get in Elbuz).
- Calls on its own. A Flows process with the “AI call” block confirms an order or reports a shipment (outgoing).
What you need from Twilio
- A Twilio number in your account.
- A SIP trunk with Origination pointing to the Elbuz address — for incoming calls.
- Termination and a Credential List in the same trunk — for outgoing calls.
- Geo permissions for the countries the AI will call; a trial account can only call verified numbers.
You create the trunk, Origination, Termination and Credential List yourself: Elbuz doesn't see or check the Twilio Console. You pay Twilio for the number and minutes at its rates, separately from Elbuz; a minute of AI conversation in Elbuz costs EUR 0.15, billed by actual seconds (voice AI pricing).
Console item names are in English, as in the Twilio interface, and come from the Twilio and LiveKit documentation (LiveKit is the platform Elbuz uses for voice calls). If an item is named differently, use these pages or ask Twilio support:
How to connect incoming Twilio calls
The order: create a trunk, enter the Elbuz address in it, attach the number to the trunk, then fill in the section in Elbuz.
Step 1. A trunk in Twilio
- Twilio Console → Products & Services → Elastic SIP Trunking → Trunks.
- Create new SIP trunk, enter a name (for example,
elbuz-ai) → Create.
Step 2. Origination: where Twilio sends incoming calls
- In the trunk, open the Origination tab.
- In the Origination URIs block, add a new Origination URI.
- In the Origination SIP URI field, enter
sip:<domain from the section>;transport=tcp, where the domain is the part of the SIP address from the “Voice on the phone” section after@. - Priority and Weight —
1and1. While there is only one URI, other values change nothing. - Save the URI.
The “Voice on the phone” section shows an address like 12025550143@<domain> with the hint “…route calls to this number to the SIP address (Zadarma — “External server”, Twilio and Telnyx — SIP trunk…)”. For Twilio you only need the domain after “@”.
Twilio fills in the number itself: with every incoming call it passes the dialed number as +<country code><number>, and Elbuz finds your line by it — with or without the plus.
Step 3. The Twilio number on the trunk
Attach the number to the trunk in one of the two ways described in the Twilio documentation:
- in the trunk — the Numbers section, add an existing number from the account;
- or in the settings of the number itself, in the Voice block, select SIP Trunking and this trunk, then save.
The number's Voice block must stay on SIP Trunking: if you select an app or a there, Twilio detaches the number from the trunk and calls won't reach the AI.
Step 4. The “Voice on the phone” section in Elbuz
- Open the AI employee card (see where to find it and who has access) and scroll to “Voice on the phone”.
- “Phone number” — the Twilio number with the country code and plus, as written in the Twilio Console:
+12025550143(number format). - “Operator” — Twilio. The “Operator addresses” field isn't needed for Twilio: Elbuz already knows Twilio's addresses.
- Turn on “Answer calls”. The section saves itself half a second after a field changes — “Voice settings saved” appears at the top.
- Call the Twilio number from your mobile. The AI should answer, and the conversation should appear in the call log.
How to turn on outgoing AI calls via Twilio
For outgoing calls, Elbuz dials the customer through your trunk's Termination and signs in to it with a username and password. Without this step the AI only answers.
Step 1. Termination SIP URI
- In the trunk, open the Termination tab.
- In the Termination SIP URI field, enter a unique name — you get an address like
elbuz-shop.pstn.twilio.com. Copy it in full.
Step 2. Username and password: Credential List
- Twilio Console → Voice → Credential lists → create a list and add a record with a Username and Password to it.
- Go back to the trunk: Termination → Authentication → Credential Lists → select this list → Save.
In Elbuz you enter the Username of the record itself, not the list name.
Step 3. The “Outgoing calls” block in Elbuz
| Field in Elbuz | What to enter |
|---|---|
| “SIP server” | Your trunk's Termination SIP URI, for example elbuz-shop.pstn.twilio.com. For Twilio the field is required: each trunk has its own address, and Elbuz can't fill it in itself |
| “Line login” | Username from the Credential List |
| “Line password” | Password of the same record; after saving, the field shows dots, and an empty field means “keep unchanged” |
| “Number shown to the customer” | the Twilio number the customer will see; if empty, the number from “Phone number” is used |
| “Call during hours” | by default 9-20, in the account's time |
To check, use “Number for a test call” and the “Test call” button: this is a real call through Twilio to the number you enter. Outgoing calls only work with “Answer calls” turned on. How the AI calls from processes is covered in the outgoing calls section of the voice AI article.
Twilio lets an outgoing call through only if the number the customer sees belongs to your Twilio account or is verified in Twilio. The country the AI calls must be allowed in Communications → Voice → Settings → Geo permissions, otherwise Twilio responds with 403 No International Authorization. A trial Twilio account can only call verified numbers.
To get the AI working on a Twilio number
What you get in Elbuz
| Feature | With Twilio |
|---|---|
| The AI answers calls to the Twilio number | yes, through your trunk's Origination |
| The AI calls customers itself (processes, “Test call”) | yes, through your trunk's Termination with a username and password |
| AI conversations in the call log and the customer feed | yes, with a transcript and summary (what remains after a call) |
| Employee calls in the log, the customer card during a call, the “Call” button | no: there is no Twilio connection in “External services” |
| Protection from third-party calls to the Elbuz address | yes: Elbuz accepts calls only from Twilio Elastic SIP Trunking signaling addresses; you don't need to enter them |
Twilio specifics
The number goes with “+” and the country code
Elbuz treats a number without a country code as Ukrainian only: 0XX XXX XX XX becomes +380…. A US number entered as 2025550143 becomes +2025550143 — Twilio never sends such a number, and the AI won't answer calls. Enter the Twilio number with “+” and the country code right away.
The SIP server isn't filled in automatically
For Zadarma and Telnyx the outgoing server address is known in advance; for Twilio it isn't, because each trunk has its own. Without “SIP server” there are no outgoing calls, even if the login and password are entered.
The “Forward the number” step in the step bar
The “Forward the number in the operator account — guide” step in the bar above the fields is green (“Calls are coming in”) if the line received an incoming call in the last 30 days. While it's red, clicking it with the Twilio operator opens this article.
Scenarios
The AI takes calls when managers can't keep up
Complete the four incoming-call steps and leave the “Outgoing calls” block empty. The AI will answer the Twilio number, and conversations with summaries will appear in the log and in the customer feed.
The AI confirms every new order
Set up outgoing calls and make a “Test call”. Then build a Flows process with the “AI call” block triggered by order creation (confirm an order). The AI calls only within “Call during hours”.
The Twilio number is in one country, customers in another
Allow your customers' country in Geo permissions and enter a Twilio number that belongs to your account in “Number shown to the customer”. Otherwise Twilio rejects the outgoing call.
What to do when the AI doesn't answer or doesn't call
| What you see | Why | What to do |
|---|---|---|
| “Enter the operator SIP server” | The line login and password are entered, but “SIP server” is empty; for Twilio, Elbuz doesn't know the address | Enter the trunk's Termination SIP URI (outgoing step 1) |
| People call the number, but the AI doesn't answer | The number isn't attached to the trunk, the Origination SIP URI has a mistake, or the number in Elbuz is entered without the country code | Check the Origination URI sip:<domain from the section>;transport=tcp — the domain must match the “Voice on the phone” section — the number's attachment, and “Phone number” in the +code… format |
| “Outgoing calls are not set up: enter the line login and password and turn on answering calls” | The login or password is empty, or “Answer calls” is off | Fill in both fields from the Credential List and turn the line on |
| A test call doesn't reach a customer abroad | The country isn't allowed in Twilio Geo permissions, or a trial account is calling an unverified number | Communications → Voice → Settings → Geo permissions — allow the country; for trial, verify the number in Twilio |
| Twilio rejects the outgoing call although the login and password are correct | “Number shown to the customer” doesn't belong to your Twilio account and isn't verified | Enter a Twilio number or leave the field empty so the line number is used |
Problems with the conversation itself — the AI is silent, cuts off, doesn't know the answer — are covered in the troubleshooting of Voice AI employee.
FAQ
What address do I enter in the Twilio Origination SIP URI?
sip:<domain>;transport=tcp, where the domain is the part of the SIP address from the “Voice on the phone” section after @. Only the domain, without the number: Twilio passes the dialed number itself. An address like number@domain is for Zadarma.
What do I enter in “SIP server” for Twilio?
Your trunk's Termination SIP URI — an address like name.pstn.twilio.com from the Termination tab. Without it, Elbuz responds with “Enter the operator SIP server”, and there are no outgoing calls.
Where do I get the line login and password for Twilio?
Voice → Credential lists — create a list with a Username and Password record, then in the trunk go to Termination → Authentication → Credential Lists, select it and save. The Username and Password go into “Line login” and “Line password”.
Do I need to enter Twilio's addresses?
No. With the Twilio operator, Elbuz itself accepts calls only from Twilio Elastic SIP Trunking signaling addresses in all regions. The “Operator addresses” field is shown only for “Other operator”.
Can I connect Twilio to the employee call log?
No. Elbuz has no Twilio API connection in “External services”, so employee calls through Twilio don't get into the log. Only AI conversations do.
Can I connect several Twilio numbers to the AI?
No. There is one line per account: one number, one AI employee.
Where to find it and who has access
- Menu
- Directories → Contacts → AI Pulse → “Agents” tab
- From the “Agents” tab
- “Agent settings” on the employee card → “Voice on the phone” section
- Twilio Console
- Products & Services → Elastic SIP Trunking → Trunks
- Access right
- “Management” — only it shows the “Agent” and “Voice on the phone” sections
- Have ready
- a Twilio account with a purchased number and access to Elastic SIP Trunking
There is no separate Twilio connection in “External services”: everything is set up in the “Voice on the phone” section of the card of the AI employee that will answer calls.
Related topics
- To set up what the AI tells customers and when it calls — AI employee on the phone.
- If you don't have an AI employee yet — AI employees.
- If you need both a manager call log and the AI on one number — Zadarma and Elbuz.
- If you're still choosing an operator — Telephony in Elbuz.
