Call Center Occupancy Calculator
Free call center occupancy calculator: occupancy rate from handle and available time, or Erlang C occupancy at N agents. Formula, example, vs utilization.
Optional, for the utilization comparison
Everything runs in your browser. The inputs are saved in the page link, so you can share the result.
Results
Updates live
Occupancy
80.0%
Handle ÷ (handle + available)
The same agent-day under three published definitions
- Logged-in ÷ shiftROI CX and Guideway call this utilization
- 93.8%
- Handle ÷ paid timeOur staffing calculator's utilization
- 65.0%
- Handle ÷ all logged-in timeGuideway's occupancy denominator
- 69.3%
Write the formula next to the number. The staffing calculator uses handle ÷ paid time.
How this is calculated
In "From your actuals" mode it divides total handle time (talk, hold and after-call work) by handle time plus the time agents sat available waiting for a contact. In "Forecast at N agents" mode it converts calls per interval and handle time into traffic in Erlangs and divides by the agents on phones, then shows the service level and average speed of answer at that headcount using the same Erlang C math as our Erlang C calculator. Everything runs in your browser.
What call center occupancy measures
Call center occupancy is the share of agents' available, logged-in time spent handling contacts: handle time ÷ (handle time + idle available time). Enter your totals to get the rate, or enter calls, handle time and agents to get Erlang C occupancy. For example, 312 handle minutes out of 390 available is 80%. Call Centre Helper warns that above 85%, agents will likely burn out.
Handle time means talk, hold and after-call work. If AI changes what reaches your agents, see how handle time shifts after AI before you trust a before-and-after comparison.
Occupancy vs utilization
Occupancy measures how busy agents are while available to take contacts. Utilization measures how much of paid or scheduled time goes to the work you track. Sources define both differently, so pick one formula, write it next to the number, and never compare numbers built different ways.
| Term | Published wording | Source |
|---|---|---|
| Occupancy | "the percentage of time that all call centre agents spend handling customer contacts" | Call Centre Helper |
| Occupancy | "Total Handling Time / (Total Handling Time + Available Time) x 100" | ROI CX Solutions |
| Occupancy | "Total amount of time spent on call by an agent / Total time spent logged in * 100" | Guideway Care |
| Occupancy | Call-related time divided by "scheduled time to talk with customers" | Verint |
| Utilization | "Total Logged In Time / Total Shift Time x 100" | ROI CX Solutions |
| Utilization | "Total time spent logged in / Total amount spent on shift * 100" | Guideway Care |
| Utilization | "the share of paid working time spent on tickets" | RTCI staffing calculator |
Sources: Call Centre Helper, "Erlang C Formula: Made Simple"; ROI CX Solutions, occupancy vs utilization; Guideway Care, occupancy vs utilization; Verint, calculating occupancy rate.
Call center occupancy formula
- From actuals: occupancy = handle time ÷ (handle time + available time) × 100
- Forecast: occupancy = A ÷ N, where A = calls × AHT ÷ interval length (traffic in Erlangs) and N = agents on phones
- Calls N agents can take at 85% occupancy: 0.85 × N × interval ÷ AHT, rounded down
Forecast mode uses the same Erlang C math as the Erlang C calculator for service level and average speed of answer. When N is at or below A, the queue grows without limit and no occupancy figure is valid.
Worked example A: one agent-day from actuals
An 8-hour paid shift is 480 minutes. The agent spends 312 minutes on talk, hold and after-call work, 78 minutes ready and waiting, 60 minutes in meetings, coaching and admin, and 30 minutes logged out on a break.
| Definition | Calculation | Result |
|---|---|---|
| Occupancy | 312 ÷ (312 + 78) = 312 ÷ 390 | 80.0% |
| Logged-in ÷ shift | (312 + 78 + 60) ÷ 480 = 450 ÷ 480 | 93.8% |
| Handle ÷ paid time | 312 ÷ 480 | 65.0% |
| Handle ÷ all logged-in time | 312 ÷ 450 | 69.3% |
The same day reads as 65%, 69%, 80% or 94% depending on the definition. State the formula next to the number every time.
Worked example B: Erlang C occupancy at N agents
100 calls per 30 minutes with a 180-second handle time gives A = 100 × 180 ÷ 1,800 = 10 Erlangs. With a 20-second answer target:
| Agents | Occupancy | SL ≤ 20 s | ASA |
|---|---|---|---|
| 11 | 90.9% | 38.96% | 122.8 s |
| 12 | 83.3% | 64.02% | 40.4 s |
| 13 | 76.9% | 79.56% | 17.1 s |
| 14 | 71.4% | 88.84% | 7.8 s |
| 15 | 66.7% | 94.15% | 3.7 s |
Fourteen agents run at 71.4% occupancy. Volume would have to reach 0.85 × 14 × 1,800 ÷ 180 = 119 calls per 30 minutes to push them to 85%, and at that load service level drops to 63.5% (ASA 39.6 seconds). The 80/20 target already fails at 109 calls, with service level at 79.6% and occupancy at 77.9%. On a small queue, service level breaks before occupancy reaches the burnout line.
AI deflection lowers occupancy first
Let an AI agent fully handle 30% of calls before they reach the queue. Offered calls fall to 70 and traffic to 7 Erlangs. Keep 14 agents and occupancy falls from 71.4% to 50.0% (service level 99.35%, ASA 0.4 seconds).
Re-plan for 80% in 20 seconds and 10 agents are enough, at 70.0% occupancy (service level 84.11%, ASA 13.3 seconds). So 30% containment removes 4 of 14 agents on phones, 29% rather than 30%. Headcount only follows if you re-plan. Count only calls that never reach a person: a deflected contact is not a resolved one.
The 85% line
85% is a convention from practitioners, not a measured standard. None of the ranking pages cite a study.
- Call Centre Helper (Jonty Pearce): "If you have an occupancy of more than 85%, your agents will likely get burnt out", and "Average Handling Time (AHT) may rise to cover it."
- Call Centre Tools warns against taking occupancy "over 85% - 90% for long periods".
- Commonly quoted bands with no study cited: 80–90% typical and above 90% a burnout risk (ROI CX Solutions), 80–85% (Guideway Care), 85–95% (Verint).
The calculator's 70% lower edge is an RTCI display band, not a benchmark. Below it, agents spend a lot of time waiting.
Related RTCI tools and guides
- Erlang C Calculator
Agents needed for a service-level target, with shrinkage and an occupancy cap.
- Customer Support Staffing Calculator
Monthly headcount for email and ticket queues, using handle time ÷ paid time.
- Support Ticket Volume Forecast Calculator
Forecast the volume, then check occupancy at your headcount.
- Reduce AI-to-human escalations without adding headcount
Fewer escalations means fewer contacts reaching the queue.
Frequently asked
How is call center occupancy calculated?
Divide the time agents spent handling contacts (talk, hold and after-call work) by that handle time plus the time they sat available waiting for a contact, then multiply by 100. 312 handle minutes and 78 idle minutes give 312 ÷ 390 = 80%. In forecasting, occupancy is traffic in Erlangs divided by agents on phones.
What is a good occupancy rate for a call center?
There is no measured standard. Call Centre Helper warns that above 85% agents will likely burn out and AHT may rise to cover it. Below roughly 70% agents spend a lot of time waiting (RTCI's display band, not a benchmark). Large queues can sit higher than small ones at the same service level.
What is the difference between occupancy and utilization?
Occupancy compares handle time with the time agents were available for contacts. Utilization compares work or logged-in time with paid or scheduled time, and its definition varies by source. On the same 8-hour day, occupancy was 80% while utilization was 65% or 94% depending on the definition.
Why does occupancy fall after adding an AI agent?
Contacts the AI fully handles leave the queue but the agents stay. With 100 calls per 30 minutes at 3 minutes each, 14 agents run at 71.4%. If AI contains 30% and nobody re-plans, the same 14 run at 50%. Re-solving for 80/20 needs 10 agents at 70%.
How do shrinkage and occupancy relate?
Shrinkage is paid time agents are not available at all (breaks, training, absence). Occupancy is measured only on the time they are available. Erlang C sets agents on phones from occupancy and service level, then shrinkage grosses that up to the number to schedule: 14 on phones at 30% shrinkage means 20 scheduled.