True Calls Per Hour - TCPH: Definition, Formula and How to Use It
True Calls Per Hour (TCPH) is a contact centre metric that normalises an agent's call handling rate to account for the occupancy environment they worked in — producing a fair, comparable measure of productivity across agents on different shifts, in different locations, or operating under different call volumes.
Unlike raw Calls Per Hour (CPH), which simply counts how many calls an agent handled, TCPH removes the influence of factors outside the agent's control — primarily their occupancy rate, which is driven by call volume, staffing levels, and service level targets. Two agents can handle very different numbers of calls in the same shift and yet be equally productive — or even have the agent who handled fewer calls operating at a faster rate.
This guide covers both CPH and TCPH — what they are, how to calculate them, the important differences between them, how to use TCPH properly (including the essential concept of a Quality Range), and why neither metric should ever be used as a standalone performance target.
What TCPH measures
The rate at which an agent handles calls, normalised for their occupancy level — enabling fair comparison across different shifts, teams, and locations.
Why CPH alone is flawed
Raw call counts are driven by factors agents cannot control — call volume, staffing levels, service level targets. Targeting agents on raw CPH is mathematically unfair.
What this guide covers
CPH vs TCPH definitions, both formulas, a worked example, the Quality Range concept, when to use TCPH, and its limitations.
What is Calls Per Hour (CPH)?
Calls Per Hour (CPH) — sometimes also referred to as contacts per hour — is the simplest measure of agent throughput in a contact centre. It counts the total number of calls an agent handled divided by the total time they were signed in. CPH is covered in more depth in the Calls Per Hour (CPH) glossary term — this guide focuses on TCPH and why it is the more meaningful metric.
For example, an agent who handled 30 calls during a 2-hour signed-on period has a CPH of 15.
In plain English
CPH is simply: how many calls did this agent take per hour? It is a raw count with no adjustment for context — and that is precisely where the problem lies.
Why Raw CPH is a Flawed Agent Metric
The fundamental problem with using CPH as an individual performance metric is that agents do not control how many calls they receive. In an inbound contact centre handling service level-based contacts — phone calls, chats, walk-ins — the volume of contacts reaching any given agent is determined by factors entirely outside their control:
📊 Occupancy rate
An agent's occupancy — the percentage of their signed-on time spent on call-related activity — is a product of call volume, staffing levels, and service level targets. Higher occupancy means more calls per hour, but the agent did not choose their occupancy rate. It was set by the operational environment they worked in.
🕐 Shift timing
An agent working the peak morning shift will almost always handle more calls than an agent on a quiet Sunday overnight shift. Comparing their raw CPH as a measure of performance is meaningless — and unfair.
👥 Team size and the Pooling Principle
Larger teams experience more consistent, predictable call arrival patterns. Agents in a large team will experience more even call distribution than agents in a small team where individual call counts fluctuate more widely. The size of the group affects individual throughput in ways agents cannot influence.
🎲 Random call arrival
Calls arrive randomly. On any given interval, some agents will be busier than others purely by chance. The mathematics of random contact arrival — modelled by Erlang C — means that call distribution is inherently uneven at the individual level. Targeting agents on this variability is mathematically unsound.
What is True Calls Per Hour (TCPH)?
True Calls Per Hour (TCPH) addresses the core flaw of CPH by normalising an agent's call count against the occupancy rate they experienced. The result is not a count of how many calls they handled — it is the rate or speed at which they were working, expressed as the number of calls they would have handled if their occupancy had been 100%.
This normalisation allows fair comparison between agents who worked in very different occupancy environments — for example, an agent on a busy peak shift versus an agent on a quieter off-peak shift. Raw CPH cannot make this comparison fairly. TCPH can.
The key distinction
TCPH does not measure how many calls an agent handled. It measures the rate at which they were working. This is a critical difference. Two agents can handle different numbers of calls and produce the same TCPH — meaning they were working at the same rate, just in different occupancy environments.
The True Calls Per Hour Formula
The TCPH formula divides the number of calls an agent handled by their occupancy rate for the same period:
💡 What this formula actually does
Dividing by occupancy normalises the call count to a common baseline — equivalent to asking: "If this agent had been at 100% occupancy the whole time, how many calls would they have handled at the rate they were actually working?" This removes the occupancy variable and leaves a pure measure of working rate, enabling apples-to-apples comparisons across different environments.
Worked Example — CPH vs TCPH
Consider two agents working the same contact centre, but on different shifts with very different call volumes.
| Metric | Agent A — Day Shift (busy) | Agent B — Night Shift (quiet) |
|---|---|---|
| Calls handled | 22 | 13 |
| Occupancy rate | 87% | 46% |
| Raw CPH view | Agent A appears far more productive | Agent B appears less productive |
| TCPH calculation | 22 ÷ 0.87 = 25.3 TCPH | 13 ÷ 0.46 = 28.3 TCPH |
| TCPH view | Agent B was actually working at a faster rate than Agent A — they just had fewer calls arriving. Raw CPH told the wrong story entirely. | |
What this example shows
Agent A handled 22 calls because their shift was busy — their occupancy was 87%. Agent B handled only 13 calls because their shift was quiet — their occupancy was 46%. Neither agent controlled their occupancy. But when you normalise for it, Agent B was operating at a higher rate (28.3 vs 25.3). A manager using raw CPH would reach exactly the wrong conclusion about which agent was more productive.
The Quality Range — The Missing Piece
Even with TCPH properly understood, there is a critical question the metric still does not answer: what is an appropriate rate?
A high TCPH might mean an agent is highly efficient. Or it might mean they are rushing calls, cutting corners, and delivering poor customer experiences. A low TCPH might mean an agent is slow. Or it might mean they are handling complex calls exceptionally well and generating high first contact resolution.
TCPH alone tells you the rate. It does not tell you whether that rate is appropriate for your operation. That is where the concept of a Quality Range comes in.
What is a Quality Range?
A Quality Range defines the band of TCPH rates that your operation has determined represents the right balance of speed and quality — fast enough to be efficient, not so fast that quality is compromised.
It is established through internal analysis of your own contacts — examining the relationship between handle time, TCPH, and quality outcomes. The right Quality Range is specific to your organisation, your contact types, and your quality standards. It cannot be borrowed from industry benchmarks.
Consider an example. Suppose your contact centre analyses its data and determines that agents operating between 22 and 26 TCPH consistently deliver acceptable quality scores, appropriate handle times, and good customer outcomes. That becomes your Quality Range:
Agent operating below the Quality Range
Could indicate a genuine performance issue — but could also indicate the agent is handling more complex calls than peers, is new and still building proficiency, or is working in a language or context that inherently takes longer. Investigate before drawing conclusions.
Agent operating above the Quality Range
Could indicate they are rushing calls and compromising quality. But could also indicate a genuine improvement or innovation that others could learn from. Always check the quality data alongside TCPH before acting. Don't assume either direction automatically.
💡 The Quality Range in practice
Contact centres that use TCPH well combine it with quality monitoring data. When an agent's TCPH sits outside the Quality Range, it triggers an investigation — not an immediate performance action. The question is always: why? Is it a skills issue, a systems issue, a complexity issue, or an opportunity? The answer shapes the response. This approach, developed by Daniel Ord and covered in the Contact Centre Management Fundamentals course at CX Skills, represents best-practice thinking on how quantity and quality metrics should work together.
When to Use TCPH — and When Not To
✓ Appropriate uses of TCPH
- Comparing agent productivity across different shifts or locations at a management level
- Identifying agents who may be outside an established Quality Range — to trigger coaching conversations
- Analysing performance trends across intervals, days, or time periods
- Comparing teams across sites, regions, or countries at an aggregate level
- Supporting root cause analysis when combined with quality and FCR data
✕ Inappropriate uses of TCPH
- As a standalone individual KPI or performance target for agents
- As the primary basis for performance ratings or incentive calculations
- Without a defined Quality Range — TCPH without quality context is meaningless
- To drive competition between agents based on call volume
- In isolation from customer satisfaction, FCR, or quality data
Limitations of True Calls Per Hour
TCPH is a better metric than raw CPH — but understanding its limitations is essential to using it responsibly.
❌ Tells you nothing about quality
The most important limitation. TCPH measures the rate of call handling — not the quality, outcome, or customer experience of those calls. An agent who handles 30 TCPH may be delivering excellent first contact resolution and high CSAT. Or they may be rushing, failing to resolve issues, and generating repeat calls. TCPH cannot tell you which. Always use alongside quality monitoring and CSAT data.
❌ Depends on accurate occupancy data
TCPH is only as reliable as the occupancy figure used to calculate it. If your ACD or WFM system calculates occupancy inconsistently — for example, including or excluding certain aux codes differently across teams — your TCPH figures will not be comparable. Ensure consistent occupancy definitions before drawing cross-team conclusions.
❌ Not appropriate for all contact types
TCPH works best for service level-based contacts — inbound phone, chat, walk-ins — where agents are generally available and waiting for contacts to arrive. It is less meaningful for email, back-office work, or outbound contacts where the volume relationship works differently.
❌ Can mask contact complexity differences
An agent consistently handling lower complexity contacts will naturally achieve a higher TCPH than an agent handling more complex contacts — even if both are performing equally well. Segment TCPH analysis by contact type or queue rather than applying it bluntly across the whole team.
Frequently Asked Questions About True Calls Per Hour
What is the difference between CPH and TCPH?
CPH (Calls Per Hour) is a raw count of calls handled divided by signed-on time. It does not account for the occupancy environment the agent worked in — meaning agents on busier shifts will always appear more productive. TCPH (True Calls Per Hour) normalises the call count against the agent's occupancy rate, producing a rate that can be fairly compared across different shifts, locations, and occupancy environments.
Is it fair to target agents on calls per hour?
No — and this applies to both raw CPH and TCPH. For inbound service level-based contacts, agents do not control how many calls they receive. Call volume is determined by the operational environment — occupancy, staffing levels, service level targets, and random call arrival patterns. Targeting agents on call quantity creates an unfair environment and drives the wrong behaviours. The better approach is to use TCPH as a management diagnostic alongside quality data, with a defined Quality Range rather than a single target number.
How do I calculate True Calls Per Hour?
TCPH = Number of Calls Handled ÷ Occupancy Rate (expressed as a decimal). For example, an agent who handled 22 calls at 87% occupancy: 22 ÷ 0.87 = 25.3 TCPH. This represents the rate at which they were working — equivalent to how many calls they would have handled if their occupancy had been 100%.
What is a good TCPH rate?
There is no universal benchmark — the right TCPH depends entirely on your contact type, AHT, quality standards, and operational context. A contact centre handling short transactional calls will naturally have higher TCPH rates than one handling complex technical support. The right approach is to establish your own Quality Range — the band of TCPH rates that your operation has determined represents the right balance of speed and quality — through internal analysis of your own data.
What is a Quality Range in the context of TCPH?
A Quality Range is the band of TCPH rates that your organisation has determined represents the right balance of handling speed and service quality. For example, if your analysis shows that agents operating between 22 and 26 TCPH consistently deliver good quality outcomes and appropriate handle times, that becomes your Quality Range. Agents outside this range — either high or low — are flagged for investigation to understand why, not automatically penalised. The Quality Range is specific to your operation and cannot be imported from industry benchmarks.
Should TCPH be used as a KPI?
Not as a standalone individual KPI or target. TCPH is best used as a management and diagnostic tool — helping managers identify agents whose working rate sits outside the established Quality Range and triggering coaching conversations. Using it as a direct performance target — especially without a Quality Range and without quality data alongside it — creates the same problems as raw CPH, just with a more sophisticated calculation.
How does TCPH relate to Average Handling Time?
They measure different things. AHT measures how long each call takes — from answer to end of ACW. TCPH measures how many calls an agent handles per hour, normalised for occupancy. The two are inversely related: lower AHT generally produces higher TCPH (agents cycle through calls faster). But as with TCPH, AHT in isolation says nothing about call quality — an agent with very low AHT may be ending calls prematurely rather than resolving them.
Can TCPH be used for chat or email channels?
TCPH is most meaningful for service level-based inbound contacts — phone calls, chats, and walk-ins — where agents are waiting for contacts to arrive and occupancy is the relevant variable. For email and back-office contacts, which are handled differently (agents pull work rather than waiting for it to arrive), the occupancy relationship is different and TCPH is less directly applicable. Interpret TCPH for non-voice channels with additional context about how those channels are managed.
Where to Next
Summary: True Calls Per Hour
True Calls Per Hour normalises an agent's call handling rate for the occupancy environment they worked in — making fair comparison possible across different shifts, locations, and call volumes. It solves the fundamental problem with raw CPH: that agents do not control how many inbound calls they receive, so targeting them on raw call counts is both mathematically unfair and operationally counterproductive.
But TCPH is not the end of the story. The metric tells you the rate at which an agent is working — it says nothing about the quality of the work. Used without a defined Quality Range and without quality monitoring data alongside it, TCPH is just a more sophisticated way of making the same mistake as CPH. The best contact centres establish a Quality Range that reflects the right balance of speed and quality for their specific operation, and use TCPH to identify agents operating outside that range — as a trigger for investigation and coaching, not as a performance target.
The goal is never the highest possible TCPH. The goal is sustainable, quality-first performance at a rate that serves both customers and agents well.
