Cold Transfer

A cold transfer (also called a blind transfer) is a call handoff where the caller is routed to a new destination with no context passed along — the receiving party knows nothing about who is calling or why until they pick up and hear it for themselves. It is the default behaviour of every traditional phone system and it gets a bad reputation it does not fully deserve.

How a cold transfer actually works

In SIP, a cold transfer is a single REFER message. The current leg sends REFERwith the destination’s address, the caller’s user agent follows the referral by dialing the new destination, and the original leg is dropped. No audio briefing, no data payload, no hold music between the old and new parties. When the new destination answers, they get a ringing call with the caller ID of the original caller (or sometimes the transferring party, depending on how the trunk is configured).

The simplicity of this mechanism is the reason cold transfers are so universally supported. Every PBX, every softphone, every carrier SIP trunk in the world supports blind transfer. Warm transfers require additional infrastructure — a dashboard to receive context, a data path separate from the audio path, a convention for what gets sent — and each of those is a place where things can break.

When a cold transfer is actually the right choice

The conventional wisdom is that cold transfers are always bad and warm transfers are always good. This is wrong. There are several situations where cold is not just acceptable but preferable:

• Transferring to a general queue. If the destination is a shared sales or support line where any available agent will pick up, there is no one-specific-person to brief. Adding context to a cold transfer in this case is wasted effort because the receiving queue will route to whoever is free.
• Transferring to an automated system. If the destination is voicemail, an IVR menu, or another AI, a warm-transfer briefing is pointless. Cold is correct.
• Emergency routing. If the caller needs to be connected to 911, a poison control center, or a crisis line, speed matters more than context. Cold transfer. Every second of briefing is a second the caller is not being helped.
• High-volume intake where context repeats.If every caller in a queue is asking the same question (“what time do you open?”), the receiving agent already knows the context. The briefing would add no value.

The warm-versus-cold question is really about whether context is expensive or cheap to carry across the handoff. When context is cheap or absent, cold is fine. When context is expensive (the caller spent two minutes explaining a complicated problem), going cold throws away work.

When cold becomes a problem

The failure mode that gives cold transfers their bad name is specific: a caller has already explained something lengthy to the first agent, the first agent initiates a cold transfer, and the second agent picks up saying “how can I help you?”. The caller now either repeats everything (annoyed) or hangs up (worse).

This happens constantly in legacy contact centers because the agent’s tools make cold transfer the one-click default and warm transfer a multi-step workflow. It is not that cold is inherently bad, it is that the tooling defaults to cold even in cases where warm would be trivial.

Cold transfers from an AI phone agent

AI phone agents have a distinct advantage here: generating a summary is free. The AI already has perfect memory of the conversation, so the marginal cost of producing a one-sentence briefing for the receiving agent is zero. This means the decision tree for AI transfers should lean warm almost always, reserving cold for the specific cases listed above.

The one caveat is latency. A warm-transfer pattern that waits for the context to be acknowledged by the receiving dashboard before initiating the SIP transfer will add seconds of silence to the call. For AI systems the best pattern is fire and forget: send the context asynchronously, initiate the cold-transfer SIP REFER immediately, and let the receiving dashboard display the context when it arrives (usually before the new agent picks up). The caller experiences what looks like a warm transfer, but mechanically it is a cold transfer with a side-channel data push.

Cold transfers in BubblyPhone Agents

BubblyPhone Agents exposes transfers through a single endpoint that performs a SIP REFER to the destination number. Whether the transfer is “warm” or “cold” is determined by whether your AI agent also sends context to your backend before initiating the transfer. See the full comparison and implementation patterns in the blog guide on warm transfer vs cold transfer for AI agents, and the glossary entry on warm transfer for the alternative.

Further reading

• IETF RFC 5589, Session Initiation Protocol Call Control — Transfer — the protocol-level definition of SIP blind and attended transfer.