Required support FTEs (model)
What is a support headcount calculator?
A support headcount calculator estimates how many customer support agents you need to handle your monthly ticket volume. It divides tickets by how many each agent resolves per month, after adjusting for shrinkage, the time agents spend in meetings, training, and time off. Support leaders, workforce planners, and founders use it to plan hiring, budget support costs, prepare for growth or seasonal peaks, and measure the impact of self-service.
Required support FTEs (model)
Tickets ÷ net productivity per seat
Embed this free calculator on your website—copy the snippet after signup and keep the Built with Calclet link for attribution (or upgrade to remove branding).

Support headcount formula
Divide monthly tickets by each agent's productive capacity after shrinkage.
FTEs needed = Monthly tickets ÷ (Tickets per agent per month × (1 − Shrinkage %))- Net tickets per agent = Tickets per agent per month × (1 − Shrinkage %).
- FTE means full-time equivalent; round up to whole agents when hiring or scheduling.
- This works best for email and ticket queues; live phone and chat staffing also depends on response time targets and peak hours.
Inputs explained
Use recent data from your helpdesk for the channel and team you're staffing.
- Monthly ticket volume
- Number of new customer tickets or conversations each month, counting each issue once.
- Resolved tickets per agent / month
- Tickets a fully trained agent resolves in a month of available working time, before subtracting meetings, training, and time off.
- Shrinkage (meetings, training, PTO) (%)
- Share of paid time agents aren't available to work tickets because of meetings, training, breaks, vacation, and sick days.
Example support headcount calculation
A support team receives 14,800 tickets a month. Each agent can resolve 520 tickets a month, and 24% of their time goes to meetings, training, and time off. Net capacity = 520 × 0.76 = 395.2 tickets per agent. FTEs needed = 14,800 ÷ 395.2 ≈ 37.45, so plan for 38 agents.
Put this calculator on your site
We'll copy this tool into your Calclet account—tweak branding and fields, then paste the embed on WordPress, Webflow, Shopify, or any HTML page. Every embed can link back to Calclet for discovery.
How to use the required support ftes (model)
- Pull monthly ticket volume from your helpdesk—normalize one created ticket per customer issue and exclude internal tasks unless they consume the same queue.
- Set resolved tickets per agent-month using resolved counts divided by active agents for the channel tier you are staffing (email vs chat vs phone may differ).
- Slide shrinkage to the percent of paid hour buckets unavailable for productive work after meetings, 1:1s, training, PTO, and offline QA.
- Compare approx. FTEs needed with net tickets per seat after shrinkage; layer concurrency, SLA targets, and span-of-hours coverage in rostering tools outside this divisor model.
Common support staffing mistakes
- Forgetting shrinkage and assuming agents spend every paid hour on tickets.
- Using new-hire productivity rates as if they were fully trained agents.
- Planning for average months instead of seasonal peaks.
- Using one productivity rate for email, chat, and phone.
- Rounding down and leaving no room for sick days or turnover.
Support staffing planning norms
- Shrinkage bands
- Contact-center workforce plans commonly embed 20–35% shrinkage for blended roles once meetings, training, and offline admin are excluded from productive handle time.
- Throughput drivers
- Tickets solved per agent-month swings with complexity, self-serve deflection, and tooling—benchmark internally from trailing CRM exports rather than generic industry tables.
- Fractional FTE reality
- Capacity models output decimals; scheduling converts to shift blocks—round up when overtime budgets are thin or SLAs are strict.
FAQs
How many support agents do I need if ticket volume grows 20%?
Increase ticket volume and rerun. 14,800 tickets growing 20% to 17,760 needs 17,760 ÷ 395.2 ≈ 44.9, so 45 agents instead of 38. Start hiring before volume arrives, since new agents take time to train.
How many agents can self-service or AI deflection save?
Reduce ticket volume by the expected deflection. If a help center or chatbot cuts 15% of tickets, 12,580 tickets need about 31.8, so 32 agents instead of 38. At $55,000 per agent per year in total employment cost, that's about $330,000 a year saved before the cost of the tools.
How much does reducing shrinkage lower headcount?
Lowering shrinkage from 24% to 20% raises net capacity from 395.2 to 416 tickets per agent. Headcount for 14,800 tickets drops from about 37.45 to 35.58, so 36 agents instead of 38. Cutting unnecessary meetings is often cheaper than hiring.
How do I calculate tickets per agent per month from handle time?
Divide available working minutes by average handle time. 160 working hours × 60 minutes ÷ 18 minutes per ticket ≈ 533 tickets a month. Enter that as tickets per agent and let shrinkage account for meetings and time off. Real output is usually lower because agents also wait between tickets and follow up.
How many extra agents do I need for a seasonal peak?
Run the peak month separately. If November volume jumps to 22,000 tickets, you need about 55.7, so 56 agents, compared with 38 normally. Temporary staff, overtime, or outsourced support can cover the 18-agent gap instead of permanent hires.
What does support cost per ticket?
Divide monthly team cost by ticket volume. 38 agents at $4,500 a month in total employment cost is $171,000 a month, or about $11.55 per ticket on 14,800 tickets. Deflection and higher productivity lower this number.
How many tickets can my current support team handle?
Multiply agents by net tickets per agent. 30 agents × 395.2 = 11,856 tickets a month. With 14,800 tickets coming in, the team falls about 2,944 tickets short each month, which shows up as a growing backlog and slower responses.
How many agents do I need for 24/7 support coverage?
Check minimum coverage as well as ticket volume. Keeping 2 agents online every hour of the week takes 2 × 168 = 336 agent-hours. With 40-hour weeks and 24% shrinkage, each agent covers about 30.4 hours, so you need about 11 agents just for minimum coverage, even if ticket volume needs fewer.
How do new hires affect support capacity?
New agents usually work below full productivity while training. If you hire 8 agents to close a 2,944-ticket gap and they work at 50% for the first months, they add about 1,581 tickets of capacity, leaving roughly 1,363 tickets uncovered. Hire earlier or plan overtime while they ramp up.
Should I round support headcount up or down?
Usually up. 37.45 FTEs means 38 agents, and many teams add a small buffer for turnover and sick days. Rounding down to 37 leaves capacity for about 14,622 tickets, about 178 short of the 14,800 needed each month.
Related calculators
Category: Customer support workforce planningTopics: Ticket capacity modeling, Shrinkage and occupancy, Support FTE sizing
Last reviewed: 2026-05-07
Reviewed by: Souhayb Kama Ldine