When to hand a conversation to a human
The handoff rules matter more than the conversation quality. Get them wrong and one bad thread costs you more than a hundred good ones earned.
Any system that talks to customers at scale will eventually hit a conversation it should not be in. What separates a safe deployment from a liability is not how rarely that happens — it is how reliably the system notices and gets out.
The non-negotiable exits
They asked for a person
Immediately. Not one more helpful message, not a clarifying question. Stop, and tell a manager right now, through a channel a manager will actually see.
They asked to be left alone, in their own words
Compliance keyword handling catches STOP. It does not catch please stop texting me, or I already told someone I am not interested, or take me off your list. Those are all clear and all have to be honoured as though they were the keyword.
They named a time to be left alone
Check back with me in two weeks means silence for two weeks. Nothing in any follow-up ladder should be able to override a customer explicit request, and if it can, that is a defect, not a setting.
Something smells wrong
A story that does not hold together, a request that resembles fraud, a legal word, a complaint taking shape. All of these go to a person immediately, with the thread attached.
One of your people is already in the thread
The moment a rep types, the system steps back. Talking over your own salesperson or double-texting a customer is the failure that makes staff distrust the whole platform, and once they distrust it they stop using it.
A system that never hands off is not confident. It is unsupervised.
The harder question: appointments
The most common way automated conversation systems embarrass a store is by claiming a booking that never happened. The customer said maybe Thursday could work, or actually that does not work for me, and the system logged an appointment.
The bar has to be an explicit agreed date and time, with negation detected properly. That does not work for me contains a day and a time and means precisely the opposite of a booking. If the evidence is not there, no appointment is created — and a missed booking is a far cheaper error than a salesperson standing around at two o clock for a customer who never agreed to come.
And a quiet one people forget
If the system sees the same inbound message three times in a row, it is probably talking to another autoresponder. It should stop and flag rather than run a loop for an afternoon.