Required support FTEs (model)
Capacity math with an efficiency haircut (`1 − shrinkage`) matches workforce planning spreadsheets—add concurrency or chat concurrency in Calclet later.
Example scenario
Workforce Planning loads 14.8k monthly tickets into the capacity model when Finance asks for FY hiring guardrails, assumes each trained tier-2 agent closes 520 resolved tickets per month at steady state for their channel mix, and books 24% shrinkage covering meetings, QA calibrations, PTO, and ad hoc projects off-queue. Net throughput per seat compresses to about 395 tickets after shrinkage (520 × 0.76), so required staffing rounds to roughly 37.45 FTE equivalents—translate to schedules with overlap rules before publishing headcount requisitions.
Required support FTEs (model)
Tickets ÷ net productivity per seat
Want a similar calculator on your website?
Describe your fields and formula in plain English, match your brand, and embed the widget anywhere—WordPress, Webflow, Shopify, or custom HTML. Capture leads when you're ready.
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.
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.
Best use cases
- Forecasting and scenario planning
- Client education and pre-qualification
- Budget and performance decision support
FAQs
Does monthly ticket volume include chats merged into tickets?
Align definitions with your CRM—many shops convert live conversations into ticket records; dedupe so volume reflects net new work units your staffing model must absorb.
Why not use Erlang C instead of simple division?
This is throughput-based sizing for async backlogs; probabilistic queueing fits real-time voice or concurrent chat where occupancy and answer-speed targets dominate—swap models when concurrency constraints bind.
Should shrinkage include schedule adherence variance?
Advanced WFM layers adherence shrink separately; if your shrinkage slider already captures offline time, avoid double-counting intraday variance inside tickets-per-agent inputs.
How do I translate ~37.5 FTE into hiring reqs?
Split by shift pattern and geography—decimal FTE maps to roster coverage plus bench for absenteeism; finance often rounds up to whole heads when salary bands are discrete.
Glossary
Scenario modeling
Testing multiple assumptions to estimate possible outcomes before execution.
Commercial intent
User behavior indicating readiness to buy, subscribe, or request a quote.
Related calculators
Category: Customer support workforce planningTopics: Ticket capacity modeling, Shrinkage and occupancy, Support FTE sizing
Last reviewed: 2026-05-07
Reviewed by: Calclet Growth Team