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.
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.
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.