Zapof

Support Team Capacity & Planning Form

1. Volume Metrics & Growth Projections

This section captures the "demand" side of the equation. Accurate historical data is the foundation of a reliable forecast.

Current Monthly Ticket Volume (Input the total number of unique support requests received in the last 30 days):

Average Handle Time (AHT) (The average duration (in minutes) an agent spends on a single ticket):

Projected Monthly Growth % (The expected month-over-month increase in ticket volume based on marketing efforts or product launches):

Seasonality Buffer % (A field to account for peak periods (e.g., "Add 15% for holiday spikes"):

 

2. Team Tiers & Performance Standards

Efficiency varies by experience. This table helps you understand your "supply" and the cost associated with each level.

Agent Level

Max Tickets / Month

Average Salary (Monthly)

Role Focus

A
B
C
D
1
Example: Junior
400
$3,500.00
General inquiries, Tier 1 troubleshooting
2
Example: Senior
250
$5,000.00
Complex technical issues, escalations
3
Example: Lead
100
$6,500.00
QA, training, and 20% ticket handling
 

3. Operational Overhead & Shrinkage

This section identifies the "Hidden Hours" that reduce your team's actual availability. Precise inputs here prevent burnout staffing by accounting for time not spent on tickets.

 

External Shrinkage (Out of Office)

Vacation / PTO (Average days taken per agent per month):

Sick Leave / Unplanned (Historical average of unexpected absences):

Public Holidays (Monthly average of paid company closures):

 

Internal Shrinkage (In Office, Non-Support)

Training & Coaching (Weekly hours dedicated to professional development and 1:1 sessions):

Team Meetings (Total hours spent in huddles, all-hands, or cross-departmental syncs):

Admin / Project Time (Hours spent on "Special Projects" or non-ticket tasks (e.g., updating the Knowledge Base)):

System Latency / Bugs (Time lost to tool downtime or technical glitches):

Net Productive Time (NPT) % (The actual percentage value of an 8-hour shift spent actively resolving tickets):

 

4. Strategic Headcount Modeling

This section allows you to define the efficiency parameters that dictate how many people you actually need to hire.

 

Projected Workload Units (The product of Current Volume multiplied by (1 + Growth)):

Weighted Capacity (The capacity based on your desired team mix (e.g., if you want 80% Juniors, the capacity leans closer to 400)):

Concurrency Adjustment (For teams handling multiple chats simultaneously, input the "Concurrent Chat Factor" (e.g., 2.5 chats at once) to adjust the required headcount downward):

Safety Net / Occupancy Target (Input a target occupancy (e.g., 85%). This ensures agents aren't working at 100% capacity every second, which is unsustainable and leads to turnover):

Total Agents Needed:

 

5. Financial Summary & Payroll Estimation

The final section translates the operational needs into a budget.

Total Required Headcount:

0

Staffing Distribution (Planned hires by tier (e.g., 7 Juniors, 2 Seniors, 1 Lead)):

Estimated Monthly Payroll:

Fully Burdened Cost:

Cost Per Ticket:

 

Form Template Insights

Please remove this form template insights section before publishing.

 

Form Template Insights

This support capacity form is designed as a structured data-collection tool that bridges the gap between operational performance and financial forecasting. The template utilizes a mix of quantitative inputs and qualitative role definitions to generate a staffing roadmap.

Section 1: Volume Metrics & Growth Projections

  • Data Characteristics: Primarily numeric and percentage-based inputs.
  • Field Nature: These fields represent the independent variables of the form. They capture historical performance and forward-looking growth estimates.
  • Logical Function: This section establishes the "Workload Baseline" upon which all subsequent calculations are built.

Section 2: Team Tiers & Performance Standards

  • Data Characteristics: Tabular data combining text strings (titles), integers (ticket counts), and currency (salary).
  • Field Nature: These are static reference points or "Standard Operating Procedures" (SOPs).
  • Logical Function: It defines the productivity expectations and cost-per-unit for different levels of expertise within the department.

Section 3: Operational Overhead & Shrinkage

  • Data Characteristics: Percentage and hourly duration inputs.
  • Field Nature: These fields represent "time-loss" variables. They are divided into external factors (out-of-office) and internal factors (non-ticket work).
  • Logical Function: This section acts as a reality filter, reducing the theoretical maximum capacity of the team to a realistic "Net Productive Time" figure.

Section 4: Strategic Headcount Modeling

  • Data Characteristics: User-defined coefficients and decimal ratios.
  • Field Nature: These are control variables that allow the user to set the "aggressiveness" of the model.
  • Logical Function: This section houses the primary mathematical logic of the form, synthesizing volume, tier capacity, and shrinkage into a final headcount requirement.

Section 5: Financial Summary & Payroll Estimation

  • Data Characteristics: Currency, integers, and cost ratios.
  • Field Nature: These are the final output or manual override fields that translate human capital needs into fiscal impact.
  • Logical Function: This serves as the reporting layer, providing the bottom-line figures necessary for budgetary approval and unit-cost analysis.

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.