Transfer rate

Transfer rate is the percentage of contacts moved from the first agent or queue to another agent, team, or queue before resolution. A warm transfer includes context passed directly between agents; a cold transfer drops the customer into a new queue with no handoff, often forcing them to repeat information. Elevated transfer rates usually signal routing misconfiguration, gaps in skill-based mapping, or missing knowledge access rather than individual agent fault. Each transfer represents an unresolved first contact, so transfer rate moves inversely with first contact resolution and inflates average handle time across the interaction chain. Example: 80 transfers out of 1,000 calls yields an 8% transfer rate.

Transfer rate is the percentage of contacts moved from the first agent or queue to another agent, team, or queue before resolution. A warm transfer includes context passed directly between agents; a cold transfer drops the customer into a new queue with no handoff, often forcing them to repeat information. Elevated transfer rates usually signal routing misconfiguration, gaps in skill-based mapping, or missing knowledge access rather than individual agent fault. Each transfer represents an unresolved first contact, so transfer rate moves inversely with first contact resolution and inflates average handle time across the interaction chain. Example: 80 transfers out of 1,000 calls yields an 8% transfer rate.

Formula

Number of transferred contacts ÷ total contacts handled × 100

Related terms

Routing

Routing is deciding which agent, team, or AI agent receives a contact, based on intent, language, skill, customer tier, and availability. Accurate routing is the cheapest available reduction in handle time, because a misrouted contact pays the cost of being read and reassigned twice.

First contact resolution

First contact resolution is the share of issues fully resolved during a customer’s first interaction, with no follow-up contact about the same problem. It correlates strongly with satisfaction and cost, but only when measured over a defined reopen window rather than at ticket close.

Average handle time

Average handle time is the mean time an agent spends on a single contact, including talk or chat time and after-contact work. Because the definition varies between teams, comparisons are only meaningful when both sides confirm whether wrap-up time is included inside the calculation being reported.

Queue

A queue is the ordered set of contacts waiting to be handled, usually segmented by channel, language, skill, or customer tier. Queue design determines who waits and for how long, making it one of the most consequential and least visible decisions in a support operation.

Escalation rate

Escalation rate is the share of contacts transferred to a higher support tier, a supervisor, or from an AI agent to a human. Reporting should separate planned handoffs, where an AI agent routes a complex or high-risk case by design, from failure escalations, where the agent could not resolve the issue; blending the two obscures true automation performance. Escalation reason codes point to specific knowledge base gaps, and the metric moves inversely with containment and first contact resolution. Example: 120 escalations from 3,000 contacts gives a 4% rate.

Support teams are no longer a cost centre.

See how AI Support Agent, Agent Assist, and VoC Analyst work on your own ticket volume.