Per-Resolution AI Support Pricing Beyond the $0.99 Headline

Intercom Fin is the source of the $0.99 in this headline. Its published rate is $0.99 for each outcome it records. That sounds like the price. It is only one line of the bill.

A resolution may mean the customer confirmed the answer. It may also mean they stopped replying for 24 hours. A rules-based flow, article recommendation or configured handoff may qualify. One issue may use an AI allowance and the helpdesk allowance.

Seats, platform fees, minimums and channel charges can sit underneath the AI charge.

Per-resolution pricing is sold as outcome-based pricing. The vendor earns more when the software finishes more work. That alignment holds only when the buyer can inspect the outcome, reject a bad classification and cap the invoice.

Per-resolution pricing charges for conversations the vendor classifies as resolved.

The hard part is finding what creates a billable resolution.

What per-resolution pricing means

A resolution is not a standard accounting unit. Every vendor defines it.

• Confirmed resolution: the customer says the answer helped or clicks a confirmation.
• Assumed resolution: the customer does not ask for more help within a set time.
• Verified resolution: a model reads the conversation and decides the issue was resolved.
• Configured outcome: a predefined event, such as a qualification or procedure handoff, completes.

Those are different products. Confirmation records a customer action. Assumption interprets inactivity. Verification adds another model's judgment. A configured outcome may be commercially useful without the AI completing the final work.

Other AI chatbot pricing models move the uncertainty elsewhere. The same problem appears in AI customer support pricing comparisons that show rates without defining their units.

Per-resolution and per-conversation pricing both depend on a conversation boundary. The vendor still decides when a thread ends, how long a customer can return and whether a reopened issue becomes a new unit. Per-resolution pricing adds a success label on top.

A low AI support cost per resolution therefore says very little about the monthly bill. The unit rate is one input. The vendor controls the event definition and usually the reporting system used to count it.

Is per-resolution pricing even right for you?

Use volume to make the first cut. The site's broader platform-buying guide uses this rough rule:

This is a shortlist rule, not a universal price boundary. A store with difficult, high-value tickets may accept a higher outcome charge. A store using AI for order status and FAQs should be harder on the price. Existing helpdesk contracts, team size and channel mix can move the break-even point.

Five ways the invoice gets away from the headline rate

The published rate answers one question: how much one recorded outcome costs. Five other decisions determine how many outcomes reach the invoice and what sits beside them.

1. Silence can become a paid success

Fin's pricing-outcomes documentation, updated June 19, 2026, counts confirmed and assumed outcomes. No request for more help within 24 hours can create an assumed resolution.

The edge case is explicit. A customer who leaves after Fin's answer without asking for more help is counted and billed at $0.99. Fin also says that a later request in the same conversation should deduct the resolution.

Why silence is hard to price:

• The answer worked, so the customer left.
• The answer failed, so the customer gave up.
• The customer moved to another channel.
• A teammate stepped in before the customer asked for a person.

All four paths can look like inactivity from inside a timer. Buyers need separate exports for confirmed and assumed outcomes, plus a defined credit window for reopens. "We credit reopens" means little if the window and reversal never appear against the original charge.

2. Simple automation can use the AI meter

"AI resolution" suggests open-ended reasoning and completed work. Gorgias's billing documentation, checked September 18, 2026, uses a wider definition.

An automation fee can apply when an inquiry ends through:

• AI Agent;
• Flows;
• Order Management;
• Article Recommendations.

It is not the same workload as investigating a failed delivery across several systems.

Ask for an event inventory before signing. Every rule, flow, recommendation, lookup, qualification and handoff that can consume a paid unit belongs on it.

3. Unequal work can carry the same price

Flat per-resolution pricing can put a one-line FAQ and a multi-system investigation on the same rate.

Fin charges one outcome per conversation. Gorgias charges when a supported automation completes the interaction. Neither structure necessarily changes the price for complexity, reply count or business value.

The ticket mix decides whether that is fair. A queue full of password resets and order-status checks should not carry the same cost assumption as technical failures that need investigation.

Zendesk and eesel split the work differently:

• Zendesk's May 2026 resolution tiers distinguish outcome classes.
• Eesel lists light tasks as free, regular support tasks at $0.40 and heavy tasks at $4.

Those bands introduce another label to audit. They also recognise that automated work does not have one value.

4. One ticket can touch two meters

