Average Handle Time (AHT) is the mean duration an agent spends actively working on a single support contact — including the time spent reading the issue, researching the answer, composing the response, and completing post-contact wrap-up tasks. AHT is a primary driver of agent capacity and cost per ticket calculations.
?
What are the components of Average Handle Time and how should each be optimized?
AHT consists of three components for email/ticket support. Read time: time from ticket assignment to first read — optimized by routing tickets to agents based on skill match (agents immediately understand the issue context) and ensuring all information is visible in the first ticket view (account context, CRM history, prior conversations). Active time: time spent diagnosing, researching, and composing the response — optimized by: knowledge base search embedded in the ticket view (finding the relevant article in 30 seconds vs. 5 minutes through browser search), AI-draft suggestions that give agents a response to edit rather than compose from scratch, and macro libraries for the most common response types. Wrap-up time: tagging, logging, escalation notation, and other post-resolution actions — optimized by automation (the helpdesk auto-tags based on ticket content) and simplified taxonomy (too many tagging options creates post-resolution friction; a focused taxonomy of 15–20 tags covers 90% of cases). For live chat and phone, AHT also includes the active conversation time — adding conversation efficiency (avoiding unnecessary tangents, guiding toward diagnosis efficiently) as an optimization dimension.
?
What are typical AHT benchmarks for SaaS support operations?
SaaS support AHT benchmarks vary significantly by channel and issue complexity. Email/ticket: median AHT 8–15 minutes for Tier 1 simple inquiries; 20–40 minutes for Tier 1 complex troubleshooting; 30–90 minutes for Tier 2 technical investigations. Live chat: median AHT 6–12 minutes including active conversation time. Phone support: median AHT 8–15 minutes for SaaS product support. AI-assisted support (agent using copilot tools): 20–35% AHT reduction is commonly reported for AI-assisted vs. unassisted agents on comparable ticket types. The most important benchmark is your own historical trend, not industry averages — a team whose AHT is improving while CSAT and FCR also improve is optimizing effectively; a team whose AHT is declining but CSAT and FCR are also declining is likely rushing resolutions.
?
How does Support Ops prevent agents from gaming AHT metrics at the expense of quality?
When AHT is used as a primary performance metric, it creates a perverse incentive: agents minimize time spent on tickets by giving fast but incomplete answers, deflecting complex issues to self-service inappropriately, or marking tickets resolved prematurely. Anti-gaming measures: never report AHT as a standalone metric — always pair it with CSAT, FCR, and recontact rate in the same dashboard so quality signals immediately surface any manipulation. Set AHT as a benchmark range, not a maximum (e.g., "target range: 8–20 minutes for Tier 1 email" — tickets resolved in < 5 minutes are flagged for QA review as potential deflection, tickets > 30 minutes are flagged for coaching review). Include AHT in QA review context (was the resolution time appropriate given the complexity of the issue? — a 20-minute AHT on a simple how-to question is a training gap; a 20-minute AHT on a complex API integration issue is appropriate efficiency). Use AHT as a coaching trigger, not a punishment signal: an agent with consistently high AHT needs knowledge or process support, not a performance warning.
Knowledge Challenge
Mastered Average Handle Time (AHT)? Now try to guess the related 5-letter word!
Type or use keyboard