Customer Support· 7 min read· By The SpideyChat Team

When Should a Chatbot Hand Over to a Human? Four Clear Triggers

Handover is not a failure, it is a feature. Here are the four moments where a bot should stop trying, and what a good handover actually looks like.

Teams tune chatbots to hand over as rarely as possible, because containment rate is the metric on the dashboard. That is backwards. A bad handover is a problem; a needed handover is the system working.

The four triggers

1. They asked. Someone who says "I want to speak to a person" gets a person. Immediately, without a "let me try to help first". Arguing with this request is the single most reliable way to turn a mild irritation into a complaint.

2. It does not know. The knowledge base has nothing relevant. The right move is to say so and offer a person, not to generate something plausible.

3. Emotional stakes. Anger, distress, anything with money or safety attached. These need judgement, and judgement is exactly what a language model does not have.

4. Going in circles. If two exchanges have not moved forward, a third will not either. Loop detection is unglamorous and it prevents most of the conversations people screenshot and post.

What a good handover looks like

Say what you are doing. "I am bringing in a colleague now" beats a silent transfer.

Pass the context. The person taking over sees the whole conversation. Making the customer repeat themselves undoes any goodwill the handover bought.

Be honest about timing. If it is out of hours, say when someone will respond rather than implying it is imminent.

Have a fallback. If nobody can take over, capture the enquiry with everything attached and set an expectation. That is a worse outcome than a live handover and a far better one than being left hanging.

The metric to watch instead of containment

Handover reason. Split them:

  • "Asked for a person": healthy, expected.
  • "No knowledge": a content gap, and each one is a specific thing to write.
  • "Looped": a bug.

That breakdown tells you what to fix. Containment rate tells you nothing, because it counts the visitor who gave up identically to the one who was helped.

The uncomfortable truth about containment

A bot that never escalates and a bot that solves everything look the same on a containment dashboard. Only one of them is real, and it is usually not the one with the impressive number.

Test the limit

Build one from your site and ask it something it cannot possibly know. What it does then is the behaviour your customers will meet on their worst day.

Related: what an AI employee can actually do.

Frequently asked questions

Is a handover a failure of the chatbot?
No. A bot that never hands over is usually stubborn rather than brilliant. What matters is the reason, and whether the handover is clean.
What is the most important trigger?
The visitor asking for a person. It should be honoured immediately and without argument, every time.
What if nobody is available to take over?
Say so plainly, capture the enquiry with full context, and give a realistic time. Silence is the worst option.
Should the human see the conversation so far?
Always. Making a frustrated customer repeat themselves is the fastest way to make a handover worse than no handover.

Want a 24/7 AI Employee for Your Website?

See how SpideyChat can answer customer questions, capture leads and handle enquiries while your team is offline.

No obligation. We will review your website and show you how SpideyChat could work for your business.

Keep reading

Customer Support

Ecommerce Chat That Knows When to Hand Over to You

Customer Support

When to Let a Chatbot Answer and When to Escalate to a Human

Customer Support

A Restaurant Assistant That Knows When to Hand Over