Average Handle Time (AHT) is the average time an agent spends on one contact, including talk, hold and after-call work. Add those three totals and divide by the number of contacts.
In short
- AHT drives staffing and forecasting.
- Pushing it down can hurt resolution and satisfaction.
- Read it next to quality and resolution metrics, never alone.
How to calculate AHT
Average Handle Time captures the full effort of a contact, not just the conversation. It sums three parts: talk time, hold time, and after-call work, which is the wrap-up an agent does after the customer is gone, such as logging notes or updating a record. You add those three across all contacts, then divide by the number of contacts to get the average.
Because AHT feeds staffing models directly, small changes matter. If AHT rises, the same volume of contacts needs more agent hours, so the metric is watched closely in workforce planning.
| Element | Detail |
|---|---|
| Formula | AHT = (total talk + hold + after-call work) / number of contacts |
| Components | Talk time, hold time, after-call work |
| Typical benchmark | Often cited near 6 minutes for voice, but varies widely |
| Watch out for | Lower AHT at the expense of resolution and quality |
Why lower AHT is not always better
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 steps, or closing a contact before the issue is really solved. That drives AHT down while pushing repeat contacts, low satisfaction, and poor First Contact Resolution up, which costs more overall.
The healthier way to read AHT is as a balance. A very high AHT can signal inefficiency or missing 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.
AHT and quality assurance
AHT on its own cannot tell you whether time was well spent, and that is exactly why it needs a quality lens. A short handle time is good if the issue was resolved and the customer was treated well, and bad if it was not. Kaizo scores the actual content of each conversation with its Internal Quality Score (IQS), so a fast contact can be checked against whether it was also a good one. By connecting conversation quality to operational metrics like AHT, and reading conversations natively from Zendesk and Salesforce, Kaizo helps teams protect quality while they work on efficiency, rather than trading one for the other.
Frequently asked questions
What is a good AHT?
There is no single correct AHT, because it depends on channel and issue complexity. A figure near 6 minutes is often cited for voice, but a technical or high-value contact should take longer. Compare AHT against your own baseline and always read it alongside resolution and quality metrics.
How is AHT calculated?
AHT = (total talk + hold + after-call work) / number of contacts. You sum talk time, hold time, and after-call wrap-up work across all contacts, then divide by the number of contacts handled in the period.
Is a lower AHT always better?
No. Reducing AHT can improve efficiency, but pushing it too low often means agents rush and issues go unresolved, which raises repeat contacts and lowers satisfaction. AHT should be balanced against First Contact Resolution and conversation quality, not minimized in isolation.
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.
Related terms
- First Contact Resolution
- First Response Time
- CSAT
- Internal Quality Score
- Customer service metrics and KPIs
Balance AHT with real conversation quality
See how Kaizo scores 100% of your conversations and links quality to metrics like handle time, straight from Zendesk or Salesforce.
