The transfer rate nobody watches

The customer has now explained the problem three times. Once to the bot, once to the frontline rep who said "let me get you to the right team," and once to the specialist who opened with "so, what seems to be the issue?" When it finally resolves, the ticket is a triumph by every number on the wall. CSAT fired before the handoffs even started. First-contact resolution credits the specialist's clean close. Average handle time looks healthy, because the work got split across three short conversations instead of one honest long one. The single metric that watched what actually happened — a customer relayed between departments like a parcel — isn't on the dashboard at all.

That metric is transfer rate, sometimes called handoff rate: the share of contacts passed from the first agent to another person, team, or queue before they're resolved. Most contact-center guidance puts the target in single digits.

Above that, the standard read is that routing is broken or the frontline isn't equipped to finish what it starts. It's an easy number to compute, and almost nobody watches it — which is exactly why it repays attention. The mechanics are simple; the interesting part is what a high one hides.

Start with resolution. A transfer is a first-contact failure wearing a more forgivable label — the same event that FCR is meant to catch, seen from the other end. SQM's benchmark data makes the cost concrete: when a call needs a second person to resolve it, the resolution rate drops.

Yet on most dashboards the handoff stays invisible while the eventual close gets celebrated. Chase FCR without watching transfers and you learn nothing about the tickets that quietly took two people and three queues — the ones most likely to be gamed into looking resolved.

The second thing a high transfer rate hides is how the routing feels from the customer's chair. Every handoff asks them to start over. Salesforce's State of the Connected Customer puts hard numbers on the friction. More than half of customers still repeat themselves to different reps:

and more than half feel they're dealing with separate departments rather than one company:

That is the transfer rate, described in the customer's own words. Effort is the part that predicts churn, and the CEB research behind The Effortless Experience is blunt about it:

A transfer is effort you administered on purpose.

This is what makes transfer rate diagnostic rather than decorative. A cost metric tells you the price of the work; a quality signal tells you where the work is going wrong. A rising transfer rate always points somewhere specific — an IVR that mis-routes, a tier-one team scoped too narrowly, a knowledge base that sends reps hunting for a colleague instead of an answer, an org chart with one wall too many. Break it out by reason code and it becomes a map of your routing's weak seams. Teams that trade rigid tiers for swarming often watch it fall, because the model is built to finish the ticket where it lands rather than relay it onward. And the handoff itself, done badly, is where context goes to die.

Leave it off the dashboard and the bill still arrives, just somewhere you aren't looking. The bounced-around customer is precisely the one who leaves:

A three-transfer ticket that finally resolves isn't a save — it's a near-miss you got away with.

Watching it well takes three habits. Count transfers per resolved issue, not per call, so one problem bounced four times reads as a single bad journey rather than four routine handoffs. Separate warm handoffs — where the context travels with the customer — from cold, blind transfers that drop them into a fresh queue to explain themselves again; only the second kind is pure waste. And never let a transfer vanish inside a downstream agent's spotless FCR: measure resolution across the whole journey, not its last leg.

Then put the number on the wall, next to CSAT and FCR. It won't flatter anyone, which is the point. It's the one metric that counts the tickets your other metrics were allowed to forget.