Agent occupancy · Documentation-based guide with original exercise

Agent occupancy and utilisation: two time denominators

Content updated:

Scope: Documentation reviewed on 15 October 2026. Examples are fictional and tests are proposed; CallsIQ has not performed product tests.

Short answer

Occupancy compares handling with time available for handling under an explicit definition. Utilisation may use the whole shift. These differ. Partition intervals without overlapping conversation, hold, after-call work and other tasks; being logged in does not establish readiness for another call.

Key verification: Intervals sum to the stated shift and both percentages reproduce from their different bases.

Sources and limitations

One report shows 75% and another 62.5%. Different denominators can explain the difference. This guide partitions a fictional shift to show why. It sets no performance target and does not justify equating spare capacity with lack of effort.

Define handling scope

Include selected components once. Do not add hold or after-call work again if already within handling. Keep breaks, training and administration separate when excluded from availability. The catalogue should explain every state and treatment of unrecorded intervals.

Fictional 480-minute shift

Agent occupancy and utilisation: two time denominators: table 1
Exclusive intervalMinutes
Call handling300
Available without handling100
Other activities and breaks80
Total480

Under these rules, occupancy = 300 / (300 + 100) = 75%. Shift utilisation for handling = 300 / 480 = 62.5%. Neither establishes quality or resolution. For different agent hours, aggregate compatible minutes first rather than averaging unweighted percentages.

Reconstruction with CloudTalk

CloudTalk documents status-interval exports in Agent Report. They may support time review; native percentages are not claimed to use this exercise’s formula. Inspect filters, custom states, period boundaries and interval starts and ends.

Using the metric

Investigate demand and activity differences before comparing people. A busy shift does not establish good service, and reserve capacity may be needed. CallsIQ has not analysed a real CloudTalk shift. A well-defined interval worksheet may suffice for a small team.

Sources and limitations

Documentary review: . Content type: Documentation-based guide with original exercise.

Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.

How to report a correction

Check current terms

Consider these options if they solve the problem described. Confirm features, limits and availability in your country.

CloudTalkAffiliate link

The labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.

How this guide was prepared

Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.