›

Support Quality

Resolution Rate vs Deflection Rate in AI Support: What to Measure (2026)

Resolution Rate vs Deflection Rate in AI Support: What to Measure (2026)

Resolution rate vs deflection rate in AI support: why deflection hides bad CX, how to measure real resolution, and how pricing aligns incentives.

Lorikeet Logo

Lorikeet News Desk

·

Updated

Deflection rate tells you how many tickets the AI kept away from a human. Resolution rate tells you how many customer problems actually got solved. Those are not the same number, and in regulated support the gap between them is where churn, complaints, and compliance risk live.

Resolution rate and deflection rate are the two metrics most teams use to judge an AI support agent, and they measure opposite things. Deflection rate counts conversations that did not reach a human. Resolution rate counts conversations where the customer's underlying issue was solved. A deflected ticket can be an unsolved one - the customer gave up, got a non-answer, or churned in silence. This guide defines both metrics, explains why deflection can mask bad customer experience, shows how to measure resolution honestly, and covers the role of independent QA and pricing in keeping the number trustworthy.

  • Deflection rate measures avoidance (no human touched the ticket). Resolution rate measures the outcome (the customer's problem was solved). High deflection with low resolution is the classic failure mode of first-generation chatbots.

  • A deflected-but-unresolved ticket often costs more than a human-handled one: the customer retries on another channel, escalates angrier, or churns without telling you.

  • Resolution is only honest when something independent verifies it. Self-reported resolution (the AI grading its own work, or "did the conversation end?") is the most common way the number gets inflated.

  • Pricing models encode incentives. Per-deflection or per-conversation pricing rewards volume; per-resolution pricing that does not charge for escalations or for resolutions you rate bad rewards solved problems.

  • The defensible 2026 setup: define resolution in business terms, verify it with independent QA on 100% of tickets, and pay only for outcomes you would accept on appeal.

The short answer: measure resolution rate, verified by something other than the AI that did the work, and treat deflection rate as a capacity number only. Lorikeet, which publishes this guide, prices and reports on resolutions for that reason, but the measurement advice below applies whichever vendor you run.

Lorikeet publishes this guide. We checked competitor details on their own websites in November 2026; if something has changed, tell us and we will update the page.

Last updated: November 2026

Deflection rate is often the headline number because it is the easiest one to make large. Turn off the "talk to a human" button, add a few self-service nudges, and deflection climbs - whether or not anyone's problem got solved. For a marketing site that is a fine headline. For a support leader accountable to a CFO, a head of compliance, or a churn target, it is the wrong number to optimize. The metric that matters is whether the customer left with their issue resolved. This article explains what each metric actually counts, why the difference is large in regulated and complex support, and how to build a measurement and pricing setup where the number you report is the number that's true.

What is deflection rate?

Deflection rate is the percentage of inbound support contacts that are handled without a human agent. If 1,000 tickets arrive and 700 never reach a person, deflection rate is 70%. It is a containment metric: it measures what the AI (or self-service layer) kept away from the queue, not what it accomplished.

Deflection rate: the share of inbound contacts resolved or abandoned without human involvement. It counts the absence of a handoff, not the presence of a solution.

Deflection has an honest use. It is a capacity metric. If you are staffing a contact center, knowing that 70% of volume never touches a human tells you how many agents you need. The problem starts when deflection gets reported as a quality or value metric, because it counts two very different events as identical: the customer whose problem was solved by the AI, and the customer who gave up and closed the chat. Both are "deflected." Only one is a good outcome.

There are several ways deflection inflates without any real improvement in service:

  • Hiding the human handoff. Remove or bury the "talk to an agent" path and deflection rises mechanically. The tickets did not get easier; the exit got harder.

  • Counting abandonment as success. A customer who reads a non-answer and closes the window is counted as deflected. The system records a win; the customer records a reason to churn.

  • Channel shifting. The chatbot "deflects" the chat, the customer immediately calls the phone line or emails. One issue, counted as deflected once and as a new contact once. Deflection up, total cost up.

  • Deflecting only the easy tickets. Answering "what are your hours" a thousand times produces a high deflection rate and tells you nothing about whether the agent can handle a disputed transaction or a failed KYC check.

What is resolution rate?

Resolution rate is the percentage of contacts where the customer's underlying issue was actually solved, end to end, without needing further human follow-up. If 1,000 tickets arrive and 650 are genuinely solved by the AI, resolution rate is 65%. It is an outcome metric: it measures what got fixed, not what got contained.

Resolution rate: the share of contacts where the customer's problem was solved to a defined standard, verified independently, with no human follow-up required and no repeat contact on the same issue.

The reason resolution is the honest metric is simple: it is the thing the customer actually wanted. Nobody contacts support to be deflected. They contact support to regain access to a locked account, dispute a charge, change a beneficiary, or understand why a transfer failed. Resolution rate is the only one of the two metrics that maps to that intent.

It is also the harder number to fake, because solving a problem leaves evidence. A resolved dispute has a credit posted. A resolved KYC hold has a verified identity and an active account. A resolved transfer query has a customer who did not contact you again about the same transfer. Deflection, by contrast, leaves only the absence of a human - which is consistent with both success and abandonment.

The catch is that resolution is only honest if it is measured honestly. There are weak versions of resolution rate that are no better than deflection dressed up:

  • "The conversation ended" as a proxy for resolution. Conversations end for many reasons, including frustration.

  • The AI grading its own work. An agent that decides whether it resolved the ticket has an obvious incentive to say yes. This is the single most common way resolution rate gets inflated.

  • Survey-only resolution with a 5% response rate, where the 95% who did not respond are quietly assumed resolved.

  • "No reopen within 24 hours" windows that close before the customer has noticed the problem is still there.

A resolution rate is only as trustworthy as the verification behind it. That is the part of the metric most worth scrutinizing.

Resolution rate vs deflection rate: the core difference

The cleanest way to see the difference is a two-by-two. Every contact lands in one of four cells:

  • Deflected and resolved - the AI solved it, no human needed. The cell you want to grow.

  • Deflected and not resolved - no human touched it, and the problem is still live. The dangerous cell: it looks like a win on a deflection dashboard and is a loss for the customer.

  • Escalated and resolved - a human finished it. Counts against deflection, but the customer is served.

  • Escalated and not resolved - a human touched it and still failed. Rare, but the most expensive.

Deflection rate adds the first two cells together and reports the sum. Resolution rate adds the first and third. The two metrics only agree if the "deflected and not resolved" cell is empty - that is, if deflection never includes abandonment, non-answers, or silent channel-switching. In practice that cell is rarely empty, and in complex or regulated support it can be the largest source of disagreement between the two numbers.

A worked example. Two AI agents each handle 1,000 tickets:

  • Agent A deflects 800 (80% deflection). On audit, 450 were genuinely solved, 350 were customers who gave up or got a non-answer. Real resolution rate: 45%.

  • Agent B deflects 650 (65% deflection). On audit, 600 were genuinely solved, 50 escalated cleanly to a human. Real resolution rate: 60%.

On a deflection scoreboard, Agent A wins by 15 points and looks like the better buy. On the metric that matters - problems solved - Agent B is well ahead, and Agent A is generating 350 hidden failures that will resurface as repeat contacts, complaints, or churn. A team that optimizes deflection picks the worse agent.

Why deflection can mask bad customer experience

Deflection's core flaw is that it is silent about the customer. It measures a queue, not a person. The events that destroy customer experience - giving up, getting a wrong answer, being trapped in a loop, repeating yourself across channels - all register as deflection successes. The metric and the experience point in opposite directions.

This matters more as the stakes of the ticket rise. For "where is the gym open until," a deflected non-answer is a minor annoyance. For "my account is frozen and I cannot access my money," a deflected non-answer is a customer who is now frightened, angry, and one tweet away from a regulator complaint. In fintech, healthcare, insurance, and telehealth - industries where the contacts are consequential - the cost of a false deflection is highest, which is exactly where leading on deflection rate does the most damage.

Three specific failure patterns deserve naming, because each one improves a deflection dashboard while harming customers:

The containment trap

When deflection is the target, the rational move is to make leaving harder. Hide the human handoff, add friction to escalation, loop the customer through self-service. Containment goes up. So does the number of people who needed help and could not get it. Deflection rewards the behavior that, past a point, defines bad support.

The silent-churn problem

A deflected-but-unresolved customer usually does not file a complaint. They just leave, or they stop trusting the channel and route around it. Because the failure is silent, it never shows up in the deflection number, the CSAT survey (they did not respond), or the escalation count. The damage is real and the dashboard is green. This is the most expensive blind spot deflection creates.

Channel arbitrage

Deflect the chat, the customer calls. The chat counts as deflected; the call counts as new volume; the issue is now handled twice and resolved once, at higher total cost. A deflection metric scoped to a single channel will report progress while overall cost per solved problem gets worse.

None of this means deflection is useless. As a capacity-planning input it is fine. The error is treating a containment metric as a quality or value metric, and buying or optimizing against it.

How to measure resolution rate honestly

Resolution is the better metric, but only if you define and verify it carefully. A resolution rate with a weak definition behind it is just deflection with a nicer label. Four things make the number trustworthy.

1. Define resolution in business terms, before launch

Resolution is not a universal constant; it depends on the workflow. A resolved dispute means a credit posted or a clear denial with the reason stated. A resolved KYC hold means a verified identity and a usable account. A resolved billing question means the customer understood the charge and did not contact you again about it. Write these definitions per workflow, in plain language, and agree them with the team that owns the outcome (often compliance or operations, not just support). If you cannot state what "resolved" means for a ticket type, you cannot honestly measure it.

2. Verify independently, not with self-grading

The agent that did the work should not be the sole judge of whether the work was done. Independent verification - a separate QA layer that did not generate the answer - is what separates a real resolution rate from a self-congratulatory one. This is where automated QA matters: a second system that reviews the ticket against the resolution definition and flags the ones that do not meet it.

Lorikeet runs this as a dedicated agent. Lorikeet pairs its customer-facing Concierge with Coach, an analytics and quality-assurance agent that performs automated QA on tickets, scores ticket quality, and runs root-cause analysis - effectively the AI evaluating the AI. Coach is also offered as a standalone product for companies using any support solution, with automated QA at $0.30 (Start) or $0.27 (Scale) per ticket, including over the top of a human team or another vendor's agent, which means the verification layer does not have to come from the same system that produced the answer.

3. Sample enough to be representative - ideally all of it

Traditional manual QA reviews 2 to 5% of tickets, which is too thin to catch rare-but-serious failures, the exact failures that matter most in regulated support. Reviewing 100% of tickets removes sampling error and catches the long tail. Automated QA makes full coverage affordable in a way that manual review never was.

4. Watch repeat contacts and downstream signals

The strongest evidence a ticket was resolved is that the customer did not come back about it. Track repeat-contact rate on the same issue, reopen rate over a window long enough to be meaningful, and where possible the downstream business signal (did the disputed charge get re-disputed, did the restored account stay active). These are harder to game than a survey because they reflect what the customer did, not what they said.

A practical note on validation before launch: the most defensible programs test the agent against historical tickets and adversarial scenarios before it goes live, so the resolution rate you report in production is one you already stress-tested. Lorikeet uses simulation and red-teaming pre-launch for exactly this, then layers inbound message checks, outbound guardrails, and 100% post-facto QA. The point is not the specific stack; it is that resolution should be proven, not assumed.

How pricing models shape the metric you get

Metrics follow money. How a vendor charges you determines which behavior the vendor is incentivized to produce, and that shows up in the resolution-versus-deflection gap.

Per-seat and per-conversation pricing

Per-seat pricing (the legacy helpdesk model) is neutral on resolution - you pay for capacity regardless of outcome. Per-conversation pricing rewards volume: the vendor is paid whether or not the conversation solved anything, which quietly aligns the vendor with deflection rather than resolution. Neither model gives the vendor a reason to care whether your customer's problem was actually fixed.

Per-deflection and "outcome" pricing

Pure deflection pricing is the most misaligned: the vendor is paid for keeping tickets away from humans, which is the exact behavior that produces the containment trap. Outcome-based pricing is better in theory - you pay only when the AI fully resolves a case - but the definition of "resolved" is doing all the work. If the vendor defines resolution and grades its own outcomes, "outcome pricing" can collapse back into deflection pricing with extra steps.

Per-resolution pricing where a bad resolution is free

The model that aligns incentives most cleanly is per-resolution pricing where unresolved tickets and escalations are not charged, and a resolution the customer rates bad is not charged either. Ask any vendor how it defines a resolution before you compare rates. That single design choice removes the incentive to inflate: the vendor is not paid for escalations or for resolutions the buyer rates bad, so padding the number with abandonments or non-answers does not pay.

Lorikeet prices this way. Lorikeet publishes its pricing: the Start plan is $2,100 a month and Scale is $5,100 a month (both billed annually), with resolved chat, email and SMS conversations at $0.99 (Start) or $0.90 (Scale) and voice at $1.50 or $1.20. Unresolved tickets and handoffs to a person are not charged. Signature is custom, with a $75K platform fee. Full details are on the pricing page. Automated QA through Coach is $0.30 (Start) or $0.27 (Scale) per ticket, and escalations are not charged: if the agent hands off to a human, you do not pay for that contact. Under Lorikeet's Quality Guarantee, a resolution you rate as bad is not charged, so the billed number tracks the number you accept. The plan fee means it costs more than pure pay-per-outcome tools at very low volume; the trade is that you can compare cost per solved problem rather than cost per contained contact.

The general principle holds regardless of vendor: ask who defines resolution, who verifies it, and what the vendor is paid for. If the answers are "the vendor," "the vendor," and "deflection," the reported number will drift away from your customers' reality.

Where deflection-oriented tools still fit

Deflection-first tools are not a scam; they are built for a different job. FAQ chatbots and self-service deflection layers do real work on high-volume, low-stakes, informational queries. For "what are your hours," "how do I reset my password," or "where is my order," a fast self-service answer that keeps the ticket out of the queue is a genuinely good outcome, and deflection rate is a reasonable proxy for it.

The larger platforms are not deflection-only tools. Fin (formerly Intercom, now part of Salesforce) prices per outcome and takes actions through Procedures; Zendesk AI agents bill per automated resolution and take actions across connected systems; Ada says its agent has the tools to complete customer tasks through APIs and integrations. With any of them, the questions above still apply: who defines resolution, and who verifies it.

The fit breaks down as ticket complexity and stakes rise. When a contact involves an action (move money, file a dispute, change a beneficiary), a multi-step workflow, or a regulated decision, "did it avoid a human" stops being a useful proxy for "did it go well." That is the band where resolution rate, independent verification, and per-resolution pricing earn their keep, and where Lorikeet is built to operate - complex and regulated support across chat, email, voice, SMS, and WhatsApp, with the audit trail to back the resolution claim.

An honest limitation: this approach is heavier than dropping a deflection widget on a marketing site. Defining resolution per workflow, wiring independent QA, and running pre-launch simulation is more setup than flipping on an FAQ bot, and it is overkill if your support volume is mostly simple informational queries. The trade is that you get a number you can defend to a CFO or a regulator, not just a number that looks good on a slide.

A practical checklist for support leaders

If you are evaluating an AI support agent or auditing one you already run, these questions surface the resolution-versus-deflection gap quickly:

  • What exactly does your "resolution rate" count, and who decided a ticket was resolved - the agent itself, or something independent?

  • What share of "deflected" tickets resulted in a repeat contact on the same issue within two weeks?

  • What percentage of tickets get QA review, and is it sampled or 100%?

  • Show me the resolution rate on the hardest ticket types, not the blended average.

  • If I define resolution differently than you do, does the number change - and who has the final say?

  • What am I billed for: seats, conversations, deflections, or resolutions I agreed to?

  • What happens to a customer who says "I want a human" immediately - is that a failed deflection or a clean escalation?

The pattern across all seven: push past the headline number to the definition and the verification behind it. A vendor confident in its resolution rate will welcome the questions. A vendor selling deflection will steer you back to the headline.

Is Lorikeet the right fit?

Lorikeet is built for complex, regulated support: fintech, healthtech, insurance and telehealth teams where the AI has to take actions in backend systems safely and leave an audit trail. It is not the right choice for everyone:

  • If most of your volume is simple informational questions and deflection is a fair proxy for success, a lighter FAQ tool will be cheaper and faster to switch on.

  • If you want a self-serve, published-price agent you can switch on inside your helpdesk within days, Fin or Zendesk's own AI agents fit that.

  • If you handle a few hundred tickets a month, the Start plan (from $2,100 a month) will be more than you need.

  • Expect more setup than an FAQ bot: resolution definitions, workflows, guardrails and simulations are configured per use case.

If you want a resolution number you can defend - one a separate QA layer scores on every ticket - see how Lorikeet measures and prices on real resolution.

Key takeaways

  • Deflection rate measures avoidance (no human touched the ticket); resolution rate measures the outcome (the problem got solved). They diverge wherever deflection includes abandonment, non-answers, or channel-switching.

  • Deflection can mask bad CX because giving up, getting a wrong answer, and silent churn all count as deflection wins. The cost is highest in regulated and complex support, exactly where deflection is most often used as the headline.

  • Resolution rate is only honest with a clear per-workflow definition and independent verification - ideally automated QA on 100% of tickets, not the AI grading itself or a 2 to 5% sample.

  • Pricing encodes incentives: per-conversation and per-deflection reward volume; per-resolution pricing that does not charge for escalations or for resolutions you rate bad rewards solved problems.

  • Deflection-first tools fit high-volume, low-stakes queries; resolution-first measurement and pricing fit complex, regulated, action-taking support.

Frequently asked questions

What is the difference between resolution rate and deflection rate?

Deflection rate is the percentage of contacts handled without a human; resolution rate is the percentage where the customer's problem was actually solved. The difference is the set of tickets that were kept away from a human but never resolved - customers who gave up, got a non-answer, or switched channels. On a deflection dashboard those count as wins. On the metric that matters, they are losses. The two numbers only agree when deflection never includes abandonment, which is rare in complex support.

Is a high deflection rate a good thing?

Only if those deflected tickets were genuinely resolved. Deflection is a useful capacity-planning input - it tells you how much volume never reaches an agent - but it is a poor quality or value metric because it counts abandonment and non-answers as successes. A team can lift deflection by hiding the "talk to a human" button without solving a single additional problem. Pair any deflection number with an independently verified resolution rate before reading it as good news.

How do you measure resolution rate accurately?

Four things make it honest: define resolution in business terms per workflow before launch; verify it independently rather than letting the agent grade its own work; review as close to 100% of tickets as possible instead of a 2 to 5% sample; and watch repeat-contact and reopen rates as downstream evidence. Automated QA makes full-coverage, independent verification affordable. A resolution rate without independent verification behind it is just deflection with a better label.

Why does deflection rate hide bad customer experience?

Because deflection measures a queue, not a person. The events that ruin customer experience - giving up, getting a wrong answer, looping through self-service, repeating yourself on another channel - all register as deflection successes. The worst case is silent churn: a deflected-but-unresolved customer rarely complains, so the failure never appears in the deflection number, the survey, or the escalation count. The dashboard stays green while customers leave.

What is independent QA verification and why does it matter?

Independent QA verification is a separate system reviewing whether a ticket was truly resolved, rather than the agent that produced the answer judging its own work. It matters because self-grading has an obvious incentive to report success, which is the most common way resolution rate gets inflated. Lorikeet's Coach agent runs automated QA, ticket-quality scoring and root-cause analysis on tickets - the AI evaluating the AI - and is also offered as a standalone product, with automated QA at $0.30 (Start) or $0.27 (Scale) per ticket, including over a human team or another vendor's agent.

How does per-resolution pricing align incentives better than per-deflection pricing?

Per-deflection pricing pays the vendor for keeping tickets away from humans, which rewards containment whether or not anything was solved. Per-resolution pricing where escalations are not charged and a resolution the customer rates bad is not charged does not pay the vendor for handoffs or for resolutions the buyer rejects, so inflating the number with abandonments does not pay. Lorikeet charges per resolution on top of a plan fee: Start $2,100/mo or Scale $5,100/mo (annual), plus $0.99 or $0.90 per resolution; Signature custom. It does not charge for escalations, and under its Quality Guarantee a resolution you rate as bad is not charged, so the billed number tracks the real one.

When should I still use a deflection-oriented tool?

For high-volume, low-stakes, informational queries - store hours, password resets, order status - a self-service deflection layer is genuinely useful, and deflection rate is a reasonable proxy for success there. FAQ bots and self-service layers do real work in that band, and broader platforms such as Fin and Zendesk AI agents also take actions and price per outcome or automated resolution, so ask how each defines and verifies resolution. The fit breaks down when contacts involve actions, multi-step workflows, or regulated decisions, where "did it avoid a human" stops predicting "did it go well" and resolution-first measurement takes over.

What resolution rate should an AI support agent achieve?

There is no single right number, because it depends on workflow mix and how strictly resolution is defined. A blended rate across easy and hard tickets is less informative than the rate on your hardest ticket types, which is where regulated risk concentrates. Be wary of vendors quoting 90%+ without saying who verified it or what counts as resolved - a high self-graded number on easy tickets tells you nothing about performance on the contacts that matter.

Complex is our comfort zone
Lorikeet offers a 30-day free trial.

Lorikeet

The AI concierge
for complex, regulated customer support

Ask AI about Lorikeet

ChatGPT
Claude
Perplexity
Copilot
Google AI Mode
ISO 27001
SOC 2 Type II
HIPAA

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

LinkedIn

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.