Use one shared KPI definition
Teams often compare numbers built on different assumptions. Standard definitions keep planning decisions reliable.
- Centralize input definitions.
- Keep time windows and scope aligned.
- Compare only like-for-like metrics.
Free tool
Agent occupancy calculator
Calculate per-agent occupancy pressure and spot over- or underload instantly.
Balance workload and buffer per agent
This calculator combines occupancy pressure with realistic productive time assumptions.
Map output to intervention thresholds
A metric without an action path is just reporting. Tie each score range to an explicit team action.
- Normal range: monitor.
- Warning range: rebalance.
- Critical range: escalate immediately.
Review output on fixed cadences
KPI impact improves when teams discuss results in recurring lead and operations checkpoints.
- Daily operational check.
- Weekly trend review.
- Monthly threshold optimization.
What agent occupancy actually measures
Occupancy is contact time divided by the time genuinely available for contact. The word travels across industries and that causes confusion: in facilities it describes used floor space or desks, in manufacturing it describes used machine capacity. This calculator only measures people time in a support team.
- Contact time = tickets, chats and calls, including the wrap-up work that follows.
- Available time = scheduled hours minus breaks, meetings, training and system downtime.
- Occupancy and utilization are not interchangeable; utilization divides by all paid time and lands lower.
Working out occupancy step by step
The arithmetic is short enough to do on paper, which matters when you want to sanity-check what a workforce tool tells you. Required hours = tickets × average handle time / 60.
- Example: 600 tickets a week × 8 minutes = 4,800 minutes, so 80 hours of handling work.
- At 30 productive hours per person that is 80 / 30 = 2.7, rounded up to three agents as your floor.
- Use productive hours after breaks and meetings, never contracted hours — that single substitution is what makes most staffing plans too thin.
From hours to headcount and staff ratio
Occupancy tells you how hard the current team is working. Headcount and staff ratio tell you how many people to roster. Keep the two calculations separate or the same meeting ends up arguing about two different numbers.
- Headcount floor = required hours / productive hours per full-time agent, rounded up.
- A staff ratio against orders or active customers is only useful as a trend for your own shop; ratios copied from a larger operation rarely transfer.
- Add a margin for leave, sickness and turnover. A team that fits exactly on paper collapses the first time someone is out.
What quietly pushes occupancy up
In ecommerce the pressure rarely comes from ticket count alone. The spikes come from work that never lands in the count as a separate ticket but still eats the day — and a smaller team feels it first.
- Repeat contact on the same order counts twice: every follow-up costs handle time again.
- Channel switching on one problem — email, then chat, then phone — doubles the work without moving your ticket count.
- Looking up order data in another system sits outside your handle-time measurement but inside the working day. Put order context beside the conversation and that gap closes.
- Promotions and holidays shift occupancy within a single week, so switch to a daily calculation before peak season rather than after it.
Enter KPI context
Calculation method
- 1) Required hours = tickets × handle time / 60
- 2) Occupancy = required hours / productive hours
- 3) Productive share = productive hours / scheduled hours
How to use this calculator in your KPI routine
-
1. Input current operational data
Use recent data from the same period and team scope.
-
2. Check output against your targets
Compare the score with your agreed KPI thresholds.
-
3. Pick the immediate next action
Map the result to a staffing, process, or communication action.
-
4. Repeat on a fixed cadence
Re-run consistently to track trend and intervention impact.
Next step
Turn this KPI into a workflow decision
Tool pages are often the first touchpoint. Use the result, but move the team to pricing, workflow setup, and live execution fast.
Open the practical guide behind the metric
Move from calculator output to the playbook that explains which workflow, staffing, or quality changes to make next.
Support capacity planning guideSee which plan fits your team
Check pricing, plan fit, and what your team gets when you move from spreadsheet math to operational execution.
View pricingChecklist for reliable KPI decisions
- Inputs come from a recent and comparable period.
- Team and channel scope is aligned in advance.
- Calculation is tied to explicit thresholds.
- Output maps to concrete next actions.
- Trend is recalculated and reviewed regularly.
Related tools
Supporting guides
Frequently asked questions
What occupancy range is healthy?
There is no benchmark that transfers between teams, because the number depends entirely on which denominator you use and how complex your cases are. Measure your own range across a few normal weeks, note what your team says about the workload at each level, and use that as your reference point. A figure copied from another company tells you nothing about yours.
Why include productive share?
Because scheduling assumptions are often too optimistic.
What if capacity buffer is negative?
Rebalance workload, reduce inflow pressure, or add capacity.
What does agent occupancy mean?
Agent occupancy is the share of available working time an agent actually spends on customer contact, including the wrap-up work after a conversation. It is not the same as being scheduled: someone can be rostered for a full day and still run a low occupancy because meetings, training and idle waiting fill the hours.
How do I calculate occupancy rate?
Add up the time spent handling tickets, chats and calls in a defined period, then divide it by the productive hours in that same period. Without per-conversation time tracking, use tickets multiplied by average handle time as a stand-in. Calculate it per day or per week, because a monthly average hides exactly the peaks that break a small team.
What is the difference between occupancy and utilization?
Occupancy divides contact time by the time an agent is genuinely available for contact. Utilization divides productive time by all paid time, so breaks, training and admin drag it down. Two teams quoting "85%" can therefore mean completely different things — always state which denominator you used.
How do I calculate a support staff ratio?
Divide the required handling hours for a period by the productive hours one full-time agent delivers in that period, then round up. For a ratio against order volume or active customers, divide that headcount by the volume figure and track the ratio over time rather than treating a single value as a target — the ratio that fits a shop selling one product line will not fit a multi-brand catalogue.
Is this the same as office occupancy or occupant load?
No, and the overlap in wording sends a lot of people to the wrong calculator. Building occupancy, occupant load and "how many people fit in a 2,000 sq ft office" are floor-space questions: they divide area by a square-footage-per-person figure, and occupant load specifically comes from fire and building codes, which vary by jurisdiction and by room use — a restaurant dining area and an office are rated differently. For anything code-related, check your local building regulations or ask a building inspector; this is not building-code advice. This calculator measures something else entirely: how hard a support team is working within its available time. The inputs are hours and tickets, not floor space, and the output says nothing about how many desks you need.
How many support agents do I need for a team of a given size?
Headcount rules of thumb quoted per company size travel badly, because they assume a contact rate you may not share. Work it from your own inflow instead: take your conversation volume for a period, multiply by your average handle time to get required hours, then divide by the productive hours one full-time agent actually delivers in that period — the calculator above does exactly this. Recalculate for your peak week rather than your average one, because that is the week that decides whether the queue holds. The same method answers internal support ratios, but a support team and an HR or IT team carry different work per employee, so do not reuse one ratio for the other.
How do I work out the cost of a support agent per hour?
Take the full employer cost for that agent over a year — salary plus employer contributions, holiday allowance, pension and insurance — and divide it by the productive hours you entered above, not by contracted hours. Using contracted hours understates your true hourly cost. This is not tax or accounting advice; have your accountant confirm which employer charges apply to you.
What occupancy is realistic during peak season?
Lower than in quiet months, and that is the point. Peak queues bring more interruptions, more escalations and more context switching, so a target that was healthy in March burns agents out in November. Plan peak staffing with a buffer instead of holding the steady-state occupancy target all year.
