Blog

Economics

Cost per resolution: how to work out the real number

The price on a vendor's page divides your bill by what the vendor counted. Your real cost divides it by what was actually resolved. The two differ by every billed unit that was not a resolution, and by every fixed charge.

The short version: your real cost per resolution is everything you paid for the AI in a month divided by the conversations it actually resolved, judged by reading them yourself: leave out anything your team finished, any hand-off you configured, and any customer who came back about the same problem within seven days. In the illustration below, $989.50 billed for 1,000 Fin outcomes, of which you judge 70% real, is $1.41 per resolution, not $0.99. The vendor's price is per billed unit, and a billed unit is whatever the vendor's definition says it is. Fin's pricing guide on fin.ai (published 27 April 2026, read 18 November 2026) multiplies resolutions by $0.99. Intercom's billing article, read the same day, also charges $0.99 for a "Procedure handoff", a hand-off to a person or workflow that you configured, and for a customer who leaves after an answer without asking for more help.

Intercom publishes its rules in more detail than most vendors, and lets you open every conversation it billed, which is what makes the method at the end possible. The guide's arithmetic compares two pricing models fairly. It is not your cost per resolution, and the gap between the two is the subject of this piece. The method works on any vendor's invoice.

Why the price per resolution is not the cost per resolution

Three things sit between the number on the pricing page and the number you should report.

Billed units that were not resolutions. Every per-resolution vendor decides what it counts. Some count a conversation where the customer stopped replying, some count a hand-off they were configured to make, and some count a conversation your own team finished. Each of those is billed at the full price and adds nothing to the denominator you care about. The vendors' silence windows are compared in our piece on assumed resolutions, and hand-offs in our piece on whether hand-offs are billed.

Customers who came back. A conversation counted as resolved, followed by the same customer writing in about the same problem, was not resolved. Some vendors take the charge off when the customer returns to the same conversation. In our comparison of eight vendors' own pages on 11 November 2026, none did so when the customer came back in a new one. That is set out in our piece on reopened conversations.

Fixed charges. A base plan or a prepaid allowance that does not carry over belongs in the numerator. In a month when the AI resolves less, they make each real resolution cost more.

Fin's guide counts outcomes as resolutions. Its billing article does not

Fin's guide "Per-Resolution vs Per-Conversation AI Pricing: What CX Leaders Need to Know" takes 50,000 conversations a month at a 65% resolution rate and lists "Billable events: 32,500 resolutions", a monthly cost of $32,175. It says "Fin counts only genuine, positive resolutions where the customer's issue was confirmed solved." It describes per-outcome pricing this way: "If the AI fails and the conversation escalates to a human agent, you pay nothing for that interaction." And it warns that some vendors "count a resolution when the customer stops responding after a timeout period".

Intercom's billing article, "Fin AI Agent outcomes", describes something wider. A resolution is counted when, after Fin's last answer, the customer "either confirms the answer was satisfactory (confirmed resolution), or exits the conversation without requesting further assistance (assumed resolution)". Fin's help centre on fin.ai puts the wait for an assumed resolution at 24 hours. The article's FAQ says a customer who is frustrated with Fin's answer and just leaves "is counted as an Assumed Resolution and will be charged", unless Fin detects the frustration and escalates. And a "Procedure handoff", where Fin runs a procedure you configured to end with a person or a workflow, is billed at the same $0.99. The same article says that, with the move to outcome billing, Fin's Resolution Rate ("the percentage of conversations that Fin resolves without human involvement") "is unaffected by this change".

So for Fin for Service, a month's charges are resolutions, confirmed and assumed, plus procedure hand-offs, at $0.99 each. If you use Fin with your own helpdesk, the first 50 resolutions are covered by the $49 base plan instead. Fin for Sales adds outcome types of its own. Intercom deserves credit for the next part: its FAQ "How do I find the specific conversations I was charged for?" points to the Performance funnel in Fin AI Agent, where each billed conversation can be opened. That is exactly what the method below needs.

What five per-resolution vendors bill, and where to find the list (November 2026)

Each cell is from the vendor's own billing or help pages, read in a browser on 18 November 2026. "Not stated" means the pages we read do not say. Every vendor's price, unit and rules for silence, hand-offs and reopens are in the AI support billing index.

