Contents5 sections
Field notesARTICLE
When the Customer Asks for a Human
Half the time they do not ask in words. What the trigger is, what the person receives, what the customer is told, and the one version of this that loses you the customer outright.
Costa4 min read
Short answer
A handover should fire on an explicit request, on a topic from the limits list, on a repeated question, on a change of register, and on a stated intention to leave. What matters afterwards is that the person receives the whole thread with what has already been promised, that the customer is told who is taking it and when, and that the handover is never made into a queue nobody is watching.
Key facts
- The person receives the full thread, a short summary at the top, and an explicit list of what the assistant has already committed to.
- The customer is told a person is taking over and by when, rather than being left with no reply.
- Outside working hours the assistant says when the answer will come instead of staging a handover into an empty queue.
- A conversation handed over twice is flagged, because the second one has a different cause.
A customer types can I talk to someone. That one is easy.
The other half of handovers arrive without the word in them, and getting those right is most of the work.
Five ways the request arrives
In words. Explicit, unambiguous, and it happens immediately with no attempt to help first. Asking what is it about? before agreeing costs more goodwill than it ever saves.
By topic. Refunds, disputes, anything on the limits list. The customer did not ask; the policy did.
By repetition. The same question a third time, phrased differently each time, means the assistant's answer is not landing. The third attempt is not the one to try harder on.
By register. The messages get shorter, or the punctuation changes, or the politeness drops out. Something moved from a question to a grievance, and that shift is visible in the text before anybody uses the word complaint.
By intention. We may need to rethink this. Are you able to hold it or should I look elsewhere. These are decisions in progress, and a person changes the outcome in a way an accurate answer does not.
The clock that matters
Time to the first sentence written by a human being. Not time to assignment, not time to the ticket appearing on a board.
The customer cannot see your queue. They see a reply, then nothing, then eventually a person. If the gap between the assistant's last message and the human's first is forty minutes, it was a forty-minute handover, whatever the dashboard says. Measuring assignment instead is the most common way an operations report ends up describing a system nobody experiences.
What lands on the person's screen
Four things, in this order.
The whole thread, in the language the customer wrote in. A two-line summary above it, because the person taking over is doing this between two other jobs. An explicit list of anything already committed to — a price quoted, a slot held, a document sent — since that is what they are now standing behind. And the open question, stated as a question, so the first thing they have to do is not reconstruct why this is on their screen.
The thing that must not happen is a person opening the conversation and asking the customer to explain again. That single move undoes the entire value of answering fast in the first place.
The sentence the customer gets
One line, with a name and a time. Marina is picking this up and will reply before six.
Not your request has been escalated, which tells the customer nothing except that they have been moved somewhere. And then the assistant stops writing in that thread. Two voices in one conversation reads as chaos, and the person who took it needs to be the one holding it.
Nine at night, and nobody there
The failure that costs a customer outright is a handover into an empty queue. The assistant promises a person, the person is asleep, and the customer waits until morning holding a promise instead of an answer.
An honest sentence beats a staged one every time: what the office hours are, when the answer will come, and everything the assistant can settle in the meantime. That is a worse-sounding message and a much better outcome, and it is the same argument as the one about answering at 02:14 at all.
Handover is where an assistant either earns the rest of the system or wastes it. Every conversation on your limits list ends here, and the customer's memory of your business is formed by whichever of the two versions above they happened to get.
Questions this raises
- Should the assistant say it is not a person?
- Yes, and early. Every business that has tried the alternative discovered that customers work it out and remember being fooled for longer than they remember the wait.
- Can the assistant keep helping after the handover?
- It stops writing to that customer. Two voices in one thread is worse than a slow answer, and the person who took it over needs the last word to be theirs.
- What if the customer asks for a human on something trivial?
- It hands over anyway. Debating the request costs more than the two minutes it takes a person to say yes, and every argument about whether a handover was warranted is an argument the business loses.