Choosing the moment a voice agent should hand over to a human is a separate topic we have covered. This piece is about what comes after the decision: what does the customer experience when the handover happens?
The most common experience is this: the customer explains their situation for three minutes, the agent hands over, a human picks up and asks — "hello, how can I help you?"
In that moment, all the trust the agent built is erased.
Three things a handover must carry
When the receiving person picks up, they should have:
- Who. The caller's name, whether they are a known customer, their history.
- What they want. A one-sentence summary. "Delivery delay, has the order number to hand."
- How far it got. What the agent said, what it promised, what information it gave. Skip the third and the receiving person may contradict the agent — which, from the customer's side, means getting two different answers.
Three ways to hand over
Warm transfer (during the call). The agent holds the line, puts the customer on hold and connects a rep. This is the best experience and the most expensive: it needs an available rep right then.
Cold transfer (callback). The agent ends the call, the record is assigned to a rep, and the rep calls back. The customer is not kept waiting but the contact breaks. This method requires a promised callback window — and the promise must hold: "today" means by six in the evening.
Handover by changing channel. The conversation starts on the phone and continues in writing on WhatsApp. For anything needing documents, photos or links, this is the most practical route.
When no rep is available
This is the most fragile point of warm transfer. The agent says "I am connecting you to a colleague" and nobody answers. The rule: do not try to connect to a place that cannot answer. If availability cannot be checked, the agent should promise a callback instead.
Hold music is not a solution; it only delays bad news.
Not lowering the threshold too far
An agent that hands over at every difficulty is not an agent, it is a switchboard. Lowering the handover threshold raises your team's load and weakens the reason the agent exists.
A healthy approach limits handover to three situations: the customer explicitly asks for a human, the topic is outside the agent's scope, and the customer is clearly dissatisfied.
Recording the handover
Every handover should leave a record: why, to whom, when and with what outcome. Without it there is no way to tell whether the threshold is set correctly.
Reviewing that list weekly shows two things at once: gaps in the agent's knowledge base (if the same topic keeps triggering handovers, that topic is missing) and the team's real workload.
What to tell the customer
The handover line should be short, clear and free of apology. "I am passing this to a colleague, I have briefed them, and they will call you shortly" is enough. There is no need to explain the agent's limitations; the customer wants the outcome.
Tomorrow: requests coming from a web form — the difference sixty seconds makes.