What is Average Handle Time?
Average duration to handle a customer contact.
How to calculate it
Calculate Average Handle Time as: Total handling time / Number of contacts. Pull the inputs from your connected data and track the trend over time in your dashboard.
Examples
Example 1
1,000 contacts handled in 7,500 minutes -> 7.5-minute AHT; don't cut it at the cost of resolution.
Example 2
1,000 contacts handled in 7,000 minutes -> 7-minute AHT. A new knowledge base trims it to 6 minutes while FCR holds steady, a genuine efficiency gain.
Why it matters
Average handle time (AHT) is the average duration to handle a customer contact and balances efficiency against resolution quality. It helps with staffing and capacity planning, but it must never be optimized in isolation. Cutting AHT at the expense of first contact resolution simply shifts cost to repeat contacts.
Benchmark context
Varies by channel and complexity; optimize it only alongside FCR and CSAT so faster handling doesn't degrade outcomes.
Common pitfalls
Cutting AHT at the expense of resolution.
The complete guide
Understanding Average Handle Time
Average handle time (AHT) is the average duration to handle a customer contact and balances efficiency against resolution quality. It helps with staffing and capacity planning, but it must never be optimized in isolation. Cutting AHT at the expense of first contact resolution simply shifts cost to repeat contacts. For context, varies by channel and complexity; optimize it only alongside FCR and CSAT so faster handling doesn't degrade outcomes. Treat an external benchmark as a reference point rather than a universal target: company stage, sector, customer mix, pricing model and measurement definitions can materially change what “good” looks like. Read Average Handle Time alongside First Contact Resolution and Response Time; together these measures provide a more balanced view and reduce the risk of optimizing one number at the expense of the wider outcome.
Make sure the numerator and denominator cover compatible populations and periods, and avoid dividing by a partial or unusually small base. Document business-hours rules, bot interactions, reopened tickets, pending time and the event that marks a case as resolved. Split the measure by channel, priority, issue type, customer tier and business-hours policy so that ticket mix does not create a misleading average. A dashboard should show the current value, prior-period comparison and a trend rather than presenting one isolated reading.
Improve the measure by diagnosing demand and flow: remove repeat contact causes, strengthen knowledge content, route accurately, balance staffing to arrival patterns and coach from quality reviews. Common pitfalls: cutting AHT at the expense of resolution. Record the definition beside the dashboard, review it when systems or processes change, and annotate unusual events so future readers can distinguish a genuine performance shift from a data or timing effect.
Sources and further reading
- ITSM metrics: what to measure and why it matters
Zendesk Accessed
- Analyzing the metrics that matter to improve customer support
Zendesk Accessed
Related KPI guides
Turn KPI definitions into governed dashboards
Metricwise helps teams define metrics once, reuse them across dashboards, and ask trusted business questions in plain English.
Get Started