ProductUse casesPricingBlogContact
Dashboard Sign in Start free
Customer Support Automation

Voicebot handover to a human: when to pass and what to pass on

Voicebot handover to a human: when to pass and what to pass on

A good voicebot handover to a human happens early, is announced out loud, and passes on a short summary so the customer never has to repeat themselves. The bot should hand over when the visitor asks for a person, when it has misheard twice, when the topic is outside its scope, or when the request needs a decision only staff can make. This article covers those triggers, what the bot should say at the moment of handover, which routes a website voice assistant can offer, and what context your agent needs.

Voice changes the rules compared with text chat. There is no screen of earlier messages for the visitor to scroll back through, frustration builds faster when a bot keeps mishearing, and a long spoken explanation of “how to contact us” is easy to forget. For the general mechanics of passing context between a bot and an agent, see our guide on handing over without losing context. Here we focus on what is specific to voice.

When should a voicebot hand over to a human?

Hand over as soon as staying with the bot costs the visitor more effort than switching would. In practice that comes down to a handful of triggers you can define in advance and check in transcripts.

  • The visitor asks for a person. “Agent”, “human”, “can I talk to someone” should never be met with another attempt to answer.
  • Repeated mishearing. If the bot has asked “could you repeat that?” twice, a third attempt rarely helps. Speech recognition struggles with names, codes and noisy rooms, as explained in our piece on why voicebots mishear words.
  • Out of scope. The question is not covered by the knowledge base, so the honest answer is to say so and point to a person. Our article on saying “I do not know” covers the wording.
  • A decision is needed. Refunds outside policy, complaints, exceptions, anything involving a specific order or account the bot cannot see.
  • Emotion or urgency. Words such as “complaint”, “urgent”, “this is the third time” are a signal to stop explaining and offer a person.

Triggers to avoid

Do not hand over on the first unclear sentence; one request to rephrase is reasonable. And do not hide the human route behind a long menu of options, because a visitor who has to fight the bot to reach a person remembers the fight, not the answer.

Voicebot handover to a human: what the bot says

The handover message should be short, say what happens next and confirm what the visitor will not need to repeat. Spoken, it has to fit in a couple of sentences, and the details should appear on screen too, because voice instructions are easy to forget.

A weak version: “I can’t help with that. Please contact our customer service department through one of the available channels.” A better version: “That needs someone from our team. I’ll show you the contact form below with your question already summarised, and someone will reply today.” If your process does not include a same-day reply, do not promise one: say what is true for your team.

  • Name the reason in plain words: “that needs a person”, “I can’t see order details”.
  • Say what happens next and roughly when, only if you can keep that promise.
  • Show the route on screen: a button, a form, a phone number or an email address.
  • Do not ask the visitor to start the story again.

Handover routes from a website voice assistant

A voice assistant on a website does not transfer a phone call, so the handover is a switch to another channel. Which routes make sense depends on who is available and when.

Route Works best when Watch out for
Live chat with an agent Someone is online during opening hours Out of hours it needs a fallback
Contact or callback form The issue can wait for a reply Ask only for details you really need
Phone number on screen The matter is urgent or complex Show hours next to the number
Email address Documents or photos need to be sent Set expectations for reply time

Small teams often cannot staff live chat all day. If that is your case, our comparison of chatbot and live chat for small teams helps decide which route to offer and when.

What context to pass to the agent

The agent needs enough to act without calling the customer back to ask basic questions, and no more. A short structured summary works better than a full transcript, although the transcript should be available if needed.

  1. What the visitor wanted, in one sentence, in plain words.
  2. What the bot already said, so the agent does not repeat the same answer.
  3. Why it handed over: request for a person, out of scope, misheard, decision needed.
  4. Details the visitor gave: an order number, a date, a product name, spelled as typed into the form rather than as the speech engine heard it.
  5. Contact details and consent, collected in the form, not read aloud.

The fourth point matters more in voice than in chat. Speech recognition can turn a product code or surname into something close but wrong, so ask the visitor to type such details in the form rather than relying on the spoken version.

How much of this travels automatically depends on the tool. Whether a platform can pass a live transcript or summary into your helpdesk is a question to check with any vendor before you buy. With Botino, the assistant answers only from your knowledge base, and you can describe your contact routes there, so the bot tells visitors plainly how to reach a person when a question is outside its scope.

Checking handovers after launch

Review handovers in the transcripts every week, because they show where the bot falls short. Look for three patterns:

  • Handovers on topics that are well documented, which point to a source problem.
  • Conversations that went on too long before a handover, which point to triggers that fire too late.
  • Handovers on the same unclear word, which point to a speech recognition issue you can fix with alternative phrasings in the sources.

Ask your agents too. They see the summaries and know when one was useless.

FAQ

Can a website voicebot transfer a visitor to a phone call?

A browser voice assistant does not run phone lines, so it cannot transfer a call. It can show a phone number, open a contact form or point to live chat. Phone call transfer is a feature of telephone voicebots and call centre systems.

How many failed attempts before a handover?

There is no fixed rule. A common practical choice is one request to rephrase, then an offer of a person. Check your transcripts and adjust if visitors give up earlier.

What if nobody is available?

Say so honestly and offer an asynchronous route: a form or an email address, with the hours when your team replies.

Decide your triggers before launch, write a short spoken handover line, show the route on screen and pass a summary the agent can act on. That is what makes a voicebot handover to a human feel like help rather than a dead end.