Warm transfer: when the AI hands the call to a person

Updated 2026-09-19 · 5 min read · By the Convo360 team

What a warm transfer actually is

A cold transfer just forwards the call, the human picks up with zero context and has to ask the caller to repeat everything. A warm transfer is different: before connecting, the system plays or reads out a short summary of what the caller needs, so the person picking up already knows why they're on the line.

This matters more on voice than on chat, because a caller who has to re-explain themselves on a phone call gets frustrated fast, there's no scroll-back to a chat history. Every re-explanation is a small tax on the caller's patience, and it's the single biggest reason handoffs feel clumsy even when the human on the other end is perfectly capable.

Done well, a warm transfer should feel invisible to the caller, like being passed to a colleague who was already in the room, rather than starting the conversation over with a stranger.

When to trigger a transfer

Not every call needs a human. Reserve transfer for situations where the AI genuinely can't help, or where policy requires a person:

• Keyword trigger: the caller says 'talk to a person', 'manager', or similar, this should always work, even mid-flow.
• Repeated failed understanding: if the agent misunderstands the same question twice, escalate rather than looping.
• Business rule: high-value orders, complaints, or anything involving a refund above a threshold you set.
• Compliance-sensitive requests: the AI should never handle password resets, OTPs or full card numbers, hand these straight to a human or a secure self-service link.

It helps to think of transfer triggers in two buckets: caller-initiated (the person explicitly asks for a human) and system-initiated (the flow decides, based on a rule, that a human should take over). Both need to exist. A bot that only escalates when it detects its own confusion will frustrate a caller who wanted a human from the start but had to fight the script to get there.

Building the transfer flow on Convo360

1. In the Flow Builder, add a transfer voice block at the point where escalation should happen.
2. Set the destination number, a team member's mobile, or a shared support line.
3. Configure the context summary: what the agent has gathered so far (name, reason, order number) gets read out to the human before the caller is connected.
4. Add a Condition block upstream to check office hours or team availability before attempting the transfer.
5. Add a voicemail block as the fallback path if the transfer isn't answered within a set number of rings.
6. Use a keyword trigger ('agent', 'manager', 'human') so callers can ask for a transfer at any point in the call, not just where you planned it.

See the Flow Builder docs for how Condition and Wait blocks combine with voice blocks like gather, DTMF menu and transfer.

It's worth mapping out the full escalation path on paper before building it in the Flow Builder, decide which intents transfer immediately, which ones the AI should attempt first, and where each destination number sits in your team's structure. A flow built without this planning tends to end up with every escalation routed to one person, which just moves the bottleneck rather than removing it.

Availability windows and voicemail fallback

A transfer attempted outside your team's working hours just rings and rings, which is worse for the caller than not offering a transfer at all. Gate the transfer block behind an availability check, a Condition on time of day and day of week, so outside those hours the call goes straight to voicemail or offers a callback instead.

When voicemail is used, tell the caller clearly what happens next: 'I've noted your number, our team will call you back by 11 AM tomorrow' is far better than a generic beep with no expectation set.

If your team works split shifts or has different people covering different intents (billing versus support, for example), you can chain multiple Condition checks so the transfer destination changes depending on both the time of day and the reason for the call, rather than every escalation going to one general number.

What happens after the transfer

Once a call is handed off, Convo360 can still log the interaction: the AI summary of the pre-transfer conversation, a CRM lead entry, and a team notification so whoever picks up (or a manager, if no one does) has a record. This keeps the handoff from becoming a black hole where the AI's context is lost the moment a human joins.

Review transfer volume in Flow Logs periodically, a high transfer rate on a specific intent usually means the AI's script or knowledge base needs an update, not that transfer is broken.

Treat transfer rate as a diagnostic, not a failure metric. Some volume of transfers is healthy and expected, the goal isn't zero transfers, it's making sure every transfer that happens is one the AI genuinely couldn't or shouldn't have handled itself.

Common mistakes when setting up transfer

A few patterns show up repeatedly when transfer flows go wrong:

• One destination for everything. Every escalation ringing the same phone means one person becomes a bottleneck for issues that could have gone to different teams.
• No availability check. A transfer that rings out after hours wastes the caller's time and often ends with them hanging up frustrated instead of leaving a voicemail.
• Missing context summary. Skipping the spoken briefing turns a warm transfer back into a cold one, the human still has to ask the caller to repeat themselves.
• No way to ask for a human directly. If the keyword trigger isn't active throughout the call, callers who want a person early get stuck working through the AI's script first.

Most of these are caught quickly the first time you listen to a handful of real transferred calls end-to-end, which is worth doing in the first week after launch.

Step by step

1. Add a transfer blockPlace a transfer voice block in the Flow Builder at the point where the AI should escalate to a person.
2. Set the destination and context summaryPoint it to a team number and configure what call details get read to the human before connecting.
3. Gate it with an availability ConditionCheck office hours before attempting the transfer so after-hours calls skip straight to voicemail.
4. Add a keyword trigger for 'talk to a person'Let callers ask for a human at any point, not only where you planned an escalation.
5. Set a voicemail or callback fallbackIf the transfer isn't answered within a few rings, route to voicemail with a clear next-step promise.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.