Call transfer: best practices so you never lose the caller

A transfer is a fragile moment. The caller has already explained their request once, they have been understood, and now they are told they are being put through to someone else. If they are faced with hold music that goes on and on, endless ringing or the voicemail of an absent colleague, their patience soon runs out.

The worst outcome is not the caller who hangs up: it is the caller who rings back, lands on reception again and has to tell the whole story a second time. They come away with an impression of disorganisation, however good the final answer.

A transfer should never be a surprise. One sentence is enough: “I’m putting you through to Claire, who handles quotes; if she’s not available, I’ll take your details so she can call you back today”. The caller knows who they are going to, why, and what will happen if the connection fails.

This announcement changes how the wait is perceived. Thirty seconds of ringing seem short when you know a specific person is going to answer; they feel endless when you have no idea where you have been sent.

The announcement also helps the colleague receiving the call. If they know the caller has been warned of a possible callback, they can let it ring during an important meeting without fear of losing the contact for good.

In a small business, transfers may depend on the memory of the person who answers: they know which requests justify disturbing the boss, and at what times the boss can be reached. The day that person is away, nobody knows when to transfer any more.

It is better to write these rules down: which requests justify a transfer, at what times, and what to do if nobody answers. They can then be applied by a stand-in, an intern or an automated system, and reviewed when the organisation changes.

These rules are best kept short. A few simple criteria are worth more than a decision tree that nobody remembers beyond the first week.

This point is easily overlooked. If the person you transfer to is in a meeting or on the road, the call must not end up in a generic voicemail box or go back to square one. It must lead to a complete message, with a clear commitment on when the caller will be called back.

Colleagues need protecting too. Transferring calls at night to a personal mobile without prior agreement, or ringing a technician’s phone mid-job for an administrative question, wears down the team’s goodwill. Transfer times are decided with the people who receive the calls.

The colleague receiving a transferred call should know, before even saying hello, who is calling and why. Failing a verbal handover by reception, a written summary that can be read quickly makes it possible to pick up the conversation where it left off: “Hello Mr Durand, you’re calling about the leak under the sink, is that right?”.

That sentence is worth all the hold music in the world. It proves to the caller that their first explanation served a purpose, and it shortens the conversation that follows accordingly.

A few seconds of reading before picking up save a full explanation. It is also a mark of respect for the caller, who does not have to make the effort of explaining their request again to someone new.

Alyas applies this logic: the voice agent picks up, announces itself as an AI, understands the request, transfers to the number you have configured in the cases you have set and, in other cases, collects the caller’s contact details and the subject of their request. The transcript and summary of every call remain available in your client area for the person calling back. The ten-day free trial lets you test these instructions in real conditions.