Occupancy, Shrinkage & Concurrency: The Math Behind Staffing

Occupancy in customer support measures the percentage of an agent’s working time spent actively handling customer interactions. It indicates how busy agents are during their shifts and helps balance workload efficiently. High occupancy can mean effective use of staff but also risks burnout if agents have limited downtime. Low occupancy may signal understaffing or inefficiency. Maintaining an optimal occupancy rate ensures agents are productive and customers receive timely support.

Shrinkage accounts for the time agents are paid but unavailable for customer interactions, such as breaks, training, meetings, and absenteeism. It’s usually expressed as a percentage of total paid time. Ignoring shrinkage leads to understaffing and poor service, so staffing plans must inflate headcount to cover these non-productive periods. Accurately calculating and including shrinkage ensures you schedule enough agents to meet demand and maintain quality support.

Concurrency refers to how many customer interactions an agent can manage simultaneously, common in chat or email support. Adjusting staffing for concurrency means recognizing that agents can handle multiple requests at once, effectively reducing the total agent hours needed. However, concurrency must be balanced carefully to avoid overloading agents and compromising service quality. Factoring concurrency into workforce planning improves resource allocation and efficiency.

To use a customer support occupancy calculator well, start by gathering accurate data on total scheduled agent time, time spent handling interactions, and shrinkage factors like breaks and training. Input concurrency levels if applicable. Ensure data consistency to avoid skewed results. The calculator will provide occupancy rates and staffing recommendations, which should guide scheduling decisions. Always cross-check outputs with real-world performance and feedback for best results.

Common errors include using outdated or incomplete data, ignoring shrinkage, relying on averages that don’t reflect peak times, and overestimating concurrency capabilities without regard to agent fatigue. Treating staffing calculators as absolute solutions without qualitative insights is another pitfall. To avoid these, regularly update input data, incorporate shrinkage correctly, monitor peak demands, validate concurrency limits, and combine quantitative data with frontline feedback for balanced planning.