Ticket deflection, explained
Ticket deflection is the share of support contacts resolved without human interaction, through self-service, an AI agent or automation, without the customer coming back with the same problem.
A common way to measure it is to divide contacts the AI resolved with no repeat contact within a set number of days by total contacts. The time frame and the definition of resolved must stay the same in every report.
Deflection is not the same as containment. Containment counts everyone who never reached a person, whether or not the problem was solved.
The best candidates are frequent, simple cases such as order status, duplicate invoices and documented questions. Cases that need judgment should go to a person with the context already gathered.
Conversations aren't support.They're infrastructure.
Step into the new era of the relationship between companies and customers.