Support Reporting
Part of Support workforce tools
Planning coverage without relying only on average handling time
Use arrivals, response targets, backlog, concurrency, shrinkage and skills alongside handling time to plan support coverage.
Average handling time helps estimate how much work contacts create. On its own, it cannot tell you how many qualified people must be available at a particular time. Plan coverage from the arrival pattern, response promise and available people, using handling time as one input.
Separate workload from coverage
Multiplying forecast contacts by average handling time estimates productive handling time. It does not show when contacts arrive, how long customers can wait, whether chats overlap or whether an agent is on a break. A weekly total can conceal an uncovered hour.
In a deliberately simplified example, 120 contacts at six minutes each represent 720 minutes, or 12 productive hours. That does not mean one person working 12 hours would meet a live response target. Contacts could arrive together, the person might lack the required skill, and part of a scheduled shift may be unavailable for replies. Use the arithmetic to check workload, not to prescribe a roster.
Impact of Misusing Average Handling Time (AHT)
- One agent working 12 hours
- May not meet live response target
- Common oversights
- Peak arrival times, skill mismatches, break periods
Add the conditions that change the answer
| Condition | Coverage question |
|---|---|
| Arrival pattern | Which intervals carry the peak, and which work can wait? |
| Response target | How long can a customer wait? |
| Backlog | What work is already due? |
| Concurrency | Can an agent manage overlapping chats in this workflow? |
| Occupancy | What share of available time can be spent handling contacts? |
| Shrinkage | What scheduled time is unavailable for customer work? |
| Skills and minimum cover | Which qualified people must be present even when volume is low? |
Define these inputs for each channel or workstream. Zendesk WFM's Forecast page presents inbound volume estimates and FTE requirements based on historical data. For any planning tool, verify how its required-staffing output handles response windows, concurrency, shrinkage, minimum cover and skills before translating it into a roster.
Build an interval plan
Start with forecast arrivals for each interval. Add backlog that must be handled within the relevant response window. Check channel behaviour: live contacts generally need people near arrival, while some email work can be completed later.
Estimate productive coverage using the response target and an agreed occupancy assumption. Account for unavailable time once, apply minimum coverage and skills constraints, and assign people.
Compare the requirement with the roster after breaks, training, leave and other duties. A person shown on two channel rosters cannot supply full coverage to both at once. If cross-trained agents switch channels, define the trigger, priority and return rule. Keep a monitored fallback for absence or a demand spike.
Inspect the assumptions behind a tool's required-staffing number. Verify how it accounts for response windows, available time and work that can wait.
Amazon Connect Scheduling plans use a published short-term forecast and provide interval-level headcount needs. Use that output to identify staffing gaps, then compare it with the actual roster and service outcome.
Review the gap after the shift
Record intervals where the roster was below requirement and whether customers waited, work accumulated or agents were diverted. Determine whether the cause was arrivals, handling effort, unavailable time, skills or an unrealistic response target. Change the relevant assumption and check the next plan. Lowering AHT solely to make a model fit would conceal the gap.
