Call Center Shrinkage: Formula, Causes and How to Reduce It

Updated October 2026.

Call center shrinkage is the percentage of paid agent time when agents are not available to handle contacts: (hours not available ÷ scheduled hours) × 100. For example, 240 lost hours out of 800 scheduled hours is 30% shrinkage.

Picture a baker who is paid for an eight hour shift. Yet breaks, a safety briefing and a late delivery eat into it, so fewer hours go into the ovens than the schedule suggests. A call center works the same way. So time disappears. The company pays for every scheduled hour, yet only part of that time is available to take contacts. This guide explains call center shrinkage, shows the formula BPOs use, and then covers how to reduce it.

Call center shrinkage: the short answer

Call center shrinkage is the share of paid time agents cannot take contacts. It covers planned time away, such as breaks and training. It also covers unplanned time away, such as sick leave and system outages. For the calculation, divide lost hours by scheduled hours and multiply by 100.

What is call center shrinkage?

Put simply, shrinkage in a call center is the gap between the hours you pay for and the hours agents spend ready to serve customers. Some teams call it contact center shrinkage, and others spell it call centre shrinkage. Workforce planners use it to turn a headcount into real capacity. For example, a team of 100 scheduled agents never has 100 agents on the phones at once. Without it, a schedule that looks full on paper leaves the queue short, and nobody can explain why the numbers do not add up until the busiest hour of the day has already passed.

Call center shrinkage matters because it sits inside every staffing forecast. Ignore it, and you schedule too few agents, so wait times rise and abandonment follows. Set it too high, and you pay for people you do not need. Both errors cost money. Neither is rare, so check the number often. The goal is an accurate number. It is not zero. Planners who track it by team and by shift can also see where the biggest losses sit, which makes every later decision about breaks, training and hiring easier to defend.

However, do not confuse it with other terms that sound alike:

What causes call center shrinkage?

In practice, call center shrinkage falls into two groups. You can see planned shrinkage on the calendar before the shift starts. Unplanned shrinkage, however, is time you cannot predict, so you estimate it from history.

Planned shrinkage

• Breaks and lunch. Every shift includes paid and unpaid time away from the queue.
• Training. New hire classes, product updates and refreshers take agents off the phones. Our notes on agent training show how to shorten this block.
• Coaching and quality reviews. One to one sessions are valuable, but they still use scheduled hours.
• Team meetings and briefings. Daily huddles and process updates add up across a month.
• Paid leave and holidays. Because approved time off is known in advance, it belongs in the plan.

Unplanned shrinkage

• Absenteeism. Illness and emergencies remove agents with little notice and raise the load on the rest of the team.
• Lateness and early exits. A few minutes per agent per day add up across a large team.
• Personal disruptions. Transport problems and family matters pull agents away mid shift.
• System and network outages. Even agents who are logged in but cannot open their tools count as lost time, because a person who is present but unable to serve a customer adds nothing to capacity during that period, no matter how the attendance system records it.
• Extra after-call work. Long wrap-up tasks keep agents unavailable. Our guide to after-call work covers the fix.
• Burnout and stress. Tired agents take more unplanned time off.

A sudden spike in call volume is not shrinkage. It is a forecasting miss. That is a different problem. Treat it that way, and fix the forecast, not the schedule. Keep the two apart, because a forecast that misses call volume needs a better model, while shrinkage that runs high needs a closer look at schedules, tools, training calendars and the working conditions agents face every day. Otherwise, the shrinkage number will hide the real problem.

Call center shrinkage formula

In short, the standard formula compares lost time with scheduled time:

Shrinkage % = (Hours agents were not available / Total scheduled hours) x 100

First, put both planned and unplanned time in the top line. Then use paid scheduled hours in the bottom line. Keep the same definition from one report to the next. Otherwise, trends mean nothing.

If your team tracks people instead of hours, use this version at a point in time.

Shrinkage % = ((Agents scheduled minus Agents available) / Agents scheduled) x 100

Shrinkage formula in BPO: a worked example

The numbers below are illustrative, not a benchmark. Say a BPO team has 100 agents, each scheduled for an 8 hour shift. That makes 800 scheduled hours for the day. Now add up the lost time. Every hour counts.

The planned total is 90 + 60 + 30 = 180 hours. In addition, the unplanned total is 40 + 10 + 10 = 60 hours. Together that is 240 hours.

So the result is 240 divided by 800, multiplied by 100, which gives 30%. The planned part is 180 / 800 = 22.5%. The unplanned part is 60 / 800 = 7.5%. As a check, the two parts add up to the same 30%. That leaves 560 productive hours, or 70% of paid time. Simple, and easy to audit later when someone questions the figure in a monthly review meeting with finance.

Shrinkage by headcount

Now a quick check by agents. For instance, suppose 100 agents are scheduled for a half hour interval and 72 are logged in and ready. The result is (100 minus 72) / 100 x 100, which is 28%. It cannot exceed 100%. If it does, the inputs are reversed.

How to calculate shrinkage in BPO, step by step

1. Pick the period. Choose a day, a week or a month, and apply it to every team you compare.
2. Total the scheduled hours. Multiply agents by shift length, and count paid hours only.
3. Total the lost hours. Pull breaks, training, meetings, leave, absence and downtime from your workforce tool or timesheets.
4. Divide and multiply by 100. Lost hours divided by scheduled hours gives the percentage.
5. Split planned from unplanned. Later, manage the two parts differently.

