Average Handling Time · Average handling time
What is Average Handling Time and why shouldn't you steer on it?
Average Handling Time is the average time an agent spends on a customer question. It's a fine planning number and a poor performance target.
In short
Average Handling Time, abbreviated AHT, is the average time an agent spends on a customer question, including the conversation itself and the work afterwards such as recording notes or creating a return. So AHT measures your team's occupancy, not your customer's waiting time.
Calculation
Required capacity = number of questions x AHT / productive time per agent
This is what AHT is for. Calculate with productive time, not contract hours: meetings, breaks and training come off. Six productive hours in an eight-hour day is a more realistic starting point for most teams than eight.
Why AHT as a target produces the wrong behaviour
Steer a team on a lower handling time and that time falls. Agents keep conversations shorter, skip the follow-up questions and pass things on sooner. The question comes back afterwards, often to a colleague, and total work rises while the number sits green.
So use AHT to plan capacity and to see which type of question takes disproportionately long. That second use is the useful one: a category that structurally takes three times as long points to a missing integration or an unclear policy.
Where the time actually goes
Part of the handling time isn't contact with the customer but lookup work: finding the order number in the webshop, checking the delivery status with the carrier, verifying the return policy. That's the time you can remove without making the conversation shorter or colder.
So measure, even if by hand for a week, how much of your handling time goes into searching. That number makes the conversation about integrations concrete.
AHT or total lead time?
| AHT | Lead time | |
|---|---|---|
| Measures | The time you spend working on it | The time the customer waits |
| Waiting counts | No | Yes |
| Use for | Planning staffing | Making promises to customers |
AHT belongs in your capacity calculation, not in an agent's assessment. Anyone judged on AHT closes conversations before the customer is done, and that returns a week later as repeat contact.
Where it goes wrong
Adding channels together
A phone call and an email have completely different handling times, and a chat where an agent runs three conversations at once different again. An average across all channels is a number you can't plan with.
Forgetting the after-work
If you only measure talk time and not the recording, the return registration and the internal note afterwards, your capacity calculation comes out structurally too low. You only notice when the roster turns out not to hold.
What to do this week
Split your handling time by channel and by topic instead of looking at an average. Find the category that stands out and ask the agents where the time goes. In practice that answer is often a system they have to open alongside.
What this looks like in a system
In Cuego the customer context sits with the conversation: order, delivery status, return history and earlier contacts, without a second screen. For recurring questions a draft is ready, built from your knowledge base and your customer data. The after-work largely disappears because a return or a task is created from within the conversation itself.
Automation & workflowsRelated terms
Canned response
A canned response saves typing on questions that keep returning. It becomes harmful the moment it answers a question that was slightly different.
Read onWorkflow
A workflow is a sequence of steps that runs by itself once something happens. The skill is choosing which steps deserve it.
Read onCustomer service
Customer service is answering questions your own setup caused. That sounds harsh and it's the most usable definition there is.
Read on