Call Center Shrinkage: Formula, Benchmarks and How to Apply It

Call center shrinkage is the share of paid agent time that can't go to handling contacts: vacation, holidays, sickness, lateness, breaks, meetings, coaching, training and system downtime. Divide the hours lost to all of them by total paid hours and multiply by 100. To staff with it, divide the agents you need on the phones by one minus shrinkage, so 25 agents at 30 percent shrinkage means planning for 36.

Most published figures put shrinkage between 30 and 35 percent. How you apply your own figure matters more than which one you pick. Adding 30 percent to the requirement instead of dividing by 0.7 puts 9 percent fewer agents on the phones than the plan needed, and on a queue taking 300 calls a half hour that drops service level from 84.5 to 38.8 percent. One daily figure used for every half hour does similar damage in the half hours that carry the team meeting. The tables below work through both, along with a worksheet for deciding what belongs in the factor.

What is shrinkage in a call center?

Shrinkage is the gap between the agents you pay and the agents available to take contacts, written as a percentage of paid time. It covers time away from the center, such as leave and sickness, and time in the center spent off the phones, such as breaks, meetings, coaching and training. A staffing model gives you agents on the phones, and shrinkage converts that into agents to schedule or hire.

The queueing literature describes the same step without using the word. In Telephone Call Centers: Tutorial, Review, and Research Prospects (Manufacturing and Service Operations Management, 2003), Gans, Koole and Mandelbaum describe the monthly employee requirement being "grossed up" by a factor between zero and one "to account for unplanned breaks, time spent training and in meetings, absenteeism and other factors that reduce employees' productive capacity." That factor is one minus shrinkage, and the requirement gets divided by it.

Shrinkage and occupancy measure different parts of the day. Shrinkage is the paid time that never reached the phones. Occupancy is measured inside the time that did, as the share of it spent handling contacts instead of waiting for the next one, and it depends on queue size and service level rather than on shrinkage (call center occupancy). Both sit on the call center metrics dashboard, and they are planned separately.

What is included in call center shrinkage?

Anything that keeps a paid agent from taking contacts belongs in the count. Which factor it belongs in is the harder question, because a center applies shrinkage twice: once to turn agents needed on the phones into agents scheduled in a half hour, and once to turn scheduled hours into people on the payroll. The second factor carries everything. The first carries only what your roster doesn't already account for.

An unpaid lunch is in neither column, because shrinkage is a share of paid time. Rarer leave types such as bereavement or volunteer leave belong in the hiring factor as a small allowance, though Call Centre Helper's guidance warns that if you already recruit extra staff to cover them, adding them to shrinkage counts them twice (how to calculate shrinkage).

How do you calculate call center shrinkage?

Add up the hours agents were paid but unavailable for contacts, divide by total paid hours and multiply by 100. When you track in-center time as a rate per day worked, calculate it in two stages: time away from the center as a share of paid hours, then in-center time as a share of the hours people were there. Adding the two percentages charges meetings to days people were on leave.

Here is an example, with inputs chosen to show the arithmetic rather than as benchmarks. A full-time agent is paid for 2,080 hours a year, 40 a week for 52 weeks. Fifteen vacation days, eight paid holidays and six sick days keep the agent out of the center for 29 days, or 232 hours. On each day the agent is in, two 15-minute paid breaks, 25 minutes of meetings and coaching, 15 minutes of training and 10 minutes of system problems and other off-phone work take 80 minutes of an 8-hour day.

Adding 11.2 and 16.7 gives 27.8 percent instead, because it charges 80 minutes a day of breaks and meetings to the 29 days the agent was away. A contributor quoted in Call Centre Helper's shrinkage article calculates out-of-center shrinkage first and in-center shrinkage on what remains, since "the in-center elements can only have an impact if they are actually there." On a requirement of 108 agents on the phones, the added figure plans for 150 people and the two-stage figure for 146.

In a spreadsheet, with the out-of-center share of paid hours in B2 and the in-center share of hours worked in B3, total shrinkage is =1-(1-B2)*(1-B3). With agents needed on the phones in C1 and shrinkage in C2, =ROUNDUP(C1/(1-C2),0) gives the number to plan for.

What is a good shrinkage rate for a call center?

Most published figures fall between 30 and 35 percent, which makes the range a fair check that nothing is missing from your count rather than a target. None of the pages below says what sample or method its figure comes from, and the useful number is the one you measure yourself, broken down by category and by half hour.

Pages read November 3, 2026.

A low number isn't automatically a good one. Call Centre Helper points out that training is usually the first thing cut when a center pushes for higher utilization, and calls very low shrinkage bought that way probably a false economy. The more common failure runs the other way: NICE names underestimating shrinkage, such as planning for 10 to 15 percent when the real figure is 30 to 35, as a cause of chronic understaffing.

How do you apply shrinkage to a staffing plan?

Divide the agents you need on the phones by one minus shrinkage and round up. Adding the percentage to the requirement instead leaves the plan short by the square of the shrinkage rate. At 30 percent, 70 agents plus 30 percent is 91, and 30 percent shrinkage on 91 leaves 63.7 on the phones, 9 percent fewer than the 70 the interval needed.

Call Centre Helper calls this the shrinkage trap. The algebra explains why it never comes out right: multiplying by one plus the rate and then losing the rate leaves one minus the rate squared, so 30 percent costs 9 percent of the requirement and 35 percent costs about 12.

The same 9 percent costs very different amounts depending on queue size. Each row below is one half hour of 5-minute calls, staffed for 80 percent of calls answered within 20 seconds under the Erlang C formula our service level guide uses. Agents on the phones are what 30 percent shrinkage leaves of the added plan, rounded down to whole people.

