Transfer Rate

In depth

Transfer rate is the share of support interactions that get passed from the first agent to someone else, another agent or another team, before the case is resolved. That hand-off can go sideways, to a peer better placed to help, or upwards, to a more senior tier. It is expressed as a percentage: transferred interactions divided by total interactions, multiplied by 100.

The calculation is straightforward. If your team handles 4,000 interactions in a month and 520 of them are transferred before resolution, divide 520 by 4,000 and multiply by 100. The transfer rate is 13%. Teams usually track it by topic and by channel, because a cluster of transfers around one topic almost always points to a specific routing rule that is sending those contacts to the wrong place first.

The reason transfer rate earns its own metric is the customer experience behind it. Every transfer risks the customer having to repeat their problem to a new person, wait in a new queue, and lose the thread of the conversation. It is consistently one of the most cited sources of support frustration, which is why teams watch it closely even when overall resolution looks healthy.

What counts as a transfer?

A transfer is any hand-off of a live case to a different agent or team. That deliberately includes lateral moves, one agent passing a chat to a colleague with the right knowledge, not just moves up a tier. This is the key distinction from its nearest sibling: escalation rate counts only the interactions that go up to a higher tier or specialist, so every escalation is a transfer, but not every transfer is an escalation.

Decide upfront how you treat the edge cases and keep the rule stable. Does an automated re-route by a routing system count as a transfer, or only an agent-initiated one? Does a warm hand-off, where the first agent stays on while introducing the next, count the same as a cold one? The answers are yours to set, so long as they stay consistent enough to compare over time.

Most transfers trace back to how contacts are routed in the first place. When ticket routing and omnichannel routing send a contact to the right team from the start, there is simply less need to move it later.

What's a good transfer rate?

There is no single benchmark that fits every team. What counts as healthy depends on how your teams are structured, how specialised your support is, and how well contacts are routed on arrival. A team with clean, accurate routing and broadly skilled front-line agents will transfer far less than one where contacts routinely land in the wrong queue.

A lower rate is generally the goal, because it means more customers reach the right person the first time, which ties closely to first contact resolution. As always, the most useful comparison is your own trend over time, read alongside satisfaction, rather than a headline figure borrowed from a different kind of business.

The most direct improvements are in routing and in context. Better routing gets contacts to the right place first, cutting the need to transfer at all. And when a hand-off genuinely is needed, carrying the full conversation with it means the customer does not start over, which prevents the repeat transfers and mis-routes that inflate the rate. Resolving the routine questions before they reach a person at all removes another whole layer of contacts that might otherwise have been transferred.