Cold Transfer
Definition
Cold Transfer
A cold transfer is a live call handoff where an agent routes a customer to another agent, queue, or department without briefing the receiver first. Also called a blind transfer, it prioritizes speed over continuity and is the counterpart to a warm transfer.
You’ll hear the term most often in contact centers, though it applies to any live-voice channel with multiple agents. It sits under the broader idea of a call transfer, which covers every handoff type.
The counterpart is a warm transfer, where the first agent stays on the line to introduce the caller. Modern PBX and cloud contact-center software make both a one-click choice in the same softphone menu.
The convenience is real, and so is the risk of dropping a customer into a queue with nobody expecting them. That risk is why customer service leaders write transfer policy down.
Key takeaways
- A cold transfer routes a caller to another agent or queue without any spoken briefing.
- It’s also called a blind transfer, and it’s the opposite of a warm transfer.
- Cold transfers save time on simple routing but frustrate customers on complex, high-stakes issues.
- Genesys, Five9, Amazon Connect, and RingCentral all label the cold option “blind transfer”.
- Managers watch cold-transfer rate as a proxy for training gaps and routing-rule health.
How it works
A cold transfer moves a live call from one agent to another destination without a spoken handoff. The originating agent presses transfer, dials the target extension or queue, then drops out before the receiving agent answers.
The customer stays on the line and hears ringing or hold music until the new agent picks up. Nothing about the issue travels with them unless a system carries it.
Most contact-center platforms — including Genesys Cloud, Five9, and RingCentral — expose the option as “blind transfer” in the softphone menu. The agent picks blind or consult at the moment of handoff.
Amazon Connect, the cloud contact-center service Amazon Web Services launched in 2017, puts both actions a single tap apart in its agent workspace. That design nudge is why policy, not software, decides how often cold transfers happen.
Here’s how the two compare on the metrics a service manager actually tracks:
| Factor | Cold transfer | Warm transfer |
|---|---|---|
| Time cost per handoff | 5–15 seconds | 30–90 seconds |
| Customer repeats the issue | Yes | No |
| Context carried to receiver | Only what IVR or CRM captured | Spoken briefing |
| Best for | Simple routing, wrong department | Complex issues, VIPs |
| Risk of dropped call | Higher | Lower |
| Agent occupancy hit | Low | Higher |
Zendesk’s 2024 CX Trends report named reducing customer effort a top-three service priority for that year, and few things add effort faster than a botched handoff.
Cold transfers also fail quietly. A caller who lands in the wrong queue for the second time rarely complains; they hang up, then call back an hour later and show up in your volume as fresh demand.
The mechanics matter less than the policy. Well-run operations set rules on when a cold transfer is acceptable, which queues can receive one, and which segments — VIPs, complaint escalations — always get warm.
Two metrics tell you whether your policy works: average handle time on the sending side, and resolution rate on the receiving side. A cold transfer that shortens one while wrecking the other is a false saving.
Examples
Cold transfers show up wherever routing is the whole job and context is cheap to rebuild. The patterns below run from a simple wrong-department bounce to cross-border overflow between an onshore team and an offshore partner.
Wrong-department routing at a US telco. A billing agent takes a call about a broken handset. Billing can’t help, so the agent blind-transfers to the device-support queue in under eight seconds. The customer repeats the issue once.
Insurance overflow to a Manila outsourcing partner. A US property insurer overflows storm-season calls to a Philippines-based business process outsourcing (BPO) partner.
The interactive voice response (IVR) menu captures the policy prefix, then cold-transfers by claim type. In 2024, one such carrier moved roughly 40% of peak-week volume this way with no measurable CSAT dip.
Healthcare appointment scheduling. A hospital front desk cold-transfers scheduling calls straight into a centralized call center queue. Names, dates of birth, and reason-for-call are captured before the transfer, so the receiver has context without a briefing.
Retail returns bounce-back. During the 2025 holiday-returns peak, a large US retailer routed refund-status calls to an automated status line. Callers who still wanted a human were escalated into the live queue afterwards.
Utility outage line during a 2025 cold snap. A regional US energy supplier cold-transferred outage reports from its main line to a dedicated storm desk. Because the reason code traveled with the call, callers never repeated the address.
Related terms
These terms sit closest to cold transfer in a contact-center glossary. Each one either names the wider category, the direct counterpart, or a metric that moves when your transfer policy changes.
- Call Transfer: the umbrella term for any live-call handoff, cold or warm.
- Warm Transfer: the counterpart where the first agent introduces the caller before dropping.
- Call Center: the operational unit where transfer policy is set and measured.
- First Call Resolution: the service metric most directly hurt by excessive transfers.
- Interactive Voice Response (IVR): the automated menu that often triggers a cold transfer to a queue.
- Average Handle Time: the productivity metric that improves when cold transfers are used well.
FAQ
When should you use a cold transfer instead of a warm one?
Use a cold transfer when routing is the whole job: a wrong-department call, a plain IVR handoff, or a queue-to-queue move. Save warm transfers for complex issues and VIP callers. See Dialpad’s warm-transfer explainer for the contrast.
Is a cold transfer the same as a blind transfer?
Yes. Genesys and Five9 label it “blind” in their softphones, while older Cisco and Avaya systems call the same action an “unattended transfer”. Either way, the receiving agent picks up with no prior briefing.
Does a cold transfer hurt customer satisfaction?
It depends on the call type. Simple routing is near-invisible to the customer. Forcing someone to retell a complex story after a blind handoff is one of the most common CSAT complaints logged in contact centers.
What’s a healthy cold-transfer rate in a contact center?
Benchmarks vary by industry, but a healthy operation keeps overall transfer rates under 15% and first call resolution above 70%. If cold transfers climb while FCR falls, the problem is usually training or routing rules.
Can you cold-transfer a call to voicemail?
Yes, and that’s one of the risks. If the destination extension is unavailable, the caller can land in voicemail with no context at all. Route to queues rather than named agents wherever you can.
How do outsourcers handle cold transfers between onshore and offshore teams?
Cross-shore cold transfers work only when the IVR or CRM captures account ID, reason-for-call, and prior-agent notes before the handoff.
Cold transfer is a small mechanic with an outsized effect on service metrics, so browse Outsource Accelerator’s outsourcing hubs for staffing and process guides that put transfer policy in context.
Independent
