What AHT Actually Measures

Average handle time is the total time an agent spends on a ticket from open to close. It includes reading the initial message, researching the issue, writing a response, waiting for customer replies, and any follow-up work.

It's a useful metric. But it's not a goal.

If you optimize for AHT alone, you get agents who rush through tickets, give incomplete answers, and close tickets prematurely. The customer writes back, a new ticket opens, and your actual cost-per-resolution goes up even though AHT went down.

The goal is to reduce AHT while maintaining (or improving) first-contact resolution rate and customer satisfaction. That's harder, but it's the only version worth pursuing.

Better Routing Gets You the Biggest Win

The single most impactful thing you can do for AHT is get tickets to the right person on the first try.

When a billing question lands with a technical support agent, they spend five minutes reading it, realize it's not their domain, transfer it to billing, and the billing agent starts from scratch. That's two agents, twice the handle time, and a frustrated customer who's been waiting.

Intent-based routing fixes this. When a system can classify "I was charged twice for my subscription" as a billing-duplicate-charge intent and route it directly to your billing team, you skip the misrouting step entirely.

Supp classifies messages into 315 intents in 100-200ms with 92% accuracy. That classification happens before any agent sees the ticket.

Better Macros Save 30-60 Seconds Per Ticket

If your agents type the same response 20 times a day, that's a macro waiting to happen. But the macro needs to be good enough that the agent can send it with minimal editing.

Bad macros actually increase AHT because agents spend time rewriting them to not sound terrible.

Build a macro library based on your top ticket types (see our guide on writing support macros). Review it quarterly. Track which macros get used and which get ignored.

Keyboard Shortcuts

Whatever help desk you use, learn the shortcuts. "Type /refund to insert the refund macro" is faster than "click Templates, scroll down, find Refund Policy, click Insert." Shaving five seconds off each ticket adds up to hours across a team.

Internal Knowledge Base

When an agent gets a question they don't know the answer to, they have two options: ask a colleague on Slack (slow, interruptive) or check the internal knowledge base (fast, self-serve).

If your KB is well-organized and up to date, agents find answers in seconds. If it's a mess of outdated articles, they ignore it and ask on Slack anyway.

A good internal KB reduces AHT by 15-25% for complex tickets. It has the biggest impact on newer agents who haven't built up institutional knowledge yet.

Automate the Simple Stuff

Some tickets don't need a human at all. Password resets, order status checks, subscription cancellations with no retention attempt. These are mechanical tasks.

If 30% of your tickets are simple, automatable requests, removing them from the queue doesn't just reduce AHT on those tickets (to zero). It reduces AHT on everything else because agents have more time and mental energy for complex issues.

At $0.30 per automated resolution, Supp handles these without any agent involvement.

Training That Actually Helps

Most support training is onboarding: here's the product, here's the tool, good luck. Ongoing training is rare.

What works:

Shadow Sessions

New agents watch experienced agents handle tickets in real-time. They see the shortcuts, the patterns, the decision-making process. Two hours of shadowing beats two days of reading documentation.

Ticket Reviews

Pick five tickets per week. Review them as a team. "This agent resolved this in two minutes; here's how." "This ticket took 45 minutes because the agent went down the wrong path initially; here's the faster route."

Product Deep Dives

When engineering ships a new feature, do a 15-minute walkthrough for the support team before customers start asking about it. Pre-emptive knowledge is faster than reactive research.

What Not to Do

Don't set AHT targets that agents feel pressured to hit. The moment you say "AHT must be under 8 minutes," agents start closing tickets early, giving shallow answers, and avoiding complex issues. Your satisfaction scores will tank.

Don't measure individual agent AHT in performance reviews. Measure team AHT as a trend. Individual variation is natural: some agents get harder tickets, some are thorough but slower, some are fast but generate more follow-ups.

Don't confuse fast with good. A five-minute resolution that solves the problem completely is better than a two-minute response that generates three follow-up messages.

Measuring Progress

Track these together, not separately:

• AHT (trending down is good)
• First-contact resolution rate (should stay flat or go up)
• Customer satisfaction (should stay flat or go up)
• Reopen rate (should stay flat or go down)
• Tickets per agent per day (should go up as efficiency improves)

If AHT drops but satisfaction drops too, you've made things worse. Roll back whatever you changed.