Human Handoff, Getting the Customer to a Person

Human handoff (also called escalation) is the moment a chatbot or voice agent stops handling a conversation and passes it to a person, along with whatever it has already learned. On chat that usually means routing into a live inbox or helpdesk. On voice it means a warm or cold transfer to a real phone.

Why it matters when you are buying or building

Handoff is the feature that decides whether customers trust your bot. An agent that answers 70% of contacts well and hands off the rest cleanly is a good deployment. An agent that answers 90% well and traps the other 10% in a loop is a bad one, and the complaints will all come from that 10%.

There are three triggers worth building in from day one. Explicit request: the customer asks for a human, and the agent should comply immediately, not negotiate. Repeated failure: two or three turns without progress, or the same question asked twice, means hand off. Sensitive topic: complaints, cancellations, anything legal or medical, anything about money going the wrong direction. Those go to a person by policy, not by the model's judgment.

Just as important is what travels with the handoff. A transfer that dumps the customer on a person who then asks "how can I help you today" wastes the entire conversation. Pass the transcript, the collected fields, and a one-line summary of what the customer wants.

A production example

The hardest part of voice handoff is rarely the decision, it is the plumbing. On one build the transfer tool referenced a hardcoded call identifier rather than the live call's control ID, so every transfer failed with an error and the caller was left with an agent apologizing in a loop. Nothing in the conversation logic was wrong. The wiring was.

That is the general shape of transfer bugs, and it is why I test transfers separately from everything else, on real calls, before any rollout. I also make sure there is a fallback for the case where nobody picks up: take a message and promise a callback, rather than dropping the caller. Full detail is in my guide to call transfer flows.

Design rules I use

• Never make a customer ask twice. The second request should transfer, no exceptions.
• Set expectations out loud: say you are transferring, and to whom.
• Have an after-hours path. A transfer to a phone nobody answers at 9pm is worse than an honest "we are closed, here is a callback".
• Track handoff rate and handoff reason in your analytics. The reasons are your roadmap for what to fix next.