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

In a cold transfer the call is passed on without any information and the caller has to explain everything again. In a warm transfer the person taking over receives the call with its context: who is calling, what they want, what has been discussed and which details have been collected. When an AI hands over to a person, that context travels in the agent’s call summary and the collected fields.

When should an AI voice agent hand a call to a person?

In four situations: when the caller explicitly asks for a person or signals an intent such as a complaint or cancellation, when the caller is clearly upset or mentions an emergency, when the topic falls outside what the agent is allowed to handle, and when the agent repeatedly fails to understand the same detail. Write these conditions into the agent’s instructions from the start and test them with test calls.

What happens to a handed-over call if no operator is available?

You need to design this in advance. The call can wait in the queue, in which case the caller should hear something about the expected wait. If the wait runs long, creating a callback record or taking a voicemail is better than dropping the call. After hours, the agent logs the request and summary and adds it to the team’s callback list for the next day.

Is a high handover rate a bad sign?

Not on its own. Look at why calls are handed over: if the caller really needs a person, handing over is the right decision. The problem is an agent that hands over routine tasks it could resolve, or hands over too late on tasks it cannot. Read the handover rate together with handover reasons, the resolution rate after handover and whether operators ask the same questions again.

Blog

Warm Transfer from AI to Human Agents: When and How

When and how should an AI voice agent hand a call to a person? Handover triggers, a sample handover summary, the queue side, what to measure and pitfalls.

By SpeaklinePublished October 22, 202610 min read

A warm transfer from AI to a human agent is when a voice agent hands a call to an operator together with the details it has collected and a short summary of the conversation. The caller does not have to start over, and the operator gets to the point from the first sentence. A good handover rests on three questions: when to hand over, how to hand over and with what information.

In this article we cover handover triggers, the difference between warm and cold transfers, what to say at the moment of handover, a sample handover summary, the queue and operator desk side, how to measure handovers and the most common mistakes.

Why is handover a voice agent’s most important skill?

An AI voice agent succeeds not by resolving every call itself but by passing on the calls it cannot resolve at the right moment and with the right information. From the caller’s point of view, a bad experience comes in two forms: the agent keeps trying to help with something that needs a person, or it hands over and the operator asks everything again. Both are fixed by design.

When to hand over: four triggers

1. Explicit requests and intents

When a caller says “I’d like to speak to someone”, the agent should not push back; it should confirm briefly and hand over. Some intents can also be routed to a person from the start: complaints, cancellations, price negotiations or contract changes.

2. Emotion and tone

When the caller is clearly angry or upset, or repeats the same thing in a rising tone, it is time to hand over. Phrases that signal an emergency need a separate rule: a clinic assistant, for example, tells the caller to dial 112, Turkey’s emergency number, without delay and transfers the call to the team if needed.

3. Outside the agent’s remit

Billing disputes, actions that need identity verification, medical or legal questions and topics with no answer in the knowledge base are not the agent’s job. The agent should not guess; it should say so plainly and hand over.

4. Repetition and getting stuck

If the agent has failed to understand the same detail twice, it should hand over rather than ask a third time. Background noise, long silences or a conversation going round in circles are also handover signals.

You can carry these triggers into the agent’s instructions as a table:

Trigger	Example phrase or signal	Target queue	Priority
Request for a person	“I’d like to speak to someone”	General queue	Normal
Complaint	“I called last week too and nobody got back to me”	Customer relations	High
Billing dispute	“I don’t accept this charge”	Billing	Normal
Emergency	An urgent health or safety phrase	112 referral and the relevant team	Highest
Out-of-scope question	No answer in the knowledge base	Specialist queue for the topic	Normal
Understanding problem	The same detail misunderstood twice	General queue	Normal

Sample handover rules by sector

Alongside the general triggers, every sector has its own handover moments:

Sector	When the agent should hand over	Taken over by
Clinic	Questions about medication, symptoms or test results	Clinical team or reception
Restaurant	Large groups, private events, allergy details	Restaurant manager
Car service center	Invoice disputes, warranty coverage, damage	Service advisor
Real estate	Price negotiation, offers, contract questions	Real estate agent

How to hand over: warm and cold transfers

The difference between a warm transfer and a cold one is whether the context travels with the call. In a cold transfer the call is simply passed on and the caller starts over. In a warm transfer the person taking over knows what the call is about and what has been done so far. Between people, this is done by the operator briefly speaking to the colleague first; when an AI hands over to a person, the context travels in writing.

A good handover follows these steps:

The agent says it is handing over. A short, clear sentence with the reason, such as “I’ll pass you to a colleague on our team for this.”
It confirms one last detail if needed. If the person taking over will need one missing item, such as a callback number or appointment date, it asks for it.
It prepares the summary. The conversation summary and collected fields are sent with the call.
It routes the call to the right queue. The handover reason decides which queue the call goes to.
It keeps the caller informed while they wait. The caller knows they are waiting in a queue; if the wait runs long, a callback is offered.
The operator opens with the summary. A line such as “I can see you’d like to move your appointment to Friday” tells the caller they were heard and confirms the detail.

What should be said at handover?

The handover line should be short, give the reason and tell the caller what happens next. Sample lines you can add to the agent’s instructions (in practice they would be in Turkish; the Turkish edition of this article has the Turkish wording):

