Raw workload
Total monthly hours required to handle the entered contact volume.
Customer support staffing calculator
Free Customer Support Staffing Calculator
Estimate how many full-time customer support agents your monthly workload requires. Enter contact volume, handle time, schedule, occupancy, shrinkage, and expected AI automation level.
The result is a monthly capacity estimate—not a hiring recommendation or real-time schedule. Potential capacity after automation does not automatically mean headcount reduction.
Four planning outputs
What Does the Staffing Calculator Show?
Productive hours per FTE
Estimated handling capacity of one full-time agent after occupancy and shrinkage.
Estimated full-time agents
FTEs required to cover the workload, rounded up.
Staffing with automation
Estimated FTE requirement after the selected contact share is removed from human workload.
The difference between rounded scenarios can support growth, backlog reduction, wider coverage, or reassignment—not necessarily headcount reduction.
Build the scenario step by step
How to Use the Customer Support Staffing Calculator
Monthly support contacts
Use handled calls, tickets, chats, or messaging conversations from one consistent month.
Average handle time
Enter the minutes required for one contact, including relevant wrap-up work.
Working schedule
Enter working days per month and paid hours per day.
Target occupancy
Enter the share of available time spent handling contacts.
Shrinkage
Include paid time unavailable for handling: breaks, meetings, training, leave, absence, and downtime.
AI automation level
Use the percentage assumed to be fully handled by AI.
Monthly cost per agent
Use loaded employment cost to illustrate capacity value—not guaranteed savings.
Calculate channels separately when their workflows differ. Paid shift length is not the same as productive handling time. Use the Average Handle Time Calculator.
Monthly capacity model
Customer Support Staffing Formula
Monthly workload hours
Monthly contacts × AHT ÷ 60
Scheduled hours per FTE
Working days × Paid hours per day
Productive hours per FTE
Scheduled hours × Occupancy × (1 − Shrinkage)
Required FTE
Monthly workload ÷ Productive hours per FTE, rounded up
Remaining workload
Monthly workload × (1 − AI automation rate)
FTE after automation
Remaining workload ÷ Productive hours per FTE, rounded up
Rounding up ensures the scenario contains at least the estimated monthly capacity.
Worked example
Customer Support Staffing Example
Suppose a team handles 10,000 monthly contacts at eight minutes each. Agents work 22 eight-hour days with 80% occupancy, 25% shrinkage, and 40% automation.
1,333 hours
Monthly workload: 10,000 × 8 ÷ 60
105.6 hours
Productive capacity: 22 × 8 × 80% × 75%
13 FTE
Current staffing: 1,333 ÷ 105.6 = 12.63, rounded up
8 FTE
After automation: 1,333 × 60% ÷ 105.6 = 7.58, rounded up
5 FTE
Potential capacity difference
The five-FTE difference could support growth, backlog clearance, wider coverage, or complex cases. It is not an instruction to reduce headcount.
Two different capacity reductions
Occupancy vs Shrinkage
Shrinkage
Reduces scheduled time because an agent is unavailable for handling.
Occupancy
Applies to remaining available time and represents the share occupied by contact handling.
Treating an eight-hour paid shift as eight productive handling hours understates required staffing. Apply both factors at the correct stage.
Monthly planning, not queue modeling
Is This an Erlang C Staffing Calculator?
No. This calculator uses a monthly capacity formula suited to budget planning, asynchronous support, hiring scenarios, and comparing assumptions.
It does not model interval arrivals, abandonment, waiting probability, answer targets, chat concurrency, or multi-skill routing. Use Erlang C or workforce-management systems for interval-level queue planning and strict service-level targets.
Read Talkdesk forecasting guidanceModel several scenarios
How AI Automation Changes Support Capacity
Automation can remove repeatable contacts from human workload, such as FAQs, basic order inquiries, initial information collection, routing, and routine follow-ups.
Impact depends on resolution, escalation, review, complexity, and new demand. Test conservative, expected, and high-automation scenarios instead of treating one percentage as a promise.
Strengthen the assumptions
How to Build a More Reliable Staffing Scenario
Use several months
Avoid basing staffing on one unusual month.
Plan variability
Account for seasonality, campaigns, launches, and growth.
Separate channels
Model phone, email, chat, and social messaging when workflows differ.
Weight AHT
Use contact volume when combining contact types.
Measure shrinkage
Prefer actual team data over a generic benchmark.
Test demand levels
Run conservative, expected, and high-demand scenarios.
Monthly averages do not prove every hour is adequately covered. Review peak periods separately before finalizing schedules.
Capacity before hiring
Plan Capacity Before Automatically Hiring
A capacity gap does not always mean another hire is the next step. First identify which conversations require human judgment and which are repetitive enough to automate.
Dealism can help teams manage conversations on WhatsApp and Instagram. AI agents can answer routine questions, collect information, and transfer complex cases with context.
Explore WhatsAppExplore InstagramRead the WhatsApp automation guideCompare WhatsApp marketing toolsBrowse all free Dealism tools
Build and test a Dealism agent →Frequently asked questions
Frequently Asked Questions
How do I calculate how many support agents I need?
Multiply monthly contact volume by AHT, then divide workload by productive monthly hours per FTE.
Should I round required agents up?
Yes. If the result is 7.4 FTE, eight full-time equivalents provide at least that estimated capacity.
Does it account for chat concurrency?
No. Model simultaneous chat handling separately with a concurrency-aware method.
Does potential FTE capacity equal guaranteed savings?
No. It is the difference between scenarios. Financial impact depends on implementation, AI resolution, escalation, and how capacity is used.
Dealism replies the second they message, sounds completely human, and quietly closes deals in the background.
Start Now
Every reply is a deal in the making.
Every reply is a deal in the making.
Every reply is a deal in the making.
