Transfer rate

What it is

Transfer rate is the complement of containment in most reporting, though the two rarely add up to 100 percent once abandoned and dropped calls are counted honestly. A transfer happens when the agent decides, or the caller demands, that a person should take over. It can be a warm transfer with context passed along, a cold transfer into a queue, or a scheduled callback.

Transfers are not all bad. A collections agent that transfers a caller disputing a debt, or a dental agent that transfers a bleeding patient, is doing its job. A transfer because the agent could not understand an accent, or looped three times on the same question, is a failure dressed as a handoff.

Why it matters when buying

Without a reason code on every transfer, the number is meaningless. With one, it becomes the primary tuning signal: the top three reasons each week tell you what to fix, whether that is a knowledge-base gap, a speech-recognition problem in one language, or an intent the agent should never have been given. It also exposes a common pattern: agents that transfer aggressively look great on customer-satisfaction and terrible on cost.

What to ask

Ask how transfers are tagged (agent-decided, caller-requested, policy-required, failure) and whether you can add your own reasons. Ask what the receiving person sees: transcript, summary, collected data, or nothing. Ask for transfer rate by intent and by language. In the demo, ask for a person directly and watch whether the agent complies at once or argues.