Handoff & service · Explore this field ↗ · Core guide · 2 min read
Human handoff is a feature, not an admission of defeat
The strongest automation knows how to stop, explain, package context, and yield control.
Offer a visible exit
Users should not need a secret phrase. Human help can be a persistent action, a plain-language command, or a channel-specific contact route. Availability, hours, expected wait, and what will be shared should be stated before transfer. When no live team exists, say so and offer a ticket or external route rather than simulating handoff.
Escalate on more than frustration
Triggers include user request, repeated repair, low confidence, missing entitlement, unavailable tools, high-value exceptions, vulnerability, safety risk, and policy-defined topics. Rules should distinguish immediate transfer from offering transfer. Intercom documents both structured escalation rules and natural-language guidance; the transferable lesson is to make conditions explicit and test them.
Send a handoff packet
A useful packet contains verified identity level, user goal, facts supplied, steps attempted, tool results, source links, unresolved question, and safety flags. Separate verified facts from model summary. The human must be able to inspect the transcript and correct the summary. Once they reply, automation should stop unless deliberately re-invoked.
Operator note
Test the transfer end to end during closed hours, long waits, channel switching, and queue failure. Measure repeat rate, context acceptance, time to first human reply, and bot re-entry errors. A handoff that drops context is just a longer form of failure.
The no-repeat handoff
When a user asks for a person, acknowledge the request first. Confirm whether help is live and provide the expected wait. Ask only for missing information that will change routing, and make it optional when urgency or frustration is high. The transfer packet should open with the user’s goal in their own terms, followed by verified account facts, attempted steps, and unresolved decisions. The human can correct the summary before relying on it. Once a public human reply arrives, automation stays silent unless the operator deliberately calls it back.
Primary reading
Sources and limits
These links support the architecture, policy, or product behavior discussed above. Vendor documentation describes vendor features; it is not independent proof of performance. Current details should be rechecked before a production decision.