Most AI support vendors bill you for a deflection; your CFO writes checks for a resolution. The distance between those two numbers is the ROI nobody prints on the quote.
Reducing customer support costs with AI means moving tickets off human queues, where each contact costs roughly $1.25 to $4 to handle, and onto an autonomous agent that closes them for a fraction of that. In 2026 the strongest platforms resolve 60-80% of inbound volume without a human and price per outcome instead of per seat. The number that actually decides your savings is not the sticker rate. It is how each vendor defines a "resolution" and whether you are charged when the customer still had to reach a person.
Human-handled tickets cost about $1.25 to $4 each once you load salary, tooling, and QA time; a per-resolution AI agent can close comparable tickets for roughly $0.80 to $2.
Three pricing models now compete: per-resolution (pay on outcome), per-conversation (pay on every chat), and per-seat (pay per human license). For the same volume they can differ 3-5x in true annual cost.
Fin by Intercom publishes roughly $0.99 per resolution, the clearest public per-resolution benchmark in the category. Most other vendors quote custom rates and describe a pricing model rather than a number.
Deflection and containment are not resolutions. A contained ticket can still leave the customer unhelped, and containment-priced tools bill you regardless of whether the person got an answer.
The highest-leverage line in any contract is who defines a resolution and whether escalations are billed. Customer-defined resolution with escalations not charged is the tightest cost alignment available in 2026.
Last updated: July 2026
The cost-reduction pitch for AI support has gotten loud, and most of it is measured in the wrong unit. Vendors quote deflection rate, containment rate, or a per-conversation price because those numbers look good on a slide. None of them is what your finance team pays. Your finance team pays for a resolved customer issue, and the gap between a "handled" ticket and a genuinely resolved one is where hidden cost lives. A tool that deflects 70% of chats but leaves a third of those customers re-contacting through a second channel has not cut your cost by 70%. This guide ranks nine platforms by the only lens that maps to a P&L: the pricing model and the true cost of a resolved ticket, including who gets to decide what "resolved" means.
What Cost Per Resolution Really Means (And the Math Your CFO Cares About)
Cost per resolution is the fully loaded price to close one customer issue end to end, from first contact to the point where the customer no longer needs help. For a human team that number lands around $1.25 to $4 per ticket in most support organizations once you include wages, benefits, tooling, training, and quality assurance. For an AI agent, cost per resolution is whatever the vendor charges each time its definition of "resolved" is met, which is where the models diverge sharply.
Per-resolution pricing: You pay only when the AI resolves a ticket. This aligns spend with outcomes, but the alignment is only as honest as the definition of "resolved." If the vendor counts a canned deflection message as a resolution, you are paying deflection prices dressed as outcomes.
Per-conversation pricing: You pay for every conversation the AI touches, resolved or not. It is predictable, but it charges you for the failures as well as the wins. A customer who asks one question, gets a wrong answer, and escalates to a human still counts as a billable conversation.
Per-seat pricing: You pay per human license, usually with an AI add-on layered on top. This is the legacy helpdesk model. It decouples price from volume, which sounds safe until you realize you are paying for capacity you automated away, plus an AI surcharge, plus per-resolution fees on top at some vendors.
Deflection and containment: A deflected or contained ticket is one the customer did not escalate to a human. It is not the same as a resolved ticket. Containment-priced and deflection-priced tools bill you when the customer gives up, closes the tab, or gets routed to a dead end, which is why containment metrics flatter the vendor and inflate your real cost per genuine resolution.
The math that matters is simple. Take your human baseline (say $2.50 per ticket), multiply by the tickets an AI can safely resolve, and compare against the AI's true cost per resolved ticket including seat fees, add-ons, and the tickets it fails and hands back. A platform charging $0.99 per resolution that also requires a seat fee and resolves only the easy 40% of your volume can cost more per genuinely resolved ticket than a $0.80 platform that safely resolves 80% and never charges for escalations. The sticker price is the smallest part of the equation.
Lorikeet is an AI customer support platform built for complex, regulated companies such as fintechs, healthtechs, and insurers. It prices on genuine resolutions (roughly $0.80 per chat, email, or SMS resolution and about $1.00 per voice resolution), never charges for escalations to a human, and lets the customer define and hold veto over what counts as a resolution. That combination is why it leads this ranking, and the rest of this guide explains the model behind every other vendor so you can compare like for like.
At-a-Glance Comparison
At a glance
Platform: Lorikeet · Pricing model: Per resolution, ~$0.80 chat/email/SMS and ~$1.00 voice; escalations not charged · Resolution stance: Customer defines and vetoes what counts · Best for: Mid-to-high-volume regulated teams that want cost aligned to genuine outcomes
Platform: Fin by Intercom · Pricing model: Per resolution, ~$0.99, usually plus a helpdesk seat fee · Resolution stance: Intercom defines what counts as a resolution · Best for: High-volume consumer teams already in the Intercom ecosystem
Platform: Zendesk AI · Pricing model: Per-seat Suite plus AI add-on plus per automated resolution (layered) · Resolution stance: Vendor-defined automated resolution · Best for: Teams already standardized on Zendesk Suite
Platform: Ada · Pricing model: Per automated resolution, typically an annual platform contract · Resolution stance: Vendor-defined automated resolution rate · Best for: Mid-market and enterprise teams with high chat volume
Platform: Decagon · Pricing model: Enterprise outcome-based, per-conversation or per-resolution, custom and opaque · Resolution stance: Negotiated per contract · Best for: Large enterprises with dedicated procurement and engineering
Platform: Forethought · Pricing model: Per resolution or annual contract; now part of Zendesk · Resolution stance: Vendor-defined; roadmap folding into Zendesk · Best for: Teams wanting resolution plus triage and QA in one stack
Platform: Gorgias · Pricing model: Helpdesk tier plus automation add-on billed by resolved interactions per month · Resolution stance: Vendor-defined automated interaction · Best for: Ecommerce and Shopify merchants
Platform: Kore.ai · Pricing model: Enterprise consumption, per-session or per-interaction licensing · Resolution stance: Session-based, not outcome-based · Best for: Large enterprises building custom conversational AI in-house
Platform: Salesforce Agentforce · Pricing model: Per conversation, layered on Salesforce licensing · Resolution stance: Billed per conversation regardless of outcome · Best for: Salesforce-committed enterprises consolidating on one vendor
The 9 Best AI Customer Support Platforms by Cost Per Resolution in 2026
1. Lorikeet
Lorikeet builds AI concierges that resolve issues end to end for complex and regulated industries, and its pricing is the sharpest cost-alignment story in the category. You pay roughly $0.80 per chat, email, or SMS resolution and about $1.00 per voice resolution. Escalations to a human are not charged, and you define and hold veto over what counts as a resolution. That last point is the difference between paying for outcomes and paying for a vendor's marketing metric. Most platforms decide internally when they have earned your money; with Lorikeet, if you do not agree a ticket was resolved, it is not billed.
Key Features
Per-resolution pricing with escalations not charged and a customer-held veto on what counts as resolved, plus a published Scale plan of 48,000 resolutions for $48,000 a year so the unit economics are legible before you sign.
End-to-end resolution rather than deflection: natural-language workflows combined with deterministic Structured Workflows handle multi-step tasks like refunds, disputes, and account changes in a single interaction.
Defence in depth for regulated environments: pre-launch adversarial simulation and red-teaming, inbound message checks, outbound guardrails, and 100% post-facto QA, which is what lets it safely automate a higher share of volume than deflection tools.
Omnichannel coverage across chat, email, voice with sub-one-second latency and multilingual auto-switching, SMS, and WhatsApp (live and rolling out), plus compliant outbound re-engagement with DNC, call-hour, and consent rules.
Coach, a standalone 100% automated QA agent at roughly $0.10 per ticket, for root-cause analysis, ticket quality scoring, and resolution verification, replacing the 1-3% manual sampling most teams rely on.
Ideal For
Mid-to-high-volume teams in regulated or high-stakes industries (fintech, financial services, healthcare, insurance, betting and gaming) that want AI spend tied to genuine resolutions and need audit trails and compliance depth. As an illustrative, anonymized example, a regulated US fintech reached around 85% autonomous automation with equal-or-better CSAT after deployment; this is not a guaranteed benchmark. One honest limitation: per-resolution economics reward mid and high volume. A very low-volume team handling a handful of tickets a day may find a flat or per-seat tool cheaper in absolute terms, and Lorikeet is candid about that.
Pricing
Per resolution: roughly $0.80 per chat, email, or SMS resolution and about $1.00 per voice resolution. Coach QA runs about $0.10 per ticket. Escalations are not charged, and the customer defines what counts as a resolution. A published Scale plan covers 48,000 resolutions for $48,000 a year. Against a human baseline of $1.25 to $4 per ticket, savings compound as safe automation rises.
2. Fin by Intercom
Fin is Intercom's AI agent and the clearest public benchmark in the category, with a widely cited rate of roughly $0.99 per resolution. It is a strong per-resolution product for high-volume consumer support, and Intercom has done more than any vendor to educate the market on outcome pricing. Two things to weigh: Intercom, not you, defines what counts as a resolution, and the $0.99 usually sits on top of a helpdesk seat fee if you are not already an Intercom customer.
Key Features
Roughly $0.99 per resolution, among the lowest published per-resolution rates in the market.
Tight native integration with the Intercom Messenger and helpdesk, with fast time to first value.
Works alongside Salesforce and HubSpot helpdesks, not only Intercom.
Strong analytics on resolution rate, plus published education on pricing models.
Ideal For
High-volume consumer businesses already using Intercom, or comfortable adopting it, that want the lowest published per-resolution sticker and a quick path from trial to deployment on relatively standard support workflows.
Pricing
Roughly $0.99 per resolution, with Intercom defining what qualifies. A helpdesk seat fee typically applies if you are not already an Intercom customer, so model the blended cost, not the per-resolution number alone.
3. Zendesk AI
Zendesk layers AI agent capabilities onto its core Suite, and for teams already on Zendesk it is the path of least resistance. The pricing model is where the cost hides. You pay per seat for the Suite, then an AI add-on per agent, then a per automated resolution fee on top. Each layer is defensible on its own; stacked together they make the true cost per resolved ticket harder to see than a single per-resolution number.
Key Features
Native to Zendesk Suite, so no middleware for existing Zendesk customers.
AI Agent for autonomous resolution plus agent-assist for human reps.
A per automated resolution billing layer on top of seats and the AI add-on.
Hundreds of prebuilt integrations; the Forethought acquisition (2026) adds triage and QA agents.
Ideal For
Teams already standardized on Zendesk Suite that want incremental AI without switching helpdesks and can absorb a layered cost structure of seats plus AI add-on plus per-resolution fees.
Pricing
A layered model: per-agent Suite licensing, a per-agent Advanced AI add-on, and a per automated resolution fee. The resolution is vendor-defined. Because the cost arrives in three layers, calculate a blended cost per genuinely resolved ticket rather than trusting the per-resolution line.
4. Ada
Ada is one of the most established automation vendors, having expanded from chatbot roots into voice and email, and it sells hard on autonomous resolution rate. The pricing model is per automated resolution, usually inside an annual platform contract. The evaluation question is the one that applies to every vendor-defined-resolution tool: what exactly counts as an automated resolution, and does it include cases where the customer was deflected rather than helped.
Key Features
Per automated resolution pricing inside an annual platform contract.
Multi-channel across chat, voice, and email.
Mature integrations with Salesforce, Zendesk, and major helpdesks.
Knowledge-base ingestion, with established enterprise deployment playbooks.
Ideal For
Mid-market and enterprise teams with high inbound chat volume that prefer a long-tenured vendor and want a per automated resolution model wrapped in a predictable annual contract.
Pricing
Per automated resolution, generally committed as an annual platform contract, with rates quoted by sales. The resolution is vendor-defined, so confirm in writing whether deflections count.
5. Decagon
Decagon is a high-end enterprise AI agent platform that offers per-conversation or per-resolution pricing, selected per contract, with white-glove implementation. Pricing is custom and unpublished, which is common at the top of the market but makes apples-to-apples comparison difficult. For large enterprises with the procurement muscle to negotiate and engineering to support a months-long deployment, it is a credible premium option.
Key Features
Customer-selectable per-conversation or per-resolution pricing.
Voice, chat, and email in one platform.
White-glove deployment with embedded engineering during launch.
Production deployments processing large interaction volumes, with enterprise-grade reporting.
Ideal For
Large enterprises with multi-million-dollar support budgets and dedicated procurement and engineering resources that want a top-of-market vendor and can negotiate the pricing model that fits their volume.
Pricing
Custom and unpublished, structured as per-conversation or per-resolution depending on the contract. Because rates are negotiated, insist on a written definition of a billable resolution before comparing against published-price vendors.
6. Forethought
Forethought offers a multi-agent platform covering resolution, triage, agent assist, discovery, and QA, and was acquired by Zendesk in 2026. If you sign now, you are signing into Zendesk's roadmap rather than an independent Forethought one. The pricing model is per resolution or an annual contract, with the same vendor-defined-resolution caveat as the rest of the deflection-leaning cohort.
Key Features
Multi-agent stack spanning resolution, triage, assist, discovery, and QA.
Natural-language business logic instead of rigid decision trees.
Multi-channel across chat, email, voice, and messaging, with broad integrations.
Ideal For
Mid-market and enterprise teams that want resolution plus triage and QA in a single stack and are comfortable being absorbed into Zendesk's roadmap after the acquisition.
Pricing
Per resolution or annual contract, with rates quoted by sales and now aligning to Zendesk's commercial model. The resolution is vendor-defined. Ask how billing and product direction change under Zendesk before committing.
7. Gorgias
Gorgias is the helpdesk and automation platform built for ecommerce, and a strong fit for Shopify merchants. Its model combines a helpdesk tier with an automation add-on billed by resolved interactions per month. For a store with predictable, product-centric questions the cost model works well, but the automated interaction is vendor-defined, and the tool is optimized for retail rather than the regulated, multi-step workflows where cost-per-resolution stakes are highest.
Key Features
Deep Shopify and ecommerce platform integration.
Helpdesk plus automation add-on billed by resolved interactions per month.
Order-aware automation (returns, order status, address changes).
Macros and rules tuned for retail, with revenue-attribution reporting.
Ideal For
Ecommerce and Shopify merchants with high volumes of order-centric questions that want support automation tightly coupled to their storefront and order data.
Pricing
A helpdesk tier plus an automation add-on priced by resolved automated interactions per month, with the interaction vendor-defined. Model the base tier and add-on together to see your true cost per resolved ticket.
8. Kore.ai
Kore.ai is an enterprise conversational AI platform used to build custom virtual assistants across support, HR, and IT. Its licensing is consumption-based, typically per session or per interaction rather than per resolved outcome. That distinction matters: session-based billing charges you for engagement, not results, so a customer who opens a session and still needs a human is a billable event. It is powerful and flexible, but it is a build-it-yourself platform, not an outcome-priced agent.
Key Features
Enterprise platform for building custom virtual assistants across many functions.
Consumption-based licensing, generally per session or per interaction.
Extensive dialog-design tooling, with on-premise and private-cloud deployment options.
Ideal For
Large enterprises with in-house conversational AI teams that want to build and own highly customized assistants and can staff the design and maintenance work a platform of this depth requires.
Pricing
Consumption-based enterprise licensing, typically per session or per interaction, quoted per contract. Because billing is session-based rather than resolution-based, map sessions to genuine resolutions to understand your real cost.
9. Salesforce Agentforce
Agentforce is Salesforce's AI agent layer, and for organizations already deep in the Salesforce ecosystem the consolidation story is compelling. The pricing model is per conversation, layered on Salesforce licensing, which means you pay for every conversation the agent handles, resolved or not. For a Salesforce-committed enterprise the trade-off may be worth it; for a cost-per-resolution buyer it is the model that least aligns spend with outcomes.
Key Features
Native to the Salesforce platform and data model.
Per-conversation pricing layered on existing Salesforce licensing.
Deep access to Salesforce CRM records and workflows, coexisting with human agents in Service Cloud.
Ideal For
Enterprises heavily committed to Salesforce that prioritize consolidating on a single vendor and data platform over optimizing cost per resolved ticket.
Pricing
Per conversation, layered on Salesforce licensing. Because you are billed per conversation regardless of outcome, calculate cost against genuinely resolved tickets, not conversations touched, to compare fairly with per-resolution vendors.
The pricing model is the ROI lever, not the sticker price. A resolution you define and never pay for on escalation is worth more than a cheaper deflection you cannot audit. See how Lorikeet prices on genuine resolutions.
How to Actually Cut Support Costs With AI
Most buying guides rank on deflection rate and demo polish. Those are downstream of the two things that decide your bill: what counts as a resolution and whether you pay when the AI fails. The criteria below are ordered by how much they move your cost per resolved ticket.
Pay Per Resolution, Not Per Deflection or Per Conversation
A deflection is the customer not escalating; a resolution is the customer being helped. Per-conversation and per-seat models charge you whether or not the issue closed, and deflection-priced tools bill you when the customer gives up. Per-resolution pricing is the only model that ties spend directly to outcomes. Confirm the billing event is a resolved ticket, not a contained session.
Insist on Customer-Defined Resolution
The single most valuable term in an AI support contract is who decides what counts as resolved. If the vendor defines it, the vendor is scoring its own exam and invoicing you for the grade. If you define it, and hold a veto, you only pay when your standard is met. Ask every vendor directly: can I define what a resolution is, and can I dispute one I do not agree with. Lorikeet answers yes to both; most of the category answers no.
Check Whether Escalations Are Billed
When the AI cannot finish a ticket and hands it to a human, are you charged. On many platforms the answer is yes, or it is buried in a per-conversation model that already counted the failed attempt. Escalations that are not charged mean you never pay twice for the same ticket, once for a failed AI attempt and again for the human who actually resolved it. Over a year at volume, this line alone can swing the economics.
Measure the Safe Automation Ceiling, Not the Demo
Cost reduction is a function of how much volume the AI can safely resolve, not how well it handles a scripted demo. A tool that only manages trivial FAQs leaves your expensive, complex tickets on human queues, so the savings cap out early. Platforms with defence in depth (adversarial simulation, message checks, guardrails, and full QA) can safely automate a higher share of real volume, including the multi-step tickets that cost the most to handle manually. Ask what percentage of your actual ticket mix the vendor expects to resolve, and what safeguards let it reach there.
Count the QA Cost You Are Already Hiding
Most teams manually sample 1-3% of tickets for quality, which is both expensive and blind to the other 97%. Automated QA that reviews 100% of interactions (Lorikeet's Coach does this at roughly $0.10 per ticket) removes a hidden line item and catches problems before they become refunds or complaints. When you compare platforms, add the cost of the QA you run by hand to the human baseline, because AI QA can retire it.
Questions to Ask Your Vendor
Demos are built to look good. These questions are built to surface the real cost model.
What exactly is a billable resolution, in writing, and does it include deflections or partial answers.
Can I define what counts as a resolution and dispute ones I disagree with.
Do I pay when the AI escalates a ticket to a human.
Are there seat fees, add-ons, or platform fees on top of the per-resolution or per-conversation price.
What share of my actual ticket mix, not a demo set, do you expect to resolve, and what makes that safe.
How do you handle QA, and is it included or an extra cost.
Show me the blended cost per genuinely resolved ticket at my volume, not the headline rate.
Lorikeet's Take on Cost Per Resolution
The cheapest per-resolution sticker in the market is not automatically the cheapest way to resolve a ticket. Cost per resolution is only meaningful when you control what a resolution is and you are not billed for the AI's failures. A platform that charges less per resolution but defines resolution loosely, bills escalations through a per-conversation model, and caps out at the easy 40% of your volume can cost more per genuinely resolved ticket than one priced slightly higher that safely resolves the hard 80% and never charges you when it hands off.
That is the reasoning behind Lorikeet's model: roughly $0.80 per chat, email, or SMS resolution, escalations not charged, and the customer holding veto over what counts. It is deliberately built for mid-to-high-volume teams in regulated industries where safe automation depth, not deflection theater, is what compounds savings. The honest caveat is that per-resolution economics reward volume; a very low-volume team may do better on a flat or per-seat tool, and that is a fine reason to choose one. If you are resolving thousands of tickets a month and want spend tied to outcomes you can audit, Lorikeet is built for exactly that.
Key Takeaways
Cost per resolution, not sticker price, is the number that reaches your P&L; two vendors with the same headline rate can differ 3-5x in true cost per genuinely resolved ticket.
Three models compete: per-resolution (pay on outcome), per-conversation (pay on every chat), and per-seat (pay per license plus AI add-ons). Per-resolution aligns spend with outcomes only when the resolution definition is honest.
The highest-leverage contract terms are who defines a resolution and whether escalations are billed. Customer-defined resolution with escalations not charged is the tightest cost alignment available.
Fin by Intercom's roughly $0.99 per resolution is the clearest public benchmark; most other vendors quote custom rates, so compare pricing models rather than assuming a single number.
Savings scale with the safe automation ceiling, not demo performance. Deflection tools that only handle easy FAQs leave your expensive tickets on human queues and cap the ROI early.
Per-resolution economics favor mid and high volume; very low-volume teams may still find a flat or per-seat tool cheaper in absolute terms.
Conclusion
Cutting support costs with AI in 2026 is less about finding the lowest advertised rate and more about choosing a pricing model that pays for outcomes you can verify. A resolution you define, on tickets you can audit, with escalations you never pay for, is worth more than a cheaper deflection you cannot inspect. The nine platforms above each represent a different point on that spectrum, from customer-defined per-resolution to per-conversation to layered per-seat models, and the right choice depends on your volume, your industry, and how much you value cost aligned to genuine outcomes.
If your support runs at mid-to-high volume in a regulated or complex environment and you want every dollar tied to a resolution you agreed was real, book a Lorikeet demo and bring your last month of ticket data. You can model the blended cost per resolved ticket against your current human baseline before you commit to anything.
