Skip to main content
Guides

What Is a Warm Transfer Call? Warm vs Cold Transfers, With Scripts

A warm transfer call introduces the caller to the next agent before handing over. Warm vs cold transfers, with scripts, a decision table and a cost sheet.

A warm transfer call is a transfer where the agent who has the caller first speaks to the person taking over, tells them who is on the line and what they need, and only then hands the call across. In a cold transfer, also called a blind transfer, the caller goes straight to the new number or queue with no introduction.

A warm transfer spares the caller a second explanation. It also costs agent time on both ends, and when the call is headed for a queue, your first agent waits in that queue too. So the choice is worth making call type by call type, and the tables and scripts here are for making it on purpose.

What is the difference between a warm and a cold transfer?

In a warm transfer the caller waits on hold while the first agent briefs the next one, then the call moves across, sometimes with a short three-way introduction. In a cold transfer the first agent sends the call and drops off, and the person who answers starts from nothing.

Warm transferCold transfer
Other namesAttended transfer, consult transfer, consultative transferBlind transfer, unattended transfer, basic transfer
What the caller hearsHold, then the new agent already knowing why they calledA ring or the queue, then the question "how can I help?"
What the receiving agent knowsWhat the first agent told them in the consultWhatever the caller repeats, plus anything in the record
Who waits for the other side to answerThe first agent and the callerThe caller alone
Agent time usedBoth agents during the consult, plus the first agent's waitThe receiving agent, while the caller explains again
If nobody answersThe first agent finds out and can offer another optionThe caller finds out, in a queue or on voicemail

The IETF's call transfer standard for SIP draws the same line. It describes a basic transfer "sometimes known as 'unattended transfer' or 'blind transfer'," and an attended transfer where the person transferring "places the Transferee on hold, establishes a call with the Transfer Target to alert them to the impending transfer," then completes it (RFC 5589). The same document describes a hybrid, the semi-attended transfer, where the agent starts the consult but hangs up before the other side answers and the transfer goes through anyway.

What does your phone platform call a warm transfer?

Few contact center platforms label their buttons warm and cold. The warm version is usually called a consult, and the cold version is just transfer, blind transfer or transfer to a queue. The table shows what agents see on six common platforms, taken from each vendor's own documentation.

PlatformCold transferWarm transferWorth knowing
Genesys CloudBlind transferConsult transferOne consult per call, though the person who receives the call can start another (Genesys)
Microsoft TeamsTransferConsult then transferNot available in Teams for the web (Microsoft)
Dynamics 365 Contact CenterTransferConsult, by call, chat or bothThe first representative can promote the consulted one to primary and step back (Microsoft Learn)
NICE CXone AgentTransfer without waiting for an answerConsult, then Transfer or ConferenceA transfer to a skill places a new call in that skill's queue, and the agent can complete it at once or wait to brief whoever picks up (NICE)
Webex Contact CenterTransfer to a queue, agent, entry point or dial numberConsult, or a conference with the customer and another agentThe consult request shows the other agent up to nine call variables, up to six of them set by your administrator (Webex)
Talkdesk Conversations mobile appBlind transferWarm transferOn a blind transfer the call ends for the first agent as soon as they tap Transfer, whether or not the other person accepts (Talkdesk)

Two details in that table change how you write transfer rules. On NICE CXone, a consult to a skill is a call into a queue, so the first agent waits in that queue like any caller. And on Genesys Cloud an agent can consult only once per call, so a rule that has one agent check with billing and then with returns won't work as written.

How do you do a warm transfer? Steps and a script

A warm transfer takes five steps: tell the caller what happens next, put them on hold, brief the next agent in about fifteen seconds, hand over with a one-line introduction, and log the transfer. Set a limit on how long the first agent waits for an answer, and decide in advance what they offer the caller if nobody picks up.

  1. Tell the caller who they'll reach, why, and that they won't have to start over.
  2. Start the consult. The caller hears hold music, and the first agent hears the other side ringing or the queue.
  3. Brief the next agent: the caller's name, whether identity is verified, what they need, and what has been tried.
  4. Introduce, or transfer. Either bring the caller back in for a three-way introduction and leave, or complete the transfer from the consult.
  5. Log it. Record the transfer reason as the call outcome, so your reports show which call types end up somewhere else.