What one billed unit costs, what it can include that is not a resolution, and where the billed list is. From each vendor's own pages, read 18 November 2026.
Vendor Price of one billed unit Billed, but you may not call it a resolution Where the billed list is
FinIntercom $0.99 per outcome. On fin.ai, with your own helpdesk, a $49 monthly base plan includes 50 resolutions; further outcomes $0.99 each A customer who leaves after an answer without asking for more (24 hours); a procedure hand-off; a teammate joining after an answer, before the customer asked for more help Performance funnel in Fin AI Agent, each conversation can be opened
AI agentsZendesk Per-resolution price not stated on the two pages read. Drawn in dollars from an allowance: $2 to $10 per agent seat a month included, by plan; unused monthly allowance does not carry over Only a "Verified resolution" counts, after an LLM checks the transcript. Silence that fails the check, and escalations, do not count Resolution allowance dashboard, filtered by tier, links to every ticket counted
Customer agentHubSpot Messaging: 50 credits per resolution; credits $10 per 1,000, so $0.50 (voice is billed per minute) A reply that shares a content source or performs an action, with no customer-started hand-off within 72 hours of the customer's last message; also any lead marked qualified, partially qualified or not qualified. Assignment by your team or a workflow does not stop it Resolutions report in the customer agent's performance analytics
AI AgentGorgias An automation fee, set by your plan, on top of the ticket fee the ticket would carry anyway Any interaction where no person is needed within 72 hours. The automation fee also covers Flows, Order Management and Article Recommendations Plan details on the Billing & usage page; a per-ticket list not stated
ScoutHelp Scout $0.75 per resolution, once per session A customer who does not ask for more help after the last AI response. No wait stated Reports, then Scout: the billable conversations

Zendesk wins this table. It is the only vendor here that does not bill a conversation just because the customer went quiet: silence that an LLM check of the transcript does not confirm is a "Contained resolution" and does not count against the allowance. Its allowance dashboard also links to every ticket that was counted. The check is still the vendor's model grading the vendor's agent, so the sample in the method below applies to Zendesk too, but there is less in the billed count to argue with.

Help Scout and Fin make the check easy. Both point to a report listing the conversations they billed. Help Scout's rule is short and public; its one gap is that it states no wait before a quiet customer counts.

HubSpot's rule puts the work on you. Only a hand-off the customer starts stops a resolution, and HubSpot's help article says that "Manual agent assignment, including assignment through workflows, is not considered a qualifying handoff". A conversation your team picked up and finished can therefore still be billed. HubSpot's performance analytics include a Resolutions report, which is where to start the check.

Gorgias adds an automation fee to the ticket fee. Its billing article says "An automation fee and a ticket fee may apply to the same ticket only when the ticket is entirely resolved by AI Agent, without human intervention." The ticket fee would be charged if a person had answered, so only the automation fee belongs in the AI numerator. The automation fee also applies when Flows, Order Management or Article Recommendations resolve an inquiry, so filter those out if you are costing the AI Agent alone.

  1. One conversation on the vendor's billed list
  2. Did someone on your team finish it, or was it a hand-off you configured? Yes Leave it out
  3. Reading the transcript, did the AI fail to answer the question asked? Yes Leave it out
  4. Did the customer come back about the same problem within 7 days, on any channel? Yes Leave it out
  5. Otherwise it counts as a real resolution, whether the customer said thanks or went quiet
Sorting one billed unit. Every unit stays in the numerator, because it was paid for. Only the ones that reach the end go in the denominator.

A quiet customer counts only if you, reading the transcript, would call the question answered. That is a stricter test than a timer, and it is why you read the conversation rather than trust the silence. Mark any you cannot judge as unclear, which counts as not resolved.

A worked example

This is an illustration, not data: the counts are invented to show the arithmetic and are not an estimate of any vendor's rates. The prices are Fin's, as read on 18 November 2026 on fin.ai, for Fin used with your own helpdesk.

Fin is billed for 1,000 outcomes in a month. The base plan is $49 and includes 50 resolutions; assume they are used in full and the other 950 outcomes cost $0.99 each, $940.50. The month's AI charges are $989.50, which is $0.99 per billed outcome. Now read a random 100 of the billed conversations. Suppose 70 were resolved by Fin on your reading, 10 were procedure hand-offs your team finished, 12 were customers who left without an answer that worked, and 8 came back about the same problem by email within a week. The real share is 70%, so the real count is about 700, and the real cost per resolution is $989.50 divided by 700: $1.41.

