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"):
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 |
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):
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:
The final section translates the operational needs into a budget.
Total Required Headcount:
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
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
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.
To configure an element, select it on the form.