Warm Transfer vs Blind Transfer: When to Use Each

Tom Reed · Updated 16 October 2026
A blind transfer, also called a cold transfer, sends the caller straight to a colleague without you speaking to that colleague first. A warm transfer puts the caller on hold while you brief the colleague, then connects them. Use blind transfers for simple, routine hand-offs to someone you know is free. Use warm transfers when the caller is upset, the issue is complex, money or account details are involved, or you aren't sure the colleague can help. On SessionPBX you can "hold calls, transfer directly or speak to a colleague before transferring", from the Windows, macOS, iOS and Android apps.
This guide covers the difference between the two, when each one fits a small team, what to say, what to do when nobody picks up, and how to stop callers being bounced around your business.
What is the difference between a warm and a blind transfer?
In a blind (cold) transfer, you tell the caller you're putting them through, send the call to a colleague's extension, and drop off the line. The colleague picks up without any context. If they don't pick up, the caller hears whatever happens next on that extension: more ringing, voicemail or a busy signal.
In a warm transfer, sometimes called an attended transfer, you put the caller on hold, call your colleague, explain who is waiting and why, and only connect the caller once the colleague has agreed to take it. The caller is never handed to an empty line, and they don't have to tell their story twice. Both are standard features of any modern PBX phone system; the choice between them is a team habit, not a technical one.
| Blind (cold) transfer | Warm (attended) transfer | |
|---|---|---|
| What the caller experiences | A short "putting you through", then ringing on a new line | A short hold, then an introduction to someone who already knows why they called |
| Speed | Quickest for you; you're off the call straight away | Slower; you stay on until the hand-off is agreed |
| Best for | Routine requests to a named person or team who is showing as available | Complaints, complex or repeat issues, payments and account changes, important callers |
| Risk | The caller rings out, lands in the wrong place or repeats everything | You hold the caller longer, and need a plan if the colleague can't take it |
| Script to use | The blind-transfer line | The hold line, the colleague brief and the introduction |
When should a small team use a blind transfer?
Blind transfers are fine for most everyday hand-offs. They keep the person who answered free to take the next call, and they suit requests where the caller already knows what they want and who can help.
Good fits for a blind transfer include:
- "Can I speak to accounts?" The caller has asked for a team by name, and that team handles exactly this kind of call.
- A named person on a known extension. The caller asks for someone specific, and that person is at their desk and showing as available.
- Simple information requests. Opening hours, a delivery address, a quick question that the receiving colleague answers every day.
- Calls that were expected. A supplier ringing back about an order that a colleague is already handling.
The one habit that makes blind transfers safe is checking presence first. Before you transfer, look at whether your colleague is showing as available, busy or away. If they're on another call or away from their desk, a blind transfer just moves the caller into a ringing phone or voicemail they didn't ask for. In that case, offer a choice instead: hold for a moment, leave a message, or take a call-back.
If you find that most of your blind transfers go to the same people for the same reasons, that's a sign your numbers or menus could send those calls there in the first place. We come back to that at the end.
When is a warm transfer worth the extra minute?
A warm transfer costs a little more of your time and asks the caller to hold. That trade is worth making whenever a cold hand-off could make things worse.
Use a warm transfer when:
- The caller is upset or complaining. Nobody wants to explain a complaint twice. Your colleague should know the background before they say hello.
- The issue is complex or has history. Repeat problems, long-running orders and anything with earlier calls behind it.
- Money or account details are involved. Payments, refunds, cancellations and changes to account details. Brief the colleague so they know what's been confirmed and what hasn't.
- It's a new-business or important call. A prospect or key customer deserves a smooth introduction, not a cold ring.
- You're handing to a manager. Escalations should arrive with the reason attached.
- You aren't sure the colleague can help. A warm transfer lets you check first. If they can't help, you can take the caller back and try someone else without the caller ever noticing.
The underlying rule is that the caller shouldn't have to repeat themselves. A warm transfer is how you keep that promise.
Warm or blind? A quick checklist
Ask yourself these questions before you transfer:
- Is the caller upset, or is this a complaint?
- Are money, payments or account details involved?
- Has the caller already been transferred on this call?
- Is the issue complex, or has it come up before?
- Is the colleague showing as available?
- Is this a routine request that the colleague handles every day?
If the answer to any of the first three is yes, use a warm transfer. If the answer to the fourth is yes, lean towards warm. If the colleague isn't showing as available, don't blind transfer; offer to hold, take a message or arrange a call-back. A blind transfer is the right call only when the request is routine and the colleague is free.

