Why Your Current Report Looks Fine
Consider a queue that took 500 calls last week. 450 were answered in under 15 seconds. 50 waited more than four minutes and 30 of those hung up.
| How it reports | What it says | What it hides |
|---|---|---|
| Average speed of answer | About 40 seconds. Sounds fine | That 450 people waited almost nothing and 50 waited a very long time. The average describes nobody's actual experience |
| Calls answered | 94%. Sounds excellent | 30 people gave up. In most businesses that is the most commercially significant fact of the week |
| Average handle time | Steady. No signal | Nothing at all about whether the problem was solved |
Nothing in that report is wrong. It is simply built from averages, and an average is dominated by the majority of easy calls. The customers you are failing are, by definition, a minority — so they are invisible in every mean you calculate.
The reframe that fixes most reporting
Stop asking “how did the queue perform?” and start asking “how many people had a bad experience, and when?” Every recommendation below follows from that change of question. It is also the question a manager can act on, whereas “average wait rose four seconds” is not actionable by anyone.
The Six That Matter
Modern platforms will report dozens of things. Six carry information you can act on; the rest are mostly decoration or inputs to these six.
| Metric | What it measures | Read it as |
|---|---|---|
| Service level | % of calls answered within X seconds | Your headline. The only common metric that describes an experience rather than an average |
| Average speed of answer | Mean wait before answer | A capacity input. Poor for judging experience — use percentiles for that |
| Abandonment rate | % of callers who hang up while waiting | The closest thing to a direct revenue measure you have |
| First contact resolution | % resolved without the customer coming back | The most valuable and the hardest to measure honestly |
| Average handle time | Talk time plus after-call work | A diagnostic and a capacity input. Never a target |
| Occupancy | % of logged-in time spent on contacts | A ceiling to stay under, not a number to maximise |
Two things deliberately absent. Calls answered per agent per day is a productivity number that rewards rushing and punishes the person who handles the hard calls well. And average call duration in isolation tells you nothing without knowing whether the issue was resolved — a shorter call that produces a callback tomorrow is more expensive, not less.
Service Level, and Where 80/20 Came From
Service level is expressed as two numbers: the percentage of calls answered, and the threshold in seconds. 80/20 means 80% of calls answered within 20 seconds. In Australia both 80/20 and 80/30 are common defaults.
Worth knowing where that came from, because it changes how much authority you give it. 80/20 is not the output of research into customer tolerance. It emerged decades ago as a workable planning convention and hardened into a default through repetition. Treating it as a universal standard is a mistake — the right threshold depends entirely on what your callers are ringing about.
| Queue | Reasonable target | Reasoning |
|---|---|---|
| Sales and new enquiries | Aggressive — 80/10 or better | The caller is comparing you with someone else right now. This is the queue where waiting costs revenue directly |
| Emergency or fault reporting | Aggressive, and measure the tail hard | The consequence of a long wait is not annoyance |
| General service | 80/20 to 80/30 is defensible | The conventional default, and reasonable when calls are routine |
| Complex case work, applications, claims | Relaxed threshold, high percentage | Callers will wait for something that matters to them. What they will not tolerate is waiting and then not being helped |
| Back office and internal | Do not set one | Measuring it produces the appearance of rigour and changes nothing |
The most common way service level gets gamed
Answering quickly and then parking the caller. The service level target is met at the moment of answer, so a queue can report 85/20 while callers routinely spend six minutes on hold after being greeted. If your service level is excellent and your abandonment is also high, this is the first thing to check — measure hold time after answer as a separate number, and look at where those abandons occur in the call.
Average Speed of Answer vs the 90th Percentile
ASA is the mean wait before a call is answered. It is genuinely useful for capacity planning and genuinely misleading for judging customer experience, and most reporting uses it for the second purpose.
Australian benchmark data illustrates the spread. ACXPA's 2026 Australian Contact Centre Best Practice Report puts self-reported speed of answer across a very wide range by sector — utilities reported the slowest at a 227-second average, while banking and finance carried the highest median at 79 seconds. The distance between sectors is large, and the distance between a sector's average and its median is itself informative.
Ask your platform for one number instead
The 90th percentile wait. “90% of callers waited less than X.” That single figure tells you what your worst-served tenth actually experienced, and it is the population that generates complaints, escalations, negative reviews and churn. A queue with a 40-second ASA and a 6-minute 90th percentile is a materially different business problem to one with a 40-second ASA and a 90-second 90th percentile — and the two are indistinguishable on an average.
If your reporting cannot produce percentiles, that is a real limitation worth raising with your provider. It is standard capability in a current platform, and the absence of it forces you to manage a distribution using only its mean.
Abandonment: The Closest Thing to Revenue
An abandoned call is a person who wanted to speak to you badly enough to ring, waited, and gave up. In a sales queue that is lost revenue outright. In a service queue it is a customer who is now more likely to leave, more likely to complain publicly, and quite likely to ring again — meaning you carry the cost twice.
ACXPA's 2026 self-reported Australian figures put voice abandonment at an average of 9% and a median of 5%. That gap is the interesting part: it means a minority of operations with very high abandonment are dragging the average well above what a typical centre experiences. If you are above 9% you are not near the middle — you are in the tail.
| Before comparing yourself to anything | Why |
|---|---|
| Check how short abandons are counted | Many platforms exclude calls abandoned within the first 5–10 seconds, on the reasoning that those are misdials. That is defensible, but it changes the number materially and makes cross-organisation comparison unreliable unless both count the same way |
| Check whether callbacks count as abandons | If a caller accepts a callback offer and hangs up, some systems record an abandon. That is a successful interaction being recorded as a failure |
| Look at when they abandon, not just how many | Abandons clustered at 30 seconds mean your greeting or menu is losing people. Abandons clustered at 5 minutes mean your capacity is wrong. Completely different fixes |
That third row is the most actionable measurement on this page, and almost nobody produces it. A histogram of abandonment by wait time tells you which problem you have. Early abandons are a design problem — too many menu options, an over-long greeting, no indication that a human exists. Late abandons are a resourcing problem, and no amount of menu redesign will touch them.
First Contact Resolution: Hard, and Worth It
FCR is the share of contacts resolved without the customer having to come back. It correlates more strongly with satisfaction and with cost than anything else here, and it is the least well measured because measuring it honestly is genuinely difficult.
For scale: ACXPA's Australian Call Centre Rankings put the banking sector at roughly 32% first contact resolution in the first quarter of 2026. Two-thirds of contacts in that sample were not resolved first time. Whatever your own number is, if you have never measured it, it is likely lower than you assume.
The repeat-contact method
Count contacts from the same customer within 7 days about the same issue. Objective and automatable, but it needs the phone system and the CRM to be linked, and it misses the customer who gave up rather than ringing back.
The agent-declared method
The agent marks whether it was resolved. Cheap and immediate, and systematically optimistic — people are poor judges of whether they solved someone else's problem.
The ask-the-customer method
A one-question survey after the call. The most accurate and the lowest response rate, and the responses skew toward the very satisfied and the very unhappy.
Use the repeat-contact method as your tracked number, because it is the only one that is consistent over time, and sample the other two occasionally to check it is not drifting. What matters far more than the absolute figure is the trend and the breakdown by contact reason — a low overall FCR is usually two or three specific issue types dragging everything down, and those are fixable once identified. AI transcription and call summarisation make the reason breakdown considerably cheaper to produce than it used to be; AI transcription and CRM notes covers how.
Handle Time and Occupancy: Diagnostics, Not Targets
Two metrics that are useful when watched and destructive when targeted.
Average handle time is talk time plus after-call work. It belongs in capacity planning, where you genuinely need it. It does not belong on a wall, because the moment it becomes a target the behaviour it produces is rushing — and rushing reduces first contact resolution, which increases repeat contacts, which increases total handle time across the operation. You end up paying more for a worse experience while the metric improves.
The rule
Watch AHT for changes and for outliers. A sudden rise means a new issue type, a system problem, or a process change. A persistent gap between two agents doing the same work is a coaching conversation. An organisation-wide reduction target is a request for worse service, and it is almost always answered.
Occupancy is the share of logged-in time spent handling contacts. Intuitively, higher looks like better utilisation. In practice it behaves like a physical limit: sustained operation above roughly 85% produces measurable degradation — errors rise, courtesy drops, sick leave rises and attrition follows. Because queues are stochastic, a team running at very high occupancy also has no absorption capacity, so a small spike in volume produces a disproportionate collapse in service level.
The related figure worth knowing is shrinkage: the proportion of paid time not available for contacts — breaks, training, meetings, leave, coaching. It is commonly 30–35% and is routinely underestimated when rosters are planned, which is the single most frequent cause of a queue that is inexplicably short-staffed every afternoon.
Read the Interval, Not the Day
The most common reporting error, and the easiest to correct.
A queue reporting 82% service level for the day looks like it hit an 80% target. Break the same day into half-hour intervals and the usual pattern appears: 95% for most of the day, and 45% between 9:00 and 10:00, and again between 1:00 and 2:00. Every customer who rang in those two windows had a poor experience, and the daily number concealed all of them.
| Look at | What it reveals |
|---|---|
| Service level by half-hour | The two or three windows where your queue actually fails. Almost always the morning open and immediately after lunch |
| Volume by half-hour, by weekday | Monday is not Wednesday. Rosters built on a daily average under-staff Monday morning every week without fail |
| Abandons by interval | Confirms which windows are hurting people rather than merely being busy |
| Occupancy by interval | Shows where the team is being asked to run at a rate no team sustains |
The cheapest fix in contact centre management
Move breaks and meetings out of your two worst intervals. It costs nothing, requires no headcount, and frequently produces a larger improvement in service level than anything else available. Most teams schedule the morning meeting at 9am and the team huddle right after lunch — precisely the two windows that are already failing.
From Symptom to Change
A number is only useful if it points to an action. This table maps what you see to what is usually causing it.
| What you see | Usually means | Do this |
|---|---|---|
| Good service level, high abandonment | Callers are answered quickly then parked, or the menu is losing them before the queue | Measure hold time after answer separately. Plot abandons by wait time. Shorten the greeting |
| Abandons cluster under 30 seconds | Design problem — menu too deep, greeting too long, no sign a human exists | Cut menu options to three or four. Put the option to reach a person early |
| Abandons cluster past 3 minutes | Capacity problem, in specific intervals | Re-roster to the interval curve. Offer callback rather than making people wait |
| Daily service level fine, customers complaining | Interval failure hidden by a daily average | Report by half-hour. Move breaks and meetings out of the failing windows |
| Low FCR concentrated in a few reasons | Knowledge, access or authority gap on specific issue types | Fix those two or three flows. Give front line authority to resolve them without escalation |
| AHT falling, repeat contacts rising | The team is being measured on speed and has responded rationally | Remove AHT as a target. Measure resolution instead |
| Occupancy above 85% routinely | Understaffed, or shrinkage was underestimated in planning | Recalculate shrinkage honestly — it is usually 30–35%, not the 20% in the plan |
| Everything looks good, revenue queue underperforming | Sales and service share a target that suits neither | Split the queues and set an aggressive threshold on the revenue one |
9% / 5%
AU abandonment: average / median, 2026
~32%
Banking FCR, Q1 2026
85%
Occupancy ceiling, not target
30–35%
Typical shrinkage
Benchmarks are context, not goals. A queue handling complex claims and one handling order status are not comparable, and a business that adopts a sector average as a target has borrowed someone else's problem. Measure your own distribution, watch the trend, and fix the two intervals where the failures actually live. That approach beats benchmark-chasing in every operation we have seen it applied to.
If you are building or rebuilding the queue itself rather than measuring an existing one, the contact centre software buyer's guide covers the capability set, one queue for voice, SMS and chat covers what changes when the same team handles more than calls, and AI call scoring covers the quality side that none of the metrics here measure.