People rarely complain that a chatbot answered a simple question correctly. They complain when it could not help and would not let them reach someone who could. The handover to a person is a small part of the build and a large part of how the bot is judged.
A chatbot is not meant to handle everything
The goal is not to keep customers away from staff. It is to answer the routine questions quickly so that staff have time for the ones that need them. A bot that resolves the common cases and passes the rest on cleanly is doing its job. A bot that traps people in a loop to protect a containment number is damaging the relationship it was built to support.
When to hand over
Define the triggers explicitly. Leaving it to the model's judgement produces inconsistent behaviour.
- The customer asks. Any request for a person should work the first time. Do not make them ask three times.
- The bot does not know. If the knowledge base has no answer, say so and offer the handover. Guessing is worse.
- The same question comes back. A rephrased question after an answer means the answer did not help.
- The topic is sensitive. Complaints, cancellations, billing disputes, legal or health matters, and anything involving an upset customer.
- The action is beyond the bot's permission. Refunds above a limit, account changes, exceptions to policy.
Hand over the conversation, not just the customer
The worst handover makes the customer start again: "Can you describe your problem?" The person taking over should see the full conversation, a short summary of the issue, who the customer is, and what the bot already tried. This is mostly an integration task. The chatbot has to write into the support tool the team already uses, in a form they can read in a few seconds.
Tell the customer what happens next
At the moment of handover, say plainly what the customer can expect. Is someone joining the chat now, or will there be an email? Roughly how long? Should they stay on the page? An honest "we will reply by email within one working day" is better than a spinner with no explanation.
Plan for when nobody is available
Outside working hours a live handover is impossible. The bot should say so, collect what is needed to follow up, create a ticket, and give a realistic time for the reply. Pretending that an agent is about to join and then going silent is the fastest way to lose trust.
Learn from every handover
Each handover is information. Review them regularly and group them by reason. A cluster of handovers on one topic usually means missing or unclear documentation, and writing that article removes the need for future handovers on it. A high number of "the customer asked for a person" at the very start of the chat may mean the bot's opening does not make clear what it can do.
Measure the right thing
The share of conversations the bot closes without a person is easy to count and easy to misread. A customer who gives up also counts as closed. Pair it with whether the issue was actually resolved, for example by asking at the end or by checking whether the customer contacted you again about the same thing.
Summary
Set clear handover triggers, pass on the whole conversation, be honest about timing and treat handovers as feedback on your content. Designing this is a core part of our AI chatbot service. If you are planning a support chatbot, tell us about your setup.