When should AI hand off to a human? Rules + template

Every owner considering an AI assistant asks the same second question: what happens when it cannot help? The answer that keeps customers is not a nicer apology. It is a hand-off — the assistant recognises the moment, says so, and a person takes over the same conversation with everything already in front of them.

Hand-off is not the assistant failing. It is the assistant routing. Decide the rules once, write them down, and the fear behind that second question mostly disappears.

The six triggers

These six cover almost every real escalation. The first four come straight from published support practice (Gleap); the last two are the ones owners regret not writing down.

Trigger 2 is usually a content problem in disguise. When the assistant keeps guessing, the fix is better source material — clear pages, a current FAQ, an honest /llms.txt brief — not a stricter rule.

Copy this hand-off policy

Paste it into your assistant's instructions and fill in the brackets. It is deliberately short: rules people cannot remember are rules nobody enforces.

# Hand-off policy — [Business name]

Hand off to a person immediately when:
1. The customer asks for a human, in any wording.
2. I am not confident, or the answer is not in my sources.
3. I have failed twice on the same question.
4. The customer is angry, distressed, or threatening to leave.
5. The topic is money, access or law: refunds over [amount], billing
   exceptions, account access, contracts, anything legal.
6. The topic is on my off-limits list: [e.g. medical advice, custom quotes].

When I hand off I will:
- Tell the customer, in one sentence, that a person is joining.
- Pass the full conversation, a two-line summary, and what they tried.
- Give a realistic time: [within 15 minutes, Mon-Fri 9-18] — never "soon".
- Outside [Mon-Fri 9-18]: take a message, confirm [email], and say when
  someone will reply.

I will never: invent a price or policy, promise a refund, or ask the
customer to repeat something they already told me. [CHECK: your exceptions]

What has to travel with them

A hand-off that drops context is worse than no hand-off — the customer explains everything twice and concludes the AI wasted their time. Everything below should arrive with the conversation, not after it (Cresta):

• the full transcript and a two-line summary of what the person wants;
• what was already tried, and where it broke down;
• the page, product or order they were looking at;
• their account details and verified identity, so nobody asks them to prove who they are twice;
• the reason for escalation — which of the six triggers fired.

In practice this is the difference between a colleague opening with "Hi, how can I help?" and opening with "I can see what happened — I will take it from here."

Say it out loud

Silence during a hand-off feels like abandonment. Three sentences are enough:

I am bringing in a colleague from our [team] — they will see this whole
conversation, so you do not need to repeat anything.
They usually reply [within 15 minutes] during [Mon-Fri 9-18].
If it is faster for you, I can take your [email] and have them write instead.

Ask your assistant to set it up

You do not have to configure this in a settings screen. Paste this into the chat:

Set up my human hand-off. Use these triggers: the customer asks for a person,
you are not confident, two failed answers, the customer is upset, anything
about refunds or billing or legal, and [my own exception].
When you hand off: say one sentence to the customer, pass the transcript,
a two-line summary and what they already tried, and promise [time window].
Outside [hours], take a message instead. Show me the policy before saving it.

Read it once, fix anything marked with brackets, and it is live. The mechanics — who gets notified, where the conversation lands, how a teammate replies in the same thread — are in the hand-off documentation and the setup guide; the shared inbox your team answers from is described on hand-off and inbox.

When a hand-off is not what they wanted

Sometimes the visitor does not want a person at all — they want the thing done: the order status, the booking moved, the return started. That is not an escalation, it is an action, and a website can now offer it directly through WebMCP page tools (Chrome docs), with the visitor confirming each one. The page tools guide shows the setup.

Get both halves right and the split takes care of itself: the assistant does what it can do, the tools do what needs doing, and a person arrives — informed — for the rest. You can try it on your own site in a few minutes, and hand-off is part of every plan on pricing, not an upsell.