Average Handle Time (AHT) is the average total time an agent spends on a single customer interaction — including talk time, hold time, and after-call work — measured from the start of the interaction to the moment all related work is complete. AHT is one of the most widely tracked contact center metrics, and one of the most often misused.
AHT formula: AHT = (Total Talk Time + Total Hold Time + Total After-Call Work) ÷ Total Number of Contacts
Average Handle Time is one of the most widely tracked metrics in customer service — and one of the most often misused. Almost every contact center reports it. Most contact center leaders are evaluated on it. Many teams set explicit targets around it.
The problem is that AHT only tells you something useful when it sits inside a broader context. On its own, optimizing for AHT often makes your customer experience worse — not better. This is the gap between what AHT measures and what businesses think it measures, and it costs a lot of operations real money every year.
Here is what AHT actually is, how to calculate it correctly, what good looks like by industry, and — most importantly — when to use it and when to ignore it.
What Average Handle Time Actually Measures
AHT is the average total time an agent spends on a single customer interaction, from the moment the interaction begins to the moment all work related to it is complete.
For a phone call, that includes:
- Talk time — the time the agent is actively speaking with the customer
- Hold time — any time the customer was placed on hold during the interaction
- After-call work (ACW) — the time the agent spends documenting the call, updating the CRM, sending follow-up emails, or completing any task the call generated
For chat and email, the components shift slightly, but the principle is the same: AHT captures the total time an agent's attention is occupied by a single contact, end-to-end.
The AHT Formula
The standard formula is straightforward:
AHT = (Total Talk Time + Total Hold Time + Total After-Call Work) ÷ Total Number of Contacts
So if your team logged 4,000 minutes of talk time, 800 minutes of hold time, and 1,200 minutes of after-call work across 800 contacts in a week, your AHT would be:
(4,000 + 800 + 1,200) ÷ 800 = 7.5 minutes per contact
This number is what gets reported. What it does not tell you is whether those 7.5 minutes solved the customer's problem, whether the customer is happy, or whether they are going to call back tomorrow about the same issue.
Industry Benchmarks for AHT
There is no universal "good" AHT number. The right target depends heavily on industry, channel, and the complexity of the interactions your team handles.
Rough benchmark ranges by industry (phone):
- Retail / e-commerce — 4 to 6 minutes
- Telecommunications — 6 to 9 minutes
- Healthcare — 7 to 12 minutes
- Financial services / banking — 6 to 10 minutes
- B2B SaaS / technical support — 10 to 20 minutes
Email and chat AHT runs differently because agents typically handle multiple contacts concurrently and the timing definitions vary. Industry benchmarks for those channels are far less standardized.
The more important comparison is internal: how does your AHT trend over time, and how does it segment by contact type? An AHT of 8 minutes that is consistently 8 minutes is a stable operation. An AHT of 8 minutes that swings between 5 and 12 depending on the week is an operation with a coaching, training, or routing problem.
Why AHT Can Mislead You
Here is the uncomfortable truth about AHT: pushing it down does not reliably improve customer experience. In many cases, it actively damages it.
Three reasons:
Lower AHT often means more repeat contacts. When agents are evaluated on speed, they rush to close contacts. They miss the underlying issue, leave gaps in the resolution, or fail to confirm the customer is genuinely set up correctly. The customer hangs up — and calls back tomorrow. AHT goes down, but Repeat Contact Rate goes up, and total cost-to-serve actually increases. We covered this dynamic in detail in The Real Cost of Repeat Customer Contacts.
Lower AHT often means worse FCR. First Contact Resolution — the percentage of contacts resolved on the first interaction — is a much more predictive metric of customer satisfaction and retention than AHT. When teams over-prioritize AHT, FCR predictably suffers. The relationship between the two metrics is well documented in contact center research: most operations that aggressively lower AHT see FCR drop within a quarter.
Lower AHT often means worse customer effort. Customer Effort Score — how hard the customer had to work to get their issue resolved — drops when agents rush to close. Customers feel processed, not served. They may not complain about it on the post-call survey, but they will quietly increase the likelihood of churning out over the next six months.
In other words: AHT is a cost metric being asked to do the job of a quality metric. It cannot do that job. When you optimize an operation purely for AHT, you optimize for the wrong outcome.
When AHT Is Genuinely Useful
This does not mean AHT is useless. Used correctly, it is a valuable operational signal. Three legitimate uses:
As a capacity planning input. Your AHT, multiplied by your forecasted contact volume, tells you how many agent hours you need next week. Capacity planning is impossible without it.
As a diagnostic for individual outliers. If one agent's AHT is dramatically higher or lower than peers handling similar contacts, that is a coaching signal. It might mean they are over-explaining, struggling with the technology, or quietly cutting corners. Either way, it is worth investigating.
As a paired metric. AHT viewed alongside FCR, CSAT, and Repeat Contact Rate paints a real picture. An operation where AHT trends down while FCR holds steady or improves is genuinely getting more efficient. An operation where AHT trends down and FCR collapses is cannibalizing customer experience for cost optics.
The rule of thumb: AHT is a meaningful metric when it is in dialogue with quality metrics. It is a misleading metric when it is reported in isolation.
How to Improve AHT Without Hurting Quality
If you have decided your AHT genuinely needs to come down — for capacity or cost reasons — there are ways to do it that do not sacrifice customer experience.
Reduce after-call work, not talk time. ACW is often inflated by clunky CRM workflows, redundant data entry, or the need to write the same notes multiple times. Streamlining the agent's documentation flow can shave 30 to 90 seconds per contact without touching the customer interaction at all.
Fix the upstream cause of common contacts. If your team is fielding 200 calls a week asking the same question, the answer is not to coach agents to answer it faster. It is to fix the website, the email confirmation, or the product itself so the question stops getting asked. This is the highest-leverage way to reduce both AHT and total contact volume.
Improve agent tooling and knowledge access. Agents who can find the right answer in 10 seconds resolve contacts faster than agents who navigate three tabs and a wiki to find it. Investments in agent enablement and knowledge base quality typically pay back faster than any other AHT initiative.
Reduce hold time, specifically. Hold time is the worst component of AHT from a customer experience perspective. Customers hate holds. If your hold time is more than 15% of total handle time, you have a process problem — agents are looking up information they should already have, or transferring to subject-matter experts on issues they should be empowered to resolve themselves.
Coach on call structure, not call speed. Coaching that focuses on how to structure an interaction — clear opening, focused diagnostic, confirm-resolve-document close — reduces AHT as a side effect without ever explicitly targeting it. Coaching that explicitly tells agents to "be faster" produces worse outcomes on every metric except AHT.
AHT in Different Channels
A note on multi-channel operations: AHT means slightly different things across channels, and you should resist the urge to compare them directly.
- Phone AHT is the cleanest version — one agent, one customer, end-to-end.
- Chat AHT is typically reported per session, but a chat agent may handle 2 to 4 conversations concurrently. Effective handle time per chat is much lower than wall-clock time would suggest.
- Email AHT is even more ambiguous because email is asynchronous. Most teams report time-in-queue (how long the customer waited for a response) separately from time-to-respond (how long the agent spent writing).
If you operate across all three channels, build separate AHT views per channel rather than reporting a blended number. The blended number will hide more than it reveals.
What Good Looks Like
A healthy AHT report includes three things:
- The AHT number itself, segmented by channel, contact type, and tenure cohort
- The companion metrics — FCR, Repeat Contact Rate, and CSAT for the same period
- A trend line over at least 8 weeks so you can see whether AHT changes are sticking or fluctuating
Reports that show only the AHT number, isolated from quality signals, will lead you to optimize for the wrong outcome. We covered the broader pattern in how to build a customer service metrics dashboard.
The Bottom Line
Average Handle Time is one of the easiest metrics to track and one of the easiest to misuse. The teams that get value from AHT treat it as a capacity signal and an operational diagnostic — not a quality target. The teams that get hurt by AHT treat it as the primary measure of agent performance.
If your operation is currently leading with AHT in performance reviews, on dashboards, and in coaching conversations, that is worth re-examining. The metric is fine. The framing around it is what does the damage.
Consumer Core Solutions helps customer service operations design metrics frameworks that balance efficiency and quality — and rebuild coaching processes around them. Reach out if you want to discuss your current operation.