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.
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.
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.