With 100 read, a 95% confidence range for 70% is about 61% to 79%. At 790 real resolutions the cost is $1.25; at 610 it is $1.62. That range, next to $0.99, is the honest version of the number. A longer worked example across five vendors, with the same invented month billed five ways, is in our piece on AI support pricing models.

How to calculate your real cost per resolution

This needs one invoice, the vendor's list of billed conversations, and a few hours of reading. It works the same way for a per-resolution, per-conversation or credit-based vendor.

  1. Add up one month of AI charges. Every line the AI caused: per-unit charges, the base plan, and credit packs or allowance top-ups bought for that month and not carried over. Leave out seats and ticket fees you would pay for anyway, and write down that you did.
  2. Get the list of what you were billed for. Every billed unit for the month, each with its conversation. The table above says where each vendor shows it. If yours does not, ask for it in writing.
  3. Read a random sample of 100. Pick them at random, not from the top of a report. Mark each one resolved by the AI, not resolved, or unclear, by your own reading, and count unclear as not resolved. Note why: your team finished it, the customer gave up, or the customer came back.
  4. Check for returns on every channel. For each sampled conversation, look for a contact from the same customer about the same problem within seven days, by email, chat, phone or social. One that came back was not resolved, whatever the invoice says.
  5. Work out the real count. Divide the resolved ones in your sample by 100 to get the real share, then multiply the month's billed count by it. With 100 read, the share is uncertain by roughly 9 to 10 percentage points either way (95% confidence), so also work out the count at both ends.
  6. Divide, and report a range. Total AI charges divided by the real count is your real cost per resolution. Report it at the low and high ends too, next to the vendor's price per unit, and repeat the check every quarter.

If you want a total cost rather than the vendor's cost, add your team's time in a second column rather than folding it in: the minutes spent finishing hand-offs, keeping the knowledge current and reviewing the AI's answers. Kept apart, the two numbers tell you which one moved.

To judge whether the AI pays, compare the real cost per resolution with your own human cost per resolved contact for the same contact types and month, not with a salary. The break-even point is the real share at which the two are equal. If the low end of your range is above it, the AI pays even on the cautious reading.

Where Varley stands

Varley sells a competing AI support agent, so read this section as a vendor talking about itself. Everything above it can be checked on the vendors' own pages.

Varley's definition page, How we count a resolution (version 1.1, read 18 November 2026), counts a resolution only "where there is positive evidence the customer's issue was dealt with", says "Silence never counts, however long it runs and however warm the last message was", and does not bill a hand-off. "If a customer comes back about the same issue within 30 days, the original charge is credited back in full and the conversation is treated as never resolved." Each of those removes one reason the method above exists, but not the method: Varley's count is still Varley's, and the page invites you to check it.

There is no self-serve export: the list of billed resolutions is sent on request within two working days, which is what step two needs. Varley does not publish a resolution rate yet. The early-access price for direct use is $0.50 per resolution, as of 28 September 2026 on the pricing page (read 18 November 2026). If you want to try it, request early access.

Right of reply

None of the companies named here was approached before publication. Every claim is taken from their own public pages, read on the date given in the sources. If anything on this page is wrong or has changed, write to support@dragapp.com and the correction will be published here with a date, including if it is inconvenient for us.

Questions

What is the formula for real cost per resolution?

AI charges for the month, divided by billed units multiplied by the share of them you judge truly resolved. Use the same month for both halves. If your vendor bills in arrears, as Help Scout does, match the invoice to the month the conversations happened. A per-conversation or credit vendor works the same way, with conversations or tickets as the billed units.

Is real cost per resolution the same as cost per ticket?

No. Cost per ticket divides by every ticket handled, solved or not, so it can fall as volume rises even when nothing more gets solved. Real cost per resolution divides only by problems solved, so a vendor that bills failures, or an AI that resolves less, shows up as a higher number instead of disappearing into an average.

Should I include my agents' time in AI cost per resolution?

Keep it as a second number. For one month, time three things: the minutes your team spends finishing each hand-off, the hours a week spent keeping the AI's knowledge current, and the hours spent reviewing its answers. Multiply by a loaded hourly cost. Add it to the vendor's charges and divide by your real count of resolutions: that is what each resolution costs the business.

What if the vendor will not give me the list of billed conversations?

Ask in writing, and say why: you want to check the invoice. If the answer is still no, sample from your own help desk instead. Take the conversations the AI took part in that month, read 100 at random, and compare the share you judge resolved with the vendor's reported rate. You lose the link to the invoice, not the check.

Changes to this piece

18 Nov 2026
First published.

Sources