Channels
Calls
Call customers from the inbox over WebRTC, WhatsApp and Telegram, set call routing, get help with call audio, and see the current state of AI voice.
Last updated: 2026-09-29
Sela supports human phone-style calls between your operators and customers, from the browser and from WhatsApp and Telegram. This page explains how calls start, how to route them, what administrators must configure so audio connects, and the honest state of AI voice.
Plan and where to find it#
- The Calls page (the sidebar shows Calls, titled Call Logs) requires the Enterprise platform plan. See Plans and billing.
- It lists recent calls with their status, start time and an AI summary, and holds the Call routing card.
- If no calling channel is connected, the page links to the channel catalog so you can connect one. The catalog card sela Calls opens this page.
- Call routing can be changed by admins only.
Kinds of calls#
| Type | How it starts | Media path |
|---|---|---|
| Browser call (web chat) | An operator calls the customer from the conversation, and the customer sees a ringing call in the chat widget | WebRTC through Sela, may need a network relay |
| Telegram call | The customer sends /call or taps the call button, an operator calls back from the inbox | WebRTC through the Telegram Mini App |
| WhatsApp call | An operator calls from the inbox after the customer permits it | Meta's own path, not Sela's relay |
| "Call us" tile | The widget shows a phone number you set manually | An ordinary phone call outside Sela |
The "Call us" number is set under Widget settings, Phone Contact Settings. It is a plain dialing number.
Operator and customer calls in the browser#
- An operator opens a conversation and starts the call.
- The customer's chat widget shows a ringing call. Ringing lasts up to 60 seconds before it is marked missed.
- The customer accepts. Their browser asks for microphone permission, so the site must be served over HTTPS. The widget frame already allows microphone use.
- Both sides exchange connection details and audio flows directly between browsers, or through a relay if a direct path is blocked.
- Either side can end the call. The call log keeps the record and summary.
React Native apps that show the widget in a WebView must grant microphone access to the WebView. See Web chat widget.
STUN and TURN for administrators#
Audio between two browsers or phones needs a network path. On most mobile carriers and many office networks a relay is needed to carry the audio.
Sela configures the relay for you. If calls stay on "connecting" or have no audio, ask Sela support to confirm the relay is active for your workspace.
Call routing#
The Call routing card on the Calls page decides who is rung for a customer's call request.
| Mode | Behavior |
|---|---|
| Ring everyone | Every agent's phone and browser rings. Whoever answers first takes the call. |
| Ring specific agents in order | Pick who Answers first and up to 5 backups under Then try, in order. Choose how long each rings: 15, 20, 30 or 45 seconds. If someone is offline, on a call or does not answer, the next rings. |
Choose what happens If nobody on the list answers: Ring everyone (no call is lost), or Mark it as missed and notify the first agent and admins. Choose Save.
Each agent can hold one active call, and a customer has one active call at a time. Calls can be put on hold and transferred to another agent, who accepts or declines the transfer. Who can change routing is covered in Team, roles and permissions.
Telegram calls#
- In the Telegram settings, turn on Call requests. See Telegram.
- A customer sends
/callor presses the call button. They see "Got it. A member of our team will call you here on Telegram shortly." and a Wait on the line button. - Operators are notified and choose Call customer on Telegram in the inbox.
- The Mini App verifies the customer through Telegram, and joins them when an operator answers.
The Mini App uses the same network relay as browser calls.
WhatsApp calls#
WhatsApp calling is available only on the Our Partner connection, when the connection is ready and the conversation belongs to it. See WhatsApp.
- In the conversation menu choose Call customer on WhatsApp.
- If the customer has already permitted calls, Sela dials ("Dialing customer on WhatsApp...").
- Otherwise Sela sends a call-permission request ("Call permission request sent to the customer on WhatsApp"). Dialing starts only after the customer agrees. If they decline you see "Customer declined call permission on WhatsApp."
- If the 24-hour window has ended, you are told to send a template first.
- If Calling is off for the number, you see "WhatsApp Calling is not enabled for this phone number in Meta WhatsApp Manager. Please enable Calling in WhatsApp Manager." Sela tries to enable it once, but you may need to do it in Meta.
Rules: one active call per operator and per customer. An offered call expires after 60 seconds, and an incoming call rings for 60 seconds. If another agent answers first you see "This call has ended or another agent answered it." Permission request messages are billed as service messages; call sessions themselves are not charged from the WhatsApp balance.
Voice status: AI voice and voice notes#
What works today:
- Voice notes. Customers can send audio messages on channels that carry them. The assistant transcribes the audio and answers as if it were typed, when Media Understanding is on. In the web widget, the microphone button appears only after a conversation is escalated to a human.
- Human calls as described above.
- Manual phone number in the widget.
Older phone-assistant settings are kept only for migration and no longer power anything. See Voice assistant for the current status.
Troubleshooting#
| Symptom | Likely cause | Fix |
|---|---|---|
| Call stuck on "connecting" | No network relay, common on carrier networks | Ask Sela support to confirm the relay is active (above). |
| No sound on one side | Microphone permission denied or non-HTTPS page | Allow the microphone; serve the page over HTTPS. |
| Customer never sees ringing | Widget closed, or the call expired after 60 seconds | Ask the customer to open the chat, then call again. |
| Calls page not in the sidebar | Plan below Enterprise | See Plans and billing. |
| WhatsApp call option missing | Not on Our Partner, or connection not ready | See WhatsApp. |
| Two agents answer the same call | Routing is set to ring everyone | Use ordered routing. |
| Voice option missing in widget | Live AI voice is unavailable | Use voice notes or a manual number. |
Can't find what you need? Contact support.