On this page
Search for "AI voice agent" and you will be sold two genuinely different products under one name. One answers your phone number. The other lets a visitor talk to your website instead of typing. They cost different amounts, take different work, and fail in different ways — so the first job is knowing which one you are buying.
Two products wearing one name
| On your phone line | On your site or app | |
|---|---|---|
| The customer | dials your number | taps a microphone in the chat |
| You need | a number, a call platform, a connection into it | the assistant you already have, switched on |
| Time to live | a project | a setting |
| Fails as | a caller stuck in a loop with no operator | a visitor who types instead |
| Best at | missed calls, out of hours, overflow | questions while someone is already looking at you |
The technology underneath is the same family. OpenAI's Realtime documentation lists WebRTC "for browser and mobile clients that capture or play audio directly" and SIP "for telephony voice agents" (OpenAI) — one voice model, two very different plumbing jobs on your side.
What the phone version really asks of you
Nobody regrets answering more calls. What owners underestimate is everything around the model: a number and a telephony account, a greeting and menu that still make sense at 2am, a rule for when to take a message rather than improvise, out-of-hours behaviour, call recording notice and consent where you operate, and a tested path to a human that works while a person is already on the line.
None of that is impossible. All of it is a project rather than an afternoon, and it is worth doing after you know how many of your customers actually prefer to talk.
What voice on your site does today
This is the half that is a switch. In Busymate AI, voice is built in rather than an add-on: turn it on and a microphone appears in the chat on your website and inside your app. What a customer says is treated exactly like something they typed — same content, same limits, same confirmation before anything changes — and with hand-off on, they can ask for a person out loud and a teammate picks the conversation up in the Inbox. There is no phone line involved; it runs through the microphone, with nothing for your customers to install. The detail is on voice support, and the human side on hand-off and inbox.
Three things follow from voice being the same assistant rather than a second one:
- It answers from the same content. Whatever you fixed for chat is fixed for voice. Bad source material sounds worse out loud, not better — the knowledge guide is still the first thing to get right, and a curated /llms.txt keeps assistants pointed at your real pages.
- It obeys the same escalation rules. The six triggers in when should AI hand off to a human do not change because the customer is speaking.
- It can still act, not just talk. A spoken "move my appointment to Friday" ends in the same page action a typed one would — the actions your page publishes through WebMCP, a proposed standard designed for workflows "with a human in the loop" (Chrome for Developers) and set up in the page tools guide, with the visitor confirming the change.
Write the spoken script before you switch anything on
Spoken answers are unforgiving: no skim-reading, no scrolling back. Short sentences, one fact each.
Voice script — [Business name]
Greeting: "Hi, you're speaking to [Business name]'s assistant.
Ask me anything about [services / an order / booking]."
Keep answers: one sentence, then offer the detail.
Never say: a price, a date or a policy that is not on our pages.
Say instead: "I don't want to guess — let me get a colleague."
Hand off when: they ask for a person, they sound upset, it's about
[billing or legal], or I've failed twice.
Out of hours: take a message, confirm [email], promise [time window].Or have your assistant draft it
Ask your AI assistant:
Read my website at https://[your-site] and draft a voice script for my assistant:
a greeting, the five questions callers most likely ask with one-sentence spoken
answers taken from my pages, and what to say when it does not know. Keep every
answer under 25 words. Mark anything you had to guess with [CHECK].Read it aloud once — that is the whole test. If a sentence is hard to say, it is hard to hear.
Which one you need
- Voice on your site, first — if customers are already on your pages and simply prefer talking, or your visitors use phones on the move. Start here: it is a setting, not a build.
- A phone agent, when calls are the loss — if you genuinely miss revenue from unanswered calls, and only after you have written the script, the escalation rules and the out-of-hours behaviour above. You will reuse all three.
- Both, eventually — one set of content, one set of rules, two ways in.
The cheapest way to find out which is which is to hear your own content spoken back: build an assistant from your URL, turn the microphone on and ask it the three questions you get most. Pricing is metered per business and voice is part of the platform rather than a channel upsell, so the experiment costs you an afternoon.
Questions
Does an AI voice agent answer my business phone number?
Only the telephony kind does, and that is a separate build: a number, a call platform and a connection into it. The voice built into a website assistant runs through the visitor's microphone in the browser or app, with no phone line involved.
Which one should a small business do first?
Voice on your website or app, almost always. It is a switch rather than a project, it reuses the content and rules you already wrote, and it tells you whether customers actually want to talk before you commit to a phone build.
Will a voice assistant handle an angry caller?
It should not try. The same escalation rules you use in chat apply out loud: when someone asks for a person, gets upset, or raises money or legal matters, the assistant says a colleague is joining rather than talking them round.
Can a customer change something by speaking?
Only what they could change by typing. A look-up still needs a signed-in customer and a change is still shown and confirmed before it runs, so speaking is a different input, never a different permission level.
What about customers who cannot or will not speak?
Voice is an addition, not a replacement. The microphone sits beside the text box, the answer is written out as well as spoken, and everything works exactly the same for anyone who keeps typing.