Cold transfer
In one sentence
A cold transfer, also called a blind transfer, passes a call to another destination with no context and no briefing, forcing the caller to re-establish their identity, problem and history; it is the default behavior whenever context passing is not deliberately built.
Not to be confused with Warm transfer.
Definition
A cold transfer hands a call to another destination with no context and no briefing, so the person who picks up starts from nothing.
It is also called a blind transfer, and it is what happens by default when nothing better has been built.
Cold transfer earns its own entry because it is the failure mode against which warm transfer is defined, and because it is what a deployment gets when context passing is left unspecified. Nobody sets out to build it; it is the shape the system takes when the clause requiring context is simply absent.
What makes a transfer cold
- No context accompanies the caller.
- The receiving party has no advance notice of the situation.
- The caller has to re-establish their identity, their problem and their history.
Where cold transfer is legitimate
- Simple redirection where no context exists to pass, such as a wrong-number correction.
- High-volume, low-complexity routing where the receiving party will gather everything anyway.
- Situations where privacy considerations restrict what may be shared with the receiving party, which is a real constraint in some regulated contexts.
Why it is disproportionately damaging after an AI interaction
- A caller who has explained their situation to an automated system has invested effort in the expectation of progress.
- Being asked to start again converts that investment into a loss.
- The reaction is not merely irritation at the transfer. It is a conclusion about whether the automation was worth engaging with at all.
The silent version, which is worse
- A transfer that happens with no explanation, so the caller does not know what happened or who they are now speaking to.
- It produces confusion on both sides and is a common consequence of poorly configured routing.
How it happens by default
- Context passing takes deliberate implementation. A transfer does not.
- A specification that requires escalation without requiring context passing will produce cold transfer, and it will do so without anyone deciding to.
- This is why the RFP clause matters more than the feature list.
Common misconception
That cold transfer is a legacy problem solved by modern platforms. It is the default behavior whenever context passing is not explicitly built, which makes it a current problem in many recent deployments.
Why it matters commercially
A cold transfer after an AI interaction produces a specific customer conclusion, that the automation wasted their time, and that verdict lands on the whole deployment rather than the single conversation. That is why context passing belongs in the requirements as an explicit clause, not on a feature list where its absence goes unnoticed until customer feedback surfaces it.
In voice specifically
The silent transfer has real force in voice and almost none in text. On a chat thread the customer can see the conversation move and read who they are now talking to. On a call a transfer with no spoken explanation drops the caller into a new voice with no idea what happened or why, so the handoff has to announce itself out loud or it disorients both sides.
Where AsqVox fits
On a website, the cold transfer equivalent is a lead captured with no conversation attached, so whoever follows up starts from nothing. Attaching the transcript and the sentiment is what prevents it, turning what would be a cold handoff into a warm one without a human ever waiting on a line.
Visual
The default that nobody chose
Transfer happens by default. Context passing has to be built.
Statistics
Every figure carries its source and year. Vendor numbers are labelled as vendor numbers, and where no reliable figure exists this page says so rather than borrowing one.
Containment of 70 to 80 percent in mature deployments means 20 to 30 percent of conversations transfer, and every one of those is warm or cold depending on whether context passing was built.
20 to 30% transferindustry rangeIndustry-reported containment ranges, 2026 - A reported range rather than an audited figure. The share that transfers is not the interesting number; whether those transfers carry context is, and that is a design decision, not a property of the platform.
A human-handled call costs roughly USD 7 to USD 12 against roughly USD 0.40 for an agent-handled call, and a cold transfer means the automated attempt cost was spent without reducing the human handling time.
USD 7 to 12 vs USD 0.40industry rangeWidely cited industry cost range, 2026 - A quoted range, not a metered figure. A cold transfer is the worst of both: the automated cost is paid, and then the full human cost is paid anyway because the human starts from nothing.
There is no published measurement of the customer satisfaction cost of a cold transfer, nor of the proportion of AI-to-human transfers that actually pass context.
-no reliable figureBoth are measurable inside a deployment and unmeasured in public. Any industry-wide satisfaction-cost or context-passing rate offered without a named sample is invented.
There is no published benchmark for repeat-explanation rates after an automated escalation.
-no reliable figureThe repeat-explanation problem is the mechanism everyone describes and nobody has quantified across deployments. Measure it on your own escalations rather than citing a figure that does not exist.
Examples
In practice
A deployment specification requires escalation to a human within a defined number of failed attempts. It does not specify context passing. The implementation satisfies the requirement completely and produces cold transfers throughout. The gap surfaces in customer feedback rather than in acceptance testing, because the acceptance criteria never mentioned context, and by then the deployment has already taught its callers that the automation wastes their time.
The everyday version
A cold transfer is being put through to someone who has no idea who you are or what you want. It is what happens automatically unless someone specifically builds the bit that passes the information along. After a customer has already explained everything to a machine, it is the single most annoying thing you can do to them.
Usage
Who says it
- Contact center practitioners, usually critically.
- Also called blind transfer, particularly in traditional telephony contexts.
Where it turns up
- In an RFP it usually appears by its absence: the requirements specify escalation and omit context passing.
- A well-drafted RFP requires warm transfer explicitly and defines the contents of the context package.
Common misuse
- Assuming modern platforms prevent it, when it is the default whenever the context clause is missing.
- Specifying escalation without specifying context.
- Treating it as acceptable after an automated interaction, which is exactly where its cost is highest.
Questions people ask
What is a cold transfer?
A cold transfer, also called a blind transfer, passes a call to another destination with no context and no briefing. The receiving party has no advance notice, and the caller has to re-establish their identity, their problem and their history from scratch. It is the default behavior whenever context passing has not been deliberately built.
Is a cold transfer ever the right choice?
Yes, in three cases. Simple redirection where no context exists to pass, such as a wrong-number correction. High-volume, low-complexity routing where the receiving party gathers everything anyway. And situations where privacy rules restrict what may be shared with the receiving party, which is a genuine constraint in some regulated contexts. Everywhere else it converts the caller's effort into a loss.
Why is a cold transfer worse after talking to an AI agent?
The caller has already invested effort explaining their situation to a machine, in the expectation of progress. Being asked to start again turns that investment into a loss, and the reaction is not just irritation at the transfer but a conclusion that the automation was not worth engaging with. That verdict then generalizes to the whole deployment, not just the one call.
How do cold transfers happen if nobody wants them?
By omission. Context passing takes deliberate implementation; a transfer does not. A specification that requires escalation without also requiring context passing will produce cold transfers, and it will do so without anyone deciding to. That is why the RFP clause matters more than the feature list, and why cold transfer is a current problem in recent deployments, not a legacy one.
Last reviewed 4 August 2026. Written and reviewed by Dhruv Dholakia, founder of AsqVox.