With the divided plan, every queue meets the target, at 80.7 to 86.7 percent. The smallest queue gets away with the added plan only because rounding up to whole people absorbs the error. The largest doesn't: 98 agents can't keep up with 100 Erlangs of work, so the queue keeps growing until callers hang up. Big queues run at high occupancy and have the least slack to lose. Erlang C assumes nobody abandons, so read the bottom rows as the direction of the damage rather than a forecast.

The divided plan can overshoot in one way. If your factor comes from historical actuals, it already contains the time agents spent out of adherence, and adding an adherence buffer on top counts it twice (schedule adherence). Call Centre Helper's article gives the same advice in general form: choose one method of applying shrinkage and use only that one.

Why does one daily shrinkage figure understaff some half hours?

Shrinkage moves through the day, because meetings, coaching and breaks cluster in particular half hours. A daily average applied to every interval leaves spare agents in the quiet ones and too few in the ones that carry the team meeting. Plan each half hour at its own shrinkage, or move the activity to a half hour with spare agents.

Call Centre Helper's article notes that shrinkage often runs highest between 9 and 11 in the morning and 2 and 3 in the afternoon, when most team and company meetings get booked, and highest across the year in the summer holidays and around Christmas.

Take the 120-call half hour from the table above, which needs 25 agents on the phones. In this example, unplanned absence runs 10 percent all day and in-center time averages 20 percent, so the daily factor is 1 minus 0.9 × 0.8, or 28 percent, and the plan puts 35 people on the schedule in every half hour. Here is what those 35 deliver in three half hours whose in-center time differs from the average.

The daily plan carries four spare agents at 8:00 and leaves 10:00 three short, which cuts its service level to about 50 percent. Planning each half hour at its own shrinkage puts 40 people on the 10:00 schedule. Moving the meeting is usually cheaper, and it is what ACXPA recommends: keep meetings and training out of peak demand windows and use quiet intervals for short coaching sessions.

How do you reduce call center shrinkage?

Go after the shrinkage that costs service and protect the rest. Move meetings, coaching and training into half hours that have spare agents, and report shrinkage in hours by category so absence and lateness each have an owner. Training and coaching should be the last things cut.

• Report hours as well as the percentage. One of Call Centre Helper's contributors argues that the percentage exists for capacity plans and means little operationally, so supervisors should see hours and minutes per day or week.
• Split productive shrinkage, such as training, coaching and one-to-ones, from unproductive shrinkage, such as unscheduled breaks, non-work codes, absence and lateness, and set reduction goals for the second group.
• Watch part-time schedules. A one-hour one-to-one is an eighth of an 8-hour day and a quarter of a 4-hour shift, so the same coaching plan raises shrinkage on a part-time team.
• Compare actual shrinkage with planned shrinkage by half hour every week. The gap tells you whether to fix the factor or the schedule.

Where an AI agent fits around the meeting hours

A roster can only move people from one half hour to another. Telvana adds capacity inside the half hour itself. It answers immediately at any hour, so a phone-menu option offered when the wait climbs, or a forwarding rule for overflow and after hours, takes calls out of the queue while the team meeting runs. Callers who would rather wait for a person keep their place in line (hold-queue relief), and a call that needs a person transfers to your team under rules you set, so count those transfers back into the queue's volume.

Shrinkage then applies to the calls that stay with your team. Recalculate agents needed on the phones for that volume and divide by your interval factor; the workforce management guide has the worksheet for the recalculation. Our team builds each agent from your scripts and transfer rules and tests it with you before it takes a live call. Pricing starts at $399 a month based on call volume, plus a one-time setup fee (pricing).

Frequently asked questions

Is lunch counted as shrinkage?

Only if it is paid. Shrinkage is a share of paid time, so an unpaid lunch sits outside both sides of the fraction, and the schedule already takes the agent off the phones for it. Paid breaks count toward the hiring factor, and toward the interval factor only when your scheduling tool doesn't already place them in each shift.

What is the difference between planned and unplanned shrinkage?

Planned shrinkage is time you schedule in advance: vacation, holidays, breaks, meetings, coaching and training. Unplanned shrinkage is time you can only forecast, such as sickness, other absence, lateness and system downtime. Put planned items in the roster where your tool allows it, and carry unplanned ones as a percentage from your own history by day of week and season.

How much shrinkage is normal in a BPO?

The ranges published for contact centers generally fall between 30 and 35 percent, and NICE puts high-efficiency BPO operations at 20 to 25 percent without saying what that figure rests on. A BPO also inherits shrinkage from each client contract, since paid training for a new program or quality sessions a client requires are time off the phones, so measure it per client program.

If shrinkage is 23 percent, what should occupancy be?

The two don't set each other. Shrinkage decides how many people you schedule to get a given number on the phones. Occupancy comes from call volume, handle time and the service level target for the agents who are on the phones. At 80 percent of calls answered within 20 seconds, it ranges from 50 percent on a small queue to more than 90 percent on a large one (call center occupancy).

Does shrinkage change when AI agents take calls?

The rate generally doesn't, because the people on your team still take the same leave, breaks and training. What changes is the requirement it applies to. Shrinkage grosses up agents needed on the phones for the calls that stay with your team, so recalculate that requirement first and apply the same factor to the new number.

Run your own shrinkage through the calculator

Our staffing calculator takes a shrinkage percentage and divides by one minus it, rounded up, so you can see what your busiest half hour needs at your own figure. To hear an AI agent take a call from your queue, book a demo and bring the half hours your meetings land in.