Call Center Outsourced evidence brief · Desk review · Published
When does an occupancy target mislead a queue review?
A review of occupancy as a diagnostic, with the denominator, the interval view, and the service measures that keep it honest.

On this page
- Key stats
- Key takeaways
- Question and scope
- What the evidence supports
- Define occupancy precisely
- Check the denominator
- Separate productive and available time
- See what occupancy hides
- Compare intervals, not averages
- Pair occupancy with service level
- Watch the multi-channel effect
- Review after-call work
- Check the shrinkage assumption
- Test a small staffing change
- Avoid a target that rewards burnout
- Report the range
- Use occupancy to ask a question
- Document the measure
- Review the target with the client
- Limits of the evidence
- Manager review questions
- Conclusion
- Put this into a support lane
- Related operating guides
- FAQs
- Sources
Key stats
- 2.67 million U.S. customer service representative jobs in 2025 (BLS)
- $21.53 median hourly wage in May 2025 (BLS)
- 289,500 projected annual openings, 2025 to 2035 (BLS)
Key takeaways
- Write the occupancy numerator and denominator and apply them to every team.
- Check the available-time denominator for meetings, coaching, and system downtime.
- Read occupancy by interval with the service level, not as a monthly average.
- Test one break or shift move before changing the whole schedule.
Question and scope
This brief asks when an occupancy target misleads a contact center queue review. The population is one queue and one review period, and the unit is an interval of scheduled agent time. The question is whether a high or low occupancy number supports the conclusion a manager wants to draw. The analysis covers definitions, denominators, and paired measures, not the design of an incentive plan. Record the queue, the interval, and the source of the hours before comparing targets.
What the evidence supports
Contact-center standards call for forecasting, scheduling, and performance measurement, but they do not set one occupancy target for every queue. Federal wage-and-hour guidance requires accurate records of hours worked and rest periods. The operating inference is to use occupancy as a question about the balance between work and available time, not as a score on its own. A number without the service result and the interval pattern can point to the wrong fix.
Define occupancy precisely
Write the numerator and denominator in plain language. Occupancy is usually the time agents spend handling contacts divided by the time they are available to handle contacts. Decide whether after-call work, hold time, and internal calls count as handling. Apply the same definition to every team in the comparison. A definition that changes between reports makes the trend meaningless. Keep a worked example beside the definition.
Check the denominator
A high occupancy can come from a small denominator rather than a large workload. Check whether the available time includes meetings, coaching, and system downtime. If those hours are excluded, the queue will look busier than it is. Reconcile the scheduled hours with the timekeeping record before drawing a conclusion. Ask for the raw hours when the report only shows a percentage.
Separate productive and available time
An agent can be busy with after-call work and unavailable for the next call. That is productive time, but it is not the same as talk time. Show the components beside the occupancy figure so the reader can see where the time went. A queue that is busy with wrap work may need a process fix, not more agents. Use the same category names in every interval report.
See what occupancy hides
A high occupancy can hide a long queue because the agents are working as fast as they can. A low occupancy can hide a skill mismatch because the right agents are idle while a specialty queue waits. Occupancy says how full the agents are, not whether the customer is being served. Pair it with the wait time and the abandon rate before acting.
Compare intervals, not averages
A monthly average can look healthy while the morning peak is overloaded and the afternoon is overstaffed. Plot occupancy by interval for a representative week and mark the service level in the same chart. The pattern often shows a scheduling problem that the average conceals. Use the interval view when deciding whether to move a break or add a shift.
Pair occupancy with service level
A target that raises occupancy without a service target can push agents to rush calls or skip after-call work. A service target without occupancy can hide idle capacity that the client is paying for. Show both, plus the abandon rate and the repeat contact rate. The review should discuss the tradeoff, not one number in isolation. Choose the target pair before the review, not after.
Watch the multi-channel effect
An agent handling chat and voice at the same time can show high occupancy while one channel waits. The systems may count concurrent contacts differently, which distorts the ratio. Define how concurrency is treated and keep the channel results separate. A blended figure can make a broken channel look busy. Test the concurrency rule with a sample of agents. Ask the platform vendor how concurrency is counted in the occupancy export.
Review after-call work
After-call work is part of the handling time, but it can also be a sign of a slow system or a missing template. Measure the wrap time beside the occupancy and the handle time. If wrap time is long, the fix may be a form or a knowledge article, not more staff. Reducing wrap time can lower occupancy while improving service.
Check the shrinkage assumption
Occupancy uses available time, and available time depends on shrinkage. If the plan assumes less shrinkage than the queue actually experiences, the occupancy target will be wrong from the start. Compare the planned and actual shrinkage for the same period. A gap there can explain a service failure without any change in agent effort. Name the assumption in the report so the reader can check it.
Test a small staffing change
Before rewriting a schedule, move one break or add one agent in a single interval. Measure the occupancy, the wait, and the abandon rate for that interval and a comparable one. A small test is cheaper than a full schedule change based on a monthly average. Record the result and the date. Keep the change for at least two weeks before judging it.
Avoid a target that rewards burnout
A target that pushes occupancy toward the limit leaves no room for coaching, breaks, or a system problem. It can also reward agents who skip rest periods or avoid difficult calls. Set the target with the service result and the legal rest rules in view. A queue that meets an occupancy goal by burning out the team is not healthy.
Report the range
Give the client the occupancy range across intervals, not only the average. Mark the intervals that failed the service target and the ones that had idle capacity. Show the sample and the period. A range makes the tradeoff visible and gives the client a fair basis for a decision. Note the intervals that had too few calls to judge. Keep the range in the client report, not only the peak figure.
Use occupancy to ask a question
Treat a high or low number as the start of a review. Ask which interval, which channel, and which request type produced it. Read a sample of calls and check the after-call work. The answer should lead to a specific change, such as a schedule move, a template, or a routing rule. Write the answer in one sentence with the evidence beside it.
Document the measure
Write the definition, the source, the interval, and the treatment of exceptions in the report. Note any change to the system or the schedule during the period. A later reader should be able to reproduce the number. An undocumented change makes a comparison unsafe. Attach the export and the date it was pulled. Name the system and the export used in the footnote.
Review the target with the client
Ask the client what decision the occupancy target is meant to support. If the goal is cost control, pair it with the service level. If the goal is service, pair it with the wait and the abandon rate. A target without a decision is a number that invites argument. Review the pair of targets at the next quarterly meeting. Ask the client which decision the target is meant to support this quarter.
Limits of the evidence
This brief cannot set the right occupancy for a specific queue, because the answer depends on the arrival pattern, the service target, the channel mix, and the cost model. The measure can show where the time went, but it cannot prove that an agent worked well. Use the result to frame a test, not to settle a performance dispute. State the period and the queue in the conclusion.
Manager review questions
Managers should ask which denominator was used, which intervals failed, and what the service level did in the same period. They should also ask whether after-call work or a system problem explains the pattern. The remaining question is which small change will be tested first. Record the answers with the interval data. Keep the answers with the interval report. Use the same definition when the target is reviewed next time.
Conclusion
Occupancy misleads when it is read alone, averaged over a month, or built on a denominator nobody checked. Use it with the service level, the interval pattern, and the after-call work. Test a small schedule change before rewriting the plan. The measure is useful when it leads to a specific question about the queue, not when it becomes the goal.
Put this into a support lane
Bring the current queue rules, the shift handoff, and one week of cases so the review can test a real promise.
Review the queue designRelated operating guides
FAQs
Is high occupancy always good?
No. It can mean the queue is understaffed and agents have no time for coaching, breaks, or a system problem. Pair it with the service result.
Should after-call work count as occupancy?
Usually yes, as handling time. Show it separately so a long wrap time points to a process fix rather than a staffing fix.