What your call transfer rate tells you about your customer experience

You call about a bill you paid last week that still says overdue. You explain it to the first person who answers, get put through to payments and explain it all again, and by the time someone can actually fix it, you've waited twice and told your story twice. That's what an unnecessary transfer feels like from the caller's side, and it makes the problem less likely to be resolved on that call.

Call transfer rate measures how often that happens. It's the share of handled calls passed to another agent, team or department during a single contact, including a dialog agent handing a call to a person. Most teams try to push the number down, but on its own it only tells you how often calls change hands. It doesn't show whether each transfer was the right call, or whether the caller's problem went with them, and some transfers are exactly what the caller needs.

Below, we look at how to work out your rate, how to decide which transfers your business wants to keep, what the unnecessary ones cost you, and how dialog agents resolve more calls end to end, so the transfers that remain are the right ones.

How to calculate call transfer rate

The calculation is simple. Divide the calls transferred in a period by the calls handled in the same period, then multiply by 100.

Call transfer rate = (transferred calls ÷ total number of calls handled) × 100

So if your team handles 2,000 calls in a month and transfers 150 of them, your rate is 7.5%. A call counts as transferred when it moves to another agent, team, department or outside party during the same contact, while callbacks and new contacts count as separate calls.

Some transfers should happen

Some calls belong with a person, and which ones is a decision for your business. A customer reporting fraud on their online banking may need a specialist right away, and many teams send formal complaints the same way. Any caller who asks for a person should reach one.

That's why a low transfer rate isn't always good news. If a person is hard to reach, you can report fewer transfers while customers hang up or call back, and their hang-ups may even be counted as containment. The signs usually show up elsewhere first, in rising abandonment while transfers stay flat, in the same customer calling about the same issue within days, in callers asking for an agent in their first sentence, and in customer satisfaction (CSAT) dropping on calls marked as handled.

Set your own criteria for what warrants a transfer

Whether a transfer rate is good depends on the criteria your business sets for which calls go to a person, so the most useful thing you can do is agree on those criteria as a team and measure your rate against them, call reason by call reason.

Most teams land on some version of these four situations.

• Your policy gives the call to a specialist, such as fraud, disputes or formal complaints.
• The caller asks for a person, at any point in the call.
• Your team wants a person to handle the call, such as a caller in a vulnerable situation. Dialog agents can handle sensitive calls like bereavements well, so this is a choice to make call type by call type.
• The task needs authority the first agent doesn't have, such as a refund above a set limit.

Transfers that meet your criteria are planned, and they don't belong in your reduction target. A 30% transfer rate on fraud calls can be perfectly healthy if your policy sends them to a specialist on purpose, while a 10% rate on password resets points to a gap, because nothing about that call needs a second person. What sits outside your criteria is the part worth reducing.

It's worth checking the planned transfers too, because a right transfer can still be a slow one. Look at how many turns it takes a caller to reach a person on those call types, and what that person sees when they pick up.

What unnecessary transfers cost

For your customer, every unnecessary transfer means a second wait, a story told twice and a lower chance of getting the problem fixed on that call. For your team, it means two people spending time on a call that one could have resolved.

Those minutes add up faster than most teams expect. As a round-number illustration rather than a benchmark, picture 100,000 calls a month with 7.5% transferred. If a third of those 7,500 transfers fall outside your criteria and each adds 3 minutes at $1 a minute, that's $7,500 a month, or $90,000 a year, before you count the repeat calls and the customers who quietly take their business elsewhere.

Where unnecessary transfers start

Go back to the caller who paid last week. They picked billing from the menu because that's where an overdue bill seemed to belong, and the billing agent found the payment had been posted to the wrong account but had no way to move it, so the call went to payments.

Most unnecessary transfers start in the same few places. Menus ask callers to pick a department for a problem they can't name, and keyword routing hears "payment" and ignores the rest of the sentence. Agents often know a policy exists but not how to apply it, or can see the problem but don't have access to the system that fixes it. And routine changes, like an address update, sometimes sit behind rules that reserve them for senior staff, so callers queue for a two-minute task.

To find your own, pull a week of transfer data from your contact center platform, tag each transfer with a reason and look for the three reasons behind most of the unnecessary ones. They're usually the place to start.

How dialog agents resolve calls end to end

Most unnecessary transfers happen because whoever answers can't complete the task. A dialog agent connected to your systems of record can, so far more calls end on the first contact and the transfers that remain are the ones your criteria call for.

Understand the whole request

A dialog agent lets your caller explain the problem in their own words, so "I paid last week but my account still says overdue" is understood as a misposted payment from the first sentence. There's no menu to guess at and no keyword to trip over.

Complete the task in your systems

The agent looks up the account, finds the payment and, where your policy allows, moves it to the right account and confirms it with the caller. The same goes for issuing a refund, moving a booking or updating an address. For tasks better done on a screen, it can text the caller a link to the right page and stay on the line until it's done.

Hand off warm when your criteria say so

When a call meets your criteria for a person, the dialog agent hands it off with the issue, the caller's identity and verification status, and the reason for transfer already on screen, so nobody asks the caller to start again. With PolyAI, the person who picks up sees why the call came to them, what the agent last told the caller and the details it has already collected, and can read the whole conversation so far.

Get better from every transfer

Every handoff is a record of where the agent stopped and why. Wren, the agent inside PolyAI's agentic dialog platform that improves dialog agents, reviews those conversations and drafts tested fixes that a person on your team approves before anything changes for callers.

Brian Jeppesen, Director of Contact Centers at Golden Nugget, approved Wren's recommendations himself and said in PolyAI's Wren launch post, "Over the previous 24 hours, I had a 33% increase in bookings, 10% increase in resolution rate, and 12% increase in conversion."

Metrics to read alongside transfer rate

Transfer rate on its own can fall while nothing improves for your customers, so it's worth reading it alongside a few other numbers.

• First-call resolution (FCR): Shows whether the call ended the issue.
• Repeat contact rate: Catches issues that came back within days.
• Abandonment: Shows who left before anyone helped.
• Handle and hold time: Separates transfers that added minutes from ones that saved them.
• CSAT on transferred and non-transferred calls: Shows your own gap between the two.
• Resolution in the system of record: Confirms the refund posted, the booking changed or the ticket closed.

Transfer the right calls and resolve the rest

Some transfers are exactly what the caller needs, and your own criteria should say which ones. The rest usually happen because whoever answered couldn't complete the task, and a dialog agent connected to your systems can resolve those calls end to end, while handing off the ones that deserve a person with the full story attached. Fix the reason, and the caller who paid last week gets the misposted payment corrected on the first call.

If you'd like to see which of your transfers a dialog agent could resolve on the first call, we can run it against a week of your own calls and show you where the work stops moving.

Call transfer rate FAQs