How it works
Designing a chatbot handoff to a human
When a bot should stop answering, what it should collect before passing over, and how to make the handoff feel like service rather than failure.
In short
A handoff should trigger when the bot is uncertain, when the visitor asks for a person, or when the topic is a complaint — and it should collect a name, a contact detail and a one-line summary before it ends.
Done well, a handoff increases trust; done badly it reads as a dead end.
Key facts
Key facts
- Three standard triggers: uncertainty, explicit request, complaint or emotional tone.
- Collect name, contact detail and a summary before closing the conversation.
- Tell the visitor when to expect a reply, and mean it.
- A handoff that promises 'someone will be in touch' with no timeframe erodes trust.
The three triggers
- · The bot cannot find the answer in your content.
- · The visitor asks to speak to a person.
- · The conversation turns into a complaint or sounds distressed.
What to capture
A name, one way to reach them, and a single sentence describing what they wanted. That is enough for whoever picks it up to open the reply with 'about your question on delivery to Cluj' instead of 'how can I help?'.
Set an expectation you can keep
'We reply within a few minutes during working hours' beats 'we'll be in touch' — as long as it is true. Handoffs fail on broken promises far more often than on technology.
The product behind this guide
A chatbot trained on your own website, live today
Defaltam builds AI chatbots that read your public pages and answer with your real prices, services and policies. Support is €79/month, Sales is €149/month, both start with a 5-day free trial, and installation is one script tag.
FAQ
Questions people ask about this
When should a chatbot hand over to a human?
When it cannot answer from your content, when the visitor asks for a person, or when the conversation becomes a complaint. It should collect a name, a contact detail and a one-line summary before closing.
How does the handoff reach me?
As an enquiry with the transcript context, delivered to the inbox you configure.
Does handing off make the bot look bad?
The opposite. A bot that knows its limits reads as competent; one that improvises reads as unreliable.
Should the bot promise a response time?
Only one you can keep. A specific, honest timeframe builds more trust than a vague promise.
Related
Keep reading.
How AI chatbots actually work →
From the visitor's question to the answer on screen: retrieval, context, the language model and why grounding in your content matters.
How to stop a chatbot from making things up →
Hallucinated prices and invented policies destroy trust. The four controls that keep a website chatbot honest, and how to test for them.
Running a multilingual AI chatbot →
How a modern chatbot answers in the visitor's language from a single-language website, where it goes wrong, and what to translate anyway.
Website chatbots and GDPR: what you need in place →
What data a website chatbot collects, what your privacy policy must say, and how to handle transcripts and consent under GDPR.
Website chatbot security basics →
Prompt injection, data leakage, abuse and rate limits — the security questions to ask before putting an AI chatbot on a public website.
Why most website chatbots fail →
Chatbots fail for four predictable reasons: no clear job, thin content, no handoff and nobody reading the logs. Each has a straightforward fix.
AI chatbot plans and pricing →
Support €79/mo, Sales €149/mo, 5-day free trial.
How to add an AI chatbot to your website →
The ten-minute install guide, platform by platform.