Average Handle Time is a duration. On its own it tells you how long something took, not whether it was worth doing. Treated as a headline, it quietly rewards short calls and punishes the conversations that resolve things.
A definition, not a verdict#
The knowledge base is explicit: the AHT definition must be stated. A conversation duration is only comparable when the start and end events, the included activities and the population are the same. Change any of those and the number moves without anything real having changed.
| AWT | Time from inbound call initiation to answer | Queue and routing scope |
|---|---|---|
| AHT / ACD | Duration of a completed interaction | Explicit start/end definition |
| ASR | Answered calls divided by attempts | The denominator |
| FCR | Defined issue resolved on first call | Issue scope and verification rule |
From the Vee Website Content Knowledge Base KPI dictionary.
Where AHT sits in the funnel#
A useful sequence runs from reach to interaction to conversion to downstream outcome. AHT sits in the interaction stage. Reading it without the stages on either side is how a process ends up optimising the middle of the funnel and losing the end of it.
Governance and limitations#
Where an AHT figure is published, it should carry its process and population. As an example of how specific that gets: Vee’s knowledge base records 116.5 seconds AHT for banking debt-collection cases that obtained a repayment commitment — a scoped reference, not a benchmark for call handling in general.
Follow The First Second
Occasional issues on the mechanics and economics of AI-powered customer contact. No noise, no vendor news.
Follow via RSS