What are the etiquette rules for transferring calls?
What are the etiquette rules for transferring calls? Tell the caller why you need to transfer them, explain who will help, ask before placing them on hold, and give the receiving person the relevant context. Return to the caller before completing the handoff, and have a clear fallback if nobody answers.
Start with a reason, rather than a sudden hold
A transfer should make the next step clearer. Explain which team can help and why, using words the caller understands. Avoid internal department codes or a vague “someone else handles that.”
For example: “Our bookings team can help you change that appointment. May I put you on a brief hold while I check who is available?”
If the caller has already explained a problem, acknowledge what you heard. Do not make a frustrated caller repeat the story merely to decide where they belong. If you are unsure of the destination, clarify the request before transferring.
Choose a warm handoff when context matters
A warm transfer gives the receiving person context before the handoff is completed. A cold transfer sends the caller on without that consultation. Twilio’s transfer documentation makes this distinction explicit.
Use a warm handoff for a complicated booking, an unresolved issue or a caller who needs a specific specialist. A direct transfer may suit a caller who explicitly asks for a known extension, provided you explain what will happen and the destination is correct. These are service-design recommendations, not universal legal requirements.
Give the receiving person a short, useful summary
Pass on the caller’s name where appropriate, the reason for calling, the action already attempted and what help they need next. Share only the information the receiving person needs for their role.
An effective example is: “Alex wants to move Thursday’s consultation. We checked the online calendar, but their preferred time needs your approval.”
Avoid subjective labels such as “difficult customer,” unnecessary personal details or reading an entire transcript aloud. Make sure the recipient is ready to take ownership. An answered line alone does not prove that the right person is available.
Return to the caller before connecting them
Once the recipient is ready, come back to the caller and explain the next step: “Thanks for waiting. Sam from bookings can help, and I’ve explained which appointment you want to move. I’m connecting you now.”
This is the final announcement in VoiceAIWrapper’s described warm-transfer flow. It avoids leaving the caller guessing whether the call has dropped or whether a new person has joined. If the staff member’s name is unknown, use the verified team name instead of inventing one.
Let the receiving person take over before ending the original interaction. The precise connection sequence depends on your phone setup, so listen to both sides during testing.
Have a polite fallback for an unanswered transfer
Agree with the business what happens if the destination is busy, closed or unanswered. A useful fallback might offer a message, a different team or a callback, depending on what the business can actually deliver.
For example: “The bookings team isn’t available right now. Would you prefer to leave a message or request a callback?”
Do not promise an exact callback time unless the workflow and team can honor it. Do not send someone repeatedly through the same transfer loop. If a caller declines to wait, respect that choice and explain the available alternative. A requested callback still needs the appropriate permission and calling setup.
For a configured VAW fallback, a caller who prefers not to wait could receive an appropriate contact link by SMS from your own number. VAW includes SMS consent and opt-out handling, but you must still establish the appropriate permission and configure the message for the purpose. Test the unanswered destination and the alternative channel together. Hold music and multiple transfer destinations can support a clearer handoff; they do not replace an explanation or permission to place someone on hold.
Test the etiquette as well as the connection
Before using a client’s number, run these scenarios:
- The caller agrees to the hold and the human answers.
- The caller declines the hold or asks why a transfer is needed.
- The destination does not answer or is closed.
- The receiving person needs clarification before accepting.
- The caller asks for a different department midway through.
- The caller disconnects during the handoff.
Check that the caller hears the first explanation and final announcement, that the human receives an accurate summary, and that private consultation audio is handled as intended. Review whether the fallback actually works rather than only checking the prompt.
For agencies, save the approved transfer script, department destinations and escalation rules with each client’s configuration. Review them whenever staffing or opening hours change. The best etiquette is a predictable handoff: the caller understands what is happening, and the next person knows how to help.