When to hand off
Four triggers cover most cases.The caller asks
The caller asks
A caller who asks for a person should get one. Arguing produces complaints, and an agent that refuses twice has already lost the call.Handle a single deflection at most: “I can log that for you right now, or put you through — which would you prefer?” If they ask again, transfer.
Safety or urgency
Safety or urgency
Some reports must reach a person immediately regardless of what the agent could do. Name them explicitly in the instructions — smoke, injury, a trapped person, anything involving danger.These should transfer without any attempt to collect details first.
Out of scope
Out of scope
A caller on the maintenance line asking about their invoice is not a failure. Transfer to the right team rather than improvising an answer.
Repeated failure
Repeated failure
If the agent has asked the same question three times and still has not understood, further attempts will not help. Poor line quality and strong accents both produce this pattern.
What the caller hears
Say that a transfer is happening and why. Silence followed by hold music reads as a dropped call.Pass the context across
The single biggest frustration in a transferred call is repeating yourself. Whoever picks up should receive what has already been established — what the caller wants, what has been collected, and why the transfer happened. Where a live screen pop is not possible, sending the summary to the destination team as a message still saves the caller from starting over.After hours
Decide explicitly what happens when no human is available:- Take a message — the agent collects details and promises a callback. Only if someone actually calls back.
- Say when to call — honest and cheap. “Our team is available Sunday to Thursday, eight to five.”
- Escalate anyway — for genuine emergencies, an out-of-hours number.

