Skip to content

Guide

What Is AHT? Average Handle Time Meaning and Formula

What is AHT? Average handle time meaning, the AHT formula with a worked example, what a good AHT score looks like, and how to lower it safely.

· Updated · 6 min read

Part of: IQS Meaning: Internal Quality Score in Customer Service

What is AHT? AHT stands for average handle time: the average time an agent spends on one customer contact, including talk time, hold time and after-call work. To calculate it, add those three totals for a period and divide by the number of contacts handled. Contact centers use it for staffing, and read it next to quality so speed does not cost resolution.

In short

  • AHT full form: average handle time (sometimes “average handling time”).
  • AHT = (talk time + hold time + after-call work) / contacts handled.
  • AHT drives staffing and forecasting, so small changes matter.
  • There is no universal good AHT score: compare against your own baseline per channel and contact type.
  • Pushing AHT down can hurt resolution and satisfaction, so read it next to quality.

What does AHT mean?

AHT means average handle time, the average total time it takes an agent to deal with one contact from start to finish, including the wrap-up work after the customer has gone.

Handle time covers the full effort of a contact, not just the conversation. It has three parts: talk time (or active chat time), hold time while the customer waits, and after-call work, which is the wrap-up an agent does after the contact ends, such as logging notes, tagging the ticket or updating a record. Some teams call it “average handling time”; the meaning is the same.

AHT is an operational metric. It tells you how much agent time each contact consumes, which is why workforce planners watch it closely. It does not tell you whether that time was well spent or why contacts take as long as they do, which is why it needs a quality measure and support insights next to it.

How is AHT calculated?

AHT is calculated by adding total talk time, total hold time and total after-call work for a period, then dividing by the number of contacts handled in that period.

ElementDetail
FormulaAHT = (total talk time + total hold time + total after-call work) / number of contacts handled
ComponentsTalk time, hold time, after-call work (wrap-up)
UnitUsually minutes and seconds, or seconds
PeriodA day, week or month, per agent, team, queue or channel
Watch out forLower AHT at the expense of resolution and quality

A worked AHT example

Say one agent handled 40 calls in a day. Across those calls they spent 200 minutes talking, 20 minutes with customers on hold and 60 minutes on after-call work. Total handle time is 200 + 20 + 60 = 280 minutes. Divided by 40 calls, the AHT is 7 minutes.

The same arithmetic works for a team: add every agent’s totals and divide by every contact the team handled. Calculate it from totals rather than averaging each agent’s AHT, or agents with few contacts will skew the result.

AHT in chat and email

For chat and email, handle time is the time an agent actively works the conversation, not the time it stays open. Agents often handle several chats at once, so chat AHT is not comparable with voice AHT, and email AHT depends on how your helpdesk records working time. Always compare AHT within one channel.

What is a good AHT score?

A good AHT score is one that resolves the issue properly in the least time for that channel and contact type; there is no single benchmark that fits every team.

Published benchmarks vary widely because they mix industries, channels and definitions (some exclude after-call work), so a figure from another company says little about yours. A password reset and a billing dispute will never have the same handle time, and a technical or high-value contact should take longer.

The more useful benchmark is your own. Track AHT per channel and per contact reason, set a baseline, and look at the outliers in both directions together with First Contact Resolution and quality. A contact type whose AHT is falling while repeat contacts rise is a warning, not a win.

Why lower AHT is not always better

Lower AHT is not always better, because agents can cut handle time by rushing, skipping steps or closing contacts before the issue is solved, which raises repeat contacts and costs more overall.

It is tempting to treat AHT as a number to minimize, but that logic breaks down quickly. An agent can shorten handle time by rushing customers, skipping verification, or closing a contact before the issue is really solved. That drives AHT down while pushing repeat contacts up and satisfaction down.

The healthier way to read AHT is as a balance. A very high AHT can signal inefficiency, missing knowledge or poor tools, while a very low AHT can signal corners being cut. The goal is not the smallest possible number, it is the time it genuinely takes to resolve an issue well.

How to reduce AHT without hurting quality

To reduce AHT safely, remove the causes of wasted time, such as searching for answers, unnecessary holds and manual wrap-up, rather than asking agents to talk faster.

LeverWhat it removesCheck it did not hurt
Better knowledge base and macrosTime spent searching for the right answerAccuracy of answers in QA reviews
Fewer holds and transfersWaiting while the agent asks a colleagueResolution on first contact
Faster wrap-up (templates, auto-tagging)Manual after-call workNote quality and tagging accuracy
Coaching on the slowest contact typesUncertainty on complex issuesQuality score on those contact types
Fixing the root cause of common contactsContacts that should never happenContact rate for that reason

The last lever is the largest: a contact that does not happen has no handle time. Our guide to reducing customer contact rate covers how to find and remove those contacts, and Kaizo’s insights show which broken process, product friction or skill gap is behind them.

AHT and quality assurance

AHT cannot tell you whether time was well spent, so it needs a quality score next to it: a short contact is good only if the issue was resolved and the customer was treated well.

A short handle time is good if the issue was resolved, and bad if it was not. A quality score such as an Internal Quality Score (IQS) checks the actual content of each conversation, so a fast contact can be checked against whether it was also a good one. Kaizo scores 100% of conversations against your own scorecard, reading them from Zendesk or Salesforce, so teams can protect quality while they work on efficiency rather than trading one for the other.

Balance AHT with real conversation quality

Take your highest-AHT and lowest-AHT contact types and read ten conversations from each before you change a target. In a live demo we will show you, on sample data, how Kaizo scores every conversation against your scorecard so you can see quality next to speed.

Let's talk Explore the Kaizo platform

Frequently asked questions

What is the full form of AHT?

The full form of AHT is average handle time, sometimes written as average handling time. It is the average time an agent spends on one customer contact, counting talk or active chat time, hold time and the after-call work needed to wrap up. It is one of the most common metrics in call centers and BPOs.

Does AHT include hold time and after-call work?

Yes. Standard AHT includes talk or active chat time, hold time and after-call work, because all three keep an agent busy and unavailable for the next contact. Some reports leave out after-call work, which makes AHT look shorter than it is. When you compare AHT between teams, tools or published benchmarks, check first that they count the same components.

How does AHT affect staffing?

AHT is a direct input to staffing models. Expected contacts multiplied by AHT gives the agent hours a queue needs, so if AHT rises from 6 to 7 minutes on the same volume, the workload grows by about one sixth and you need more agent hours to keep the same service level. That is why workforce planners track AHT per queue and channel.

What is the difference between AHT and FRT?

AHT measures how long it takes to handle a contact once it is being worked, while First Response Time measures how long the customer waits before getting any reply. One is about effort per contact, the other is about initial responsiveness. A team can have a fast first response and a long handle time, or the reverse.

In KaizoDashboardsCoverage, quality trends and coaching impact report natively. No BI project, no monthly assembly job.See Dashboards

On this page

See this in a live demo

We will walk you through Kaizo with realistic sample conversations, so you see the example scored, explained and coached.

Trusted by global support teams

  • Foot Locker
  • Canva
  • GetYourGuide
  • Instacart
  • BlaBlaCar
  • UiPath