What Is Case Deflection? How AI Cuts Support Volume
Learn what case deflection is, how it differs from ticket deflection, how to calculate the case deflection rate, and how AI ticket deflection cuts support volume.
Case deflection is when a customer resolves their own issue through self-service, such as a knowledge base, community, or AI assistant, so they never need to open a support case. A higher case deflection rate means lower support costs, faster answers for customers, and more time for your agents to focus on complex work.
What is case deflection?
Case deflection is the practice of resolving customer questions before they become support tickets. Instead of emailing or calling an agent, the customer finds the answer themselves through self-service resources: a knowledge base article, a community thread, an automated workflow, or an AI assistant that answers in context. The case is deflected because it never enters your support queue.
Deflection does not mean ignoring customers. Done well, it gives them a faster path to resolution than waiting for an agent, while freeing your team to focus on the issues that genuinely need a human. It is one of the main reasons organizations invest in a self-service portal.
How case deflection works
When a customer arrives in your customer portal with a question, a good deflection flow understands what they are asking, surfaces the most relevant answer, and only escalates to a case if self-service cannot resolve it. It works in three tiers:
- Tier 1, Passive (knowledge base and FAQs): the customer searches and self-resolves.
- Tier 2, Interstitial (suggested articles): relevant articles surface during case creation, before the case is submitted.
- Tier 3, Conversational (AI assistant): the customer asks a question in plain language and gets a direct, sourced answer drawn from your published content.
Case deflection vs. ticket deflection
The two terms describe the same goal with different vocabulary. Ticket deflection is the common phrase in IT and helpdesk contexts, where requests are called tickets. Case deflection is the same idea in CRM and customer-service contexts (Salesforce, for example, calls support records cases). Both measure how many potential support requests are resolved through self-service before they reach an agent.
How AI improves case deflection
Traditional deflection relies on the customer searching and reading. AI raises the ceiling by answering directly. Instead of returning a list of links, an AI assistant interprets the question in plain language and responds with an answer.
The thing that separates a useful AI answer from a generic one is what the AI is grounded in. The Magentrix Wizard Assistant answers from your own published content: published Articles, published Wiki pages, and the Document Library files your administrator selects for indexing. It cites its sources, so the customer can see where an answer came from and open the underlying article. Because it is grounded in content you control rather than the open web, the answers reflect your product and your policies.
Security is inherited rather than bolted on. Every answer respects the roles, sharing rules and field-level security you have already configured, so a customer only ever sees answers drawn from content they are already permitted to open. Guest and unauthenticated access is blocked entirely.
Alongside the assistant, Magentrix offers AI ticket deflection on case management: when a customer begins creating a case, a relevant article is surfaced before they submit it. That is deflection at the exact moment of highest intent, and it is the single most direct way to move the rate.
How to improve your case deflection rate
- Keep your knowledge base current and written around real customer questions.
- Surface suggested answers at the point of case creation, not buried in a separate help center.
- Add an AI assistant that answers in context, grounded in your published content.
- Publish the articles you want the AI to use. Unpublished content is not indexed, so coverage is something you control.
- Review deflected and escalated topics monthly, and write new content for the gaps.
How case deflection is measured
The core metric is the case deflection rate: the share of potential support interactions resolved through self-service rather than by an agent. Use this standard formula:
Case deflection rate = (Total self-service sessions - Total cases created) / Total self-service sessions x 100
For example, if 10,000 customers use your Magentrix portal's knowledge base or AI assistant in a month and 2,000 of them go on to submit a support case, then 8,000 were deflected and your case deflection rate is 80%.
There is no single universal benchmark, so track your own rate over time and aim to move it up as your content and AI coverage improve.
One caution worth building into your reporting: deflection is not the same as resolution. A session that ends without a case is not automatically a success, because the customer may simply have given up. Track deflection alongside signals that show the answer actually landed, such as article helpfulness ratings, whether the same customer opens a case shortly afterwards, zero-result search queries, and customer satisfaction.
Bringing it together
Case deflection lowers support cost and speeds up answers by helping customers help themselves. The biggest gains now come from pairing a solid knowledge base with an AI assistant that answers in context from content you have published, and from surfacing the right article at the moment a customer is about to open a case. See how this works in the Magentrix customer portal and across our customer management solutions.
See case deflection in action
If you want to cut support volume with self-service and AI ticket deflection built into your customer portal, book a demo and we will show you how case deflection works with your own content.
What is case deflection?
Case deflection is when a customer resolves their own issue through self-service, such as a knowledge base, community, or AI assistant, so they never need to open a support case.
What is the difference between case deflection and ticket deflection?
They describe the same goal. Ticket deflection is the term used in IT and helpdesk contexts, while case deflection is the equivalent in CRM and customer-service contexts such as Salesforce. Both measure self-service resolution before an agent is involved.
How is case deflection measured?
Case deflection rate equals total self-service sessions minus total cases created, divided by total self-service sessions, times 100. For example, 10,000 self-service sessions with 2,000 cases created is an 80% deflection rate. Track the trend over time rather than a single universal benchmark.
Is case deflection the same as resolution?
No. A session that ends without a case is not automatically a success, because the customer may have given up. Track deflection alongside article helpfulness ratings, whether the customer opens a case shortly afterwards, zero-result searches, and customer satisfaction.
How does AI improve case deflection?
An AI assistant answers questions in plain language instead of returning a list of links. The Magentrix Wizard Assistant is grounded in your published Articles, published Wiki pages, and the Document Library files your administrator selects for indexing, and it cites its sources. Answers respect your existing roles, sharing rules and field-level security.
Does Magentrix support AI ticket deflection?
Yes. Magentrix offers AI ticket deflection on case management: when a customer begins creating a case, a relevant article is surfaced before they submit it. The Wizard Assistant also answers questions from your published content and cites its sources.
