Average handle time (AHT) measures how long an agent spends on a single customer interaction, from the moment it starts to the moment it is fully wrapped up, including any after-call work like notes or follow-up tasks. It is a genuinely useful efficiency and capacity-planning metric, but it becomes dangerous the moment it is treated as a target agents are pushed to minimise, because customers do not experience their call as a number to be reduced.
What Does Average Handle Time Actually Measure?
AHT is typically calculated as talk time plus hold time plus after-call work, averaged across a group of calls or a period of time. It is a workload and staffing metric at heart. Contact centres use it to forecast how many agents are needed to handle expected call volume, to compare workload across different types of enquiries, and to spot when a particular issue type is taking unusually long to resolve, which can signal a process or training gap worth investigating.
What AHT Is Good At
Used correctly, AHT helps with staffing forecasts and capacity planning, and it can flag process problems, such as a system that is slow to load or a script that makes agents ask redundant questions. A sudden increase in AHT for a specific issue type is often a useful early signal that something upstream has broken.
What AHT Cannot Tell You
AHT says nothing about whether the customer's problem was actually solved, whether they understood the explanation, or whether they will need to call back. A short call that ends with an unresolved issue looks efficient on the dashboard and is actually a failure.
Why Does Chasing AHT as a Target Backfire?
The moment agents are evaluated primarily on keeping AHT low, their incentives shift away from actually solving the customer's problem. This shows up in predictable and damaging ways. Agents rush explanations, cutting corners on confirming the customer actually understood what was said. They avoid fully documenting the interaction to save time on after-call work, which then hurts the next agent who has to pick up the thread. And they may resolve the immediate symptom rather than the root cause, because a full fix takes longer than a quick workaround.
- Repeat contacts rise, because a rushed resolution often does not actually resolve anything, sending the customer back to the queue days later with the same problem.
- Customer satisfaction falls, since customers can usually tell when they are being hurried off the line, and it damages trust even if the immediate issue was technically closed.
- Agents feel pressured and disengaged, which is one of the quieter drivers behind agent burnout and attrition in contact centres that over-index on speed metrics.
- Complex issues get mishandled, because agents facing an AHT target have a built-in incentive to transfer or defer anything that looks like it will take too long.
What Should Replace AHT as the Primary Target?
The healthier approach is to track AHT as one input among several, rather than as the headline metric agents are managed against. First contact resolution, customer satisfaction scores, and quality assurance scoring together give a much more honest picture of whether the contact centre is actually doing its job well. A call that takes longer but resolves the issue completely on the first attempt is usually cheaper for the business overall, once the cost of repeat contacts is accounted for, even though it looks worse on an AHT report.
First Contact Resolution as a Counterweight
Pairing AHT with first contact resolution creates a healthier tension: agents are not rewarded for either dragging calls out unnecessarily or rushing them, because both extremes hurt the resolution metric or the efficiency metric respectively.
Quality Scoring as a Guardrail
Structured quality reviews that check whether the agent actually addressed the customer's need, not just whether they followed a script quickly, help catch the specific ways that AHT pressure erodes service quality before it shows up in satisfaction scores weeks later.
How Should AHT Be Used in Practice?
AHT is most useful when it is analysed by issue type and by trend, not as a single company-wide average agents are compared against individually. A spike in AHT for billing enquiries specifically might point to a confusing new invoice format. A steady rise across the board might point to a system slowdown rather than agent performance. Segmenting the data this way turns AHT from a blunt performance stick into a genuinely useful diagnostic tool, which is closer to how experienced operations teams actually use it.
How Does This Connect to Broader Contact Centre Strategy?
Metrics like AHT sit inside a larger service level framework that should be negotiated and understood by both the business and its outsourcing partner, if the function is outsourced. A well-structured service level agreement defines which metrics matter, how they are weighted, and what happens when targets are missed, ideally with resolution quality given at least as much weight as speed. Businesses evaluating outsourcing partners should ask directly how the provider balances AHT against quality, since a partner that leans too heavily on speed alone is optimising for the wrong outcome. It is also worth understanding the underlying technology, since tools covered in our guide to choosing contact centre technology, like a well-integrated CRM, can genuinely reduce handle time without sacrificing quality, which is a very different thing from simply pressuring agents to talk faster. A partner that can show, with real examples, how a specific system change reduced handle time on a particular issue type without hurting satisfaction scores is demonstrating exactly the kind of evidence-based improvement that should be the goal, rather than a target hit through pressure alone.
How Should AHT Targets Be Set in the First Place?
Setting an AHT target well requires looking at historical data segmented by issue type, then building in a reasonable range rather than a single rigid number. A target based on the fastest agents' best performance, rather than a realistic average across the team and across issue complexity, sets everyone up to feel like they are constantly falling short. It is also worth revisiting targets periodically, since a target set when a product was simple may no longer make sense after new features or policies have made typical enquiries genuinely more complex to resolve properly.
Involving Agents in Target Setting
Agents who handle calls every day often have the clearest view of which parts of a call are genuinely time-consuming and why. Involving experienced agents or team leads in setting or reviewing AHT targets tends to produce more realistic numbers than targets set purely from a spreadsheet by someone removed from the daily work.
How Does AHT Interact With Staffing and Cost?
AHT feeds directly into workforce planning, since it is one of the core inputs used to calculate how many agents are needed to hit a given service level at a given volume. Because of this direct link to staffing costs, there is a natural commercial pressure to want AHT as low as possible, since lower AHT theoretically means fewer agents needed for the same volume. This is precisely why the metric needs a counterbalance. A business that pushes AHT down through pressure rather than through genuine efficiency gains, such as better tools or clearer processes, often finds the apparent savings erased by the cost of repeat contacts and dissatisfied customers, which is a cost that rarely shows up on the same dashboard as the original AHT figure. Forecasting teams that build in a realistic buffer for issue complexity, rather than assuming every call in a category will take the average amount of time, also tend to avoid the trap of chronic understaffing that pushes AHT pressure onto agents in the first place.
Frequently Asked Questions
What is considered a good average handle time?
There is no universal good number, since AHT varies enormously by industry, issue complexity, and channel. A benchmark that makes sense for a simple retail enquiry line would be far too aggressive for a technical support or claims-handling operation, so comparisons should be made against similar issue types, not generic industry averages.
Should agents be told to keep calls short?
Agents should be encouraged to be efficient and avoid unnecessary delays, but explicit pressure to cut calls short tends to backfire by increasing repeat contacts and lowering satisfaction. A better framing is training agents to resolve issues thoroughly and efficiently, rather than quickly for its own sake.
Does a high AHT always mean poor performance?
No, a higher AHT can reflect a more complex issue mix, more thorough problem-solving, or better documentation, all of which can be good things. It is much more useful to look at AHT alongside first contact resolution and customer satisfaction than to judge it in isolation.
How does after-call work factor into AHT?
After-call work, such as writing up notes or triggering a follow-up task, is usually included in the AHT calculation because it is genuine work time tied to that interaction. Cutting corners on after-call work to lower AHT tends to create problems for whoever picks up the case next.
How should AHT be used when evaluating an outsourced contact centre partner?
It is reasonable to review AHT trends as part of ongoing performance management, but it should never be the only or primary metric in the service level agreement. Asking how the partner balances speed against resolution quality and customer satisfaction is a better indicator of whether they will manage the metric responsibly.
If you would like an honest, practical view on this for your own business, get in touch via Connect Centre Group's contact page.