Research: how AI support vendors define and bill a resolution

Of 14 AI customer-support vendors whose own documents we read on 8 November 2026, the six that define a resolution count a conversation the customer did not escalate, and where they state a window it is 72 hours or less. They bill on six different units (resolution, automated interaction, session, action, conversation, and outcomes set per contract), and three publish a price per resolved outcome: Intercom, Zendesk and Help Scout. Gorgias prices its automated interactions by plan, but the page read showed conflicting figures.

Every fact below comes from the vendor's own public documentation; a date in a source link is the date the page itself shows. Figures that appeared only in third-party writing are left out, and the page makes no claim about any vendor's results.

Definitions#

Read on 8 November 2026.

VendorWhat countsWhen it is decidedWhat voids itCustomer asked?Source
Intercom (Fin)Two kinds of resolution: confirmed (the customer replies that the answer helped) and assumed (the customer leaves after Fin's last answer without asking for more help). A reply to a greeting alone does not countNo window statedA request for a human or more help, or a failed Procedure. A resolved conversation the customer returns to is deducted, even in a later billing period. A teammate joining after Fin answered can still leave it resolvedImplicitly; confirmed and assumed count alikeIntercom, updated 23 Sep 2026
Zendesk (AI agents)Since 18 May 2026, three tiers. Zendesk's "Verified resolution": the AI answered, the customer did not ask for further help, and Zendesk's LLM check after the conversation ended confirmed it was resolved. "Contained resolution": handled to completion but failed that check. "Assisted escalation": a human completed itWhen the conversation ends: 72 hours after the first email; 2 hours after the first message on messaging by default, configurable up to 72; at hangup on voiceA request for further help; a human completing the conversationNo; Zendesk's own LLM checkZendesk
HubSpot (Customer Agent)The agent replied from a content source or took an action, with no qualifying handoff in the window. A lead marked qualified, partly qualified or not qualified also counts as resolved72 hours after the visitor's last response; a lead qualification at onceOnly a handoff the visitor starts (asking for a human, a configured phrase); a manual assignment, including by workflow, does not void it. Once set, the status does not change after a live-agent message, a transfer request or negative feedbackNo; the share of visitors who said the agent helped is reported as a separate figureHubSpot, updated 25 Sep 2026
Gorgias (AI Agent)An automated interaction: a request fully handled by AI Agent (or Flows, Order Management, Article Recommendations) where the customer does not need a humanWithin 72 hoursA human reply within 72 hours turns the billing into a ticket only; a handover bills the ticket fee onlyNoGorgias
AdaAn automated resolution: a conversation that is relevant, accurate, safe and contained (no transfer to a human), assessed after it endsWhen the conversation ends: on End Chat or hang-up, when a human ends an escalated one, or after 24 hours idle on web chat and social, 72 hours on emailA transfer to a human, marked Not Resolved at onceNo; reviewers can give feedback on a label in the dashboard, which does not change itAda docs, Ada, 17 Jun 2026
Help ScoutA single AI chat session resolved without human help: the AI gave a full answer and the customer did not ask for moreNo window statedA request for more helpNoHelp Scout, updated 5 Nov 2026
Freshworks (Freddy AI Agent)A session, the billed unit: a unique interaction between a customer and the AI Agent. No resolution is definedChat: interactions within 24 hours of the session's start are one session. Email: one 72-hour window from the first emailNot statedNot statedFreshworks
SierraAn outcome with criteria agreed in each contract, such as a resolved support conversation, a saved cancellation or an upsellNot publishedUnresolved conversations and escalations are generally not chargedNot statedSierra
DecagonA fully resolved conversation, not defined further. The page says outcomes such as a customer who stops responding can be unclear, and recommends per-conversation billing to avoid that disputeNot statedEscalations are not charged under resolution billingNot statedDecagon, 10 Dec 2024
GladlyIts glossary defines the autonomous resolution rate in general (conversations closed by AI without escalation, over conversations AI takes on) and says there is no standard industry definition. It does not say how Gladly countsNot statedEscalation, in the general definitionNot statedGladly

Salesforce, Kustomer, Forethought and Crescendo define no resolution on the pages read; their billing is below.

Billing#

Read on 8 November 2026. Prices change; the linked page is the reference.

VendorBilling unitPublished list priceSource
Intercom (Fin)Per outcome, once per conversation; confirmed and assumed alike. A Procedure that ends in a handoff is its own billable outcome. Qualifications are billed separately. Fin on another help desk has a monthly minimum of 50 outcomes$0.99 per outcome; $9.99 per qualificationFin pricing
ZendeskPer automated resolution in Zendesk's "Verified resolution" tier, beyond an allowance included per agent per month by plan; contained resolutions and assisted escalations are not billed$1.50 each when 100 or more are bought ahead; $2.00 pay as you goZendesk pricing, tiers
Help ScoutPer AI resolution, once per session, billed monthly in arrears; no charge when the customer asks for more help$0.75 per resolutionHelp Scout
Gorgias (AI Agent)Per automated interaction, on top of the ticket fee; a handover bills the ticket fee only. Each plan includes an allowanceOn the pricing page, by planAutomate pricing, Gorgias pricing
HubSpot (Customer Agent)HubSpot Credits$0.010 per credit; the pages read do not say how many credits a resolved conversation usesHubSpot pricing
Freshworks (Freddy AI Agent)Per session$49 per 100 additional sessions on Growth, Pro and Enterprise; 500 free sessions once per account; packs expire with the payment cycleFreshworks
Salesforce (Agentforce)Per action (Flex Credits) or per conversation for customer-facing agents; no resolution is billed, and "conversation" is not defined on the page$500 per 100,000 Flex Credits, an action being 20 credits ($0.10); $2 per conversation; user licenses on topSalesforce
SierraPer outcome, criteria agreed in each contract; routing or greeter interactions may be billed by conversation countNot publishedSierra
DecagonPer incoming conversation, or a higher rate per fully resolved conversation; never per seatNot publishedDecagon, 10 Dec 2024
ForethoughtA platform fee plus an outcome-based cost, by quoteNot publishedForethought
AdaNo billing unit on the pages readNot publishedAda pricing
KustomerNo AI billing unit on the pages readNot publishedKustomer
GladlyNo billing unit on the pages readNot publishedGladly pricing
CrescendoNo billing unit on the pages readNot publishedCrescendo

Where the definitions agree#

  • An escalation to a person stops the outcome from counting, though each vendor draws the line at a different event.
  • The unit is the conversation, charged once however many questions it holds (Intercom, Zendesk, Help Scout; Freshworks counts sessions the same way).
  • An answer is required: a reply to a greeting alone does not count at Intercom, and HubSpot needs a reply from a content source or an action.
  • Every vendor that states a window counts silence after the answer toward success; Zendesk and Ada add their own model's check.

Where they differ#

  • Window. 72 hours at HubSpot and Gorgias and for Zendesk email; 2 hours by default, up to 72, for Zendesk messaging; idle timers of 24 hours on chat and 72 on email at Ada; none stated at Intercom, Help Scout, Sierra and Decagon.
  • Handoff. Zendesk files a conversation a human completed as an assisted escalation. HubSpot ignores manual assignment and live-agent messages after the status is set. Intercom can still count a conversation a teammate joined after Fin answered.
  • Later contact. Intercom deducts a resolution the customer returns to. HubSpot freezes the status once set. Gorgias turns the billing into a ticket only if a human replies within 72 hours. The Zendesk and Ada pages read do not address a customer who comes back after the conversation ended.
  • Confirmation. Intercom names a confirmed tier and bills it like an assumed one. Zendesk and Ada use their own model's assessment. None of the definitions read requires an explicit answer from the customer that the issue was resolved.
  • What else counts. HubSpot counts a lead marked qualified, partly qualified or not qualified as a resolution; Intercom bills qualifications as a separate outcome.

Against Attify's standard#

The Attify Audited Resolution Standard tests each vendor's own resolved flag exactly as set, then asks for no repeat contact within 7 days and no handoff of any kind, with a judge confirming a sample. Every window stated above is shorter than 7 days, and no vendor documents a handoff rule that strict. That is a reading of definitions and says nothing about any vendor's results; the check-by-check comparison is in how AI support agents define and bill a resolution.

Not known#

  • How long Intercom waits before counting an assumed resolution. Its article states no window; the figure in circulation comes from third-party writing only.
  • How many HubSpot Credits a resolved conversation uses. HubSpot's pages read do not say.
  • Gorgias's current price per automated interaction. The pricing page read showed conflicting plan prices, so none is given here.
  • How Salesforce defines a billed "conversation", and where the Agentforce session outcome is reported.
  • How Zendesk and Ada treat a customer who comes back after the conversation ended.
  • Prices and resolution windows for Ada, Sierra, Decagon, Kustomer, Forethought, Gladly and Crescendo. Third-party figures exist and are not used.
  • Dates for the Intercom, Zendesk, Salesforce, Freshworks, Ada, Gladly and Crescendo pricing pages, which show none.
  • What vendors' contracts say. Sierra and Decagon both say outcome criteria are agreed per contract, and this research read public pages only.

Vendors#

A vendor described here can send corrections with a link to its own documentation under the right of reply. Attify updates the page and the date it was read.

Questions

What counts as a Fin resolution, and does it count a conversation where the customer just stops replying?

Intercom counts two kinds: confirmed, when the customer replies that the answer helped, and assumed, when the customer leaves after Fin's last answer without asking for more help. Both are billed alike, so a customer who stops replying after an answer can be counted.

A human agent finished the conversation after Fin replied. Does Fin still count it as resolved?

It can. Intercom's article says a teammate joining after Fin answered can still leave the conversation resolved; a customer asking for a human is what stops it from being billed.

How does Zendesk decide a conversation was an automated resolution I get billed for?

Since 18 May 2026, Zendesk bills its "Verified resolution" tier: the AI answered, the customer did not ask for further help, and Zendesk's own LLM check after the conversation ended confirmed the request was resolved. Conversations that fail the check, or that a human completed, are not billed.

If Fin answers and the customer goes quiet for 24 hours, am I billed for a resolution?

Intercom's own article gives no waiting period for an assumed resolution; the 24-hour figure appears only in third-party writing. What the article does say is that an assumed resolution is billed the same as a confirmed one.

What window should I use to count a customer coming back as a failed AI resolution, 3 days or 7?

The vendors that state a window use 72 hours or less, and some state none. Attify's standard uses 7 days.

Sources

  1. Intercom. Fin AI Agent outcomes. Updated 23 Sept 2026. Read 8 Nov 2026.
  2. Intercom. Fin pricing. Read 8 Nov 2026.
  3. Zendesk. About automated resolution tiers. Read 8 Nov 2026.
  4. Zendesk. Zendesk pricing. Read 8 Nov 2026.
  5. Salesforce. Agentforce pricing. Read 8 Nov 2026.
  6. HubSpot. Analyze your customer agent's performance. Updated 25 Sept 2026. Read 8 Nov 2026.
  7. HubSpot. Customer Agent pricing. Read 8 Nov 2026.
  8. Gorgias. Automate pricing. Read 8 Nov 2026.
  9. Gorgias. Gorgias pricing. Read 8 Nov 2026.
  10. Freshworks. Freshdesk Omni pricing. Read 8 Nov 2026.
  11. Ada. Understand and improve your AI Agent's automated resolution rate. Read 8 Nov 2026.
  12. Ada. What is automated resolution in AI customer service. Published 17 Jun 2026. Read 8 Nov 2026.
  13. Ada. Ada pricing. Read 12 Nov 2026.
  14. Sierra. Outcome-based pricing for AI agents. Read 8 Nov 2026.
  15. Decagon. Pricing AI agents. Published 10 Dec 2024. Read 8 Nov 2026.
  16. Kustomer. Kustomer pricing. Read 8 Nov 2026.
  17. Forethought. Forethought pricing. Read 8 Nov 2026.
  18. Help Scout. AI Resolutions Pricing. Updated 5 Nov 2026. Read 8 Nov 2026.
  19. Gladly. What is autonomous resolution rate?. Read 8 Nov 2026.
  20. Gladly. Gladly pricing. Read 8 Nov 2026.
  21. Crescendo. Crescendo pricing. Read 8 Nov 2026.