Support Capacity Planning

Capacity planning requires five categories of input. Volume forecast: a statistically grounded projection of future ticket volume, incorporating historical seasonal patterns, projected customer growth rate (from Sales Ops), planned product releases (from Product Ops — major releases generate volume spikes 1–2 weeks post-launch), and pending changes to the self-service program (improved deflection reduces volume; new channel launches increase it). AHT estimate: current AHT by ticket tier and type, adjusted for planned process improvements or new tool introductions. Agent efficiency factors: average agent utilization target (typically 70–80% of working time on productive ticket handling; the remainder is training, team meetings, admin, and breaks); scheduled absence rates (PTO, sick leave, holidays — typically 15–20% of raw headcount); and learning curve for new hires (new agents operate at 60–70% of full productivity for their first 90 days). SLA targets: the performance standards that define "sufficient coverage" — these constrain the minimum coverage level. Planned headcount changes: known upcoming departures and their replacement timelines. From these inputs, Support Ops builds a month-by-month capacity model for the next 2–4 quarters.

A capacity model translates volume forecast into required headcount. Simplified structure: Monthly Required Capacity (hours) = (Projected Monthly Volume × AHT) / Agent Utilization Rate. Example: 10,000 tickets × 15 minutes AHT × (1/0.75 utilization) = 3,333 productive agent-hours required. Monthly productive agent-hours per FTE: 160 working hours × 0.75 utilization × 0.85 attendance factor (accounting for PTO and absence) = 102 productive hours per FTE per month. Required FTE = 3,333 / 102 = 32.7 FTE. Round up to 33 FTE with hiring lead time factored in. The model should be built in a spreadsheet with scenario toggles: "what if growth is 10% higher than projected?" and "what if we improve AHT by 10% through AI assistance?" — enabling leadership to see the sensitivity of headcount requirements to key assumptions. This model is presented quarterly to the VP of Support and the CFO, connecting support operations directly to the workforce planning budget.

Capacity planning is a persuasion challenge as much as an analytical one: Finance and HR leadership reviewing headcount requests look for rigor, business impact linkage, and alternatives considered. Presentation structure: (1) Current state — current headcount, current performance metrics, current utilization rate. (2) Projected demand — the volume forecast with confidence range and the assumptions driving it. (3) Gap analysis — projected volume at current headcount vs. projected volume with the requested headcount, translated to SLA compliance rates (not just "we need 5 more agents" — "without 5 additional agents, our SLA compliance will fall from 94% to 71% in Q3, directly impacting enterprise renewal risk for these 12 accounts"). (4) Alternatives considered — what efficiency improvements (AI, process changes, deflection programs) are already planned and how much of the gap they close. (5) Request — the specific number of hires, by quarter, with hiring timeline factored in. This format demonstrates that the request is the minimum required after all efficiency alternatives have been pursued, making approval significantly more likely than a headline headcount number without analytical support.