What should you say during each type of transfer?
Good transfers sound calm and deliberate. A few short, rehearsed lines do more than any amount of improvisation. For greetings, tone and general phone manners, see our guide to business phone etiquette; the scripts below cover the transfer itself.
Transfer script box
- Before a blind transfer (to the caller): "Sarah in accounts looks after invoices. I'll put you straight through to her now. If she's just stepped away, you'll be able to leave her a message."
- Before putting the caller on hold for a warm transfer: "I'd like to get you to the right person rather than make you explain this twice. Can I put you on hold for a moment while I brief my colleague?"
- The colleague brief (who, what, what's been tried): "I've got Mark Ellis from Hartley Builders on hold. He's calling about a duplicate charge on last month's invoice. I've confirmed his account and the invoice number, but I can't issue refunds. Can you take him?"
- Connecting and introducing: "Mark, I've got Sarah from accounts here. I've explained the duplicate charge and she has your invoice in front of her. I'll leave you with her."
- If the colleague can't take it: "Sarah's on another call at the moment. Would you like her to call you back this afternoon, or would you prefer to leave her a message?"
The colleague brief is the heart of a warm transfer. Keep it to three parts: who is calling, what they need, and what you've already tried or confirmed. Anything more and the caller waits longer than they should; anything less and your colleague starts from scratch.
Always ask before putting someone on hold, and come back to the caller if the hold runs on, even just to say you're still trying.
What happens if the colleague doesn't answer?
Every transfer needs a fallback, because colleagues will sometimes be on another call, away from their desk or simply miss it. The worst outcome is a caller left ringing out with nobody on the other end. Agree a fallback ladder as a team so everyone handles it the same way:
- Take the call back from hold. With a warm transfer, you're still on the line. Go back to the caller, explain, and offer the options below.
- Offer a named call-back. "Sarah will call you back before four" is better than "someone will get back to you". Write down the number, the reason and who owns the call-back.
- Send to voicemail, with the caller's agreement. Ask first: "Would you like to leave Sarah a voicemail?" Then make sure that voicemail is actually checked. Our guide to business voicemail setup covers greetings and who checks which mailbox.
- Route to a group or queue. If the call is for a team rather than a person, send it to the team's ring group or queue so the next free colleague picks it up.
This is a process for people, not a promise about automatic features. The point is that whoever started the transfer owns the caller until someone else has clearly taken over. If calls regularly end up unanswered after a transfer, look at how your numbers and teams are set up; our guide to call routing for small businesses walks through the options. On SessionPBX, ring groups and call queues are part of the Teams Business plan. Teams Phone and Teams Business are SessionPBX plans, not Microsoft Teams.
On the voicemail step, SessionPBX lets members listen to and download voicemail in the portal, and "receive new messages by email with the recording attached", which makes it easier for a colleague to pick up a message quickly.

How do you stop "pass the parcel" calls?
"Pass the parcel" is when a caller gets transferred from person to person, repeating their story each time, until they give up or lose their temper. It usually happens when nobody is sure who handles what.
A one-page set of team transfer rules prevents most of it:
- Aim for one transfer per call. If you can't find the right person in one move, take a message and get the right person to call back rather than guessing again.
- Keep a transfer directory. A short list of who handles what, by topic, with their extension. Short, memorable extensions help here; see our guide to a phone extension numbering plan.
- Check presence before transferring. If the colleague isn't showing as available, don't send the caller there blind.
- Own the call until it's handed over. The person who answered is responsible for the caller until a colleague has confirmed they've got it.
- Log repeat transfers. Note the topics that keep getting passed around. That list tells you where your routing or your directory needs fixing.
Team leads can use the same list for coaching. If you want to listen in on how new starters handle transfers, our guide to call monitoring, whisper and barge covers how supervisors can coach on live calls.
Forwarding is a different tool for a different job. A transfer moves a call you've already answered. Forwarding decides where calls go before anyone answers, for example when you're busy, don't answer, or are away. If you're transferring calls because someone is out of the office, set up business call forwarding instead.
When should you fix routing instead of transferring?
If the same transfers happen every day, the problem isn't the transfer. It's that those calls are arriving in the wrong place.
Look at your log of repeat transfers and ask:
- Do most calls to the main number end up with one team? Give that team its own number, or add a menu option that sends callers straight there.
- Does one person spend their day passing calls on? A ring group or queue for the receiving team takes them out of the middle.
- Do out-of-hours calls get transferred to voicemail every evening? Business-hours routing can send them there automatically.
Fixing routing is a bigger topic than this guide. For the design side, see our guides to call routing for small businesses and hosted PBX call queues and IVR. For the features a modern system should cover, see small business phone system features and our overview of the cloud-based phone system.
Transfers on SessionPBX
SessionPBX is a hosted PBX with native apps for desktop and mobile. In its own words, you can "call colleagues and customers from Windows, macOS, iOS and Android. Hold calls, transfer directly or speak to a colleague before transferring." Team chat and presence let you "see who's available" before you transfer, and you can forward calls to "an internal destination or external number". Teams Phone covers everyday calling, messaging and voicemail, with your own SIP carrier for external calls. Teams Business adds ring groups, call queues, visual call flows with IVR and business hours, recording and supervision tools. Both are SessionPBX plans, not Microsoft Teams. Compare plans and start a free trial on the SessionPBX hosted PBX page.
FAQ
Is a cold transfer the same as a blind transfer?
Yes. Both mean sending a caller to a colleague without speaking to that colleague first. The two terms are used interchangeably.
Is an attended transfer the same as a warm transfer?
Yes. An attended transfer is a warm transfer: you stay on the line, brief the colleague while the caller holds, and connect them once the colleague agrees to take the call.
Can you do warm transfers from a mobile?
On SessionPBX, yes. Holding a call, transferring directly and speaking to a colleague before transferring are all available in the Windows, macOS, iOS and Android apps, so the same habits work whether you're at a laptop or on your phone.
What should happen if a transferred call isn't answered?
Have an agreed fallback rather than relying on the phone system to sort it out. Take the caller back from hold, offer a named call-back, send them to voicemail with their agreement, or route the call to the right team's group or queue.
Does a warm transfer take much longer?
It adds a short briefing while the caller holds. For routine requests that isn't needed, which is why blind transfers still have a place. For complaints, account changes and complex calls, the brief usually saves time overall, because your colleague doesn't have to start again and the caller doesn't have to repeat themselves.


