AHT Has No Place as a Contact Centre Metric. Here's What It Does to Call Volume.

Every week, in contact centres around the world, the same meeting happens.

Someone opens a PowerPoint. Or pulls up a RAG dashboard. They compare this week to last - answer rates, wait times, abandon rates. The numbers aren’t good enough. A decision gets made quickly: we need to reduce AHT.

The first time it happens, someone in the room might push back. Ask a question. Challenge the logic.

By the third or fourth time, they’ve stopped. Not because the logic got better. Because they learned that pushing back doesn’t change the outcome - it just makes you look like the problem.

So they nod. They take the message back to their team. And the loop begins.

What follows isn’t a performance improvement. It’s a damage sequence - to your customers, your frontline staff, and eventually your cost base. And it plays out the same way, in every contact centre that treats AHT as a capacity lever.

For a full breakdown of how repeat demand builds, compounds, and affects contact centre performance, see The Complete Guide to Repeat Demand in Contact Centres.

What Is Average Handle Time - And Why It Becomes a Problem

Average Handle Time (AHT) is the average duration of a customer contact, including talk time, hold time, and after-call work (ACW). It is calculated as: (talk time + hold time + after-call work) ÷ total contacts handled. The contact centre industry average sits between 4 and 6 minutes depending on sector and contact type.

AHT becomes a problem the moment it is used as a performance target. Not because the measurement is inaccurate - it accurately reflects how long calls take. The problem is what happens to agent behaviour, call quality, and repeat contact volume when reducing that number becomes the objective.

The AHT pressure doesn’t start at the front line. It starts in a leadership meeting and travels downward - changing shape at each layer, losing context at every step.

Layer 1: Senior leadership reacts to a dashboard. Call volumes are up. Wait times are rising. Abandon rates are climbing. The instinct is to look for capacity. AHT looks like the lever. A target gets set.

Layer 2: Middle management receives the target. They may have reservations. But the target comes from above, it’s framed as urgent, and challenging it carries risk. They nod. They take ownership of the message.

Layer 3: Team leaders are now responsible for delivering the target to their teams. Some of them genuinely understand why it’s wrong. They might even say so, privately, in sympathy, to their team members. But the target doesn’t move. So, neither do they.

Layer 4: Frontline agents receive the pressure directly. They’re told to handle calls faster. They’re shown metrics. They’re coached on pace. They watch others around them hit the target, and they feel the gap.

By the time the pressure reaches the front line, all the context has been stripped away. What remains is a number. And the message that the number must come down.

The 4 - 6 Week Window: When AHT Targets Push Good Agents Into Bad Decisions

Not everyone responds to AHT pressure immediately. Some agents resist. They keep handling calls the way they always have with the diagnostic depth the customer actually needs.

These are often your strongest performers.

But across hundreds of operations, a pattern repeats itself.

Within four to six weeks of sustained AHT pressure, even the holdouts change.

It doesn’t happen gradually. It happens in a moment - usually after weeks of hearing how colleagues are hitting the target, weeks of being called out for being above it, and one conversation that makes them feel like they’re the problem.

And then they do something dramatic to get the number down.

What does that look like in practice?

• Rushing callers. Not exploring the underlying issue. Getting to a resolution… any resolution…fast.

• Redirecting demand. Telling customers to email instead. The call ends quickly. The demand doesn’t disappear. It moves somewhere harder to measure.

• Deflecting entirely. Telling callers to ring back later. The metric resets. The customer’s problem doesn’t.

• In the most extreme cases: cutting calls. Connecting briefly, two or three seconds… and disconnecting. Enough to register as answered. Not enough to help anyone.

Here’s what makes this phase particularly damaging: leaders reward it.

The numbers start looking better. A team leader who’s been struggling to shift their team’s AHT sees the metrics move and recognises it as progress. They praise the improvement in their next one-to-one. They call it out positively in a team meeting. For a few weeks, the agent who found the most aggressive way to cut call time is held up as someone who figured it out.

The praise doesn’t last long. But the behaviour it reinforced does.

This is also why coaching-based responses to performance problems, rather than structural ones, so rarely move the needle once this pattern is established.

If this pattern is already running in your operation, the AHT Loop Intervention gives you a structured way to find the source, redesign the constraint, and produce the evidence that shows what changed.

