When AI chat should stop and fetch a person
The measure of a good assistant is not how much it answers. It is how fast it gets out of the way.
Every assistant will meet conversations it should not be in. The question is whether it notices, and how much of the customer's patience it spends before acting.
Triggers that should never be argued with
- Anyone asking for a person, in any wording
- Money leaving your account — refunds, chargebacks, cancellations
- A complaint, or anything with an angry tone
- A second attempt at a question it already failed
- Anything legal, medical or safety-related
Carry the conversation with them
The moment that costs you the customer is being asked to explain it all again. Whatever the assistant already learned — the order number, the problem, what it tried — should arrive with the handoff. A tool that cannot do this is adding a step to your support process rather than removing one.
Route it somewhere real
A handoff that raises a flag in a dashboard nobody watches is not a handoff. It should land where your team already looks: the helpdesk queue, an email, a phone alert. Decide that before you turn the assistant on, not after the first complaint.
Measure the ones that never happened
Look for conversations where the customer asked the same thing three times and left. Those are handoffs that should have fired and did not, and they are invisible in every deflection metric.
Do not ask permission
"Would you like me to connect you to a colleague?" is a question that costs a turn and answers nothing. If the assistant has decided a person is needed, fetching one is the answer.
Handoff is a whole reply, not a footnote
A common mistake is writing rules that both answer and hand off. The customer gets the handoff line and loses the answer. Pick one per situation.
Carry the conversation with them
The moment that costs you the customer is being asked to explain everything again. Whatever the assistant already learned — the order number, the problem, what it tried — should arrive with the handoff. A tool that cannot do this is adding a step to your support process rather than removing one.
Route it somewhere real
A handoff that raises a flag in a dashboard nobody watches is not a handoff. It should land where your team already looks: the helpdesk queue, an email, a phone alert. Decide that before you turn the assistant on, not after the first complaint.
Measure the ones that never happened
Look for conversations where somebody asked the same thing three times and left. Those are handoffs that should have fired and did not, and they are invisible in every deflection metric.