What is handoff?

Why it matters

Handoff quality is what customers actually judge AI support on. They forgive an assistant that cannot answer. They do not forgive being asked to repeat everything to a person who then repeats the same failed suggestion. The transfer, not the model, is where trust is won or lost.

What to know

• The handoff must be available on demand. A customer asking for a human should get one without negotiating.
• Carry the transcript, not a summary alone, so the agent can see the exact wording the customer used.
• Include what the AI already tried, so the agent does not repeat a failed suggestion.
• Timing matters: hand off before the customer gets frustrated, not after three failed attempts.
• Billing for handoffs means charging the customer for the product failing, which is worth checking in any contract.

An example

Example: a customer spends four messages describing a billing discrepancy, asks for a person, and the agent opens the ticket already showing the transcript, the account, and the AI note that the discrepancy matches a known proration case. Nothing is repeated.

Common mistakes

• Hiding or delaying the request-a-human path to protect deflection metrics
• Passing a summary without the original transcript
• Handing off without stating what the AI already attempted
• Paying a vendor for conversations the AI could not resolve

Questions