Not sure if this is your dominant loop? The Performance Scorecard will identify which structural problem is driving your results in under five minutes."

When Praise Becomes a Disciplinary: The Hidden Cost of AHT Misconduct

The discovery of what’s happening rarely comes from someone looking for misconduct.

It comes sideways.

A spike in customer complaints. A broker raising concerns. A QA review triggered by something unrelated.

Someone, for an entirely different reason pulls call length data and notices a pattern: calls at two or three seconds. Enough to connect. Not enough to speak.

Then comes the investigation. And the conversation that follows is one of the most corrosive things that happens in a contact centre.

The leader who praised the improving numbers now has to address the behaviour that produced them. The agent who was told, explicitly or implicitly, that their performance was heading in the right direction is now facing disciplinary action.

What almost never happens in that conversation: any acknowledgment that the target created the behaviour. That the praise reinforced it. That the system designed the outcome it’s now punishing someone for.

Instead, the focus lands entirely on the misconduct. The individual is let go.

And then the operation absorbs costs it never attributed to the AHT target:

• Recruitment costs for the replacement hire.

• Onboarding and training time before the new agent reaches competency.

• Lost institutional knowledge, the customer relationships, the product familiarity, the operational context that walked out with the person who was dismissed.

• The morale impact on colleagues who watched what happened and drew their own conclusions about how the operation treats its people.

A genuinely good employee, someone who was capable, who cared, who held out longer than most, became a conduct case. Not because they were a bad employee.

Because the system handed them a target they couldn’t achieve within the rules, watched them struggle, rewarded the moment they broke those rules, and then punished them for it.

The AHT target didn’t just fail to solve the capacity problem. It manufactured a disciplinary case and a recruitment cost.

What AHT Targets Do to Your Customers and Your Recontact Rate

At every stage of this sequence, there’s a customer on the other end of the call.

They’ve already waited. Because the operation is under pressure: high volumes, long queues, rising abandon rates. These are always the conditions that trigger the AHT reduction push in a contact centre. The customer has already absorbed that delay before the call even connects.

When it does connect, they’re speaking to someone who has been trained, through targets, through coaching, through the behaviour of colleagues to treat the length of the call as the problem. Not the customer’s unresolved need. The call length.

So the customer gets rushed. They hear frustration in the agent’s voice, even if the agent is trying to hide it. They’re told to email instead, even though their preference, the channel they chose, was to call.

They’re told to ring back. Or, in the worst cases, the call simply ends.

They call back. Now frustrated. Now requiring more time to handle because they have to re-explain, re-authenticate, re-establish context. Now more likely to escalate. Now more likely to complain.

The customer who wasn’t given what they needed in the first interaction doesn’t disappear from the demand picture. They return to it at higher cost, with lower satisfaction, with less goodwill toward the operation.

What we reduce by one minute in one call generates another four-to-five-minute call where the customer was not given what they needed the first time.

This is not a trade-off.

It’s a debt.

And it compounds directly into your recontact rate.

The Structural Loop: How AHT Targets Generate the Call Volume They Were Meant to Fix

The relationship between AHT and call volume in a contact centre is the opposite of what most dashboards suggest - the metric doesn't reduce demand, it regenerates it.

When you step back from individual interactions and look at what’s happening across the system, the pattern becomes clear:

• Call volumes rise or wait times increase.

• Leadership targets AHT as the capacity lever.

• Diagnostic depth drops as calls shorten.

• Unresolved demand returns as repeat contacts.

• Call volumes rise further.

• AHT targets tighten in response.

  
  

The metric that was supposed to create capacity is generating the demand it was meant to absorb.

From the outside, it looks like performance is slipping. From the inside, the system is doing exactly what it was designed to do.

This is not a coaching problem. It is not a motivation problem. It is not an individual performance problem. It is a structural loop, created by the AHT target itself, and it will continue to run until the mechanism is diagnosed and redesigned.

Call volume increased after reducing AHT?

This is why.

Not because the team failed.

Because the system responded exactly as it was built to.

How to Improve AHT Without Generating More Contacts

