# What is Warm Transfer?

Also called attended transfer, consultative transfer.

A warm transfer is a call handoff in which the transferring party first speaks privately with the destination, passes context, and only then connects the caller. It contrasts with a cold or blind transfer, where the call is redirected immediately with no consultation. Warm transfers preserve continuity at the cost of a longer handoff.

In telephony terms a warm transfer is an attended transfer. The original call is placed on hold, a consultation call is dialed to the destination, and once the destination accepts, the two legs are bridged and the transferring party drops off. Blind transfer skips the consultation entirely, using a REFER-style redirect that gives the destination no advance notice and no chance to decline gracefully.

In agent-assisted flows, the same shape applies when a conversation moves from an automated handler to a person. The system opens the connection, delivers a structured summary of what has happened so far, including verified identity, the stated issue, and any actions already taken, and only then joins the caller. The summary can be spoken in a whisper leg or presented on screen as a screen pop.

Context transfer is the point of the pattern. Without it the customer repeats themselves, which is consistently one of the most cited frustrations in support surveys. Systems therefore attach call variables, transcripts, and CRM record links to the transfer so the receiving party opens with knowledge rather than questions.

Warm transfer has costs. It occupies two lines and two parties for the consultation period, so it is usually reserved for escalations, sensitive accounts, and cases where identity has already been verified. Many contact flows use warm transfer for escalation paths and blind transfer for simple routing corrections such as reaching the wrong department.

## Key points

- Consultation happens before the caller is connected
- Blind or cold transfer redirects with no handoff conversation
- Structured context prevents the caller repeating themselves
- Whisper audio or a screen pop delivers the summary
- Occupies two legs, so it is reserved for escalations

## In practice

An automated handler has verified a caller, confirmed a duplicate charge, and reached the limit of what it can resolve. It places the caller on hold, dials the billing queue, and speaks a short whisper summary naming the account, the transaction, and the verification already completed. The receiving specialist accepts, sees the transcript on screen, is bridged in, and opens by confirming the refund rather than by asking for the account number.

## Related terms

- [Telephony Integration](/en/glossary/telephony-integration)
- [Channel Routing](/en/glossary/channel-routing)
- [Interactive Voice Response](/en/glossary/interactive-voice-response)
- [Queue Position](/en/glossary/queue-position)
- [Conversation Thread](/en/glossary/conversation-thread)

[Back to the AI Glossary](/en/glossary)