Support Resource Calculator

Before You Start

Choose Your Mode

Data You’ll Need

How the Math Works

Adding New Customers uses a capacity-based FTE model: (productive hours × 60) / handle time = cases per agent per month. New tier case volume divided by this figure gives the FTE gap. For 24/7 coverage, a shift multiplier of 4.7x accounts for PTO, sick, and shift rotation.

Upgrading Existing Customers uses a capacity tax model grounded in queueing theory. When you pull agents into a dedicated pod, the standard pool shrinks. SLA degradation follows the conservation law from priority queueing — the impact is nonlinear, meaning small reductions in the pool can cause disproportionate SLA degradation. The tool also accounts for context switching penalties when pod agents handle mixed work (20% productivity loss per Gloria Mark’s research), proactive engagement time deductions, and escalation velocity impact.

Sources & Citations

• FTE capacity formula — standard workforce management model (HDI, TSIA)
• 24/7 shift multiplier (4.7x) — HDI Workforce Management Guidelines, TSIA Support Services Benchmark 2022
• Context switching cost (23 min recovery) — Gloria Mark, UC Irvine, “The Cost of Interrupted Work: More Speed and Stress”, CHI 2008
• SLA cannibalization (conservation law) — Cobham, “Priority Assignment in Waiting Line Problems”, Operations Research, 1954
• Cases/agent/day benchmarks — MetricNet Service Desk Benchmarks 2023, HDI Support Center Practices Report 2022
• Escalation cost ratios (T1:T2:T3 = 1x:3.2x:4.7x) — MetricNet Cost Per Ticket Analysis 2024
• SLA attainment tiers — TSIA Support Services Benchmark 2022, MetricNet 2023
• TAM/CSM ratios — TSIA Customer Success Benchmark 2023, Gainsight CS Index 2023
• Support cost as % of revenue — TSIA 2022 aggregate, KeyBanc SaaS Survey 2023

Key Terms

Handle Time (AHT)

Average minutes an agent spends working a single case, including research, response, and documentation. Not wall-clock time — this is hands-on-keyboard time.

Utilization Rate

Percentage of an agent’s paid hours spent on productive case work. The rest goes to meetings, training, breaks, and admin. Industry average is 50–55%. If your agents say they’re at 90%, they’re either burning out or not counting overhead.

SLA (Service Level Agreement)

Contractual commitment for how quickly you respond to and resolve cases. Usually defined per priority level (P1–P4). Measured in hours. “Response” = first meaningful reply (not an auto-ack). “Resolution” = issue resolved or workaround in place.

Priority / Severity Levels (P1–P4)

Priority and severity are used interchangeably in most support organizations — both refer to the urgency and impact classification of a case. Some orgs distinguish them (severity = customer impact, priority = internal handling order), but in practice they’re typically the same value. P1/Sev1 (Critical): System down, no workaround, business stopped. P2/Sev2 (High): Major feature broken, workaround exists but painful. P3/Sev3 (Normal): Degraded functionality, workaround available. P4/Sev4 (Low): Cosmetic issue, enhancement request, how-to question.

Business Hours vs Calendar Hours

Business hours = your support team’s working hours (e.g., Mon–Fri 8am–5pm). Calendar hours = 24/7/365. P1 SLAs are typically measured in calendar hours (the customer doesn’t care that it’s Saturday). Lower priorities often use business hours.

FTE (Full-Time Equivalent)

One person working full-time. 2.5 FTE could mean 2 full-time agents and 1 half-time. Used for staffing math because not all roles are 1:1.

Capacity Tax

The hidden productivity cost of servicing premium customers with existing staff. Includes context switching (dropping a standard case to handle a premium one), proactive engagement time, faster escalation overhead, and the reduced pool available for standard work. The tax is nonlinear — pulling 5 agents from 150 costs more than 3.3% of capacity.

Pod

A small, dedicated team assigned to specific premium accounts. Typically 4–6 people including a mix of L1 agents, L2 engineers, and a senior/architect. Pod members primarily serve their assigned accounts but may pick up standard queue work in downtime.

Swarming

Multiple engineers collaborating on a critical incident simultaneously, rather than one person working it alone. Premium P1s might get 3–4 engineers swarming vs the standard 1–2. Reduces resolution time but multiplies the engineer-hours consumed.

Spillover

When pod agents pick up work from the standard queue during downtime. Adds capacity back to the standard pool, but at reduced efficiency due to context switching between premium and standard work.

Context Switching

The productivity loss when an agent switches between tasks. Research shows it takes ~23 minutes to fully regain focus after an interruption (Gloria Mark, UC Irvine). In this tool, spillover work incurs a 20% productivity penalty to account for this.

SLA Cannibalization

When premium tier commitments degrade standard tier performance. Pulling agents into a pod reduces the standard pool. The impact is nonlinear — from queueing theory, wait times grow exponentially as utilization approaches capacity. A 5% reduction in agents can cause a 10–15% increase in response times.

Protection Floor

A minimum number of agents you reserve for the standard tier regardless of premium demand. Prevents SLA cannibalization by capping how many agents can be pulled into pods. Similar to the “guaranteed minimum bandwidth” concept in network engineering.

Shrinkage

Time agents are unavailable for customer work: meetings, training, breaks, PTO, sick days. Industry average is 30–35%. This is already factored into the utilization rate in this tool.

Escalation Velocity

How quickly a case moves from T1 to T2 to T3. Premium tiers often mandate faster escalation (e.g., escalate P1 after 30 min vs 2 hrs for standard). Faster escalation means more cases reach expensive senior tiers, even if T1 could have resolved them with more time.

All calculations run in your browser. Nothing is stored or sent anywhere.