Shrinkage

Shrinkage is the portion of paid or scheduled time during which agents cannot take calls. It bundles up everything that pulls people off the phones: breaks, lunches, training, team meetings, coaching sessions, system outages, and unplanned absences. If you schedule ten agents but only seven are reachable at any given moment, you have roughly 30 percent shrinkage.

This number matters most when you are figuring out how many agents to hire. If you need seven people answering calls during your busy hour and your shrinkage runs 30 percent, you cannot schedule just seven. You need roughly ten on the books so that, after the usual breaks and absences, seven are actually live. Ignore shrinkage and you will be chronically short-staffed when it counts.

Planned versus unplanned

It helps to split shrinkage into planned and unplanned. Planned shrinkage covers scheduled breaks, training, and meetings you knew about in advance. Unplanned shrinkage is the surprise stuff: sick days, no-shows, and agents who linger in Not ready longer than they should. Tagging each pause with a Pause code lets you see which bucket your shrinkage is coming from.

Do not confuse shrinkage with Occupancy. Shrinkage is about scheduled time lost before agents are even available; occupancy is about how busy the available agents are. Both feed into whether you hit your Service level target, and watching Schedule adherence alongside shrinkage tells you whether people are actually working the hours you planned for them.

A practical way to start is to measure your real shrinkage over a few weeks rather than guessing. Pull how much logged-in time went to each Pause code, add in absences and late starts, and you will get an honest percentage that is often higher than managers expect. Once you know the true figure, you can build it into your staffing math instead of being surprised every busy hour. Tighten the parts you can control, like trimming overlong meetings or following up on chronic no-shows, and accept the parts you cannot, like legally required breaks. Shrinkage will never hit zero, and trying to force it there just pushes agents into staying in Not ready off the books, which hides the problem instead of fixing it.