The lines below fill steps 1, 3 and 4, plus the line for when nobody answers. Replace the brackets with your teams and numbers.

MomentWho hears itLine
Before the holdCaller"I'm going to bring in [name or team], who handle [topic]. I'll tell them what you've told me so you don't have to repeat it. You'll hear hold music while I reach them."
The briefingNext agent"Hi, it's [your name] in [your team]. I have [caller's name] on the line, already verified. They need [request]. I've [what you tried], and it needs [why it's yours]. Can you take them now?"
The introductionBoth"[Caller's name], I have [agent's name] from [team] with me. They know about [issue in a few words] and will take it from here."
Nobody answers in [your limit]Caller"[Team] is with other callers right now. I can put you through to their line, or have them call you back at [time]. Which would you prefer?"

Keep the briefing to facts the next agent can act on. If it runs past twenty seconds, the caller's account of the problem probably belongs in the record instead, where the next agent can read it while they talk. For the cold transfer line and the rest of a call's wording, see the call center script examples.

When should you use a warm transfer instead of a cold one?

Use a warm transfer when retelling the story would cost the caller more than the consult costs you: long or sensitive explanations, escalations, and handoffs outside your center. Use a cold transfer for simple misroutes, into a queue that is already running long waits, and anywhere a person isn't free to take a consult.

SituationTransferWhy
The caller reached the wrong team and has said littleCold, into the right queueThere is nothing to retell, and a consult adds a wait for both of you
The caller has explained something long or sensitive, such as a billing dispute, a failed repair or a bereavementWarmThe retelling takes longer than the consult, and the caller feels the difference
An upset caller, or a request for a supervisorWarm, with the three-way introductionThe caller hears that the new person already knows
The call goes outside your center, to a partner, a vendor or a field teamWarmYou find out whether someone actually answered before you let go
The target queue is running long waitsCold, into a priority lane, or a callbackA consult would park your agent in that queue as well
The receiving team is closed or nobody is signed inNo transfer: take the details and book a callbackSome platforms end a call sent to an empty queue
A self-service option or AI agent hands the call to a personWhatever the vendor supports; if it's cold, send it to its own number or priority queueThe person answering should know where the call came from

Platforms differ on the empty-queue row. In Dynamics 365 Contact Center, a call transferred to a queue that has no representatives is ended automatically and its status set to Closed (Microsoft Learn), while in Genesys Cloud a call transferred to a queue waits there for the next available agent (Genesys). Check which one your platform does before you write the after-hours row.

How much agent time do warm transfers cost?

A warm transfer costs your first agent the wait for the other side plus the consult, and costs the receiving agent the consult. It saves the receiving agent the time a cold transfer spends getting the story again. The worksheet nets those out into agent hours a month, so you can see whether a warm-transfer rule is cheap or expensive in your center.

Enter it in a spreadsheet as below. The example values are an illustration, not a benchmark: replace them with your own.

CellWhat it holdsExampleFormula
B1Warm transfers a month1,500Input
B2Seconds the first agent waits for the other side to answer50Input
B3Seconds the consult lasts30Input
B4Seconds a cold-transferred caller spends retelling the story45Input
B5Extra agent seconds per warm transfer65=B2+2*B3-B4
B6Extra agent hours a month27.1=ROUND(B1*B5/3600,1)
B7Seconds saved for the caller per warm transfer15=B4-B3

Where the inputs come from:

  • B2 is the receiving queue's average speed of answer when warm transfers go to a queue, or how long the person usually takes to pick up when they go to a direct line.
  • B3 is in your platform's consult or conference reports. If you can't find it, time twenty recorded transfers.
  • B4 comes from twenty recorded cold transfers: time from the moment the receiving agent answers until they start working the request.

Row 7 is easy to overlook. Both kinds of transfer make the caller wait for the other side, so the caller only comes out ahead when the consult is shorter than the retelling it replaces. If your consults run longer than the retelling, a warm transfer costs everyone time, and the case for it rests on how the call feels to the caller. That can still be right for an upset customer, but it is hard to justify for a routine misroute.

If row 6 is large, look at why calls are being transferred at all before you argue about which kind. Transfers by menu option and by call type, covered in call routing, show which first stops need better instructions.

