When should a bot hand over to a human? A practical rule

The conversation about automating customer service is usually framed as a binary: automate everything and save money, or keep people and give good service.

In practice, the businesses that do best don’t choose. They split — and the split follows a fairly clear rule.

The rule: cost of being wrong

The useful question isn’t “can the system answer this?” It’s “what happens if it gets it wrong?”

If a customer asks about delivery times and the system is wrong, the cost is low: it gets corrected and life goes on. If a customer asks whether they can return an opened product and the system improvises a policy that doesn’t exist, the cost is high — you’ve made a commitment you won’t honour.

With that rule, the split organises itself.

Automate without hesitation when the answer is objective and lookup-based: order status, availability, price, delivery times, payment methods, opening hours, store locations.

Automate with a safety net when recommendation is involved: comparing two products, suggesting a size, proposing a compatible accessory. The system adds real value here, but it needs live catalogue access and it needs to be able to say “I don’t know” instead of inventing.

Don’t automate complaints, policy exceptions, negotiations, or any conversation carrying emotional weight. A frustrated customer talking to a bot becomes a more frustrated customer.

What a good handover looks like

Three conditions, and all three have to hold:

It’s fast. A handover that takes four minutes to find someone has already failed.

The customer repeats nothing. No re-entering the order number, no re-explaining the problem.

The agent gets full context. The conversation, the browsing history, the cart. Without it, the agent starts from zero and the handover was cosmetic.

Any chatbot for online store that automates well but hands over badly will generate more friction than it saves — and the friction lands precisely on your most complicated, most valuable conversations.

The trigger list

Beyond the general rule, four concrete triggers should force a handover every time:

• The customer asks for a person, explicitly. No retention loops.
• The same question is asked twice without being resolved.
• The message contains frustration signals — profanity, capitals, “this is unacceptable”.
• The order value is above a threshold you define. High-ticket conversations deserve a human.

Where to start

Don’t try to cover everything. Take your last hundred conversations, classify them by type, and pick the single most frequent one. It’s almost always order status.

Automate that one properly, with a clean handover when it goes off-script. Measure how much time it frees over a month. That number gives you both the criteria and the internal justification to decide the second one.