Support metrics glossary
Average handle time, minus the folklore.
Average handle time is the average total time one customer contact takes, from first hello to the last note on the ticket. It is the most watched number in support, and the one most often pushed the wrong way.
Last updated 14 August 2026
At a glance
AHT is total talk time plus total hold time plus total after-call work, divided by contacts handled.
What AHT actually measures
Talk time is the minutes an agent spends actively helping the customer. Hold time is every minute the customer waits while the agent hunts for an answer. After-call work is everything after the contact ends: the summary, the tags, the follow-up note.
Add the three across every contact in a period, divide by the number of contacts, and you have average handle time.
The formula, worked through
One week at a fictional team, 1,000 calls, numbers chosen so the arithmetic is easy to check.
| Component | Total minutes | Per call | Share of AHT |
|---|---|---|---|
| Talk time | 4,600 | 4.6 minutes | 59% |
| Hold time | 1,100 | 1.1 minutes | 14% |
| After-call work | 2,100 | 2.1 minutes | 27% |
| All work, 1,000 calls | 7,800 | 7.8 minutes | 100% |
The total, 7,800 minutes divided by 1,000 calls, is an AHT of 7.8 minutes, and there is no honest universal benchmark, because the right number swings with your issue mix and channel. A password reset and a billing dispute should not share a target.
The take most vendor blogs skip
Average handle time is not a speed score for agents. It is the largest single input into your cost per ticket, because support cost is mostly paid human minutes. Treat it as a stopwatch and three things happen. Agents cut contacts short. Customers call back. First contact resolution drops, and the second contact costs more than the minute you saved.
The levers that actually lower average handle time attack the parts the customer cannot see. Kill hold time: one searchable place where every answer lives, and routing that reaches the right agent first. Kill after-call work: an agent assist that drafts the summary while the conversation is warm.
Or remove the easy contacts from the queue entirely. That lever has a twist: automating simple questions, like the order-status tickets we cover on our WISMO page, pulls the fastest contacts out of the average. AHT rises even as cost and effort fall. That is not failure. It is arithmetic.
AHT is not first response time
First response time stops the clock at the first reply. AHT runs it to the end of the job. Ace one, bloat the other, and your blended number hides both facts.
Average handle time questions, answered
What is average handle time (AHT)?
The average total time one customer contact takes, including the parts the customer never sees: talk time plus hold time plus after-call work, divided by contacts handled. Report it per channel: chat concurrency makes a blended number useless.
What is a good average handle time?
There is no honest universal benchmark, and anyone who gives you one without knowing your issue mix is guessing. Judge your own trend: same channel, month over month. If it falls while first contact resolution and satisfaction hold steady, that is a win. If it falls because agents rush, you bought a worse queue with a nicer chart.
How do you calculate AHT?
Add talk time, hold time and after-call work for the period, then divide by the number of contacts. With 4,600 minutes of talk, 1,100 of hold and 2,100 of after-call work across 1,000 calls: 7,800 divided by 1,000 is 7.8 minutes. Use the same period for every input, or the number lies.
Is a lower AHT always better?
No. Lower is only better if resolution quality stays put. Shave 30 seconds by ending borderline contacts early and those customers call back, so the queue pays twice. Watch it next to first contact resolution and re-open rate, never alone.
What is the difference between average handle time and first response time?
First response time measures the wait for the first reply. Average handle time measures the whole job, first contact to wrap-up. A team can ace the first and still bloat the second: reply in 30 seconds, resolve in 3 days. Track both, and never blend them.
How do you reduce AHT without hurting quality?
Go after the invisible parts. Cut hold time by giving agents one searchable place where answers live. Cut after-call work with an agent assist that drafts summaries from the conversation itself. Then check what reaches the queue at all, because automating repetitive questions shrinks the work, not the care.