The AI charge may sit beside:

• the helpdesk subscription;
• human seats or ticket tiers;
• voice and SMS usage;
• minimum commitments;
• onboarding and overages.

Gorgias documents that a ticket fully resolved by AI can count toward the helpdesk ticket allowance and the automated-interaction allowance. One issue consumes two units.

Fin has another stack. Its pricing page, checked September 18, 2026, listed a $49 base with 50 outcomes on another helpdesk, then $0.99 for extra outcomes. With Intercom, pricing started at $29 per helpdesk seat per month plus $0.99 per outcome.

The AI customer service cost per ticket has to include the system receiving the ticket. Compare complete invoices at the same volume.

5. Reopens and minimums change the effective rate

Fin caps billing at one outcome per conversation and says a later same-thread request should deduct the resolution. The unanswered part is the boundary: how long does the system treat a thread as the same conversation, and does the deduction appear clearly?

Minimums change the other end of the calculation. Fin's $49 base includes 50 outcomes, and unused outcomes do not roll over.

An alert reports a growing invoice. It does not stop one. A hard limit, approval gate or automatic fallback does.

When the dashboard and the support queue disagree

Official documentation describes intended behaviour. Practitioner reports show where the rule can collide with support work. The examples below are individual reports in Intercom's community, not evidence that every Fin customer sees the same result.

In an April 2024 thread, a user described Fin giving a clearly incorrect answer before the customer abandoned the chat. An Intercom support engineer said conversations charged despite not being resolved should be investigated. The case exposes the accounting problem: an inactivity rule can classify a failed answer as success unless another signal changes it.

A January 2025 discussion described teammates stepping in when Fin produced dangerous or nonsensical answers. The operator said the cases were still assumed resolved because the customer had not selected "Speak to Human." A later official clarification said a teammate reply after Fin does not itself prevent billing. The customer must ask for more help or a person.

Early intervention can then cost twice. A responsible agent wants to intervene before the customer complains. If early intervention does not reverse the outcome, the company can pay for an AI resolution and then pay a human to repair it.

Sixteen conversations are not a benchmark. They are enough to show why an aggregate rate needs conversation-level sampling. The vendor's financial definition and the buyer's quality standard are not identical.

One model up close: Aissist

The comparison below covers cost structures, not product quality.

What the price buys

Aissist is an AI-first automation layer for teams already using Intercom, Zendesk, Freshdesk or Gorgias. Its free tier includes 1,000 conversations a month with no card. The Growth rates supplied during our review were about $0.25 per email resolution and $0.60 per chat resolution, with no contract.

The channel split matters. Two thousand recorded email resolutions would create a much smaller usage line than two thousand recorded chat resolutions. A buyer forecasting Aissist needs the expected mix, not one blended headline price.

Aissist also has a resolution cap. That is a real budget control: the team can put a boundary around paid resolutions rather than discovering uncapped usage after the month closes. The free allowance and no-contract structure make a live test easier to start.

The cap controls the maximum exposure. It does not make the rate flat. The bill still scales with interactions until it reaches that cap, so Aissist is not a flat bill as volume grows.

What running it looked like in our test

Signup crawled the connected site and created 18 specialist sub-agents from its content. A debug view exposed the stages behind an answer, cited sources and the time each stage took; one test answer took 14.6 seconds. That made the answer easier to inspect than a chatbot that returns only the final text.

The free tier uses Aissist's basic engine. Its advanced engine and traffic-dependent Pulse insights could not be tested on the trial. Webchat also needs a connected helpdesk; the product did not provide a standalone embed code in our test. Those limits matter when a small team expects a complete chatbot that can be pasted straight onto a site.

The full Aissist hands-on review covers the tests, score and product limits.

The other five, in one line each

A 2,000-chat store paying for Fin

Here is the bill using Fin's public prices checked September 18, 2026:

The $879 is the modelled Fin-plus-Intercom bill before tax and any extra products or channels. The $29 seat price is a starting price, so a real plan can be higher. The example does not include Shopify's own cost because it is not part of the support-vendor invoice.

That is the point of forecasting in plain numbers. Ask the vendor for your expected conversation volume, recorded outcome rate and every fixed charge. Calculate a normal month and the busiest month. Then calculate the case where the AI improves and records more outcomes.

