Short answer
Estimate phone staffing from calls per time slot, conversation and after-call duration, and available time per person. Workload calculations provide an initial reference; validate peaks and concurrent calls before converting them into shifts.
Key verification: Compare expected workload, answered calls and observed waiting during a trial shift.
Sources and limitationsTo estimate how many people should answer calls, calculate the workload of each slot and divide it by the minutes that each person can realistically dedicate. Includes conversation and subsequent work. The result is a first estimate of capacity; it does not guarantee a waiting time or resolve arrival peaks.
A daily average can hide a busy morning and a calm afternoon. Use time slots consistent with your shifts and reduce their size when calls are concentrated in short periods.
The data you need
- Calls offered to the team in each slot, including those that could not be answered.
- Average talk time for comparable queries.
- Subsequent work: notes, response preparation or task closure.
- Minutes reserved for other functions, breaks and meetings.
- People really present and capable of answering that query.
Phone history helps check moments and records; Aircall explains its query and export in the Call History guide . Do not confuse the time since login to the system with minutes of an agent's work. Waits and transfers require reviewing the definition of each field.
If you only have data on answered calls, the estimate may underestimate demand: some potential work was lost before speaking. Identify that limit on the calculation sheet.
A workload formula with explicit assumptions
Slot load = expected calls × (talk minutes + subsequent minutes).
Capacity per person = duration of the slot × proportion dedicated to the telephone × expected occupancy within that time.
Estimated people = load ÷ capacity per person, rounded up.
Dedicated ratio discounts other tasks. Occupancy leaves room within telephone time for variation and intervals; Don't discount the same meetings there again. No percentage in this example is a standard that you should copy.
Fictional example with three time slots
Let's assume five-minute queries and one minute after that. Each person spends 75% of the hour on the phone; Within those 45 minutes, an occupancy of 80% is planned. The capacity used is 60 × 0.75 × 0.80 = 36 minutes per person.
| Strip | Expected calls | Load | Division | Estimated people |
|---|---|---|---|---|
| 9:00–10:00 | 8 | 48 minutes | 48/36 = 1.33 | 2 |
| 10:00–11:00 | 12 | 72 minutes | 72/36 = 2 | 2 |
| 11:00–12:00 | 18 | 108 minutes | 108/36 = 3 | 3 |
The data is invented to reproduce the operation. The table estimates planned capacity, it does not demonstrate that two people will answer all calls in an hour nor does it recommend hiring three permanent positions.
What changes if the conversation lasts longer
In the period of twelve calls, if the conversation and subsequent work add up to eight minutes, the load increases to 96. The division 96/36 = 2.67 requires three people with the same assumptions. Reviewing duration and subsequent work can be as relevant as looking at volume.
Separate query types if they have different loads. A new quote and a short confirmation should not share a average without reviewing your mix. You can calculate each type separately and add their minutes in the slot.
The main limit: simultaneity
Twelve calls spread over an hour behave differently than twelve calls that arrive together. The above formula adds work, but does not model the order of arrival, customer patience, number of lines or distribution of durations.
Therefore, it contrasts shorter strips, simultaneous peaks and calls that exhausted the wait. If you need to commit a service level, use an appropriate queuing model with its assumptions and validation; this division is not an Erlang C calculation.
Convert the estimate into a testable shift
- Prepare a week with the people really available per slot.
- Identify where you can reinforce another team and what queries you know how to resolve.
- Set aside time to return pending items and do any subsequent work included.
- Compare expected load, offered calls, answered calls and observed waiting.
- Adjust duration, dedication and coverage when the data contradicts the assumption.
A phone system can help you see activity and distribute calls, but it does not create human availability. First define the turn; then configures a queue with output . If the demand comes from campaigns, also check your time schedule .
Sources and limitations
Documentary review: . Content type: Calculation with fictional data.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- Call History guidesupport.aircall.io
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
AircallOfficial plans and termsCloudTalkAffiliate linkThe labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.