KPIs and metrics

Reducing Average Handle Time Without Hurting Call Quality

How to reduce average handle time safely: split AHT into talk, hold and wrap-up, remove real delays, and track resolution and satisfaction alongside it.

Call editorial team · Published · 5 min read

Few measures are as tempting, or as dangerous, as average handle time. It is easy to calculate and it moves staffing costs, so managers watch it closely. But push it the wrong way and you get agents who hurry callers, transfer calls to avoid long ones, or close a case before it is solved. The caller rings again, and your real workload rises.

A contact centre agent with a headset reviewing a customer record on screen
Illustrative image

This guide explains what AHT includes, how to find where the minutes go, which improvements are safe, and how to protect quality while you work on it. It sits alongside Contact Center KPIs Explained.

What AHT includes

AHT is the average time an agent spends on one contact from start to finish. It has three parts:

PartWhat it isTypical cause of excess
Talk timeTime speaking with the callerUnclear questions, long greetings, repeated explanations
Hold timeTime the caller is on hold or being transferredAgent searching for answers, asking a colleague
After-call workNotes, tickets and follow-ups after the callFree-text notes, duplicate data entry, many systems

Some desks add the ringing or authentication time as a fourth part. What matters is that you agree on the definition and keep it consistent, otherwise comparisons across months mean nothing.

Why AHT alone is a poor target

A call that is too short is often a call that did not resolve the problem. When a target is set on AHT alone, people respond reasonably: they finish calls quickly. The cost appears elsewhere, in repeat calls, escalations and lower satisfaction.

Healthy and unhealthy AHT improvement

HealthyUnhealthy
How it is achievedBetter tools, scripts and trainingPressure to end calls sooner
Effect on resolutionStays the same or improvesFalls; callers ring back
Effect on agentsLess frustration, clearer workStress, shortcuts, turnover
What you trackAHT with resolution and satisfactionAHT alone

Find where the time goes

Before changing anything, measure. Split AHT by call type, by agent group and by its three parts. Averages across everything hide the truth: a billing call and a delivery question have different natural lengths.

A short diagnosis

  1. Split by call typeGroup calls by reason and note the longest types.
  2. Split by partFor each type, see whether talk, hold or after-call work dominates.
  3. ListenReview a sample of long calls in each type, with recordings or transcripts.
  4. Name the causesWrite the reason each long call took time: a search, a policy question, a system delay.
  5. Choose onePick the cause that appears most and fix that first.

Looking at the distribution, not just the mean, helps too. A small number of very long calls can pull the average up; those may deserve their own escalation path rather than a general push on speed.

Reduce talk time without rushing

Tighten the opening

A greeting that identifies the business, asks how to help and verifies identity in a smooth order saves seconds on every call. Write it, test it, and let agents say it naturally.

Ask better questions

Open questions invite long stories; targeted questions get facts. Train agents to start open, then narrow: "What happened?" followed by "When did that start?" and "What did you see on the screen?"

Use call scripts as guides

A short guide for common call types helps with sequence and key points, while leaving room for the human. How to Write a Sales Call Script has techniques that also apply to service calls.

Fix the menu

Calls that arrive at the wrong team waste time before the conversation starts. If agents often say "let me transfer you", review the menu in IVR Menu Design.

Reduce hold and search time

Holds usually mean the agent is looking for something. Make that quicker.

Good content matters more than good search. Building a Knowledge Base for Support and AI covers writing it.

Reduce after-call work

After-call work is often the easiest part to shorten, because it does not involve the caller at all.

Ways to shorten wrap-up

  • Structured notesReplace free text with a short form: reason, outcome, next step.
  • Automatic summariesLet a tool draft the call summary, and have the agent check and correct it.
  • TemplatesOffer ready-made replies and follow-up messages for repeat situations.
  • Fewer systemsReduce re-keying by linking the phone, CRM and ticketing tools.
  • Clear outcome codesA short list of outcomes saves time and gives better reports.

Call summaries drafted by AI can reduce typing, but a person should review them before they are saved. AI Call Summaries looks at how.

A hypothetical example

Imagine a small support desk where order-status calls are the longest type. Listening to a sample shows that agents spend much of each call looking up the order in one system and the delivery status in another, then typing a long note. None of that is the agent's fault.

Talk time barely changes, because the conversation itself is fine. Hold time and wrap-up fall, and resolution stays steady. That is what a safe improvement looks like: the same quality of conversation, with less friction around it.

Protect quality while you improve

Three safeguards keep the effort honest.

Set targets that make sense

Set AHT targets per call type, and revisit them after each change to tools or processes. A target should describe what a competent agent, using good tools, can reasonably do. If most of the team misses it, the target or the process is wrong. Make the staffing model aware of the new figures; Workforce Management shows how handle time feeds scheduling.

Monthly AHT review

  • AHT split by call type and by its three parts
  • A sample of long calls listened to and causes noted
  • First call resolution and satisfaction checked alongside
  • One improvement chosen, assigned and dated
  • Targets reviewed for call types whose process changed

Supporting this in Call

In Call, agents set their status, including a wrap-up state after a call, so after-call work is visible. Call history keeps a summary and transcript for each call, which helps both writing up and reviewing long calls. Knowledge sources let you keep the answers your AI agent and your team rely on in one place. Quality scorecards and the Queues screen show averages such as handle time and answer speed per queue, which you can read next to resolution and satisfaction. See Setting Up Call Queues and Building Quality Scorecards in Call.

Frequently asked questions

What is a good AHT?

There is no universal figure. It depends on your call types, so compare your own trends by call type and judge them alongside resolution and satisfaction.

What does AHT include?

Talk time, hold time and after-call work, averaged across calls. Some teams also include authentication or ringing time; just keep the definition consistent.

Can lowering AHT hurt customers?

Yes, if it is done by rushing. Callers may ring back, which raises workload. Track first call resolution and satisfaction with it.

What is the quickest way to reduce AHT?

Often shortening after-call work through structured notes, templates or reviewed automatic summaries, since it does not affect the conversation with the caller.

Should agents be ranked by AHT?

Avoid it. Compare within the same call type and use the numbers to find coaching needs, not to punish.

How often should AHT be reviewed?

Monthly for targets and weekly while you are making changes, split by call type rather than as one desk-wide number.

Track handle time by queue in Call

In the demo console you can try incoming calls in a simulation.

Related guides