Calls Per Hour - CPH: Definition, Formula and Why It's Misused
Calls Per Hour (CPH) — also referred to as contacts per hour — is the number of calls a contact centre agent handles divided by the time they were signed in. It is one of the simplest measures of agent throughput available, and one of the most widely misused as a performance metric.
CPH tells you how many calls an agent took per hour. What it cannot tell you is whether those calls were resolved well, whether the agent had any control over how many calls arrived, or whether a higher number actually represents better performance. Used as a standalone individual KPI, CPH creates perverse incentives and measures the wrong things.
For a fairer, more meaningful measure of agent productivity that accounts for the occupancy environment agents work in, see True Calls Per Hour (TCPH).
What CPH measures
The raw number of calls an agent handles per hour of signed-on time. Simple to calculate, but heavily influenced by factors the agent cannot control.
The core problem
Agents do not control how many inbound calls they receive. CPH is driven by occupancy, shift timing, team size, and call arrival patterns — not individual effort or skill.
The better alternative
True Calls Per Hour (TCPH) normalises CPH for occupancy, enabling fair comparison across different shifts, teams, and locations. Combined with quality data, it is a far more meaningful measure.
What is Calls Per Hour (CPH)?
Calls Per Hour (CPH) is a contact centre metric that measures the total number of calls an agent handled during a period divided by the number of hours they were signed in and available. It is a raw count of throughput — how many calls passed through an agent's hands per hour of their shift.
CPH is sometimes called contacts per hour, transactions per hour, or productivity rate depending on the organisation and platform. In all cases, the underlying calculation is the same: calls handled divided by time available.
In plain English
CPH answers one question: how many calls did this agent take per hour? It says nothing about whether those calls were handled well, whether the agent had any control over the volume, or whether a higher number actually means better performance.
The Calls Per Hour Formula
The CPH formula is straightforward:
For example, an agent who handled 30 calls during 2 hours of signed-on time has a CPH of 15.
What is included in signed-on time
Signed-on time is the total period the agent was logged into the contact centre system and available to receive calls — including talk time, after call work, and idle/waiting time between calls. It typically excludes breaks, training, and meetings where the agent is not in the queue.
What "calls handled" means
Generally refers to inbound calls answered and completed. Most contact centres exclude very short calls (disconnections, misdialled calls) below a defined threshold — though the exact definition varies by organisation and platform configuration.
Why CPH is Flawed as an Individual Performance KPI
The fundamental problem with using CPH to measure individual agent performance is that agents working inbound service level-based contacts — phone calls, chats, walk-ins — do not control how many contacts they receive. The number of calls arriving at any agent is determined by factors entirely outside their control.
❌ Occupancy is not in the agent's control
An agent's occupancy rate — the percentage of their signed-on time spent on call-related activity — is driven by call volume, staffing levels, and service level targets set by management. An agent on a peak shift will naturally have higher CPH than an agent on a quiet overnight shift, regardless of their individual skill or effort. Comparing their CPH as a performance measure is fundamentally unfair.
❌ High CPH can mean poor quality
An agent who rushes calls, cuts conversations short before issues are resolved, or fails to capture accurate notes will have a high CPH. So will an agent who is genuinely efficient. CPH cannot distinguish between the two. Rewarding high CPH without quality oversight actively incentivises the wrong behaviour.
❌ Shift timing creates unfair comparisons
Peak shifts generate more calls. Overnight or weekend shifts generate fewer. An agent who always works the busy morning shift will always show higher CPH than an agent who works Sunday nights — even if the Sunday agent is working faster and handling calls more effectively.
❌ Call complexity is invisible
A short, transactional call has a very different handle time from a complex complaint or technical support call. An agent who handles mostly simple contacts will achieve much higher CPH than one dealing with complex cases — but neither is necessarily more productive. CPH makes no adjustment for call type or complexity.
CPH vs True Calls Per Hour — What's the Difference?
True Calls Per Hour (TCPH) directly addresses the core flaw of CPH by normalising an agent's call count against the occupancy rate they experienced during the period. The result is not a count of how many calls they handled — it is the rate at which they were working, expressed as the number of calls they would have handled if their occupancy had been 100%.
Calls Per Hour (CPH)
Formula: Calls ÷ Signed-on time
What it tells you: How many calls the agent took per hour
What it misses: Whether they had any control over that number — occupancy, shift timing, team size, and call arrival patterns all affect CPH regardless of agent behaviour
Best use: High-level operational reporting — not individual performance management
True Calls Per Hour (TCPH)
Formula: Calls ÷ Occupancy rate
What it tells you: The rate at which the agent was working, normalised for the occupancy environment they were in
What it misses: Still says nothing about call quality — must be paired with a Quality Range and quality monitoring data
Best use: Fair comparison across shifts and locations — as a diagnostic tool, not an individual target
A practical example
Agent A handles 22 calls at 87% occupancy on a busy day shift. Agent B handles 13 calls at 46% occupancy on a quiet night shift.
Raw CPH: Agent A (22 calls) appears far more productive than Agent B (13 calls).
TCPH: Agent A = 22 ÷ 0.87 = 25.3. Agent B = 13 ÷ 0.46 = 28.3. Agent B was actually working at a faster rate — CPH told exactly the wrong story.
Appropriate Uses of CPH
CPH is not without value — it is just frequently used for the wrong purpose. There are legitimate contexts where raw CPH provides useful information.
✓ Where CPH adds value
- High-level operational reporting at the team or centre level
- Capacity planning — understanding overall throughput at aggregate level
- Trend monitoring — are we handling more or fewer calls per agent over time at similar occupancy?
- Comparing outbound dialler campaigns where agents have more control over contact rates
- As a contextual input alongside occupancy data, quality scores, and other metrics
✕ Where CPH should not be used
- As a standalone individual agent KPI or performance target
- To compare agents on different shifts without occupancy adjustment
- As the basis for performance ratings, bonuses, or incentives
- To compare agents handling different call types or complexity levels
- Without pairing with quality and outcome data
Frequently Asked Questions About Calls Per Hour
What is a good calls per hour rate?
There is no meaningful universal benchmark for CPH because the figure varies enormously based on call type, average handle time, and occupancy environment. A contact centre handling short transactional calls might see CPH in the 20–40 range; a complex technical support operation might see 6–12. The number is only useful when compared within the same context — same call type, similar occupancy levels, similar shift conditions. Comparing CPH across different environments without adjustment is not meaningful.
Is CPH the same as calls per hour productivity?
CPH measures throughput — how many calls were handled per hour. Productivity is a broader concept that encompasses both volume and quality. High CPH with poor first contact resolution, low CSAT, and high repeat call rates is not productive — it is expensive. True productivity in a contact centre requires measuring both the rate of work (TCPH is better than CPH for this) and the quality of outcomes.
Can I use CPH to compare agents on different shifts?
Not meaningfully — not without occupancy adjustment. An agent on a peak morning shift will almost always have higher CPH than an agent on a quiet overnight shift, regardless of how they are performing. To compare agents fairly across different shifts or locations, use True Calls Per Hour (TCPH), which normalises for the occupancy environment each agent worked in.
What is the difference between CPH and TCPH?
CPH is calls handled divided by signed-on time — a raw count. TCPH is calls handled divided by the occupancy rate — a normalised rate that removes the influence of how busy the environment was. Two agents can have very different CPH figures but the same TCPH, meaning they were working at the same rate in different occupancy environments. TCPH is the fairer measure for cross-shift and cross-site comparison. See the full TCPH guide for detail.
Should CPH be a KPI for contact centre agents?
No — not as a standalone individual KPI for inbound service level-based contacts. Agents do not control how many inbound calls they receive. Setting CPH as a personal target creates pressure to rush calls, cut conversations short, and prioritise volume over quality. The best contact centres do not target agents on call quantity for inbound contacts. If you want to measure productivity fairly, use TCPH alongside quality and outcome data with a defined Quality Range.
Where to Next
Summary: Calls Per Hour
Calls Per Hour is a simple measure of agent throughput — total calls handled divided by signed-on time. It is easy to calculate, easy to report, and widely used. It is also widely misused as an individual performance target in contexts where it is neither fair nor meaningful.
For inbound service level-based contacts, agents do not control how many calls arrive. CPH is driven by occupancy, shift timing, team size, and random call arrival patterns. Targeting agents on raw CPH creates pressure to rush calls and prioritise volume over quality — the opposite of what good contact centre management should achieve.
The better alternative is True Calls Per Hour (TCPH) — which normalises call counts for occupancy and, when combined with a defined Quality Range and quality monitoring data, provides a genuinely useful picture of how productively agents are working. Use CPH for operational reporting at the team level. Leave it off individual agent scorecards.


















