Call transfer quality: is the agent transferring well?

Short answer

Transfer quality is checked with four questions: was the transfer needed, was the customer told why and to whom, was the information passed to the next person, and did the customer have to tell their story again? The last one is broken most often — "I've already explained this three times" is one of the most expensive sentences in a contact center.

A transfer is not the end of the agent's job; it is the middle of the customer's journey. A team that does not score it as its own criterion tries to cut the number of transfers but never sees the number of bad ones.

Why transfers are a quality problem

For the customer, a transfer creates two risky moments: waiting and re-explaining. Both lengthen the call, drain patience and lower the chance of a resolution. For the agent, a transfer is sometimes the easiest way out of a complicated issue — especially when call length is watched closely.

• Unnecessary transfer: the agent could have solved it but did not
• Wrong destination: the customer lands in the wrong team and is transferred again
• Unexplained cold transfer: the customer ends up in another queue knowing nothing
• Transfer without context: the next person knows nothing and asks everything again
• Dropped transfer: the line cuts and the customer has to call back

Warm and cold transfers

1. 1Cold transferThe agent routes the customer to another line or queue and does not join. Fast, but the customer re-tells everything — unless the information was passed in the system.
2. 2Warm transferThe agent first speaks to the next person, explains the situation, then connects the customer. Takes longer, but the customer does not repeat themselves.
3. 3Noted transferBefore transferring, the agent writes a short note in the system: who, what they want, what was done, what remains. It combines a cold transfer's speed with a warm one's context.

Which type is right depends on the issue's complexity and the company's rule. What matters for evaluation is that the chosen type was done according to the rule.

Illustrative example: a transfer form

The form below is an illustrative example. It applies only to calls with a transfer; on a call without one, every line is "not applicable" and does not affect the score.

1. 11. The transfer was justifiedYes: the issue was outside the agent's authority or knowledge and this matches the company's escalation rule. No: the answer was in the knowledge base the agent could reach.
2. 22. The customer was told whyYes: an explanation such as "this is for the technical team — they can check your line" was given.
3. 33. The customer was told where and what to expectYes: the team's name and an expected wait or callback time were stated.
4. 44. Context was passed onYes: in a warm transfer the next person got a spoken summary, or a note was written in the system. This cannot be fully checked from the first leg alone — the note system or the second leg is needed.
5. 55. The customer agreedYes: "Shall I connect you to the technical team?" was asked, or the customer asked for it.

Illustrative transfer note template

Context is lost most often because there is no written note. The template below is an illustrative example; adapt the fields to your system. The goal is for the receiving agent's first words to be "I can see the issue with your order, I'm checking it" rather than "how can I help?"

1. 1CustomerName, contact number and customer ID — and "identity verified" if it was.
2. 2What they wantOne sentence, close to the customer's own words: "Order 3 days late, wants a refund, does not accept a new date."
3. 3What was doneWhat the agent already checked or did: "Courier status checked — waiting at the warehouse."
4. 4What remainsThe decision or action expected from the receiving side: "Refund approval."
5. 5What the customer was toldThe promised timeframe or next step — the receiving side must not contradict it.

When these five fields are filled in, the customer does not re-tell the problem even without a warm transfer.

Evaluate the receiving side too

Transfer quality does not depend only on who transfers. The receiving agent has criteria of their own, and these should be checked separately:

• The receiving agent introduced themselves and showed they knew why the call was transferred
• They did not ask again for information already given — name, order number, problem — or explained why when they did
• If the issue had to be transferred again, this time it went to the right place
• At the end of the call the resolution or next step was clear

To avoid mixing two agents' criteria in one call, each side is evaluated on their own part of the call.

Without a transfer rule, evaluation is a dispute

The first criterion — "the transfer was justified" — can only be checked fairly when there is a written rule. It usually covers:

• Which topics the first line resolves and which must be transferred
• When a warm transfer is mandatory — for example a complaint, a VIP customer, a second transfer
• Which fields the transfer note must contain
• What happens if the next line is busy: callback, message, waiting in queue

Analysing transfers at team level

1. 1Most-transferred topicWhich topic is transferred most? If most transfers cluster on one topic, the first line's training or knowledge base on it is weak.
2. 2Repeat transfersIf the same customer is transferred twice in one call, the escalation map has an error.
3. 3Differences between agentsIf one agent's transfer share on the same call type is far above the others', review their calls — but a comparison that ignores call type and shift is unfair.
4. 4Outcome after transferAre transferred calls resolved, or does the customer call back? That comes from telephony and the ticketing system.

Typical mistakes

• Saying "one moment" and sending the customer to another queue without explanation
• Telling the customer "they'll call you" without knowing who or when
• Writing only "customer is unhappy" in the transfer note — nothing about what
• Setting a target to cut transfers, so agents try to answer questions they do not know
• The receiving side saying "that's not my job" and transferring again

Limits

• The two legs of a transferred call are often separate recordings; joining them needs telephony data
• A transcript does not prove that a transfer note was written in the system
• In a three-party conversation — a warm transfer — separating speakers gets harder; AWS's generative evaluation guidance also notes that such calls reduce accuracy
• Whether a transfer was justified cannot be judged without a written escalation rule
• Transfer count is not the sole measure of an agent's quality

What Vexvon Audio Analyzer offers

Vexvon Audio Analyzer analyses each uploaded recording separately; it does not join the two legs of a transferred call automatically and does not read transfer events from telephony. What it works on is the content of the call:

• You write the transfer criteria above into your call standard
• On every call each criterion is judged as met, partial, missed or not applicable — on a call with no transfer, these criteria do not count against the agent
• Next to each judgement, what the agent said to the customer is shown as transcript lines
• The call's short summary is useful context for the receiving agent too

More: Vexvon Audio Analyzer. How to measure whether the problem was solved after a transfer is covered in first call resolution measurement; handing a call from an AI agent to a live agent is covered in AI-to-human call handoff.

First step

Pick 10 transferred calls from last week in your telephony. Check the five criteria above for each, and note what the customer had to repeat on the receiving side. The information repeated most is the first field your transfer note needs. This article belongs to the support quality and coaching section. To try it on your own recordings, get in touch.

Further reading on this topic: de-escalation call quality, call recording analytics integration.