How do you make a cold transfer less blind?

A cold transfer doesn't have to arrive blind. Tell the caller where they're going, send transferred calls to their own queue or priority so they don't wait behind new callers, and have your platform tell the receiving agent where the call came from. Most of that is set up once in the phone system rather than done by agents on every call.

  • Say where the call is going and give a number in case it drops, as in the cold transfer line in the script examples.
  • Write one line in the record before you let go, if your desktop shows notes or call variables to the next agent. On Webex Contact Center, for example, the popover on an incoming call shows variables your administrator chooses (Webex).
  • Give transferred calls a faster lane. The second example in call center call flow sends tier 1 transfers into the tier 2 queue at a higher priority, so the caller doesn't queue twice.
  • Add a whisper. In Amazon Connect, an agent whisper plays only to the agent and runs before the customer is taken out of queue. It can last up to two minutes and doesn't appear in transcripts (Amazon Connect). "Transferred from billing, account verified" is the short version of a briefing.
  • Make common destinations one click. Amazon Connect's quick connects are a list of destinations for common transfers, and its documented example is a quick connect for tier 2 support (Amazon Connect).

The inbound call center guide covers where transfer rules sit among the other setup decisions.

How Telvana passes a call to your team

Telvana's AI agents resolve what they can first: they answer from your knowledge base, look up customers, check availability, and book, reschedule and cancel appointments in the tools you connect. When a caller needs a person, the agent makes a cold transfer, an ordinary call to the number you choose, such as your main queue. We set that number and the rules for when to use it with you while building the agent.

The person who picks up doesn't get a summary first. The recording, transcript and summary are in the portal once the call ends (connecting your phone system). A Transfer Caller ID setting decides which number your team sees: the caller's or the agent's. If your phone system has a priority queue or a direct line, point the transfer there so the caller doesn't start again at the back (hold queue relief), and if your platform can play a whisper on that queue, use it to say the call is coming from the AI assistant.

Pricing is from $399 a month, based on call volume, plus a one-time setup fee. For what else to settle about an AI agent's handoffs before you buy, see AI call center agents.

Frequently asked questions

What is a warm vs cold transfer?

A warm transfer is one where the first agent speaks to the next person before handing the caller over, so the caller doesn't have to explain again. A cold transfer, or blind transfer, sends the caller straight to the new number or queue with no introduction, and the person who answers starts from the beginning.

What does it mean to provide a warm transfer in customer service?

It means the agent stays with the caller until someone who can help has been reached and briefed. The caller waits on hold during the consult, then is introduced or passed across, and the new agent opens with what they already know instead of asking the caller to start over.

What should you do before transferring a call?

Check that the transfer is needed and that the destination is open and staffed. Tell the caller who they'll reach and why, note the reason in the record, and decide what you'll offer if nobody answers. For a warm transfer, have the four facts of the briefing ready: name, verification, request, and what was tried.

Is a warm transfer the same as a conference call?

Not quite. In a warm transfer the first agent usually talks to the next agent privately while the caller is on hold, then hands over. A conference brings all three people onto the line together. The two combine well: on NICE CXone, for example, an agent can brief the next agent first, then click Conference to merge the calls and Leave once the caller is introduced (NICE).

What is a semi-attended transfer?

It is a hybrid in which the agent starts a consult, then hangs up before the other side answers, and the transfer completes anyway. The IETF describes it in its SIP call transfer standard, for example when the agent is content for the caller to reach the other person's voicemail. It saves the first agent's wait but loses the briefing.

Can an AI agent do a warm transfer?

Some AI voice platforms offer it. Bland's AI, for example, calls your agent, briefs them and then merges the caller in, on its Enterprise and Agent Phone tiers, as our Bland AI alternatives comparison notes. Others, including ours, use a cold transfer to a number you choose and keep the transcript and summary for your team to read.

Map your transfers before you add an AI agent

Bring your transfer rules, or a list of the call types that most often end in a transfer, to a demo. We'll show you which of those calls an AI agent can finish on its own and where its transfers should land in your queues. Book a demo.

More guides

Put AI agents to work in your contact center.

Book a demo. We'll walk through your call types, show you which ones Telvana can take, and let you hear it handle one.

See pricing

Or call our AI at 1 (650) TELVANA