Want help applying this guide?Ask the DripTell team
Customer support shrinkage is the share of paid team time that cannot be used to handle customer work. Breaks, training, meetings, coaching, leave, system problems, and required administrative work all reduce usable capacity. Treating those hours as if agents were available produces a staffing plan that looks complete but fails when messages arrive.
Measure shrinkage from time records, keep planned and unplanned causes separate, and apply the result to each queue and interval. The purpose is not to blame people for necessary activities. It is to turn a paid schedule into an honest estimate of service capacity.
Define shrinkage before calculating it
Microsoft defines shrinkage as the percentage of time representatives are unavailable to handle conversations, including breaks and other activities. Its capacity-planning guidance also explains that a higher shrinkage assumption requires more representatives to meet a service-level target.
A practical definition is:
Shrinkage rate = unavailable paid time ÷ scheduled paid time
If a team schedules 400 paid hours and 88 hours are unavailable for customer work, shrinkage is 22 percent. The usable capacity is 312 hours. Do not subtract unpaid time twice. If lunch is outside paid hours, it should not appear in either side of the formula.
| Time category | Include as shrinkage | Why |
|---|---|---|
| Paid break or scheduled training | Yes | Paid time is not available for customer work |
| Team meeting or one-to-one coaching | Yes | Necessary activity still reduces queue capacity |
| Approved leave inside the staffing plan | Yes | The scheduled person cannot handle conversations |
| Unpaid meal outside scheduled hours | No | It is already outside paid capacity |
| Time actively answering or wrapping a conversation | No | It belongs to productive handling time |
Separate planned and unplanned shrinkage
Planned shrinkage includes activities a manager can see before the day begins, such as training, coaching, breaks, meetings, and approved leave. Unplanned shrinkage includes sickness, late arrival, unexpected system downtime, and urgent non-queue work.
The distinction changes the response. Planned shrinkage belongs in the schedule. Unplanned shrinkage needs a reserve, a trigger, or a recovery rule. Combining both into one monthly percentage hides whether a failure came from a poor plan or an unexpected event.
Keep the categories small enough to act on. “Other” should never become the largest bucket. At the same time, do not create dozens of codes that agents cannot apply consistently. Five to eight stable causes are usually more useful than a perfect taxonomy nobody trusts.
Calculate shrinkage by useful interval
A single annual rate is useful for budgeting but weak for daily operations. Training may cluster on Tuesday mornings, sickness may rise during a season, and meetings may overlap the busiest hour. Calculate the rate by week, queue, and interval where volume changes matter.
- 1Define paid capacitySet the scheduled paid-time denominator and exclude unpaid time once.
- 2Separate causesKeep planned activities apart from sickness, outages, and other surprises.
- 3Calculate by intervalMeasure by queue and interval so peaks and recurring collisions stay visible.
- 4Convert to staffingApply the measured rate after workload, handling time, and concurrency assumptions.
For each interval, record scheduled paid capacity and unavailable paid time by cause. Then compare the result with conversation arrivals, backlog growth, and customer wait. The occupancy guide helps distinguish unavailable time from the share of available time spent handling work. The schedule adherence guide shows whether people were in the activity the plan expected. These are related measures, not substitutes.
Use a weighted rate when combining teams. Averaging a 10 percent rate from a two-person queue with a 30 percent rate from a twenty-person queue produces a misleading result. Add the unavailable hours and divide by all scheduled paid hours instead.
Convert the rate into a staffing requirement
Suppose the workload model says a queue needs 12 people available. With 20 percent shrinkage, scheduling 12 people is not enough.
Scheduled people = required available people ÷ (1 − shrinkage rate)
The calculation gives 15 scheduled people because 12 divided by 0.8 equals 15. Round only after calculating. For messaging, apply the team’s real concurrency and handling assumptions before adding shrinkage. The conversation-capacity guide explains why an agent’s safe workload depends on task complexity and interruption, not a universal chat count.
Do not use a high shrinkage rate as permission to overstaff every interval. Use the cause pattern. A predictable training block may be moved. A recurring system outage needs engineering work. Persistent sickness may require a reserve or a safer schedule.
Review causes without punishing necessary time
Shrinkage becomes harmful when it is presented as wasted time. Coaching, calibration, security training, and breaks protect quality and people. Removing them may improve one capacity report while increasing errors, absence, or turnover later.
Review the result with three questions:
- Was the activity necessary?
- Was it scheduled in the least damaging interval?
- Could the same outcome require less queue disruption?
Look first for avoidable collisions, duplicate meetings, manual reporting, unreliable tools, and work that should be automated. Keep individual health information private and use aggregated causes where personal detail is not required.
Connect shrinkage to the operating plan
Forecast volume and handling time first, convert that workload into required available capacity, and then add a measured shrinkage allowance. Our support-volume forecasting guide explains how to separate channel, queue, interval, and special events before staffing. A shared inbox can keep queue ownership and conversation state visible, but it does not replace workforce records.
Refresh planned shrinkage when the schedule changes and review unplanned shrinkage weekly. Keep the original assumption beside the actual result. If the team misses service while actual shrinkage is close to plan, investigate forecast error, handling time, concurrency, or routing instead of blaming availability.
Start with four weeks of trustworthy data. Publish the definition, category rules, and owner of each correction. If your capacity records are split across tools, map the operating model with DripTell before adding more automation.
Frequently Asked Questions
What is a healthy customer support shrinkage rate
There is no universal healthy rate. It depends on paid-break policy, training, leave, meeting load, system reliability, and the type of service. Use your own measured causes and compare planned with actual results instead of copying an industry number.
Is occupancy the same as shrinkage
No. Shrinkage measures scheduled paid time that is unavailable for customer work. Occupancy measures how much of the available handling time is occupied by active customer work and related wrap-up.
Should training and coaching count as shrinkage
Yes when they occur during paid time that was part of the staffing plan. Counting them does not mean they are waste. It ensures the schedule funds necessary development without pretending the person can handle conversations simultaneously.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy