Agent turnover is the largest hidden cost in most support operations, and the usual explanations are wrong. What the data consistently points at, and what outsourcing does and does not solve.
The cost is bigger than the recruitment invoice
When a support agent leaves, the visible cost is hiring and training a replacement. The larger cost is invisible on any budget line: the weeks of reduced productivity while the new agent gets up to speed, the lower resolution rate during that period, the supervisor time spent coaching instead of managing, the errors that generate repeat contacts, and the pressure the vacancy puts on everyone still there — which is itself a leading cause of the next resignation.
Contact centers have historically run attrition rates far above most other functions, and in high-volume consumer operations rates that would be a crisis elsewhere are treated as normal.
Why agents actually leave
Pay is the reason given in exit interviews and rarely the whole story, because exit interviews reward safe answers. What shows up more reliably in the operational data:
- Sustained high occupancy. The single most predictive number. Agents held above the mid-eighties for weeks have no recovery time between contacts, and burnout follows on a schedule.
- Powerlessness. Taking complaint after complaint with no authority to fix any of them is corrosive in a way that volume alone is not.
- Schedule instability. Shifts that change with little notice make life outside work unplannable, and people leave for jobs that pay the same and are predictable.
- Nowhere to go. If the only progression is into a supervisor role that rarely opens, capable agents leave to progress.
- A bad first thirty days. A large share of attrition happens in the first three months, which points at hiring and onboarding rather than at the job.

What reduces it
Bring occupancy down to a sustainable band and hold it there — this usually requires accepting a slightly lower utilization target, and it pays for itself in tenure. Widen agent authority so that resolving a common problem does not require permission. Publish schedules further ahead and protect them. Build a progression ladder that does not depend on someone leaving: quality, workforce management, training, escalation specialist, subject matter expert.
And fix hiring for the job as it is. Screening for empathy and resilience predicts tenure better than screening for typing speed, and being honest in the interview about what the work involves loses you candidates who would have quit in week six anyway.
What outsourcing does and does not solve
Outsourcing moves the recruitment, training and attrition problem to a provider whose core business is running it — genuinely useful, because they hire continuously, have a bench, and absorb a resignation without your program feeling it. It does not make turnover disappear, and any provider claiming otherwise is describing something other than a contact center.
What matters when you buy is what the provider does about it. Ask for their actual attrition rate on comparable programs, how long an agent stays on your account specifically, what the bench looks like, and how knowledge is retained when someone leaves. A provider that answers those precisely is managing the problem; one that answers vaguely is passing it to you as inconsistent service.
See how agents are trained and developed, or read about distributed staffing models.
Measure it in a way that shows you something
A single annual attrition percentage tells you almost nothing about what to do. The same headline figure can describe two completely different problems with completely different remedies.
Split it at least three ways. Early attrition — people leaving within the first ninety days — points at hiring, onboarding or a job that was described inaccurately, and it is the most expensive kind because none of the training investment was recovered. Tenured attrition points at progression, management or pay relative to the market. Voluntary versus involuntary separates a retention problem from a selection problem; a team with high involuntary exits is hiring wrong, not managing wrong. Then look at where it concentrates: by team, by shift, by queue. Attrition is rarely evenly distributed, and a rate that sits at the organisation level hides the fact that one supervisor or one particularly punishing queue is producing most of it.

The first ninety days decide most of it
Because early attrition is both the most costly and the most fixable, it deserves disproportionate attention. The causes are consistent across operations and mostly sit outside the agent's control.
Recruitment that undersells the difficulty produces people who leave when they meet the real job — a realistic preview reduces early exits even though it reduces the offer-acceptance rate. Training that ends at go-live rather than tapering leaves new agents alone at the point they are least equipped. No nesting period, or one where supervision is nominal, means the first difficult call is faced unsupported. Scheduling that gives new hires the worst shifts as a matter of seniority guarantees a hard first month. And a first performance conversation framed around metrics the agent has not yet been enabled to hit converts anxiety into resignation. Each of these is a design choice, not an inevitability.
What retention actually costs, and what it saves
Retention interventions are usually assessed against their direct cost and rarely against what the departures cost, which makes them look expensive. The full cost of a leaver includes recruitment and onboarding, training time for both the new hire and whoever supports them, the productivity gap during ramp, the supervisor time consumed, the licence and equipment churn, and the quality effect on customers handled by someone still learning. On most operations that total is a substantial multiple of a monthly salary.
Set against that, the interventions that reliably move it are unglamorous: schedule predictability and some element of choice, which consistently rates above small pay differences; supervisor span narrow enough that coaching actually happens; a visible progression path even where the steps are small; and mixing difficult queues with recovery work rather than concentrating the hardest contacts on the same people. If you are outsourcing, ask providers for attrition on comparable programs with a stated definition — and treat a refusal to define it as the answer.
Frequently asked questions
What attrition rate should we expect from a provider?
Ask for the rate on comparable programs rather than the company-wide figure, which blends easy accounts with hard ones and is close to meaningless. More useful than the headline is average tenure on your account specifically, and the ninety-day figure, since early attrition points at hiring and onboarding rather than at the work. A provider that tracks these and shares them is managing the problem; one that offers a single flattering number probably is not.
Is offshore attrition worse?
It varies far more by market, employer and program than by the offshore-versus-onshore distinction, and treating geography as the explanation usually hides the real cause. Mature delivery markets have well-established contact center career paths and can show strong tenure; some onshore operations churn badly. The questions that matter are the same everywhere: what is occupancy, what authority do agents have, how stable are schedules, and what does progression look like.
Does work from home help or hurt?
Both, and which one dominates depends almost entirely on how it is run. Remote work removes commuting and widens the hiring pool, which helps tenure. It also weakens the informal support that gets a struggling agent through a bad week, and isolation shows up in attrition within months. Programs that succeed replace what the floor used to provide deliberately — structured check-ins, live coaching, real team contact — rather than assuming it will happen.
How do we keep knowledge when agents leave?
Assume they will leave and design for it, rather than relying on tenure. Knowledge that lives in an agent's head walks out with them; knowledge in a maintained, searchable base that agents actually use during live calls does not. The test is whether a new agent can find the answer to a common question in under a minute without asking a colleague. If the answer is no, your knowledge base is documentation rather than a working tool, and every resignation costs more than it should.
Running the operation
Keep reading
The rest of this cluster, for the question you are actually working through.
- First Call Resolution: The Metric Most Contact Centers Measure Wrong
- CSAT, NPS, CES and the Metrics Worth Putting on a Dashboard
- How to Reduce Call Abandonment Without Just Adding Agents
- Seasonal Support Staffing: Covering a Peak Without Carrying It All Year
- Writing a Call Center SLA That Means Something
- PCI Compliance in a Call Center: Where Card Data Actually Leaks