If the store's audit accepts 600 of the 800 recorded outcomes, its effective cost is $879 / 600, or about $1.47 per accepted resolution. Dividing only the AI line by all 800 vendor-recorded outcomes would produce $0.99 and hide the seat cost and the rejected classifications.

The vendor-recorded rate reconciles the invoice. The audited rate evaluates the product.

Run the meter before you pay against it

Ask the vendor to label outcomes for 30 days without charging. Sample different channels, languages, ticket types and complexity levels. Review whether each customer received a complete answer without human completion.

For every rejection, record a reason:

• Wrong answer
• Partial answer
• Abandonment
• Early human intervention
• Duplicate session
• Simple flow charged at the full rate
• Reopen not credited

Do not use the pilot to produce one flattering automation percentage. Use it to find which definitions have to change before money follows the label.

A simple worksheet needs these columns:

A sheet like this is more useful in a contract discussion than another feature comparison.

Pricing only matters after answer quality

A cheap AI agent that gives wrong answers creates a second cost: human repair. Pricing pages cannot tell you how well an agent handles your policies, edge cases or missing documentation. Check the site's hands-on tool reviews alongside the rate sheet. The Aissist review is one example of the process: test the product on real questions, trace negative findings back to the runs and keep the commercial placement separate from the score.

A variable bill still needs a ceiling

Predictable does not have to mean flat. It means the buyer can reproduce the meter and choose the maximum exposure.

• Contract definition. Write down confirmation, silence windows, teammate intervention, reopens, session boundaries, channel differences and every non-generative automation that shares the unit. Sales copy is not a billing definition.
• Hard currency ceiling. Alerts at 50%, 75% and 100% report spend; they do not stop it. At the ceiling, the agent should pause, fall back to the human queue or ask for approval. A currency cap is clearer than a unit cap when channels carry different rates.
• Lower rate for simpler work. Routing, article clicks, static FAQ flows and basic lookups should cost less than a verified multi-step resolution. Zendesk's tiers and eesel's task bands take different routes to the same sensible idea: a "helpful" click is not equal to an investigation.
• Declining price at volume. Better documentation and wider automation increase the number of paid outcomes. Volume bands stop every gain from flowing to the vendor at the same unit rate.
• One complete cost sheet. Put platform, seats, ticket tiers, outcomes, voice and SMS, onboarding, support, minimums, overages, tax and currency in one model. The outcome rate alone is not a budget.
• Exportable event log. Each paid unit needs a ticket ID, timestamp, channel, trigger, outcome class, verification result and reversal status. Aggregate charts cannot reconcile an invoice.
• Automatic credits with consequences. If the same issue returns inside the agreed window, reverse the charge next to the original event. If an audit crosses an agreed false-resolution threshold, credits should apply or billing should pause while the classification is fixed.

Do this this week

• Start with a free tier or trial. Connect a narrow set of help content and send it real past questions, including questions the documentation does not answer.
• Run a shadow invoice. Let the vendor label outcomes without charging, then audit the conversations against your own definition of a complete answer.
• Sign only after the labels and the bill agree. Put the event definition, hard ceiling, reopen credits and export rights into the contract.

The questions worth taking into the sales call

• What exact event creates a billable resolution?
• Does customer silence count, and after how long?
• Does any teammate intervention void the outcome, or must the customer request a person first?
• Can one conversation be billed more than once?
• Which flows, rules, article recommendations, routing steps, order lookups, handoffs and qualifications use the meter?
• Is every outcome the same price regardless of complexity?
• Can we export and dispute every charged conversation?
• Which base, seat, ticket, channel, onboarding and support fees sit underneath the AI charge?
• Do unused units expire, and does excess usage pause or become automatic overage?
• Will you run a no-charge shadow invoice against our tickets?

If a vendor cannot answer the first question without showing a help article, contract clause or event schema, the rate is not ready to compare.

Compare the meter before you compare the cents

The rate cannot tell you whether silence is billable, a static flow costs the same as an investigation, two meters touch one ticket or reopens receive credits.

Compare the billing definition, event log and cap before comparing cents.

WRITTEN BY AR · UPDATED 2026-09-18

I read the fine print. Vendor pricing pages, billing definitions, terms, funding filings and acquisition notices — then I do the arithmetic nobody publishes: what a platform actually costs at your volume, what its headline metric is really counting, and who owns it now. I do not run benchmarks, and no page here pretends otherwise.

Editorial policy