ticket deflection: what to automate first
Prioritizes what to automate first for ticket deflection. Covers the analysis, the ROI ranking, and the rollout sequence. Use when starting a deflection program. Not for chatbot design details.
TL;DR
Rank ticket types by volume times handle time, then automate the top three that are also deterministic (password resets, common VPN fixes, status checks). Self-service plus good KB articles deflect more than chatbots in year one. Measure deflection as tickets avoided, reported monthly.
The error
(Strategy task; no error.)Steps
- Pull last quarter's tickets: volume and average handle time per category. Expected: ranked list by total hours. The top of this list is your automation backlog.
- Filter for determinism: the fix must be the same every time. Expected: shortlist. Password resets and "how do I" questions qualify; weird bugs do not.
- For each shortlisted type, pick the cheapest deflection: KB article, self-service link, or automation. Expected: mapped. Do the cheap thing first.
- Implement the top three, then measure: compare ticket volume for those categories before and after. Expected: deflection visible in 1 to 2 months.
- Report monthly: tickets deflected, hours saved, what is next. Expected: reported. Deflection programs die without visible wins.
When to use
- Starting or rebooting deflection efforts
- Justifying automation investment
When not to use
- Low ticket volume (handle it live)
- Complex diagnostic work (not deflectable)
Compatibility
- Any ITSM with categorization and reporting
Variants
Proactive deflection
Status page and announcements deflect incident-driven tickets before they are filed.
Community deflection
User forums answer the long tail; seed them with KB content.
Why it happens
Deflection ROI concentrates in a few high-volume deterministic categories. Automating the long tail first is the classic mistake; the top three types are most of the value.
Edge cases
- Do not deflect what should be a conversation (security incidents, HR issues).
- Deflection that frustrates users creates more tickets, not fewer; measure satisfaction too.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_i1mgMqvBmNSfBkKSlscEzA
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.