Average Handle Time Outlier Review

Use it when an agent's AHT is materially above or below the campaign average and you need to determine whether the variance is justified or a performance issue. It is especially useful after a reporting cycle, a QA trend review, or when a supervisor notices repeated long or unusually short contacts. The template helps separate legitimate complexity from avoidable delays, process friction, or call-control issues.

Yes. High AHT often points to hold time, wrap time, navigation delays, or weak call control, while low AHT can indicate rushed handling, incomplete documentation, or missed discovery. The template includes an outlier direction field so you can document either pattern and tie it to customer impact and quality risk. That makes it useful for both coaching and audit trail purposes.

A team lead, QA analyst, operations supervisor, or contact center manager usually completes it. The reviewer should have access to call recordings, screen recordings, disposition notes, and campaign-level metrics so the analysis is evidence-based. In some centers, QA and the supervisor co-review the case to align on coaching and corrective action.

Most teams run them on a weekly or biweekly cadence, but the right frequency depends on call volume and how volatile the queue is. High-volume campaigns may need a rolling review so outliers are caught quickly, while lower-volume queues can be reviewed monthly. The key is to keep the review close enough to the interaction that coaching is still actionable.

Check whether the interaction involved unusual complexity, multiple systems, escalations, or a customer issue that required extended explanation. Then compare the sample against hold time, after-call work, transfer count, and documentation quality to see whether the extra time was productive or wasteful. If the agent maintained first contact resolution and complete notes, the variance may be justified even if it is outside the norm.

It turns a metric into a specific coaching plan by capturing the skill gap, process gap, recommended support action, target AHT, and follow-up date. That makes the review usable as a documented development record instead of a vague performance note. It also helps managers avoid generic feedback and focus on the exact behavior that changed the handle time.

A common mistake is treating every long call as poor performance without checking complexity or compliance requirements. Another is focusing only on talk time and ignoring hold time, wrap time, transfers, and documentation quality. Teams also sometimes skip the follow-up date, which makes it hard to confirm whether the coaching actually reduced the variance.

Yes. You can adapt the review context for voice, chat, email, or blended queues and add fields for campaign-specific tools, scripts, or disposition rules. Many teams also add quality checkpoints for regulated interactions, escalation handling, or language support. The template is most effective when the review criteria match the actual work the agent performs.

Ad hoc notes are faster, but they often miss the root cause, the customer impact, and the follow-up action needed to correct the pattern. This template creates a consistent record across agents and campaigns, which makes trend analysis and coaching easier. It also reduces the chance that a legitimate outlier is mistaken for a performance problem, or that a real issue is left unresolved.