Planning calls per hour = staffed agents × 60 × target utilization ÷ (average handling minutes + after-call work minutes). Use handling time across all answered calls, not a billing buffer.
Worked example
Three staffed agents provide 180 agent-minutes per hour. At a hypothetical 70% planning utilization, 126 minutes remain for handling and after-call work. If a call uses 20 handling minutes plus 5 after-call minutes, 126 ÷ 25 = 5.04 calls per hour. Across a six-hour shift that is 30.24 calls of average workload capacity.
These are illustrative assumptions, not RingFunnel performance data or recommended routing limits. Round down when thinking in whole calls, but recognize that even a lower daily cap cannot prevent simultaneous arrivals.
Fictional solo-agent example
For one agent, assume a hypothetical 70% planning utilization, 20 minutes of handling and 5 minutes of after-call work: 1 × 60 × 0.70 ÷ (20 + 5) = 1.68 calls per hour on average. Across six hours, 1.68 × 6 = 10.08 calls of average workload capacity.
The 70% assumption is not an industry standard, and 10.08 is not a guaranteed call quantity. This is an average planning example, not an arrival schedule or concurrency guarantee. One person cannot answer overlapping live calls, and a lower call cap does not ensure that arrivals will not overlap.
Choose inputs from your own records
- Staffed agents: people available to answer during the specific time block, excluding unavailable staff.
- Handling time: average time an answered call occupies an agent, including short and long conversations. A 90-second billing threshold is not a substitute.
- After-call work: average time needed for notes and other work before the next call.
- Planning utilization: the share of staffed time you choose to allocate to handling and after-call work. The remaining share represents allowance for other demands and variability.
- Staffed hours: the length of this scenario. For changing staffing, calculate separate time blocks instead of assuming a full day has the same capacity.
Count after-call work once
Check your reporting system's definition before copying an average handle time into this calculator. For example, NiCE's AHT Actual metric already includes talk, hold and after-call work. This calculator adds its handling and after-call fields together, so those two inputs must not overlap.
Use the handling field for the average time an agent is occupied by an answered call before after-call work begins, including hold time that occupies that agent. Enter the separate average after-call work in the other field. Use the same answered-call population and time period for both averages. If your report already combines the two, obtain the separate components before using it here; do not add after-call work twice or substitute the billing threshold.
In a fictional example, a report shows 25 minutes including 5 minutes of after-call work for the same calls. Enter 20 handling minutes and 5 after-call minutes, not 25 plus 5. With three staffed agents and a hypothetical 70% utilization, the intended calculation remains 126 ÷ 25 = 5.04 calls per hour. Double-counting those five minutes would instead produce 126 ÷ 30 = 4.20. Neither number predicts arrivals, recommends a routing cap or guarantees calls.
What this calculator cannot tell you
This is arithmetic workload planning, not a queueing or service-level model. It does not use the distribution of arrivals, call lengths, breaks or abandonments. Two calls arriving at once can still overwhelm one available agent even when the daily total is below the estimate.
A concurrency limit, a daily delivery cap and a billing cap solve different problems. Confirm each with your provider and verify pause and overflow behavior. Do not increase an order or routing cap automatically because this tool shows spare capacity.
Your scenario stays in your browser
The calculator computes locally and does not submit inputs or results. Downloading creates a CSV on your device. Existing site analytics preferences still apply; the calculator does not send scenario values to analytics.
Turn the estimate into a buying brief
Use your scenario alongside the buying specification. Compare real delivered and live-answered counts in the call-test scorecard, then revise your staffing assumptions from observed results.
Use capacity planning alongside demand forecasting
Call center capacity planning starts with the people available to answer. This tool estimates workload capacity from staffing levels and average handle time. It does not predict when calls will arrive or how long callers will wait.
Use historical data for separate volume forecasting. Compare demand by hour with your staffing plan, and allow time for breaks, notes and other work. Contact centers handling chat, email and phone calls should account for those competing demands rather than treating every staffed minute as phone capacity.
For workforce planning, compare several realistic scenarios. Do not treat the result as a service level agreement or a routing limit. Long-term staffing decisions also need arrival patterns, wait times and service quality evidence that this simple calculator does not model.