Appearance
Calls (AI voice)
Give your AI sales assistant a voice. The Calls channel puts an AI voice assistant on the phone — it answers inbound calls and places outbound ones, speaks in a voice you choose, and turns every call into a normal conversation in the client's chat, complete with a transcript and a playable recording. There's also a browser-based Web SDK option that lets visitors talk to the assistant right on your website, no phone number required.
Use it for AI reception, qualifying leads by phone, appointment confirmations, follow-up call-backs, or a "Talk to us" voice button on your site.
At a glance
| You need | Where | Result |
|---|---|---|
| An assistant to connect | Channels → your assistant → Calls | Assistant selected for voice |
| A way to connect | Provider: SIP Trunk, Twilio Account, or Web SDK | Telephony (or in-browser) transport chosen |
| A voice + settings | The Calls panel | Voice, speed, first message, max duration set |
| The channel switched on | Connect agent to this channel toggle | Assistant starts answering / can be dialed |
Connect in 4 steps:
- Open Channels and select your assistant, then open the Calls channel.
- Choose a Provider — SIP Trunk, Twilio Account, or Web SDK.
- Pick a Voice (preview first), then fill in the required fields and click Connect phone number (or Create SDK Agent for Web SDK).
- Turn on Connect agent to this channel.
In the app
Everything on this page lives under Channels → your assistant → Calls. App URL: https://app.mychatbot.app/channels
Choose a provider
The Provider dropdown decides how calls reach your assistant. Pick one:
| Provider | What it is | Best for |
|---|---|---|
| SIP Trunk | Connects your own SIP telephony to the AI voice assistant | Businesses that already run a SIP trunk / PBX and want to keep their carrier |
| Twilio Account | Uses a phone number you already own in your Twilio account | Anyone with a Twilio number who wants the fastest phone setup |
| Web SDK | An in-browser "click-to-talk" voice widget on your website — no phone number, no carrier | A "Talk to us" voice button, product-page assistants, demos |
A single connected phone number handles both inbound (a customer dials you and the AI answers) and outbound (the platform dials the customer, used by auto-recall and call campaigns).
Set up the channel