Why shrinkage changes your staffing plan

This is why a roster needs more people than the forecast says. For example, say the forecast calls for 70 agents on the phones and your shrinkage is 30%. The correct schedule is 70 / (1 minus 0.30) = 100 agents.

Still, a common mistake is to add 30% to 70, which gives 91 agents. Check it. Run the numbers. 91 agents at 70% availability give about 63.7 available agents, which is below the 70 you need. So divide by one minus shrinkage. It is a small change, but it matters. For more on forecasting and scheduling, see our guide to workforce management.

What is an acceptable call center shrinkage percentage?

There is no single acceptable number. Overall, the right level depends on your industry, your channels, how much training your products need, local leave rules and how often processes change. Anyone who quotes one figure for all teams is guessing, because a team that trains monthly on complex products will always lose more hours than a team that handles a short list of simple requests.

Instead, set your own range from three to six months of history. Do it by team and by shift, since a night queue and a day queue rarely lose time in the same way or for the same reasons. Next, look at the two halves separately, because they behave differently and call for different decisions from the people who run the schedule. In practice, the planned part is a decision that you can adjust, for instance by moving a training class out of a busy week and into a quiet one with a lighter forecast. In contrast, unplanned shrinkage is a signal, and a rise points to a problem in schedules, tools or morale. Very low shrinkage is not always good either. If it falls because training and coaching were cut, quality will pay for it later.

How to reduce call center shrinkage

Since some lost time is healthy, the aim is to cut the avoidable part of call center shrinkage and plan the rest accurately. These steps usually help most:

• Stagger breaks and meetings. Spread them across the day, so the queue is never left uncovered at peak times.
• Schedule training in low volume windows. Your forecast shows the quiet intervals, so you need not pull agents at random.
• Offer flexible schedules. For example, split shifts, part time options and shift swaps reduce last minute absence, and they let agents cover personal commitments without taking a full day off, which keeps more hours inside the plan.
• Track absence patterns. Look for repeat days, teams or managers that stand out, then fix the cause.
• Shorten after-call work. Templates and guided wrap-up steps return minutes to every contact.
• Fix the tools. Frequent outages and slow screens create unplanned downtime. Report them quickly.

After that, tackle the causes that show up day to day:

• Track adherence in real time. Alerts show when agents drift from the schedule, so supervisors can respond within minutes.
• Cut avoidable calls. Self-service and chatbots handle routine questions, so fewer contacts reach agents.
• Protect agent well-being. Reasonable workloads, fair schedules and real recognition for good work reduce absence linked to agent burnout.
• Review monthly. In addition, compare planned and unplanned shrinkage with the forecast, then adjust the schedule so that the next month starts from the real numbers and not from last year’s assumptions, which may no longer match how your team works.

Reduce shrinkage with better knowledge access

Some call center shrinkage comes from the work itself. When agents cannot find an answer, calls run longer, wrap-up takes more time, and new hires need more classroom hours before they take live calls. Training time and extra after-call work both count toward lost hours, so they are worth attacking first.

Search time is a real cost. For instance, McKinsey Global Institute estimated that interaction workers spend nearly 20 percent of the workweek looking for internal information or tracking down colleagues. That study covers knowledge workers in general, not call centers alone, and it dates from 2012. Even so, it shows why one searchable source of answers matters, since every minute an agent spends hunting for a policy detail is a minute that the schedule counted as productive but the customer never saw.

Knowmax is an AI-powered knowledge management platform that sits beside your CRM or help desk, so agents keep the tools they already know. Agents search one call center knowledge base, follow guided workflows during a live contact, and see answers in the same place. As a result, new agents can reach live calls sooner, and routine questions need less coaching. Gartner also found that 58% of service leaders aim to upskill agents into knowledge management specialists, which means agents who help maintain answers also spot the gaps that waste time.

Customers can also solve simple questions through self-service. That helps too. Consequently, fewer contacts reach the team at all. Meanwhile, Gartner expects knowledge management systems, live chat and self-service portals to surpass phone and email as the most valuable customer service technologies by 2027. Better knowledge access does not remove call center shrinkage. It does shrink the part caused by searching, retraining and rework.

Shrinkage in hours, and how it differs from utilization

A percentage hides the scale, so also express shrinkage in hours. Using the worked example above, 240 lost hours across 100 agents is 2.4 hours per agent per eight hour shift, which leaves 5.6 available hours each. Planners schedule by interval, so hours per agent and hours per day are easier to act on than one monthly percentage.

Shrinkage also differs from utilization. Shrinkage measures time lost before contacts can be taken, while utilization measures how the remaining available time is used. In the same example, 560 hours are available. If agents spend 420 of those hours on contacts and related work, utilization is 420 / 560 = 75%. Both numbers are illustrative. Our guide to agent utilization rate covers the calculation, and the table earlier shows how occupancy differs.

Shrinkage and the metrics around it

This metric does not stand alone, so read it next to productivity, service level, average handle time and customer satisfaction. If shrinkage falls but satisfaction drops too, you may have cut coaching or rest that agents needed. If both rise together, check the unplanned causes first.

To compare tools for this work, start with this overview of knowledge management software. In short, treat call center shrinkage as a planning input, not a punishment. Measure it by team, split planned from unplanned, and fix the avoidable causes. Finally, staff to the number you actually have. Without it, nothing else works.

Frequently asked questions about call center shrinkage