Request for a person:  "Of course, I'll put you through to a colleague on our team now.
                        I'm passing on what we've discussed, so you won't need to start over."
Complaint:             "I'm sorry about the trouble. It's better for a colleague in charge
                        to handle this, so I'm transferring you now."
Out of scope:          "I don't have the information to answer that properly. Let me
                        pass you to a colleague who knows this topic."
Waiting:               "All my colleagues are on calls right now. You can keep holding,
                        or I can arrange for them to call you back when they're free."
After hours:           "Our team is outside business hours right now. I've logged your
                        request with my notes, and they'll call you first thing tomorrow."

Adapt the lines to your business’s tone, but do not have the agent promise anything you cannot guarantee, such as an exact callback time.

With what information? A sample handover summary

The call summary is the heart of the handover. Here is a sample summary from a fictional call to a car service center:

Handover reason: Caller disputes an item on a service invoice and asked for someone in charge.
Caller: Ayşe Y., existing customer, 0532 xxx xx 47
Topic: Service invoice dated 14 October
Details collected:
  - Number plate: 34 ABC 123
  - Disputed item: "A/C gas refill"; caller says she did not ask for it
  - Preference: resolve by phone, then written confirmation by e-mail
What the agent did: Read out the invoice items and shared the work note; caller was not satisfied.
Tone: Tense; said "nobody is listening to me" twice.
Suggested next step: Service advisor to check the work order and call the customer back.
Record: Call recording and transcript on the call card.

What makes a good handover summary:

Short and action-oriented. The operator should be able to read it in seconds and know what to do.
Says what the agent did and could not do. The operator does not repeat the same step.
Keeps the caller’s own words. Especially with complaints, the caller’s wording conveys the tone accurately.
Flags assumptions. If the agent is not sure about a detail, it marks it as “not confirmed”.
Holds no more personal data than needed. A summary is personal data too; leave out details that do not help. For recording and retention rules, see our guide to KVKK for AI phone assistants.

The queue and operator desk side

The handover does not end when the agent’s part is done; the call still has to reach the right operator at the right speed.

Queue by reason: Topics such as billing, technical support and bookings should go to separate call queues; the ACD distributes the call to an available operator in that queue.
Priority: Handovers such as complaints and emergencies can be moved up the queue.
The operator’s screen: When the operator picks up, the summary, collected fields and, if needed, the transcript should be on the same screen. An operator who has to look for the summary in another system turns a warm transfer into a cold one.
No operator available: Set a maximum wait time. When it is exceeded, create a callback record or take a voicemail. After hours, the agent adds the request and summary to the next day’s callback list.
Supervisor: Live monitoring of queues and ongoing calls helps spot stuck handovers early.

Measurement: is the handover working?

Metric	How to calculate it	What it shows
Handover rate	Calls handed over ÷ calls answered by the agent	How wide the agent’s scope is
Handover reasons	Share of handovers by reason	Which topics could be added to the agent, or should go to a person from the start
Unnecessary handover rate	Calls the agent could have resolved but handed over ÷ all handovers	Gaps in instructions and the knowledge base
Wait time at handover	Time between the handover and the operator picking up	Queue and staffing plan
Abandonment at handover	Calls dropped before reaching an operator after handover ÷ handovers	The waiting experience
Resolution after handover	Handovers resolved by the operator ÷ handovers	Whether calls reach the right queue
Re-ask rate	Calls where the operator asked again for information in the summary ÷ sampled handovers	Summary quality

The last metric may not be measurable automatically; track it by reading a few handover transcripts each week. Set targets against your own baseline, not someone else’s average.

Testing your handover rules

Handover is the flow to test most before going live. Add these scenarios to your test calls:

The caller says “I’d like to speak to someone” in the first sentence.
The caller starts calm and gets increasingly annoyed.
A question with no answer in the knowledge base.
A call from a noisy place where the same detail is misunderstood twice.
A moment when every operator is busy, and an after-hours call.
A check that the summary and collected fields really appear on the operator’s screen after handover.

For a detailed test list, see our checklist for testing a Turkish AI phone assistant.

Common mistakes

Making handover hard: Trying to talk a caller out of “I want to speak to a person” destroys trust quickly.
Handing over too late: By the time the agent has asked the same question four times, the caller is already frustrated.
Handing over without context: The summary is written but never reaches the operator’s screen.
One queue for everything: If every handover lands in the same queue, calls that need a specialist reach the wrong operator.
Forgetting after hours: A handover with no operators on duty leaves the caller waiting in an empty queue.
Long summaries: A summary the operator cannot read in time is not a summary.
Not measuring: Widening or narrowing the agent’s scope without looking at handover reasons is guesswork.

Warm transfer in Speakline

In Speakline you define the handover conditions; when one is met, our Turkish-speaking voice agent passes the call to the relevant queue together with a call summary. Operators pick up the call, together with the summary the agent prepared, from a browser-based operator desk. On the call center side, queues, live monitoring and reports work together; calls can be recorded and stored with their transcripts, and voicemail can be taken when no operator is available.

You can send call outcomes and summaries to your CRM through our API and webhooks. To see how an IVR and a voice agent can share one flow, read our IVR vs AI voice agent comparison; if you would like to design your handover rules together, get in touch.