Contact centre benchmarks
Benchmark ranges for service level, ASA, FCR, AHT, occupancy, abandonment, adherence, shrinkage, and attrition — by channel and industry. These are attainable ranges observed across UK and European operations, not theoretical optima.
Key metric benchmarks
The four columns span from high-performing (tight) through typical to warning-level (danger) ranges.
80/20 is a convention, not an optimum. Regulated industries (FCA, NHS 111) often mandate tighter thresholds.
ASA is the mean across all calls including those answered immediately. It is not the same as service level.
Each 1% FCR improvement removes ~1–1.5% total inbound volume. Transactional ops target 80–90%; advisory ops 65–75%.
Highly industry-dependent. Transactional: 2–4 min. Insurance claims: 12–20 min. Technical support: 10–18 min.
Above 90% agents have no recovery time — AHT creep and burnout follow. Below 75% is typically overstaffed.
Exclude short abandons (< 5–8s) from your reported rate — they are likely misdials or IVR bounces, not true service failures.
Adherence below 85% is operationally significant — every missed 6 minutes per agent per hour is a lost agent-hour per shift.
Operations over 35% often have structural absence problems. Use gross-up: required ÷ (1 − shrinkage%) to get staffed agents.
BPO attrition often runs 50–80%. Below 15% suggests high tenure or unusual labour market conditions — not always positive.
Benchmarks by channel
The same metric has different typical ranges depending on channel. Chat and email sustain higher occupancy because agents control their own pacing. Voice queues have stricter service level requirements because customers experience wait time in real time.
AHT benchmarks by industry
AHT varies more by industry than any other metric. Comparing AHT to industry benchmarks (not cross-industry averages) is the only meaningful benchmark for this metric.
Complex queries (loans, disputes) extend to 15+ min
High AHT driven by information gathering and first-party claim creation
Order status and returns are short; complaints extend to 8–12 min
Technical fault diagnosis is the primary AHT driver; billing queries shorter
Patient access typically 4–6 min; clinical query lines run 10–20 min
Tariff changes and debt management extend AHT; meter reads are short
Bimodal: simple checks 3–5 min; group bookings 20–40 min
High process complexity; variable AHT across council services
Using benchmarks correctly
Benchmarks describe the industry, not the optimum
The 80/20 service level target is the most cited benchmark in contact centres and possibly the least examined. It originated from a single AT&T study and became industry convention. The right service level is defined by your abandonment tolerance, cost per call, and regulatory requirements — not convention. Use benchmarks as context, not targets.
Metric interactions matter more than individual benchmarks
High FCR reduces volume. Higher occupancy reduces cost but increases AHT and attrition. Lower AHT increases throughput but may reduce FCR if agents are rushing. Benchmarking individual metrics in isolation misses these interactions. The correct check is: are our metrics consistent with each other, or are we gaming one at the expense of another?
Compare to your own operation over time first
Industry benchmarks are averages across diverse operations. Your operation's internal trend — AHT this quarter vs. last quarter, FCR this month vs. baseline — is a more actionable signal than an industry comparison. External benchmarks are useful for a periodic sanity check, not for day-to-day management.
Small team effects distort benchmark comparisons
Erlang C's efficiency curve means a 10-agent team will naturally run lower occupancy than a 50-agent team at the same service level. Small operations always benchmark unfavourably on occupancy and cost-per-call. This is a mathematical property of queue theory, not a management failure.
Benchmark questions
What is the standard service level target for a contact centre?
The most cited benchmark is 80/20 — answer 80% of calls within 20 seconds. This originated from AT&T research in the 1980s and is an industry convention, not a scientifically optimal target. Many operations use 80/30. Regulated sectors (FCA, NHS) often mandate tighter thresholds such as 90/15. The right service level depends on your abandonment tolerance, cost envelope, and regulatory requirements.
What is a good FCR rate for a contact centre?
Transactional operations (account queries, order tracking) typically achieve 80–90% FCR. Complex advisory operations (financial advice, insurance claims) typically achieve 65–75%. B2B operations typically run 50–65% due to multi-party decisions. As a general rule, FCR below 65% in a transactional operation signals a root-cause problem — each 1% FCR improvement removes approximately 1–1.5% of total inbound volume.
What is the target occupancy rate for a contact centre?
The industry benchmark for sustainable occupancy is 85–88% for inbound voice. Above 90% is a danger zone — agents have no recovery time, leading to AHT creep, call-avoidance, and burnout. Below 75% typically indicates overstaffing. Chat and email queues can sustain slightly higher occupancy (88–92%) because agents control pacing. Very small teams naturally run lower occupancy due to Erlang C's staffing efficiency curve.
What is the industry average for contact centre shrinkage?
Total shrinkage typically ranges from 25–35% for inbound voice. Breakdown: annual leave 10–15%, short-term sickness 6–10%, training 4–8%, meetings 3–5%, system downtime 1–2%, personal/bathroom 2–4%. Over 35% typically signals structural absence problems. Apply shrinkage with gross-up: staffed agents = required agents ÷ (1 − shrinkage%).
Check your metrics against these benchmarks
Run Erlang C for your voice queue, model FCR impact, check shrinkage — all free, no sign-up required.
Detailed metric guides
Service level explained
What 80/20 means and when to change it
FCR guide
How to measure, benchmark, and improve FCR
AHT guide
Drivers, benchmarks, and reduction levers
Occupancy explained
Sustainable ranges and the danger zone
Shrinkage explained
What counts, how to apply it correctly
Abandonment rate
Measurement, benchmarks, and levers