Core metrics

What is average handle time?

Also known as: AHT

Published September 10, 2026 · Reviewed by the Fidiora team

Definition

Average handle time is the mean duration an agent spends on a single contact, including talk or chat time, hold time, and after-contact work such as notes and tagging. It is a capacity planning metric. It tells you how many contacts a team can absorb, not how well those contacts went.

Why it matters

Average handle time is the number most often used to justify headcount, and the number most often gamed. Pushing it down without changing the work simply moves cost elsewhere: agents rush, quality drops, customers come back, and total cost per resolved issue rises even as the dashboard improves.

What to know

  • After-contact work is frequently excluded by accident, which understates true handle time by a wide margin.
  • Handle time distributions are heavily skewed, so the median is a better planning input than the mean.
  • A rising AHT is not automatically bad. If automation removes the short easy contacts, the human average must rise.
  • Compare AHT within an issue type. Across issue types the number is close to meaningless.
  • AHT plus reopen rate together tell you far more than AHT alone.

How to calculate it

AHT = (total talk or chat time + hold time + after-contact work) / number of contacts

An example

Example: a team automates password resets, which took two minutes each. Average handle time jumps from nine minutes to fourteen. Nothing got worse. The quick contacts left the human queue, so the remaining mix is harder by definition.

Common mistakes

  • Setting an AHT target without segmenting by issue type
  • Excluding after-contact work from the calculation
  • Treating a rise in AHT after automation as a regression
  • Rewarding agents on AHT, which reliably increases reopen rate
Where Fidiora fits

Fidiora removes the short repetitive contacts from the human queue entirely, which usually raises human average handle time and lowers total cost per resolved issue at the same time. Read the two numbers together rather than celebrating or panicking about either alone.

See Pricing
FAQ

Questions

What is a good average handle time?
There is no portable benchmark, because the number is driven almost entirely by issue mix. A team handling refunds and a team handling API debugging cannot be compared. Track your own AHT per issue type and watch the trend.
Why did our AHT increase after adding AI?
Because automation removes the easiest and shortest contacts first. The humans are left with a harder mix, so their average rises. Check cost per resolution instead, which should fall.
Should agents be measured on handle time?
Not as a primary target. Individual AHT goals reliably push agents to close early, which raises reopen rate and total cost. Use it for capacity planning, not performance management.

Related terms

First response time First response time is the elapsed time between a customer submitting a request and receiving the first meaningful reply... Cost per contact Cost per contact is the average fully loaded cost of handling one customer interaction, calculated by dividing total sup... Reopen rate Reopen rate is the share of tickets marked resolved that are subsequently reopened, either by the customer replying or b... First contact resolution First contact resolution is the share of customer issues fully solved during the first interaction, with no follow-up, t...
Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

Start Free Book a 15-min Demo

No credit card · Live in under an hour