Average Handle Time

Goal of the analysis:

Average Handle Time (AHT) measures the average active time an agent spends handling a customer contact, usually defined as talk/chat time plus hold time plus after-call work (ACW). The goal is to quantify efficiency by channel and queue, understand drivers of variation, and balance speed with quality (first contact resolution, CSAT). For executives, AHT informs staffing and cost-to-serve, signals process/tool friction, and highlights where automation or training can unlock capacity without compromising customer outcomes.

Data required:

• Interaction and timing data (by channel):
  • Voice/phone: call start/end, talk time, hold time, transfers/conference, wrap/ACW duration, disconnect reason.
  • Chat/messaging: conversation start/end, agent join time, active chat duration (agent typing/reading), concurrent session count, wrap time.
  • Email/ticket/asynchronous: timestamps and durations for each agent “touch” (worklog), number of touches, total agent work minutes per case.
  • Bot/IVR handoff timestamps to separate pre-agent time from agent handle time.
• Ticket and customer metadata:
  • Ticket/interaction ID, queue/skill, priority/severity, issue category/subcategory, product/version, language, region.
  • Customer tier/entitlement, account segment (consumer, SMB, enterprise).
  • Outcome metrics: first contact resolution (FCR), reopen rate, CSAT/DSAT, escalation flags.
• Agent/workforce context:
  • Agent ID, role/skill, tenure, schedule (WFM), occupancy, adherence, time-off.
  • Coaching/QA scores, knowledge certification status.
• Process and tooling signals:
  • CRM/CTI integration logs (screen-pop latency), system response times, knowledge article usage, macro/template utilization.
  • Transfers, reassignments, swarming participation, approval workflows.
• Governance and definitions:
  • Formal AHT definitions by channel and queue (e.g., what counts as hold vs idle; ACW cutoff).
  • Exclusions: test calls, short abandons, spam, contacts under X seconds, or bot-contained interactions.
• Systems and sources:
  • CRM/ticketing (Salesforce, Zendesk, ServiceNow), CCaaS/ACD (Genesys, Five9, NICE), chat/messaging (Intercom, LivePerson), WFM (Verint, Calabrio), knowledge systems, data warehouse/BI.

Detailed step-by-step instruction on how to conduct the analysis:

1. Define AHT by channel and scope.
   • Voice AHT = (Talk time + Hold time + ACW) / Calls handled.
   • Chat AHT (concurrency-adjusted) = (Sum of agent active chat time + Wrap) / Chats handled. Use platform “active” time to avoid double-counting when agents handle multiple chats.
   • Email/ticket AHT = Sum of agent worklog minutes per case (active handling and wrap) / Tickets handled. Report per-case AHT and per-touch AHT.
   • Decide measurement window (rolling 4–12 weeks) and unit (minutes).
2. Extract interaction records. Pull raw interaction logs with timestamps, durations, agent IDs, queue, and metadata. Normalize time zones to UTC and deduplicate merged/interrupted sessions.
3. Clean and classify.
   • Exclude abandons before agent connection; separate IVR/bot time from agent handle time.
   • Cap extreme outliers (e.g., stuck sessions) using winsorization or exclude with reason codes.
   • Map transfers: attribute handle time to each handling queue; also compute “end-to-end agent time” per case.
4. Assemble case-level views (for multichannel/asynchronous).
   • Link interactions to cases/tickets. Aggregate total agent handle minutes across all touches per case.
   • Count touches, days to resolve, and whether FCR was achieved (one-and-done).
5. Compute core metrics.
   • AHT by channel/queue/team/agent: mean, median (p50), p75, p90.
   • Component mix: share of talk vs hold vs ACW (voice); active vs wrap (chat); work minutes per touch (email).
   • Variance and stability: coefficient of variation (CV) of AHT; control charts for top queues.
   • Operational ties: occupancy, arrival rate, backlog at start-of-interval, transfer rate.
6. Segment and compare. Slice by issue category, product/version, customer tier, language/region, priority, time-of-day/day-of-week, and agent tenure/skill. Create complexity bands (simple/how-to, transactional, technical).
7. Link to outcomes and quality.
   • Correlate AHT with FCR, CSAT, DSAT, reopen rate, and escalations by segment.
   • Identify optimal ranges where FCR/CSAT are maximized and DSAT minimized (avoid chasing lowest AHT if quality suffers).
8. Diagnose drivers of long AHT.
   • Pareto by category/queue of high-AHT contacts; drill into hold reasons (tool latency, approvals, troubleshooting) and ACW causes (documentation burden, disjointed systems).
   • Analyze knowledge usage: low use correlated with long AHT; identify content gaps.
   • Check transfers/reassignments and CTI/CRM lags (screen-pop latency).
