Average Handle Time (AHT) is the average duration of a customer interaction including talk time, hold time, and after-call work. Formula: AHT = (Total Talk Time + Total Hold Time + Total After-Call Work) ÷ Number of Interactions. Industry average is 4–8 minutes depending on contact type.
Definition
AHT measures how long the average handled interaction takes from start to finish, including the work that happens after the customer disconnects. Because it rolls talk time, hold time, and after-call work into one number, it is often the first metric leaders watch when labor costs rise or service levels slip.
The problem is that AHT can mislead teams when it is treated as a speed contest. A shorter call is not always a better call. Some interactions need time to uncover the real issue, explain policy clearly, secure payment, or complete enrollment accurately. If leaders ignore that, they may cut seconds from the call and add far more cost through repeat contacts, failed conversions, or compliance mistakes.
Formula
The standard formula adds total talk time, total hold time, and total after-call work, then divides the sum by the number of interactions handled. If a team spends 3,000 minutes talking, 300 minutes on hold, and 600 minutes on wrap-up across 500 contacts, AHT is 7.8 minutes.
That single number is useful only when you also know the contact mix. Technical troubleshooting, insurance enrollment, and debt recovery all require more explanation than simple order status calls. AHT should always be segmented by queue, intent, and outcome.
AHT benchmarks by vertical
| Vertical | World-class | Good | Average | Needs improvement |
|---|---|---|---|---|
| Collections | 6–7 min | 7–8 min | 8–9 min | >9 min or <6 min without good outcomes |
| Insurance enrollment | 8–9 min | 9–10 min | 10–12 min | >12 min or unusually short calls with low conversion |
| B2B SaaS support | 5–6 min | 6–7 min | 7–8 min | >8 min |
| Technical support | 10–11 min | 11–13 min | 13–15 min | >15 min |
Why collections and enrollment AHT floors exist
Some call types have a natural floor below which the result usually gets worse. Collections is one of them. A payment conversation often requires verification, context, objection handling, and a next-step summary. If AHT drops too far, it may mean agents are skipping discovery or rushing customers into a short close that never turns into payment kept.
Insurance enrollment has the same pattern for different reasons. Customers need enough time to understand plan choices, dates, and documentation requirements. Short calls can look efficient while conversion accuracy falls or later callbacks rise. In both cases, very low AHT is not proof of strength. It can be a warning that agents are moving too quickly for the job in front of them.
AHT vs. CSAT trade-off
There is no rule that longer calls create better experience. There is also no rule that shorter calls do. The useful question is whether time spent on the call was productive. If a call is long because the agent repeats information, puts the customer on hold twice, or cannot find the right workflow, that hurts CSAT. If the call is long because the agent is solving a layered issue thoroughly, that can improve satisfaction and first call resolution.
That is why leaders should not push a single sitewide AHT target across very different queues. The right goal is the shortest call that still achieves the right outcome with the right customer experience.
After-call work as the hidden driver
Many teams focus on talk time because it is easy to hear and easy to coach. Yet after-call work often explains why AHT drifts up. Weak note templates, manual documentation, extra system hops, and unclear case-close rules can add a minute or more to every interaction. Across a full month, that becomes a major labor cost.
Unlike live conversation time, after-call work is also easier to redesign. Better CRM defaults, shorter wrap-up codes, clearer compliance prompts, and automation for repetitive notes can pull AHT down without forcing agents to rush the customer.
How automated call scoring surfaces AHT anomalies
Average values hide a lot. Two agents can have the same AHT for completely different reasons. One may spend extra time doing excellent discovery. Another may spend the same extra time in silence, poor hold handling, or circular explanations. Automated call scoring helps separate those patterns.
That matters because the fix for a healthy long call is not the same as the fix for an unhealthy long call. Analytics can show whether AHT outliers are tied to call type, script confusion, transfer behavior, or specific reps. That makes AHT useful for diagnosis instead of just pressure.
FAQ
What is a good average handle time?
It depends on the queue. General support may sit at 4 to 8 minutes, while collections, enrollment, and technical support often need more time.
Why can lower AHT be worse?
Because shorter calls can come from rushed discovery, weak explanation, or incomplete resolution that creates more work later.
What is included in AHT?
Talk time, hold time, and after-call work divided by the total number of handled contacts.
How does after-call work affect AHT?
It can quietly add major labor time, especially when systems force manual notes or duplicate steps after every call.
How can call scoring help with AHT?
It identifies whether long calls come from useful issue resolution or from waste such as dead air, repeated explanations, or weak hold handling.
Score Your Calls for AHT Patterns
Find the difference between healthy long calls, hidden wrap-up waste, and the conversations that are dragging time without improving outcomes.
Email: amanda@altorlab.xyz
Related metrics: CSAT Score, Deflection Rate, Escalation Path, Agent Occupancy Rate, First Call Resolution