A customer asks a question, gets two unhelpful answers, asks for a person, waits, and is greeted by an agent who says how can I help.
She explains the whole thing again. The agent reads back through the transcript while she waits. The problem is resolved in ninety seconds by somebody who needed thirty seconds of context they could have had automatically.
Her view of the business is now shaped by the handover rather than by the resolution. That is the part almost every implementation gets wrong.
1. Let the customer ask for a person at any point
Always available, always honoured, never buried. A system that resists this creates the frustration it was meant to prevent, and it is the fastest way to lose trust.
2. Hand over on low confidence rather than guessing
An answer offered uncertainly is worse than an escalation. The decision to stop is as important as the ability to answer, which is the ground in how chatbots decide when to hand off to a.
3. Hand over on frustration signals
Repetition, short replies, capital letters and rephrasing the same question. These are recognisable and they are the moment to stop trying.
4. Set a maximum number of attempts
Two or three, then a person. An endless loop of clarifying questions is the experience people describe when they say they hate chatbots.
5. Route sensitive topics immediately
Bereavement, complaints, safeguarding, financial difficulty and anything legal or medical. These should never be attempted, regardless of confidence.
6. Pass the whole conversation across
Not a summary alone. The agent should see exactly what the customer typed and what was answered, because the wording matters.
7. Add a short summary on top
What the customer wants, what has been tried and what the agent needs to decide. An agent reading three lines opens far better than one reading forty.
8. Never make the customer repeat themselves
This is the entire test of a handover. If the first agent message is a general greeting, the handover has failed regardless of how fast it was.
9. Pass the identity and account context
Who they are, what they bought, what is open on their account. Assembling this manually is most of an agent's handling time.
10. Be honest about the wait
A stated position in a queue or an expected time. People wait far more patiently when told, and abandon quickly when left uncertain.
11. Handle the out of hours handover differently
Capture what is needed, state clearly when somebody will reply, and do not imply availability that does not exist. An honest tomorrow beats a vague shortly.
12. Hand back cleanly where appropriate
After an agent resolves something, returning routine follow up to automation is fine as long as it is stated rather than silent.
13. Measure the handovers, not just the deflections
Handover rate, reason and what happened afterwards is where the improvements come from. Most teams measure only what was deflected.
14. Treat it as the moment the whole thing is judged
A clean handover makes automation feel like a service and a poor one makes it feel like an obstacle, which is the same boundary problem as handover questions between bookkeeper and accountant. The pressure on a small team juggling this is described in one person many jobs and the messages in between, and the specific care needed with anxious customers in claustrophobia and locked in questions. See features, start at try, and the sector view sits under small business.