The conventional approach to improving AHT - coaching agents to handle calls faster, tightening scripts, adding efficiency targets - reliably reduces handle time while increasing repeat contact volume. The contacts don't disappear. They return. If the goal is to improve AHT without generating more inbound demand, the starting point is not duration. It is resolution.

AHT has no place as a metric in a customer service contact centre.

Not as a primary measure. Not as a secondary measure. Not as a directional indicator. Because every customer is different, their needs are different, and what a good resolution looks like is different.

A metric that treats every call as if it should take the same amount of time is not measuring performance. It’s measuring conformity to an arbitrary standard while hiding what’s actually happening underneath.

If you want to understand whether your contact centre is performing, study demand - not duration.

• What are your recurring call reasons? Which problems keep returning?

• What is your recontact rate within 7 to 14 days? How many customers are calling back about the same issue?

• Where does resolution break down? At what point in the interaction does the customer’s need go unmet?

• What demand is being created by process gaps, by policy failures, by system limitations, by information that isn’t reaching customers before they need to call?

Stability in a contact centre does not come from calls getting shorter. It comes from fewer calls returning.

What Contact Centre Leaders Who Reject AHT Targets Do Differently

There are leaders who see through this. They exist in every type of operation. And they share a specific set of characteristics.

They’ve spent real time with their teams and inside the call flow. They understand what an interaction actually involves: not from a dashboard, but from listening, from sitting alongside agents, from understanding the constraints the frontline is operating inside.

They connect metrics together. They don’t look at AHT in isolation. They look at AHT alongside recontact rate, alongside customer satisfaction, alongside complaint volume.

They understand that a metric improving while adjacent metrics deteriorate is not a success, it’s a signal.

They have the conviction to hold that position. Either because they’ve been in a frontline role themselves and know what the pressure actually feels like, or because they’ve watched this loop play out enough times to choose to do something different.

These are the leaders who can stand in a meeting, look at the same dashboard that prompted the AHT target, and say: that number is not the problem, and reducing it is not the solution. And mean it.

A Contained Starting Point for Reducing Repeat Demand

If this pattern is active in your contact centre, you do not need a transformation programme to start understanding it.

Pick one high-volume repeat call reason. Track how often it returns within 7 to 14 days.

Review call notes for signals of partial resolution, interactions that ended but left the customer’s underlying need unmet. Identify what agents couldn’t resolve in a single interaction, and trace the structural barrier that prevented full resolution.

That single study will likely tell you more about your actual capacity problem than months of AHT reporting.

If the pattern is showing up across your operation and you want a structured way to find the source, redesign the constraint, and build the evidence that shows what changed - that’s exactly what the AHT Loop Intervention is built to do.

Reflection

If call volume increased after reducing AHT in your operation, it doesn’t mean the team failed.

It means the system prioritised speed over resolution. And then handed the consequences to your frontline, your customers, and eventually your cost base.

The question is not how to coach harder or push the target further.

The question is: what demand did speed create and what is it costing you to keep generating it?

Not sure if this is the dominant pattern in your operation? The Performance Scorecard will identify it.

FAQ

Can reducing AHT increase call volume in a contact centre?

Yes. When diagnostic depth drops due to shortened interactions, unresolved demand returns as repeat contacts - increasing total volume rather than reducing it. The metric improves while the underlying problem compounds.

Why do repeat calls increase after AHT improves?

Because shorter interactions trade resolution for throughput. The call ends. The customer’s need doesn’t. They call back - often more frustrated, requiring more handling time the second time around.

What should contact centres measure instead of AHT?

Recontact rate within 7–14 days, recurring demand patterns, first contact resolution failure modes, and demand created by process gaps. Duration tells you how long calls take. These measures tell you whether demand is actually being resolved.

Is AHT a useful metric in a customer service contact centre?

As a performance metric applied to individuals or teams, AHT reliably produces the behaviours described in this post - rushed calls, deflected contacts, and partially resolved interactions that return at higher cost. The risk is not theoretical. It is structural and predictable.

How do I reduce repeat demand caused by AHT targets?

Start with the data you already have. Pull your recontact rate. Map your top recurring call reasons. Show the volume of demand returning within 7–14 days and estimate the handling cost. The case for structural redesign is almost always sitting inside your existing data - it just hasn’t been connected to the metric causing it.