Ticket deflection
Ticket deflection is the share of customer issues resolved without human agent involvement, through AI, self-service, or automation.
Ticket deflection is the share of incoming customer issues that get resolved without a human agent's involvement, through AI auto-resolution, self-service tools, or workflow automation. It's the most-watched metric in AI-for-support deployments and the most-marketed metric across vendors.
In context
Deflection is structurally measured the same way across vendors: tickets closed without human intervention divided by total incoming tickets. The simplicity is a feature for dashboards and a bug for buyers: a 60% deflection rate hides whether the deflected tickets were resolved correctly, whether the customer was satisfied, and whether the underlying issue recurred.
Published 2026 benchmarks: Zendesk's enterprise median is 41.2%; top quartile 58.7%. Intercom Fin averages around 41% with best cases at 65%. The Auralis customer cohort lands at ~60% steady-state in repetitive-question categories.
The POV essay "Deflection is the wrong goal, outcomes are" argues that deflection is an activity metric and the business cares about outcomes: AHT, FRT, CSAT, and recoverability. A contract that specifies only deflection is buying activity, not outcomes.
How Auralis uses Ticket deflection
Auralis contracts on deflection alongside AHT, FRT, CSAT, and recoverability, not deflection alone. ~60% steady-state in repetitive categories is the locked cohort number; the contract includes the outcome metrics that determine whether the deflection is a win or a hidden cost.