Designing the handoff to a human

What should trigger a handover?

Four categories, and only one of them is the agent being unsure. First, the caller asking, in any phrasing, including the ones that are not requests: real person, speak to someone, is this a robot, and the sigh followed by hello. Second, emotional signals: raised voice, swearing, distress, repeated frustration. Third, subject matter you decided in advance is off limits, such as complaints, refunds, legal threats or anything safety related. Fourth, repeated recognition failure on the same turn.

The fourth is the one teams get wrong by tuning it too tight. If the agent asks the same question three times, the caller has already concluded the system is broken, and a fourth attempt confirms it. Two failures on the same slot is a reasonable ceiling.

Write these triggers down as rules rather than leaving them to the model's discretion. An intent classifier or a keyword list that always transfers is more reliable than hoping the generated response chooses to, and it gives you something you can test.

The trigger nobody configures is time. A call that has run past the point where an agent could plausibly still be helping, three or four minutes of going in circles, should hand over on duration alone. Callers rarely ask for a person that late; they have already concluded the call is wasted and are staying on out of hope. A ceiling on call length, with a transfer at the end of it rather than an apology, recovers some of them.

What makes a handoff feel like a dead end?

Silence, repetition, and being asked to start again. The caller experiences a handoff as a dead end when the agent says it is transferring and then nothing audible happens for several seconds, when the transfer fails and drops them back into the same opening prompt, or when the human who answers opens with how can I help, having received none of the last two minutes.

The repetition case is the most damaging because it is invisible to your metrics. The call shows as answered, then answered again, and nothing marks the second call as the same person retrying. Callers do not retry twice.

Fix the audible part first because it is nearly free: say what is happening, name the wait, and keep a ringback or an announcement playing. A caller who has been told they are being put through to the workshop and it may take twenty seconds will wait. A caller in silence assumes the line has died and hangs up at about five.

What does the person receiving the call need?

A one-line reason, the caller's number, and whatever was already captured, delivered before they speak. If your telephony supports it, that means a whisper announcement to the agent's handset or a screen pop; if it does not, a message in the channel your team actually watches, sent at the moment of transfer rather than after the call ends.

Keep it short enough to be read while the phone is ringing. Reason for the transfer, the caller's name if given, the number to ring back on, and one line of what they said. Anything longer will not be read, and a summary nobody reads is worse than none because it makes the handoff look designed when it is not.

The test is whether the human can open with a sentence that proves continuity. Something like: I understand you are calling about a leak at a rental property. If they cannot say that, the caller repeats the whole story and the handoff has failed even though the transfer succeeded.

What should happen when nobody picks up?

This is the case that matters, because most handoffs happen when your team is busy or closed. The agent must not promise a transfer it cannot complete. It should attempt the route, detect that it failed, and come back on the line with an honest statement: nobody is free at the moment, here is what I can do instead.

The alternatives, in order of usefulness: offer a specific callback time rather than someone will call you back, take a number and confirm it digit by digit, and send an alert to a person immediately rather than adding a row to a queue nobody reads until Monday. If the caller has already been waiting, say how long they have been waiting and apologise for it plainly.

One rule prevents the worst outcome: never end a failed handoff by returning the caller to the top of the conversation. Ending the call with a clear commitment is better than looping, and callers accept a no far more readily than a circle.

Warm transfer or cold transfer?

Cold transfer, sometimes called blind transfer, hands the call over and drops the agent out of it. It is simple, it costs nothing, and it fails in exactly one place: if the destination does not answer, the caller lands in a voicemail they did not choose, or the call clears. Cold transfer is acceptable only when you can guarantee someone answers.

Warm transfer keeps the agent on the leg long enough to confirm a person is there, deliver the whisper summary, and then bridge the caller in. It costs more, because two legs are live at once and the platform is still consuming minutes, and it needs your telephony to support attended transfer. It is worth it for the emotional and commercial cases, where a dropped handoff costs a customer.

A reasonable default is cold transfer to your main line during staffed hours, warm transfer for anger, complaints and named-person requests, and no transfer at all out of hours, replaced by a callback commitment the system can honestly make.

Whichever you choose, the transfer needs a timeout the agent controls rather than one your carrier controls. Left on default behaviour, a call can ring at an unattended desk for a long time while the caller has no idea whether anyone is coming. Fifteen seconds of ringing, then the agent back on the line with an honest alternative, beats forty seconds followed by a voicemail nobody checks. Pick the number deliberately and test it with the phones switched off.

How do you test the handoff this week?

Ring your own number five times and try to break the exit. Ask for a person in the first three seconds. Ask in the middle of an answer. Ask while the agent is speaking, to check whether interruption is recognised. Swear once. Then repeat all five with your team's phones switched off, because that is the state the system will actually be in at seven in the evening.

Time the silence in each case with a stopwatch. Anything over three seconds without audio needs an announcement. Then check what arrived at the other end: did a summary appear, did it contain the number, and could a colleague have opened the call knowing why it came.

Finally, look for the silent failure in your logs: two calls from the same number within a few minutes. That pattern is your handoff failing, and it will not appear in any containment or success metric your vendor reports.