9. Agent-level insights and coaching. Compare agents to peer medians within the same queue and complexity band. Flag outliers with paired QA scores to distinguish skill gaps vs case mix.
10. Trend and seasonality. Build weekly time series for AHT and component mix; overlay events (releases, promotions) and staffing levels to explain changes.
11. Operationalize reporting. Automate ETL from CCaaS/CRM/chat into BI. Refresh weekly. Publish queue-level targets and track actions with owners and expected AHT/FCR/CSAT impact.

Format of the output of analysis:

• Executive summary: AHT by channel (p50/p90), component breakdown, SLA adherence, and impact on FCR/CSAT.
• Stacked bars showing AHT components (talk/hold/ACW) by queue; for chat, active vs wrap; for email, minutes per touch.
• Heatmaps by issue category/product showing AHT and volume.
• Control charts and trend lines for AHT and p90 by queue; annotations for releases or staffing changes.
• Scatter plots of AHT vs FCR/CSAT by queue and agent; bubble size by volume.
• Pareto of top drivers (transfers, tool latency, missing knowledge) and a remediation tracker.

How to interpret results:

• Lower is not always better. Very low AHT with low FCR or CSAT indicates rushing. Aim for an optimal band that balances quality and speed.
• High AHT with high FCR may be acceptable for complex technical cases (Tier 2/3); invest in deflection and better triage upstream rather than forcing speed.
• Component mix matters: excessive hold time suggests tool or approval bottlenecks; high ACW points to documentation/process friction; long talk time with many transfers indicates routing/skill mismatches.
• Channel differences: chat AHT reflects concurrency; ensure comparisons use active time. Email AHT should be assessed per case and per touch alongside resolution time and SLA.
• Variance is a signal: wide p90 vs median shows inconsistent execution or spiky complexity; tighten processes and playbooks to reduce tails.

Steps a company can take to improve on this measure:

• Process and routing:
  • Optimize IVR/bot triage and skills-based routing; reduce transfers via clearer queues and entitlements.
  • Introduce standard troubleshooting playbooks and guided workflows for high-volume categories.
  • Adopt swarming for complex cases to solve once quickly rather than multiple handoffs.
• Tooling and automation:
  • Integrate CTI–CRM–KB for screen pops and context; use macros/templates and auto-summaries to cut ACW.
  • Deploy AI-assisted suggestions and next-best actions; prefill forms and case fields via RPA/APIs.
  • Monitor and remediate system latency; prioritize performance fixes on agent desktops.
• Knowledge and content:
  • Build and maintain a high-coverage knowledge base with article quality KPIs tied to AHT/FCR.
  • Embed in-flow knowledge surfacing in agent UI; require article linkbacks for resolved cases to reinforce usage.
• People and coaching:
  • Target coaching using peer benchmarks within the same complexity band; pair with QA feedback on soft skills.
  • Onboard with scenario-based training and shadowing; certify on priority products/issues.
  • Right-size chat concurrency by skill to avoid ballooning AHT and DSAT.
• Channel and offer design:
  • Deflect simple intents to self-service and in-product help; steer urgent issues to real-time channels.
  • For complex enterprise issues, offer scheduled callbacks with preparation to reduce live handle time.
• Governance and targets:
  • Set queue-specific AHT bands tied to FCR/CSAT; review p90 and variance, not just averages.
  • Prevent gaming: monitor repeat contacts and resolution quality alongside AHT.

Benchmark comparisons:

General benchmarks:

• Voice (general support, mixed complexity): 4–6 minutes AHT typical; best-in-class Tier 1 often 3–5 minutes; technical Tier 2/3 can be 8–15+ minutes.
• Chat/messaging: 6–10 minutes of active handle time per conversation with 2–3 concurrent sessions for simple intents; complex technical chats can average 12–18 minutes with lower concurrency.
• Email/ticket (asynchronous): 15–30 minutes of cumulative agent work per case is common for standard issues; complex cases can exceed 45–90 minutes across multiple touches.
• Top performers pair target AHT bands with FCR ≥70–80% and CSAT ≥85–90% for Tier 1 queues.

Segment- or industry-specific benchmarks:

• E-commerce/retail: voice AHT 3–5 minutes; chat active time 4–7 minutes; heavy seasonality requires tight p90 control.
• B2B SaaS Tier 1: voice/chat AHT 5–8 minutes; Tier 2 technical 10–20 minutes; email work minutes per case 20–40.
• Telecom/ISP: voice AHT 6–9 minutes due to troubleshooting; strong scripts and tools can lower hold/ACW components.
• When external benchmarks are limited or misaligned, build internal targets by queue and complexity band; compare top quartile teams, track p50/p90 and variance, and ratchet targets quarterly in tandem with FCR/CSAT to avoid quality erosion.