- Go to Channels, select your assistant, and open the Calls channel.
- Under Provider, choose SIP Trunk, Twilio Account, or Web SDK.
- Under Voice (Optional), pick a voice — use Play preview / Stop preview to hear it first. The voice you pick also sets the assistant's primary spoken language.
- Fill in the required fields for your provider (see below), then click Connect phone number (or Create SDK Agent for Web SDK).
SIP Trunk fields
| Field | Notes |
|---|---|
| Phone Number* | Your number in international format, e.g. +1 212 555 0123. |
| Address* | The provider's SIP server: a hostname (it must contain a dot), an IPv4 address or localhost, with an optional :port (1-65535), e.g. sip.provider.com:5060. Enter the host or IP only — no sip: prefix or full URI. It is not your trunk name or a login: no spaces and no @. A value that does not fit is refused with "Invalid SIP address: this is the provider's server address, e.g. sip.provider.com:5060 (not a trunk name or login)." The same check applies when you change the address in Edit Settings. |
| Transport | TCP (default) or TLS. Use TLS for encrypted signaling. |
| SIP Trunk Username (Optional) | For SIP digest authentication. Leave empty to use IP-allowlist (ACL) authentication instead. |
| SIP Trunk Password (Optional) | Paired with the username for digest auth. |
Twilio Account fields
| Field | Notes |
|---|---|
| Phone Number* | The Twilio number to connect, in international format. |
| Twilio Account SID* | Starts with AC…. |
| Twilio Auth Token* | From your Twilio console. |
Web SDK
No phone, SIP, or Twilio fields — pick a voice and settings, then click Create SDK Agent. See Web SDK: voice on your website below.
A phone number can be connected only once
A phone number can only be connected once. If you see "A channel with this phone number is already connected," it's already in use on another Calls channel.
Tune the voice and behavior
These settings are shared by all providers and appear in the same panel.
| Setting | What it does |
|---|---|
| Voice (Optional) | The voice your assistant speaks with; preview before choosing. Also sets the primary language. |
| LLM | The model that powers the assistant's responses during the call. |
| TTS Model | The text-to-speech model. Picked automatically per language; adding extra languages forces the higher-quality v3 Conversational model. |
| Speech Speed | Speaking rate (0.7 = slower, 1.2 = faster). Default 1.2. |
| First Message | The assistant's opening line. Defaults to your assistant's welcome message. |
| Max Call Duration (minutes) | Hard cap on call length. Default 10 minutes. |
| Additional languages | Languages the assistant can switch to mid-call, with an optional greeting per language, plus Automatic language switching to detect the caller's language. |
| End conversation | Customize how and when the assistant wraps up and ends the call. |
Transfer to a human operator (phone only)
When you connect the channel, the optional Human Operator Number section lets the assistant hand a call off to a person. Pick one of three transfer modes — choosing a mode clears the fields of the other two:
| Mode | What you set |
|---|---|
| Operator number | The phone number to transfer to, plus a Transfer Condition describing when to hand off (for example, "the caller explicitly asks for a human or manager"). |
| Phone line | An internal line/extension dialed when transferring (e.g. 901), plus a Transfer Condition. |
| DTMF tones | A DTMF instruction telling the AI when to hand over and which keys to press (0-9, *, #; W is a 1-second pause, w is 0.5 seconds — e.g. 1W801). The tones are dialled into the call already in progress, so your PBX does the transfer. Turn on Send audible tones (in-band) only if your PBX ignores the default RFC 4733 signalling. |
Later, in Edit Settings, the Transfer to human operator toggle turns the handoff on or off. Not available for Web SDK.
Sound during tool calls
Sound during tool calls picks what the caller hears while the assistant looks something up — Typing, Elevator music 1–4, or No sound — so the caller knows the line is still alive. The sound plays during every lookup, whether or not the assistant just spoke. Before it transfers the caller to a person or ends the call, the assistant always says something first, so the caller is not left in silence. Preview each sound before choosing.
Noise and pauses
In Edit Settings, the Noise and pauses section tunes how the assistant handles background voices, short pauses, and words that should not interrupt it:
| Setting | What it does |
|---|---|
| Filter out background voices | Ignores everyone except the caller, so a second person in the room is not transcribed. |
| Narrowband voice detection | Tuned for phone-quality 8 kHz audio. Shown for phone providers only; leave off for browser calls. |
| Silence before the agent speaks again, s | 1–30 seconds, or -1 so the assistant never re-engages. New assistants start at 5; 8–10 stops the constant "are you still there?" on slow lines. |
| Words that do not interrupt the agent | Comma-separated backchannel words (e.g. "uh-huh, right, okay"). |
| Recognition keywords | Comma-separated brand, product, and street names that transcription otherwise mangles. |
TIP
Additional languages automatically switches the assistant to the higher-quality v3 Conversational voice — which bills at the higher rate. See Billing below.
Turn it on
New Calls channels start switched off. Turn on Connect agent to this channel to bind the number to the assistant and go live. Toggle it back off any time to pause without disconnecting.
If the line has no voice agent yet, the switch stays off and you see: "This phone line has no voice agent yet. Open the line, save its settings, then switch it on."
Connecting a provider does not activate calls
Until you turn the channel on, the assistant won't answer inbound calls or accept the binding — connecting the provider alone is not enough.
How a call becomes a conversation
When a call ends, MyChatBot writes it into the client's chat thread automatically:
- The full transcript is added to the chat as assistant/caller messages.
- The recording becomes playable inside that conversation — you can listen in the browser, seek, and download it.
- The chat is matched to the caller by phone number, so a returning customer lands back in the same thread and the assistant already knows who it's talking to.
Everything shows up on the Chats screen just like a text conversation, so your team can review, follow up, or hand off from one place.
TIP
Recordings are fetched live from the voice provider on demand rather than stored by MyChatBot, so they always reflect the source. If a very old call has been purged upstream, its recording may no longer play back. When the call's transcript is stored in the chat history, the call stays in the chat: the card is rebuilt from that transcript and marked "Recording no longer available at ElevenLabs — transcript from chat history", with no player. See Calls in chats.
Auto-recall (retry unanswered calls)
For outbound phone calls, open Edit Settings and turn on Automatically recall if not answered, then set Retry after N minutes. If the client doesn't pick up, the assistant tries again — up to 3 attempts, stopping automatically once the client answers or the limit is reached. Auto-recall applies to phone providers only, not the Web SDK.
Only a call nobody picked up is recalled. A client who picked up and hung up while the assistant's opening line was playing counts as reached and is not called again, even though none of their words were transcribed (see Call outcomes and funnel statuses). In a call campaign that dials only through Calls and has more than one lead, a call the phone provider refused for line capacity is not auto-recalled either: the campaign itself puts the client back in its queue (see Call outcomes and funnel statuses).
Call outcomes and funnel statuses
Outbound call outcomes update the client's funnel status automatically:
- A call with a transcribed client turn always counts as reached.
- A call that connected and ended during the opening line counts as reached and keeps the client's status when the transcript is the assistant's opener and nothing else. This is typically a client who says "hello" or "no" over the opener and hangs up: Calls agents don't let the client interrupt the first message, so those words are not transcribed and the chat shows only the assistant's opener. No
NotAnswered, no auto-recall and no campaign retry. - Every other call with no transcribed client turn counts as nobody picked up and sets the client to
NotAnswered: no connected duration, no opener in the transcript, a detected voicemail, the assistant ending the call itself after silence, or the assistant saying anything after the opener. A voicemail or answering machine that stays silent is usually caught here, because the line stays open past the opener. - A call that could not be placed sets
NotAnsweredtoo, except invalid or unreachable numbers, which becomeWrongNumber. - In a call campaign that dials only through Calls and has more than one lead, a call the phone provider refused for line capacity (a SIP 5xx such as 503, typically when the line is overloaded) sets no status and starts no auto-recall, as long as the call still belongs to the campaign. The campaign tries the client again later without using up one of their attempts. Every other 5xx, including in a one-lead campaign or one that also uses other channels, still sets
NotAnswered. - An answered call changes nothing by itself — your assistant's instructions decide what status a real conversation earns.
Every call that could not be placed is also written to the client's chat Activity, once per attempt: the call provider's failure notice and the sender that dialed never add two entries for the same call. A refusal that carries a SIP code while the call is being placed is recorded only by the provider's notice, so the sender writes no second entry for it. A failure with no SIP code (for example a transport or platform error) is written by the sender. The entry shows the channel (Calls), a title and the reason as its error line, both in the interface language. The title is Call not completed (amber) when the client decided the outcome (busy, declined, no answer, wrong number) and Call error (red) when the carrier or the platform failed or the line was overloaded. The SIP code, the conversation id and the English reason line are technical details: they appear only with the chat's Debug mode switch on (see Chats). The reason is one of:
| Reason shown | Colour | What happened |
|---|---|---|
| The number is unavailable or does not exist | Amber | The number is invalid or does not exist (SIP 404, 410, 436, 484, or a provider reason saying the number is invalid, does not exist or is unallocated). |
| The client is busy or declined the call | Amber | The client's line was busy (SIP 486, 600). |
| The client declined the call | Amber | The client rejected the call (SIP 603). |
| The client did not pick up | Amber | The phone rang but nobody picked up, or the request timed out (SIP 408, 480, 487). |
| The line is overloaded. Please try again later | Red | The provider's line was at capacity (SIP 503 only). The client's phone never rang. |
| The carrier could not connect the call. If this keeps happening, contact your carrier | Red | Any other 5xx. A carrier also answers 500 for its own faults or for an invalid number, so it is not treated as capacity. |
| The call could not be placed because of a platform error | Red | Any other failure, including a provider refusal of the line's SIP address (SIP 400 Bad Request URI): check the SIP address in the Calls line settings. |
A call the client declined, did not answer or that went to a wrong number is a final result for that attempt: a send loop does not redial it.
The entry is written only when the client already has a Calls chat. A failed call never creates one.
Each automatic status change is also recorded in the Activity of the chat the call belongs to (the Calls chat for an AI call, the Binotel chat for a missed incoming Binotel call) as a Funnel status changed entry with the actor System. It covers NotAnswered after an unanswered call, NotAnswered or WrongNumber for a call that could not be placed, and NotAnswered for a missed incoming Binotel call (see the Binotel recipe). The entry shows the previous and the new status; the previous status is left out when the client had none. It is written only when the status actually changed, so a repeated miss under auto-recall adds no entry. For a call that could not be placed, the entry is written only when the client already has a Calls chat. Changes made before this entry existed are not added retroactively. See Activity events.
These automatic status changes behave exactly like a manual status change: they arm any published follow-up targeting the new status for that client. That is the backbone of missed-call outreach — see the follow-up recipe for the full chain, including delivering the message through a different assistant's Telegram or Viber channel.
With auto-recall on, a repeated miss keeps the status without re-arming the sequence — the client gets the follow-up once, not once per retry.
Keeping the voice assistant in sync
The voice assistant is built from your assistant's instructions and knowledge base at the moment you connect the channel.
- If you change the assistant's instructions later, a Sync prompt appears — click Sync Agent to push the latest instructions to the voice assistant.
- Knowledge base is a snapshot taken at channel creation. Changing which integrations feed the assistant requires recreating the Calls channel to take effect.
- Revoking or recreating the Calls channel keeps your call history. The old voice agent is kept at the voice provider rather than deleted, so the recordings and transcripts of earlier calls stay available in their chats.
TIP
Use Make a test call in the panel to talk to your assistant live in the browser and hear the current voice, first message, and behavior before going live — this works for every provider.
Web SDK: voice on your website
The Web SDK provider is the same Calls channel with no phone number. Instead of connecting a carrier, it gives you an Agent ID and an embed you paste into your site so visitors can click a button and talk to your assistant in the browser (using their mic and speakers).
To set it up:
- In the Calls channel, set Provider to Web SDK.
- Pick a Voice and tune the shared settings (first message, LLM, speed, max duration, languages).
- Click Create SDK Agent.
- Copy your Agent ID from Connection Details (it looks like
agent_1301kzy0…). - Turn on Connect agent to this channel, then paste the embed below into your site.
Web SDK calls also land as conversations in the client's chat, with transcript and recording, and bill exactly like phone calls (see below). Human-operator transfer, auto-recall, and outbound dialing are phone-only.
Once the Calls channel is revoked, its old Agent ID refuses new calls, so remove the embed from your site or replace it with the Agent ID of the new channel.
The embed
Two tags, anywhere in the page. They add a floating microphone button; a visitor clicks it, grants mic access, and is talking to your assistant.
html
<script src="https://storage.googleapis.com/mychatbot-widget-assets/v2/calls.js"></script>
<script>
MyChatBotCalls.mount({
agent_id: "YOUR-AGENT-ID",
name: "Acme Assistant"
});
</script>Replace YOUR-AGENT-ID with the Agent ID from Connection Details. Nothing else is required — the control brings its own styles, and during a call it becomes a compact bar showing who is speaking, with mute, end-call, and a button to read the live transcript.
The snippet in the app is a different one
The Integration Snippet in Connection Details has two tabs. Script Tag shows the older v1/calls.js script: MyChatBotCalls.init({ agent_id }) plus MyChatBotCalls.start({ caller_id }) bound to a button you build yourself — no ready-made control. npm Package shows the @mychatbot/client usage. The v2/calls.js embed with MyChatBotCalls.mount(...) on this page is the newer, ready-made control; use it unless you want to build your own button.
Ask Claude for it
If you set your assistant up through the MyChatBot connector in Claude, you can just ask — "give me the embed code for my voice agent" — and Claude returns this snippet with your real Agent ID already filled in.
Options
Everything except agent_id is optional.
| Option | What it does |
|---|---|
agent_id | Required. Your Web SDK Agent ID. |
name | The assistant's name, used for the button's label and tooltip. |
color | Accent colour, any CSS colour. Defaults to MyChatBot purple. |
position | "bottom-right" (default) or "bottom-left". |
target | A CSS selector or element to render inside, instead of floating in a corner. |
transcript | "collapsed" (default — a button opens it), "open", or "off" to remove it. |
client_tools | Page functions the assistant may call mid-conversation. See below. |
onCallStart | Called once when the call connects. |
onCallEnd | Called once when it ends, with { reason, seconds } — reason is "hangup" (the visitor pressed end) or "remote". |
Each visitor's browser gets its own caller identity automatically, so conversations don't merge into one thread.
Let the assistant act on your page
client_tools are functions on your page that the assistant can call while it talks — search a catalogue, apply a code, jump to a section. Each tool has a definition the assistant reads and a handler you write.
html
<script>
MyChatBotCalls.mount({
agent_id: "YOUR-AGENT-ID",
name: "Acme Assistant",
client_tools: {
applyDiscountCode: {
definition: {
description: "Apply a promo code to the visitor's cart.",
parameters: {
code: { type: "string", description: "The discount code", required: true }
}
},
handler: function ({ code }) {
// your page's own code
return "Applied " + code + ".";
}
}
}
});
</script>Whatever the handler returns is spoken back into the conversation, so return a short confirmation ("Applied SPRING10, 10% off") rather than nothing.
parameters is a flat map, not a JSON Schema
Each entry is a parameter name mapped to { type, description, required }, where type is "string", "number", or "boolean". Writing it as a JSON Schema — { type: "object", properties: { … } } — is rejected, and the page carries on as if nothing happened: the call still connects, but the assistant never receives the tool.
Using npm instead
If your site is a JavaScript build, install @mychatbot/client and drive the call yourself — useful when you want your own button and your own UI rather than the ready-made control.
js
import { MyChatBotCalls, defaultCallerId } from "@mychatbot/client";
const calls = new MyChatBotCalls({ agentId: "YOUR-AGENT-ID" });
await calls.start({ callerId: defaultCallerId() });defaultCallerId() keeps a stable per-browser identity so each visitor gets their own conversation thread. Client tools work the same way here, passed as clientTools to start().
TIP
For the full storefront setup — a voice assistant that searches products and drives the page — follow the Voice storefront guide.
Billing
Calls are billed by duration, converted into your plan's AI messages. The panel shows the exact rate, for example "Rate: 3 AI messages per minute of call".
| Voice quality | Rate |
|---|---|
| Standard voices | 3 AI messages per minute of call |
| High-quality voices (v3 Conversational / multilingual) | 5 AI messages per minute of call |
- Billing is prorated by the second — there's no per-call minimum, so a 10-second call bills a fraction of a message.
- If you configure Post-Call Functions (actions like writing a lead to your CRM after the call), that adds a small fixed charge per call that actually runs them.
- Web SDK calls bill on the same rates — there's no separate SDK price.
- Adding Additional languages moves the assistant to a high-quality voice, so it bills at the 5 messages/minute rate.
Outbound calls require an active assistant and balance
Outbound calls are refused if the assistant is switched off or the account balance is drained. Top up or re-enable the assistant to place calls again; when a Calls assistant is switched back on, its phone line is reconnected to the voice provider straight away.
See also
- Voice storefront guide — the full in-browser voice widget on your website
- Call campaigns — run outbound calling campaigns
- Build an agent
