contact center · 9 min read
Call Center Shrinkage
Call center shrinkage is the percentage of paid time agents are not available to take calls. See the formula, typical benchmarks, categories, and how to reduce it.
Call center shrinkage is the single most common reason staffing plans fail. A manager runs an Erlang C calculation, schedules exactly that many agents, and still misses service level — because the Erlang number assumes everyone scheduled is on the phones, and shrinkage guarantees they are not. Understanding and measuring shrinkage is what turns a theoretical agent count into a workable schedule.
What call center shrinkage is
Shrinkage is the portion of paid time when agents are not available to handle contacts. It is not waste — most shrinkage is necessary and planned — but it must be accounted for, because it is the difference between headcount on the schedule and headcount actually taking calls.
Every hour of shrinkage is an hour you paid for but cannot deploy against demand. That is why shrinkage sits at the center of workforce management alongside utilization and occupancy.
The call center shrinkage formula
The formula is simple; the discipline is in capturing every category consistently:
Shrinkage = (total unavailable paid time ÷ total paid time) × 100
Worked example: a team paid for 400 hours in a week records 130 unavailable hours across breaks, training, meetings, and absence. Shrinkage = 130 ÷ 400 = 32.5%.
Measure it over a representative period (a full week or month) rather than a single day, and ideally per interval, because shrinkage is not evenly distributed — training and meetings cluster at particular times.
Categories of shrinkage
Shrinkage splits into planned and unplanned. Separating them tells you what is controllable and what is structural.
| Type | Examples | Controllable? |
|---|---|---|
| Planned — internal | Breaks, lunches, coaching, meetings, training | Partly — schedule around demand |
| Planned — on-queue non-talk | System issues, wrap-up overrun | Yes — workflow and tooling |
| Unplanned | Absence, sickness, lateness, early leave | Yes — adherence and culture |
| Structural | Statutory breaks, mandated training | No — must be planned for |
Unplanned shrinkage, especially absence and poor schedule adherence, is where most operations have the biggest opportunity.
How to factor shrinkage into staffing
Shrinkage turns a base agent requirement into a schedulable number. The two-step method is standard:
- Find base agents. Use an Erlang C calculator to get the agents needed on the phones for your service level.
- Gross up for shrinkage. Divide by (1 − shrinkage). Twelve agents required at 30% shrinkage means scheduling 12 ÷ 0.70 ≈ 18 agents.
Skipping the gross-up is the classic mistake that leaves teams permanently understaffed even though “the Erlang math said 12.”
How to reduce call center shrinkage
You cannot — and should not — eliminate shrinkage. The aim is to cut the avoidable portion and to schedule the rest around demand.
- Attack unplanned absence with adherence tracking, culture, and flexible scheduling.
- Schedule planned shrinkage off-peak so training and meetings do not collide with call spikes.
- Cut on-queue non-talk time by automating wrap-up and simplifying disposition.
- Forecast per interval so breaks are staggered against demand rather than taken in bulk.
- Measure adherence to close the gap between the schedule and what actually happens.
Why accurate shrinkage beats low shrinkage
A center with 35% well-measured shrinkage will out-staff a center with an optimistic 20% guess, because the first one schedules enough agents to actually be available. The win is not a lower number on a dashboard — it is a staffing plan that survives contact with reality. Measure shrinkage honestly, feed it into your Erlang C model, and your occupancy and service levels stabilize.
Frequently asked questions
What is call center shrinkage?
Call center shrinkage is the percentage of paid agent time that is not available for handling contacts. It covers planned time like breaks, training, meetings, and coaching, plus unplanned time like absence, sickness, and lateness. Shrinkage matters because it is the gap between the agents you schedule and the agents actually on the phones — ignore it and you will be chronically understaffed.
How do you calculate call center shrinkage?
Shrinkage = (total unavailable paid time ÷ total paid time) × 100. Add up all the paid hours agents were not available for contacts — breaks, training, meetings, absence, admin — and divide by total paid hours. For example, if a team is paid for 400 hours in a week and 130 of those hours are unavailable, shrinkage is 130 ÷ 400 = 32.5%.
What is a typical call center shrinkage rate?
Most contact centers run shrinkage between 30% and 35%, though it varies widely by industry, channel, and how much training and coaching an operation invests in. Some run as low as 20% and others above 40%. The exact figure matters less than measuring it accurately and feeding it into your staffing model — a plan that ignores shrinkage will always understaff.
How do you factor shrinkage into staffing?
First calculate the base agents required with an Erlang C model, which tells you how many agents must be on the phones to hit your service level. Then divide that number by (1 − shrinkage) to get the gross agents to schedule. If Erlang says you need 12 agents on the phones and shrinkage is 30%, you must schedule 12 ÷ 0.70 ≈ 18 agents to actually have 12 available.
Plan staffing that survives reality with DialPhone
Shrinkage only works as a lever when you can measure availability accurately and act on it. DialPhone’s contact center includes AI Workforce Management — forecasting, scheduling, and adherence — plus real-time wallboards so managers can see availability and handle time as they happen.
Automating wrap-up also trims on-queue non-talk time. Start from the Erlang C calculator for your base agents, then gross up for shrinkage, and track utilization and occupancy alongside it.
About the author
Growth Operations Lead at DialPhone
Darshan leads Growth Operations at DialPhone, where he owns three interconnected programs: the comparison content operation, the open VoIP Pricing Dataset, and the test-call methodology used to verify every pricing claim published on the site.
His research process starts with hands-on product trials and live vendor quotes — not marketing pages. Pricing figures are cross-checked against actual invoices and re-verified on a rolling quarterly cycle, with the underlying dataset kept public for independent re-verification. That dataset now covers 40+ VoIP and virtual-number providers across the US and Canada market.
Darshan also leads DialPhone's AI receptionist evaluation program, running structured test-call scenarios across English, Spanish, and French to assess transcription accuracy, intent routing, and escalation behavior. Methodology notes and raw scoring are archived in the research section.
For factual corrections or dataset discrepancies, Darshan can be reached at the DialPhone editorial address. Verified corrections are published as errata with a changelog date — no silent edits.