Voice Calls
Visitors call your team from the widget — setup, what visitors see, answering in the dashboard, timings.
Audience: Logged-in customers.
Voice Calls let a visitor start a real voice conversation with your team straight from the chat window — no phone numbers, no dialing, no extra software on either side. The call runs browser-to-browser between the visitor's page and your dashboard, rides the same operator seats as Live Agent, and has no per-minute fees or per-call charges.
Calls are an escalation inside live chat: the call button lives in the live-chat window, follows the same online/working-hours rules as live chat, and the text conversation keeps working during the call — a visitor can paste a link or send a screenshot while talking to you.
This page is only about a visitor talking to a person on your team. Speaking to the AI assistant instead — dictating a question by voice, or having its written answer read aloud — is a separate feature with its own settings; see Voice Features.
Plan availability
Calls ride the Live Agent seats you already have. Which plans include them is the Voice calls row of the Live Agent plan table: Plan availability.
Turning calls on — the three switches
These three switches decide whether a visitor can call:
- Your plan includes voice calls — see Plan availability above.
- The website switch — Dashboard → Live Chat → Settings → Voice calls. It is set per website and is off by default: until you turn it on, visitors to that site never see a call button.
- Each operator's personal Calls switch — in the Live Chat header, just left of the Online toggle, shown while that operator is online. It's on by default. While the site does not take calls it is shown switched off and locked, with the reason. An operator without a headset can switch it off and keep answering text chats only — they stop being rung, while teammates with it on are still rung.
What your visitors see (the widget side)
- The call button — a green phone button in the live-chat header. It appears when calls are enabled for the site, and it works only while at least one operator is online, accepting calls, and not already on a call. If every operator who takes calls is on another call, the button greys out and reads "Everyone is on another call right now — you can wait here or keep chatting", and it comes back as soon as one of them hangs up. If operators are online but are not taking calls, it reads "Calls are not being answered right now — you can still chat here". There is no queue and no cooldown.
- The button can also be missing for a reason on the visitor's side, and then it's hidden rather than greyed out, with no message. The two common causes: the page hosting the widget sets a
Permissions-Policythat doesn't hand the microphone down to embedded content, or the visitor is in an in-app browser (opening a link from inside Instagram or Facebook is the common one) that doesn't support the call APIs. If calls work for you in a normal browser tab but a visitor reports no button, check those two first — see Voice Features for the same issue on the microphone button. - Starting a call — the visitor taps the button, their browser asks for microphone permission (a standard browser prompt we can't skip — it's how browsers protect users), and the header shows "Calling the operator…" with a hang-up button. A call can be the first thing the visitor does; no message is needed before it.
- Ringing — your team rings for up to 45 seconds. The visitor can hang up while it rings.
- If the call is not answered — the call ends and, if the site has a lead form, the visitor is offered it straight away ("Leave your contact details"), so a missed call still becomes a lead in Dashboard → Leads. Without a form they see a note to try again later — a good reason to have one. See Lead Forms.
- During the call — the chat header shows the operator's name (or "Connected" when the operator's name is hidden) and a call timer, with mute and hang-up buttons. Chat stays usable alongside the voice.
- In the conversation — small grey system lines record "Call started" and "Call ended" with the duration, for both sides' context.
- Connection hiccups — a brief network blip usually passes unnoticed. When the connection drops, the call waits up to 30 seconds for it to come back on its own; if it doesn't, or the browser reports the connection as failed, the call ends with a message and the visitor can call again. A weak connection usually lowers audio quality rather than dropping the call.
- Limits — switching networks mid-call (for example walking out of Wi-Fi onto mobile data) ends the call; the visitor just calls back. On iPhone, locking the screen or leaving the browser mutes the microphone — that's how iOS works, so the widget shows the visitor a "Keep this screen open during the call" note.
Answering calls (your dashboard side)
- Incoming call — a ringing banner with sound appears anywhere in the dashboard, not just on the Live Chat page. Outside Live Chat, a short notice and a dot on Live Chat in the sidebar also mark the call. Desktop notifications (Live Chat → Settings) cover new visitor messages, not calls: a call reaches you only through an open dashboard tab.
- Who rings — every operator who is online, accepting calls and not already on a call rings at once, for up to 45 seconds. The first to accept takes the call; the other operators' banners close without an error message. Declining removes the banner for you and the call keeps ringing your teammates; when the last operator still ringing declines, the call ends at once and counts as missed.
- On a call — a compact call panel (visitor label, timer, mute, hang up) stays with you while you move around the dashboard. Navigating between pages does not drop the call.
- One call per operator — while you're on a call you won't be rung again, and the visitor-side button reflects it. A free teammate can take a second, parallel call independently. The moment you hang up, you're available again — instantly.
- Missed calls — a call that ends unanswered (it rang out, or the operators who were rung declined it) leaves a "Missed call" line in the conversation and goes through the usual missed-chat notification; a visitor who hangs up while it is still ringing is not a missed call. Whatever the visitor left in the contact form lands in Leads. A visitor who called and was not answered is a warm lead — follow the form entry up quickly.
Privacy and recording
- Calls are not recorded and not transcribed. We keep a call record with its start, answer (when somebody answers) and end times, how it ended, and which operator answered. Those fields power the call outcomes and timing in Live Chat analytics. The record is deleted together with its conversation. The conversation also keeps system lines such as "Call started", "Call ended" with the duration, or "Missed call".
- Audio flows directly between the two browsers whenever the networks allow it. When a visitor's network requires it, audio is relayed through our servers for as long as the call lasts, and we do not keep a copy.
- Call records contain no audio, session-description data, or IP addresses.
- Microphone access is controlled by the browser on both sides; muting is instant and local.
Quick reference
| Ring time before "no answer" | 45 seconds |
| If the call is not answered | Visitor is offered the contact form if the site has a lead form — the lead is kept |
| Connection-drop grace | 30 seconds to auto-recover, then the call ends |
| Next call after a hang-up | Immediately — no cooldown |
| Calls per operator | One at a time; teammates take parallel calls |
| Recording | Not recorded or transcribed; the call record and the conversation's system lines are kept |
| Cost | No per-minute or per-call fees; see Live Agent plan availability |