What it means
A support team has eight-hour paid shifts, but agents are not handling customer contacts for all eight hours, because time goes to breaks, coaching, training, system issues and waiting for the next contact. Utilisation asks how much of the chosen capacity is used for the work defined in the numerator.
NiCE describes utilisation as work produced relative to work capacity, noting that breaks, vacation and sick days can complicate measurement, while its separate occupancy definition focuses on time handling interactions relative to logged-in time. Start by writing down the denominator, since paid hours include more than time logged into a contact platform, logged-in hours exclude time when an agent is away from the platform, and scheduled contact-ready hours may exclude meetings, training and breaks.
Next define the numerator: handling time usually includes conversation and related follow-up work, some teams also include approved back-office work, and a broad numerator will produce a higher rate without any change in customer service. A reporting tool may use different labels, so read its data dictionary.
For a paid-time view, an agent paid for eight hours who spends 5.6 hours handling contacts and their follow-up has 70% utilisation. This does not imply that the remaining 2.4 hours were wasted, since they may contain scheduled breaks, learning or a reserve for unexpected demand.
For a logged-in occupancy view, suppose the same agent was logged in for seven hours: 5.6 hours of handling then gives 80%, so the two values answer different questions even though they describe one shift. Use the rate with service measures.
High utilisation may cut apparent cost per contact but leave too few agents ready for sudden arrivals, so customers wait longer, abandon the queue or receive rushed service, and response time, abandonment and quality should be examined together. Watch employee experience too, because a steady stream of contacts without recovery time can make demanding work harder to sustain, and a manager should examine schedule adherence, absences and feedback, not only a single productivity percentage.
At team level, weight the calculation by time. The average of two agents' percentages can mislead when one works a full shift and another works a short shift, so sum eligible handled hours and eligible capacity hours before dividing.
Clean up data status codes as well: if an agent is marked ready while attending a meeting, idle time rises incorrectly, and if after-contact work is marked as handling indefinitely, the opposite happens, so audit status transitions against schedules and case records. For an owner, the useful question is whether the team has enough capacity to serve customers well at a sensible cost.
Agree on the definition, review the drivers and investigate outliers before treating a higher utilisation number as an automatic win.
In practice
Real-world examples.
Example
A helpdesk logs 560 customer-handling hours against 800 defined paid-capacity hours in a week. On its stated paid-time basis, team utilisation is 70%. Breaks and training remain in the denominator.
Example
An agent spends 5.6 hours handling contacts during seven logged-in hours. A separate logged-in occupancy measure is 80%, even though a paid-eight-hour utilisation measure for the same work is 70%.
Example
A chat team appears to record nine contact-hours in an eight-hour shift because three simultaneous chats have overlapping timestamps. The manager fixes the measure to count agent work time rather than summing each chat's elapsed duration.
Formula
Calculation
Illustrative paid-time utilisation = eligible contact-handling and follow-up hours / defined paid-capacity hours x 100. Example: 560 / 800 x 100 = 70%. A logged-in occupancy version uses logged-in or available platform hours under the tool's own definition; do not silently swap denominators.Case study
Seen in the real world.
This entirely fictional case follows Northbank Support, an invented software helpdesk. Its weekly paid-time utilisation rose from 69% to 86% after a hiring freeze. Managers celebrated lower apparent cost per ticket, but unresolved requests and evening overtime increased.
The team checked arrival peaks, support quality and status codes. It scheduled cross-trained cover during the busiest hours, protected training time and reported customer wait alongside utilisation. The company and figures are invented; the case does not prescribe a universal target.
Watch out
Common mistakes.
- Calling logged-in occupancy and paid-time utilisation the same measure.
- Adding the elapsed duration of concurrent chats as if an agent worked those hours sequentially.
- Raising the utilisation target without watching queue delays, service quality and staff strain.
Questions
People also ask.
What is the difference between utilisation and occupancy?
Labels vary by tool. Often occupancy uses logged-in handling time, while utilisation compares defined work with broader work capacity; confirm each denominator.
Is there a universally good percentage?
No. Channel mix, case complexity, breaks and service goals change the useful range.
Can a high rate indicate a problem?
Yes. Persistent high load can leave little room for arrival peaks, recovery, training or careful follow-up.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%