Contact centre metrics, defined.
Nine measures that come up in every contact centre conversation, what each actually counts, and the ways each is commonly reported to look better than it is.
Containment
Self-service rateThe share of contacts resolved without a person. A call is contained when the customer's request is finished end to end by the system they reached, rather than transferred, escalated or abandoned.
How it is measured. Contained contacts ÷ total contacts. Watch what the denominator includes: counting only calls that entered the automated flow flatters the number against counting everything that reached the line.
Deflection
The share of contacts kept out of the queue at all, usually by answering the question in another channel before the customer calls. Often used loosely as a synonym for containment, which it is not.
How it is measured. Contacts avoided ÷ contacts that would otherwise have arrived. Genuinely hard to measure honestly, because the counterfactual is an estimate.
Average handle time
AHTHow long an agent spends on a contact from answer to finished, including talk time, hold time and the after-call work of writing it up.
How it is measured. (Talk + hold + after-call work) ÷ contacts handled. A falling AHT is only good news if resolution holds: the fastest way to cut it is to transfer more.
First contact resolution
FCRThe share of issues settled on the first attempt, with no callback, no second contact and no follow-up ticket.
How it is measured. Issues resolved first time ÷ total issues, usually over a window long enough to catch a repeat call, often seven days.
Average speed of answer
ASAHow long a customer waits in the queue before a person or a system picks up. Distinct from AHT, which starts once the contact is answered.
How it is measured. Total wait time ÷ contacts answered. It excludes abandoned contacts, which is why a bad day can show a healthy ASA.
Abandonment rate
The share of customers who hang up before being answered. The metric that most directly reflects what waiting feels like, and the one most likely to be excluded from a queue report.
How it is measured. Abandoned contacts ÷ total contacts offered. A short-abandon threshold, discounting hang-ups in the first few seconds, is common and should be stated.
Transfer rate
The share of contacts passed to another person or team. High transfer is a routing problem, a training problem, or a sign that the first line cannot reach the system holding the answer.
How it is measured. Transferred contacts ÷ contacts handled. Worth splitting into customer-requested and system-driven transfers, which have very different causes.
Occupancy
The share of an agent's logged-in time spent on contacts rather than waiting. A capacity measure rather than a service one.
How it is measured. Handle time ÷ logged-in time. Sustained occupancy above roughly 85% is associated with burnout and attrition, so it is a cost signal in both directions.
Customer satisfaction
CSATA direct post-contact rating from the customer, usually a single question on a short scale.
How it is measured. Satisfied responses ÷ responses received. Response rates are low and skew to the extremes, so it reads better as a trend than as a number.
What these look like in production
On the City of Kingsport's utility line, Grace resolved60.3% of 20,379 calls end to end, averaged 1:53 against a 4:00 agent baseline, and held speed of answer at zero: every call answered on the first ring, so nothing was abandoned in a queue.
Common questions
What is call containment?
Containment is the share of contacts resolved without a person: the customer's request is finished end to end by the system they reached, rather than transferred, escalated or abandoned. It is calculated as contained contacts divided by total contacts, and the definition of the denominator matters, since counting only calls that entered the automated flow flatters the result.
What is the difference between containment and deflection?
Containment is about contacts that arrive and are resolved without a person. Deflection is about contacts that never arrive, because the question was answered somewhere else first. They are often used interchangeably, but deflection depends on estimating a counterfactual and containment does not.
What is a good average handle time?
There is no universal figure, because handle time depends on the mix of work. It is also easy to improve for the wrong reason: the fastest way to cut handle time is to transfer more calls, so it should always be read alongside first contact resolution and transfer rate.
Is average speed of answer the same as average handle time?
No. Average speed of answer measures how long a customer waits before being answered. Average handle time measures how long the contact takes once it has been answered. A contact centre can have a healthy speed of answer and a poor handle time, or the reverse.
Why can abandonment rate look better than the experience feels?
Because it is often reported with a short-abandon threshold that discounts hang-ups in the first few seconds, and because average speed of answer excludes abandoned contacts entirely. A queue that many customers give up on can report a healthy speed of answer for the ones who stayed.
Ready to deliver faster, more consistent service?
See how Grace handles a real call on your systems: voice, chat, email and beyond.