What is it
Per-Resolution Pricing is a billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
It is the canonical way to implement outcome-based pricing in customer service: instead of paying per seat, per token, or per API call, the buyer pays per resolved conversation — and pays nothing when the AI hands off to a human. Intercom defined the category in 2023 by pricing its Fin AI Agent at a flat $0.99 per resolution, the same rate across every plan tier and for standalone Fin running inside Zendesk or Salesforce. The pitch is structural alignment: Intercom is the rare AI vendor whose financial model only makes money when the AI actually works.
Fifteen of the corpus’s companies now meter on resolutions, and the cluster spans the whole go-to-market spectrum. At one end sit self-serve vendors that publish the rate — Intercom Fin and Yellow.ai both expose $0.99 per resolution publicly. In the middle are hybrids that graft a resolution meter onto an existing platform — Zendesk AI, Gorgias, Forethought, Kustomer, and Gladly. At the far end are pure-outcome, sales-gated agents — Sierra, Decagon, Ada, Maven AGI, Lorikeet, and Parloa — plus Pixee, which extends the unit outside support entirely by billing per resolved vulnerability. The tightness of that cluster makes per-resolution the bellwether for the corpus’s outcome-based pricing trend: when one category converges this hard on an outcome unit, the rest of AI software is watching.
The hard part is definitional. A “resolution” is whatever the vendor says it is, and that single choice decides whether the vendor’s incentives align with the buyer’s or quietly diverge from them. Decagon is candid about it — its own glossary admits “what counts as a resolution” is genuinely contested for abandoned chats and partial answers. The rest of this page is mostly about who counts what.
How it works
The mechanic is simple — bill = resolutions × rate — but the design lives in two decisions: what counts as a resolution, and whether the resolution charge sits on top of a seat fee, a ticket fee, or nothing at all.
| Vendor | Resolution unit | Published rate | Sits on top of |
|---|---|---|---|
| Intercom Fin | Fin conversation closed without human escalation | $0.99 / resolution | $29–$132 / seat / mo (optional) |
| Yellow.ai | Resolved chat conversation (after 500 free/mo) | $0.99 / resolution | Free tier — no seat fee |
| Zendesk AI | Automated resolution above plan allowance | Usage-billed (not a clean public number) | $19–$115 / agent / mo Suite seats |
| Gorgias | AI Agent fully automates a conversation end-to-end | $0.90 / resolution | Ticket-metered tiers |
| Forethought | Resolved issue under outcome meter | Quote-only | Platform access fee (Team/Pro/Enterprise) |
| Kustomer | Customer-facing AI agent “engaged conversation” | Quote-only (per engaged conversation) | Seat tiers (gated) |
| Gladly | Sidekick AI “assisted conversation” | Quote-only (per assisted conversation) | Per-Hero seat package |
| Sierra | Issue the AI agent fully resolves (“a job well done”) | Not published; blended with volume rate | Annual enterprise contract |
| Decagon | Conversation resolved start-to-finish, no human help | Not published (~$95K/yr floor, third-party) | Annual enterprise contract |
| Ada | Conversation the AI actually resolved | ~$1–$3.50 (third-party; not published) | Nothing — pure outcome, sales-gated |
| Maven AGI | Autonomous resolution across chat + voice | Not published | Annual enterprise platform commitment |
| Lorikeet | Successfully resolved ticket (refunds the unhappy ones) | 0.80–0.95 credits (chat/email/SMS); 1.20–1.50 (voice) | Nothing — annual credit pool only |
| Parloa | Per-interaction resolution (conversation volume) | Not published (~$300K/yr floor) | Negotiated enterprise contract |
| Pixee | Resolved vulnerability (SAST + SCA finding remediated) | Custom quote, off annual scanner findings | Nothing — unlimited developers included |
Worked example (Intercom Fin). A support team on the Advanced tier with 10 agents and 5,000 Fin resolutions in a month pays 10 × $85 in seat fees plus 5,000 × $0.99 in resolution fees — $850 + $4,950 = $5,800, of which 85% is the outcome line, not the seat line. That ratio is the whole point: as the AI deflects more, the seat fee shrinks to a floor and the resolution meter becomes the bill. You can model exactly this split in the Intercom pricing calculator.
Worked example (Yellow.ai free-then-meter). A team on Yellow.ai’s Free tier resolving 2,000 conversations in a month pays for none of the first 500 (included) and 1,500 × $0.99 = $1,485 on the overage — the same $0.99 unit as Intercom, but exposed on a self-serve tier with no seat fee underneath it at all.
Worked example (Lorikeet credits). A team on Lorikeet’s Scale plan (48,000 credits/year) resolving 3,000 chat tickets in a month draws 3,000 × 0.80 = 2,400 credits against the annual pool — and pays for none of the tickets the AI failed to resolve, because Lorikeet refunds resolutions the customer is unhappy with.
The “engaged”/“assisted” framing at Kustomer and Gladly is the loosest definition in the table: a conversation the AI touched can count, not only one it closed end-to-end. At the strict end, Sierra and Decagon bill only when the agent resolves an issue with no human help — and Zendesk AI sits apart again, billing automated resolutions only above a plan allowance, so successful deflection grows the bill above the included floor. For the mechanics of metering these tiers, see usage thresholds and overage alerting.
Companies using this
Fifteen corpus companies meter on resolutions. Fourteen are AI customer-support products — from self-serve, published-rate vendors like Intercom Fin and Yellow.ai, through hybrids like Zendesk AI, Gorgias, and Forethought, to pure-outcome sales-gated agents like Sierra, Decagon, and Maven AGI — and Pixee extends the same outcome logic to security, billing per resolved vulnerability rather than per resolved ticket. The table below shows each vendor’s resolution definition, published rate, and what (if anything) the resolution charge sits on top of.
Patterns observed
-
The published rate has converged on $0.99. The two vendors that expose a self-serve rate — Intercom Fin and Yellow.ai — land on the exact same $0.99 per resolution, and Gorgias sits a dime under at $0.90. When independent vendors price the same unit inside a 10-cent band, the market has found a reference price, and Intercom’s 2023 number is clearly the anchor everyone else calibrates against.
-
Most of the cluster keeps the rate private, and opacity scales with deal size. The self-serve vendors publish; the enterprise ones don’t. Sierra, Decagon, Ada, Maven AGI, Forethought, and Parloa all bill per resolution but quote every deal — third-party estimates put Decagon near a $95K/year floor and Parloa above $300K/year. Outcome pricing and price opacity travel together here: a buyer can know the unit is a resolution and still be unable to model spend before entering sales.
-
The resolution sits on a different base at each vendor — and the base is shrinking. Intercom Fin layers it (optionally) on a seat fee, Zendesk AI grafts it onto per-agent Suite seats, Forethought blends it with a platform access fee, Gorgias puts it on a ticket-metered tier, and Lorikeet and Ada put it on nothing at all. The trajectory is clear: the fixed base is becoming a floor while the resolution meter becomes the bill, exactly the dynamic the outcome-based pricing trend tracks.
-
Definition is the real product decision. Sierra and Decagon only bill when the AI resolves an issue end-to-end without human help — strict, buyer-friendly. Kustomer and Gladly bill on “engaged”/“assisted” conversations the AI merely touched — looser, and easier for the meter to fire. Zendesk AI bills only automated resolutions above an included allowance, and Lorikeet goes furthest the other way, refunding resolutions the buyer is unhappy with. The unit is nominally identical across all six; the firing rule is not.
-
The strongest alignment claim wins the narrative. Every vendor in the cluster markets incentive alignment — Sierra’s “pay for a job well done” and Pixee’s “traditional tools profit when your backlog grows; we only profit when it shrinks” are the sharpest framings, while Lorikeet’s “you don’t pay for that ticket” guarantee is the strongest contractual version of it. Decagon even publishes a defense of resolution-based pricing in its glossary, turning the billing model itself into a sales asset.
Counterexamples & variants
The clearest variant is Pixee, which proves per-resolution isn’t a support-only unit: it bills per resolved vulnerability (calculated off annual SAST + SCA scanner findings), with unlimited developers included, framing the model as “pay per vulnerability resolved, not developer seats.” The outcome unit generalizes to any domain where an AI closes a measurable backlog item rather than consuming a seat — support tickets, security findings, or anything else with a countable definition of “done.”
The clearest counterexample to transparency is the sales-gated enterprise tier — Sierra, Decagon, Ada, Maven AGI, and Parloa. All meter on resolutions but publish no rate at all. Ada pivoted away from its old Core/Advanced/Pro tiers to an outcome model in 2023 yet shows only a “book a consultation” form; Parloa’s /pricing path 404s entirely; Sierra communicates its model as a philosophy (“pay for a job well done”) rather than a number. A buyer can know the unit is a resolution and still be unable to forecast spend before entering sales.
Kustomer and Gladly are the soft-definition variant — their “engaged”/“assisted conversation” meter charges for AI involvement, not strictly for an unescalated resolution, so the unit looks like per-resolution but can fire on conversations a human still finished. Zendesk AI is the incumbent-hybrid variant: it never fully commits to the outcome unit, keeping per-agent Suite seats ($19–$115/mo) for humans and billing automated resolutions only above a plan allowance — an outcome meter grafted onto a seat platform rather than replacing it, which lets Zendesk protect its seat base while answering pure-outcome challengers. And Forethought is the explicit-blend variant: rather than choose, it states outright that “our pricing model is a blend of platform access fees and an outcome-based pricing cost,” hedging predictability against value alignment inside a single contract.
What this means for buyers vs vendors
For buyers
Read the resolution definition before the rate. A “engaged conversation” at Kustomer or Gladly that fires whenever the AI touches a ticket can cost more than a $0.99 “unescalated resolution” at Intercom Fin that only fires on a clean deflection — the per-unit price is meaningless without the firing rule. Model your spend at your real deflection rate, not the vendor’s demo rate, and watch the base underneath: at Zendesk AI the resolution meter only kicks in above a plan allowance, so a rising deflection rate is exactly what grows your bill.
Treat the sales-gated vendors — Sierra, Decagon, Ada, Maven AGI, Parloa — as un-forecastable until you have a quote, and use the self-serve anchors (Intercom Fin and Yellow.ai at $0.99, Gorgias at $0.90) as your sanity-check reference price when you do. Watch for separate channel charges — voice generally carries higher economics than chat at nearly every vendor — the way any metered line shows up across usage invoicing and billing cycles. Ground your forecast in the introduction to usage-based pricing, settle on your value metric with choosing the right usage metric, and run the numbers in the Intercom pricing calculator.
For vendors
Per-resolution is the strongest alignment story in AI pricing — you only earn when you deliver — but the definition is a liability if it’s loose. A meter that fires on “assisted” conversations, as at Kustomer and Gladly, invites disputes the first time a buyer audits its bill against its actual deflection logs. The durable versions are the strict ones: Sierra’s and Decagon’s end-to-end-resolution rule, Intercom Fin’s unescalated-resolution rule, or Lorikeet’s refund guarantee.
Decide next whether to publish. The self-serve winners — Intercom Fin, Yellow.ai — turned a transparent $0.99 into a category anchor and a PLG on-ramp; the enterprise players — Sierra, Maven AGI, Forethought — keep the number private to tailor each deal to volume and channel mix. Either can work, but opacity costs you buyer trust and lengthens the sales cycle, so Decagon’s move — publishing a philosophy even while quoting privately — is a smart hedge. Whichever you choose, keep the resolution charge on top of a thin platform floor so you’re not fully exposed to a buyer’s deflection variance, and settle the resolution definition in the contract, not the marketing page — see the outcome-based pricing trend for how the category is hardening these definitions.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| Ada | AI agent platform for automated customer service across chat, email, voice, and SMS | No | 2026-06-07 | ||
| Decagon | AI customer support agent platform | No | 2026-06-11 | ||
| Forethought | AI customer support automation | No | 2026-06-11 | ||
| Gladly | AI-first customer experience (CX) platform built around lifetime value rather than ticket deflection | No | 2026-06-07 | ||
| Gorgias | Conversational AI helpdesk for ecommerce — ticketing, chat, and an AI Agent that automates support and drives sales | No | 2026-06-07 | ||
| Intercom | Fin AI Agent + Customer Service Suite | No | 2026-07-06 | ||
| Intercom Fin | Fin AI Agent for customer service | No | 2026-06-30 | ||
| Kustomer | AI-first CRM and customer-service platform unifying omnichannel support, automation, and AI agents | No | 2026-06-07 | ||
| Lorikeet | AI customer-support agent that resolves chat, email, SMS, and voice tickets | No | 2026-06-07 | ||
| Maven AGI | Enterprise AI agent platform for customer support | No | 2026-06-11 | ||
| Parloa | Enterprise AI Agent Management Platform (AMP) for contact-center voice and chat automation | No | 2026-06-07 | ||
| Pixee | Pixee agentic security engineering platform | No | 2026-06-08 | ||
| Sierra | Conversational AI customer agents | No | 2026-06-11 | ||
| Yellow.ai | Conversational CX automation platform | Yes | 2026-06-11 | ||
| Zendesk AI | Zendesk AI agents, Copilot & Advanced AI for customer service | No | 2026-06-11 |
Explore this theme in the knowledge graph
FAQ
What is per-resolution pricing?
Per-resolution pricing is a billing unit where an AI customer-support vendor charges only when its AI agent resolves a customer issue without human escalation. Intercom's Fin defined the category at $0.99 per resolution; the customer pays nothing for conversations the AI fails to close.
What counts as a resolution?
It varies by vendor, and the definition is the whole game. Intercom Fin counts a conversation closed without human handoff; Sierra and Decagon bill only when the AI resolves an issue end-to-end; Kustomer and Gladly meter a broader 'engaged' or 'assisted' conversation. Always read the vendor's resolution definition before signing.
How much does a resolution cost?
Published rates cluster at $0.99: Intercom Fin and Yellow.ai both charge $0.99 per resolution. Most enterprise vendors — Sierra, Decagon, Ada, Maven AGI, Forethought, Parloa — meter on resolutions but don't publish a rate; third-party data puts Ada near $1–$3.50 per resolution.
Is per-resolution pricing the same as outcome-based pricing?
Per-resolution is the most common billing unit used to implement outcome-based pricing in customer support — the vendor only earns when it delivers the outcome (a resolved ticket). See the outcome-based pricing trend for the broader pattern across categories.
Why do support AI vendors charge per resolution instead of per seat?
Because an AI agent does work a human seat used to, so 'how many seats?' stops mapping to value. Charging per resolution aligns the vendor's revenue with the buyer's outcome — the vendor only makes money when the AI actually solves the ticket.
Do incumbents like Zendesk use per-resolution pricing?
Yes, as a hybrid. Zendesk keeps per-agent Suite seats ($19–$115/mo) for humans but bills its AI agents on automated resolutions above a plan allowance, grafting an outcome meter onto a seat-based platform rather than replacing it.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Image PricingA billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Per-Video PricingA billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Outcome PricingA billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.
- Per-Datapoint PricingA billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Robot-Hour PricingA billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Browser-Hour PricingA billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-IP PricingA billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.