Industry TemplatesFree calculatorPDF, Excel, Word export

Customer Service Desk Staffing Calculator

Staffing a customer service desk is a workload question: how many hours of contacts arrive, and how many productive hours does one agent really provide. This calculator makes the assumptions explicit so you can defend a headcount request or test what a new portal would save.

Your numbers

contacts

Phone, email, portal and EDI items needing a human.

min

Talk or work time plus after-contact work.

hours
25 %

Breaks, leave, training, meetings, sickness.

80 %

Share of available time spent on contacts. Above about 85 percent teams burn out.

$/hr

Your results

Agents needed (rounded up)
4
Cost per contact
$9
Daily workload
18 hrs
Contact hours to be handled each day.
Productive hours per agent
4.8
Hours per agent actually available for contacts.
Agents needed (exact)
3.75
Daily staffing cost
$1,024

This is a workload model that assumes contacts arrive evenly. Real queues have peaks, so add a buffer for the busiest hours or use an Erlang-based tool for phone service level targets.

Save results:

Agents needed vs daily contacts

Sweeps Contacts per day from 20 to 400, holding your other inputs fixed.

Handle time review

Optional: see where agents lose minutes switching between ERP screens and how it could be reduced.

Optional. The tool and every export work without this. No spam.

How to use the calculator

Enter daily contacts and average handle time, ideally from your inquiry log. Set paid hours, shrinkage and target occupancy. Shrinkage covers everything that removes an agent from the queue, and 20 to 30 percent is common. Occupancy is the share of available time spent on contacts, and a target around 75 to 85 percent leaves slack for peaks.

The formula

Workload hours equal contacts times handle time divided by 60. Productive hours per agent equal paid hours times (1 minus shrinkage) times occupancy. Agents needed equal workload divided by productive hours, rounded up. Cost per contact is daily staffing cost divided by contacts. With the defaults, 120 contacts at 9 minutes is 18 workload hours, and each agent gives 4.8 productive hours, so you need 4 agents.

What-if analysis

Change one input at a time. Cutting handle time from 9 to 7 minutes by giving agents ERP access in one screen can remove most of an agent. Deflecting a share of status inquiries to a portal lowers contacts directly. The chart shows how headcount rises with volume, so you can see where the next hire is triggered.

  • Lower handle time: better tools, templates, fewer system switches
  • Lower contacts: proactive notices, portal, EDI acknowledgments
  • Lower shrinkage: scheduling, cross-training, absence control
  • Occupancy too high: queues lengthen and quality drops

Common mistakes

Using total handle time that excludes after-contact work, ignoring shrinkage, and planning for the average day instead of the peak. Month end and shipment cutoffs often double volume. Add a seasonal or weekday factor to contacts when you see recurring peaks.

Frequently Asked Questions

What shrinkage should I use?

Measure it from your own data: paid hours minus hours available on the queue, divided by paid hours. Twenty to thirty percent is a typical range once leave, breaks, training and meetings are counted, but your figure may differ.

Why not plan for 100 percent occupancy?

Contacts arrive randomly. At very high occupancy, any burst creates a long queue, and agents have no recovery time. A target around 75 to 85 percent balances cost against responsiveness and burnout.

Does this work for email and portal work?

Yes, for non-real-time work it is a good fit because the queue can absorb peaks. For live phone service levels, such as answering most calls within a set time, use an Erlang C tool in addition.

How do I estimate handle time?

Use the order status inquiry log or your phone and ticket system reports. Include after-contact work such as updating the ERP and sending follow-ups, since that time is also not available for the next contact.

Netray can help cut handle time by giving agents a read-only ERP assistant for order, shipment and invoice questions, which lowers both minutes per contact and escalations.