Why Reducing AHT Can Increase Repeat Calls in Contact Centres

You looked at the volume.

You looked at the handle time.

The logic seemed straightforward.

If calls are taking too long and there are too many of them, reducing handle time should ease the pressure.

So you set the target.

You coached to it.

You hit it.

And the volume didn’t drop.

For many contact centre leaders this is one of the most disorienting patterns in operations.

The intervention was rational.

The data supported it.

The target was met.

But the problem is still there - sometimes worse than before.

The reason is structural.

In most cases, that structure is repeat demand - where the system generates additional contacts because issues are not fully resolved the first time.

If you want a full breakdown of how repeat demand works across contact centres, start here.

Reducing AHT targets is a legitimate response to a capacity problem. It is the wrong response to a repeat demand problem. And in most operations where call volume continues to climb despite efficiency work, repeat demand is what is actually driving it.

Can Reducing AHT Increase Repeat Calls in Contact Centres?

Reducing AHT can increase repeat calls in contact centres when shorter interactions prevent agents from fully resolving the customer’s underlying issue.When resolution depth is compressed, customers contact the organisation again, creating repeat demand and increasing overall contact volume.

In these cases the operation meets its efficiency target but generates more work.

Signs AHT Targets Are Driving Repeat Demand

Many operations discover this pattern only after it has already embedded itself.

Typical signals include:

• call volume rising even though handle time is falling

• repeat contact rates increasing within 7–14 days

• shorter calls showing higher repeat rates by contact reason

• agents closing calls quickly but customers contacting again about the same issue

These signals suggest the system is compressing resolution depth, not improving efficiency.

What AHT Targets Actually Measure in Contact Centres

Average handle time targets exist to manage capacity.

If agents spend longer than necessary on calls, the operation carries excess cost per contact. Tightening the target reduces that cost.

The logic works when the cause of long calls is inefficiency.

But the target assumes something important:

that the call is complete.

It measures the time required to complete the interaction.

That assumption breaks when the reason calls are long is complexity rather than inefficiency.

A call that runs long because an agent is resolving a complicated issue is not the same as a call that runs long because the agent is struggling to manage the interaction.

AHT targets treat both situations identically.

They apply pressure to shorten the interaction regardless of what is happening inside it.

In a repeat-demand environment, the longest calls are often the ones where agents are working hardest to achieve full resolution.

Compressing those calls does not make them efficient.

It makes them incomplete.

Why AHT Targets Create a Structural Problem

AHT targets are not just a measurement - they are a behavioural signal sent to every agent on every call. When a target exists, agents optimise toward it. That is not a performance problem. That is how targets work.

The structural problem with AHT targets specifically is that they create pressure at the wrong point in the interaction. They compress the end of the call - the part where resolution depth is established - without any visibility into what happens after the call closes. An agent hitting their AHT target is doing exactly what the system is asking them to do. The system just isn't asking for the right thing.

This is why AHT targets can remain in place for months or years without anyone identifying them as the cause of rising repeat contacts. The target is being met. The metric looks healthy. The demand keeps climbing.

Why Call Volume Increases After Reducing AHT

To understand this pattern, it helps to separate contacts from causes.

Repeat demand is not customers having more questions.

It is customers returning because their previous contact did not fully resolve their issue.

When AHT targets compress the resolution sequence - when calls end at the moment the presenting question is answered rather than when the underlying issue is resolved - customers contact again.

That return interaction is treated as a new call.

It is resourced.

Handled.

Counted.

The original call is logged as completed.

The operation has met its AHT target while generating additional contact volume at the same time.

This pattern is a direct expression of repeat demand building inside the system rather than new demand entering it.

You can see how this feedback loop forms across contact centres here.

The AHT Loop: How Efficiency Targets Create More Demand

This relationship between handle time and repeat contacts forms a feedback loop.

Handle time targets are tightened to reduce cost per contact.

Agents respond by reducing call depth.

Resolution becomes incomplete.

Customers contact again.

Those repeat contacts increase overall call volume.

Rising volume is interpreted as increased demand.

The operation tightens efficiency targets further to manage the cost.

The loop reinforces itself.

The intervention designed to reduce demand is helping to create it.

The Data That Reveals the Pattern

Most operations already have the data needed to see this mechanism.

The problem is that the data is rarely combined.

Pull together three reports:

• handle time by contact reason

• repeat contact rate by contact reason

• time window between first and return contact

Look for contact reasons where repeat contact rates are highest among the calls with the shortest handle times.

That pattern indicates AHT-driven truncation.

The target is compressing calls that require depth to resolve.

Standard AHT reporting does not show this.

It measures efficiency within the call, not what happens after the call ends.

That gap is where the repeat demand loop lives.

Why Coaching and FCR Targets Often Miss the Problem

When reducing AHT fails to reduce volume, operations typically respond in one of two ways.

More coaching.

Or stronger FCR targets.

Both responses focus on the call itself.

Coaching agents to close calls faster increases pressure on the point where resolution depth is already being sacrificed.

FCR targets measure whether customers return within a defined window, but they cannot capture every form of repeat demand.

Customers may return after the measurement window, or about a slightly different aspect of the same underlying issue.

Both responses diagnose at the interaction level.

The cause sits at the system level.

What AHT Targets Cannot Reach

AHT targets operate only on what happens inside the call.

They cannot act on:

• downstream processes that fail after the call ends

• authority limits preventing agents from resolving issues

• missing information systems

• approvals or callbacks required from other teams

These mechanisms generate repeat demand.

None of them respond to handle time targets.

This is not an argument against AHT targets.

When calls are genuinely long due to inefficient interaction management, handle time targets are the correct tool.

The question is whether that is actually the problem.

A Quick Diagnostic to Run This Week

Take your top ten contact reasons by volume.

For each one, pull the repeat contact rate within fourteen days.

Rank them.

Look at the three with the highest repeat rates.

Now ask:

What would need to be true for this issue to be fully resolved on a single call?

If the answer is deeper probing or stronger call control, coaching may help.

If the answer involves system access, authority, downstream processing, or information from another team, the cause is structural.

Those structural cases are where tightening AHT targets will not work.

They are also where the most meaningful improvements sit.

The Bottom Line

Average handle time targets are a capacity management tool.

They assume that shorter calls produce a more efficient operation.

That assumption holds when calls are long for the wrong reasons.

When calls are long because resolution requires depth, compressing them does not reduce work.

It generates more contacts.

The operation then measures those contacts as demand.

Reducing repeat demand requires something different.

It requires identifying which contacts are returning because the system could not resolve them the first time - and redesigning the structural conditions that created them.

When you are ready to step back and understand how these patterns connect across your operation, not just within individual metrics:

Read the full breakdown of repeat demand in contact centres.