Meet Monica, a workforce planner at a call center. Arjun and Sara are two of her agents. They're fictional, but their days are familiar. We'll follow them to show how shrinkage looks from the planner's desk and from the agent's chair.
What is call center shrinkage?
Call center shrinkage is the share of paid agent time when agents can't handle customer contacts. The time goes to breaks, training, meetings, leave, sickness and system problems. Planners use it to decide how many agents to schedule, because paid hours and available hours are never the same.
Genesys describes it as the percentage of paid staff time that agents are unavailable to handle customer interactions.
Monica schedules enough agents for a busy Monday, yet the queue still backs up. Arjun is in training, Sara is on a break, and another agent called in sick.
In short: a schedule built on paid hours alone overstates who can answer calls.
What is the call center shrinkage formula?
The shrinkage rate equals unavailable paid hours divided by total paid hours. Add up every paid hour when agents can't take contacts, divide by all paid hours on the schedule, and show the result as a share of the whole. Split the total into planned and unplanned parts to see where the time goes.
Shrinkage rate = unavailable paid hours ÷ total paid hours
Swipe sideways for full table
Item (example week) | Example hours | Type |
|---|---|---|
Total paid hours | 400 | Base |
Breaks and lunch | 40 | Planned |
Training and coaching | 15 | Planned |
Team meetings | 10 | Planned |
Planned leave | 15 | Planned |
Sick leave | 12 | Unplanned |
Late or early exits | 5 | Unplanned |
System downtime | 3 | Unplanned |
Total unavailable | 100 | Shrinkage is 25% |
These example numbers are made up to show the steps. They are not a benchmark.
Shrinkage calculator
Enter hours for one period. The starting numbers are the made-up example week above. Replace them with your own. With those starting numbers, the calculator shows:
Swipe sideways for full table
Result | Starting example |
|---|---|
Shrinkage rate | 25% |
Planned share of paid hours | 20% |
Unplanned share of paid hours | 5% |
Unavailable hours | 100 |
Agents to schedule | 40 |
Agents to schedule = agents needed on the phones ÷ (1 minus the shrinkage rate), rounded up.
Monica fills in her own team's week with the same layout. The unplanned part turns out to be small, so she looks at planned time first.
In short: split the total, and you know where to act.
How do you calculate shrinkage in WFM and Excel?
In a workforce management (WFM) tool, shrinkage usually comes from scheduled and actual time states. In Excel, list each hour category by week, add the unavailable hours, and divide by paid hours. Use the same period for both numbers, and keep category names the same every week.
Swipe sideways for full table
Column | What to enter | Example formula |
|---|---|---|
A: Week | The week start date | none |
B: Paid hours | All scheduled paid hours | none |
C: Planned hours | Breaks, training, meetings, leave | none |
D: Unplanned hours | Sickness, lateness, downtime | none |
E: Shrinkage % | Share of paid time unavailable | =(C2+D2)/B2, formatted as percent |
Sara's hours come from her time records, not from the schedule. Monica uses the records, because the schedule shows plans, not what happened.
In short: use actual hours, not planned ones, for the unplanned part.
What causes call center shrinkage?
Shrinkage has two sources. Planned shrinkage is time you schedule: breaks, training, meetings and leave. Unplanned shrinkage is time you can't predict: sickness, lateness, early exits and system downtime. Some sources call these internal and external, so choose one set of terms and keep it.
Breaks and lunch
Paid rest time built into every shift.
Training and coaching
Time off the phones to learn and improve.
Meetings
Team briefings and one-to-one talks.
Leave
Planned vacation and public holidays.
Sickness and lateness
Time lost without much warning.
System downtime
Tools that fail or load slowly.
Arjun's shift often starts late because his login tool is slow. Nobody counts it, so it sits in the gaps of Monica's plan.
In short: name each cause, or it hides inside the total.
What is a good call center shrinkage rate?
There's no single correct rate. A good rate is one you can plan for, explain and improve. Vendor guides often cite a common range, but they rarely name a source, and definitions differ. Compare your rate with your own history first, and with others only if the definitions match.
Monica compares her rate with a sister center. That center leaves breaks out of its count, so the two numbers can't be compared.
In short: compare like with like, and start with your own trend.
How does shrinkage affect staffing and service level?
Shrinkage raises the number of agents you must schedule. Divide the agents you need on the phones by one minus your shrinkage rate. Service level is the share of contacts answered within a target time, and short staffing from ignored shrinkage pulls it down.
Swipe sideways for full table
Step | Example (made-up numbers) |
|---|---|
Agents needed on the phones | 30 |
Shrinkage rate | 0.25 |
Agents to schedule | 30 ÷ (1 − 0.25) = 40 |
Monica's forecast says she needs agents on the phones for a big launch day. She schedules that number plus the shrinkage margin, and not the bare number. Good capacity planning starts there.
In short: divide by one minus shrinkage, or you'll be short.
How do you reduce call center shrinkage?
Reduce shrinkage by fixing the causes you can control. Schedule training and meetings in quiet hours, track adherence to the schedule, and look for patterns in sickness and lateness. Don't aim for zero, because breaks and training are needed for agents to stay well and do good work.
Employers
- Move meetings and coaching to low-volume hours.
- Check schedule adherence daily, and talk to people before you judge.
- Review sickness and lateness patterns by shift and team.
Agents
- Tell your planner early about known time off.
- Check your own attendance record and raise errors.
According to its attendance docs, We360.ai shows presence, punctuality, working hours and break patterns, with trends for late arrivals and break time. That can feed the unplanned part of your formula, through its attendance insights. See how it fits BPO teams.
Sara's lateness spikes on one weekday. Monica checks the attendance trend and learns that a shuttle bus runs late that day.
In short: look for the pattern before you blame the person.
How do you track shrinkage fairly for agents?
Track shrinkage as a team measure, tell agents which time counts and why, and let them see their own attendance data. A rate is a planning tool, not a punishment. Counting a short break against one agent builds resentment, while counting it in the team's plan is fair.
We360.ai gives clear, real-time productivity insights without micromanaging.
In We360.ai, managers see attendance for their assigned teams, and employees see their own information, according to the same docs. Open data is easier to accept than numbers an agent never sees.
Sara asks whether Monica tracks her breaks. Monica says yes, as part of the team's plan, and shows Sara her own record.
In short: tell agents what counts, and show them their own numbers.
FAQ
What is the difference between shrinkage and attrition? +−
Shrinkage is paid time when agents can't take contacts. Attrition is people leaving the company. Both reduce the staff you have, but shrinkage is counted in hours each week, and attrition is counted in people over months. Plan for both when you build a schedule.
How do you handle shrinkage for remote or hybrid agents? +−
Count it the same way as for in-office agents, using actual time records, not guesses. Remote agents may lose time to home internet or power problems, so give that cause its own line. Tell agents what counts, so nothing about home work feels hidden.
How do you forecast shrinkage for the next quarter? +−
Start from your past weekly rates and split them into planned and unplanned parts. Adjust the planned part for known events such as training and leave. Keep a margin for sickness, then compare each week with the forecast and correct it.
Can attendance tracking data improve shrinkage accuracy? +−
Yes. Attendance data shows actual start times, breaks and absences, so records can replace guesses. We360.ai's attendance module shows presence, punctuality, working hours and break patterns, according to its docs. Check any data against your own definitions before you use it.
How do you reduce absenteeism-driven shrinkage? +−
Look for patterns by day, shift and team, then talk to the people involved. Check workload and schedules, and offer flexible options where you can. Avoid punishing every absence, because that can push sick agents to work and hide the real cause.
Does my employer track my breaks and shrinkage time? +−
Often yes. Employers count break and attendance time in their plans, usually as a team figure. They should tell you what is tracked and let you see your own data. If you're unsure, ask HR what counts as shrinkage and who can see it.
What counts as shrinkage? +−
Any paid time when agents can't take contacts: breaks, training, meetings, leave, sickness, lateness and system downtime. Pick a clear list, write it down, and count it the same way every week. If the list keeps changing, your rate will drift.
Related Guides

Workload management is how a team assigns and balances tasks so people have time to finish them. IBM describes it as a multi-step effort to plan and schedule work and supply the resources that work needs. This guide looks at the people side of that effort.
