Definitions and measurement
Reopened conversations: are you billed twice?
Every reopen rule published by the eight vendors compared here covers a customer who comes back to the same conversation. None covers the customer who comes back by email, by phone or in a fresh chat about the same problem.
The short version: as read on eight vendors' own pages on 11 November 2026, only two of them, Intercom's Fin and Featurebase's Fibi, publish a rule that takes the charge off when a customer reopens, and only when the customer reopens the same conversation. Both bill a conversation at most once and take a counted resolution off the bill if the customer "later returns to the same conversation seeking further assistance (even across billing periods)". HubSpot publishes no deduction: an email reply more than 72 hours after the customer's last message reopens the conversation, and another resolution uses more credits. Gorgias turns an email reply that arrives more than 10 days after the last message, or a chat more than 3 days after, into a new ticket, which "may be billable if it receives a reply from your helpdesk" (the ticket fee), with an automation fee only if it is resolved without a person, by the AI Agent or another automation such as Flows. Zendesk, Help Scout and Salesforce do not say, and Zendesk's own explainer describes a reopen condition that its billing page does not contain. And none of the eight says a charge comes off when the customer comes back about the same problem in a new conversation, which is the case Fin's own buyer's guide uses to show that the first conversation "was not truly resolved".
That gap matters because the same-conversation rule is the generous part. Intercom's rule has also improved. An Internet Archive capture of its billing article from 2 December 2023 said a customer would be charged "for one resolution per conversation during a billing period". Since at least 6 January 2026 the article has said once per conversation, with the deduction applying even across billing periods. Featurebase's billing page uses the same sentences. Neither sets a time limit on the deduction.
What eight vendors do when a customer comes back (November 2026)
Each cell is from the vendor's own billing or help pages, or for Salesforce its launch announcement, read in a browser on 11 November 2026. "Not stated" means the pages we read do not say. Prices for each billed unit are in the AI support billing index.
| Vendor | Back in the same conversation | Back in a new conversation, same problem | Windows stated |
|---|---|---|---|
| FinIntercom | The resolution is deducted, even in a later billing period. A conversation is charged at most once | Not covered: the deduction is for the same conversation | None on the deduction |
| FibiFeaturebase | The resolution is deducted, even in a later billing period. Billed once per conversation, "even if the conversation is reopened" | Not covered: the deduction is for the same conversation | None on the deduction |
| Customer agentHubSpot | Nothing is billed until 72 hours after the customer's last message. After that, agent messages, transfers and negative feedback do not change the status. An email reply after 72 hours reopens it, and another resolution uses more credits | Not stated | 72 hours from the customer's last message |
| AI AgentGorgias | Not automated if a person is needed within 72 hours; after that, not stated. A reply after 10 days by email, or 3 days by chat or SMS, starts a new ticket: a ticket fee if your helpdesk replies, an automation fee only if automation resolves it without a person | A ticket of its own. Merged tickets are still charged for what each contained | 72 hours (a person needed); 10 days email, 3 days chat or SMS (new ticket) |
| AI agentsZendesk | Not stated. Billed only if an LLM check of the transcript confirms the request was resolved when the conversation ends | Not stated | Conversation end: 72 hours after the first email, 2 hours by default on messaging. No reopen window |
| ScoutHelp Scout | Not stated. Charged once per session | Not stated | Not stated |
| Help AgentSalesforce | Not stated. No charge if the customer asks for a human, gives negative feedback or "walks away unhappy" (launch announcement) | Not stated | Not stated |
| Freddy AI AgentFreshdesk, bills sessions | No extra charge inside the session: 24 hours from the start of a chat, 72 hours from the customer's first email | Not stated | 24 hours (chat), 72 hours (email) |
Fin and Featurebase win the first column. A deduction with no time limit that reaches into a later invoice is the most generous same-conversation rule on the list, and both put it in writing. Intercom's pricing page says it in one line: "If the conversation is later reopened, the outcome is refunded." Its help article words the same rule as a resolution being deducted.
HubSpot publishes no deduction, and says so plainly. Its help article on the customer agent says that "Subsequent actions, such as messages from a live agent, a transfer request, or negative feedback, will not change the resolution status", and that after an email reply more than 72 hours later "If the customer agent delivers another resolution, additional credits are consumed." A buyer can price that. HubSpot frames it as happening "if separate issues are resolved over time", which is often true; the page does not say how it treats a customer whose first problem came back. It also earns credit: a reply in the same thread within 72 hours of the customer's last message costs nothing extra, because nothing has been billed yet.
Gorgias is the only vendor here that publishes, channel by channel, when a reply stops being part of the old ticket. After 10 days on email and 3 days on chat or SMS, a reply becomes a new ticket. Inside 72 hours, a person stepping in means the interaction was not automated. Between the two, its page is silent on whether an automation fee already counted is reversed. The new ticket's own charges follow the usual rules: "The new ticket may be billable if it receives a reply from your helpdesk", which is the ticket fee, and an automation fee applies only if the AI Agent or another automation feature resolves it without a person.
Freshdesk never claims a resolution, so a return inside the window simply costs nothing more. It bills a session: everything within 24 hours of the start of a chat is one session, and on email "All AI-generated responses" within 72 hours of the customer's first email count as one. It is the plainest unit on the list, and it makes no claim about whether the problem was solved.
Zendesk deserves credit first: silence alone is not billed. A conversation where the customer simply stopped replying is a "Contained resolution" and does not count against the allowance unless an LLM check of the transcript, run when the conversation ends, confirms the request was resolved.
But Zendesk's own explainer describes a reopen rule its billing page does not contain. "Understanding outcome-based pricing" gives Zendesk's model as its example, and then says a resolution "is often defined by a 72-hour quiet period, meaning the ticket stays closed, and the customer does not reopen the conversation". Its billing page, "About automated resolution tiers" (edited 30 September 2026), times the end of an email conversation from the first email and does not mention a reopen. Google's AI Mode, asked on 11 November 2026 whether a reopen is billed again, told us that a Zendesk customer who reopens inside 72 hours is not charged again. We could not find that in Zendesk's billing terms. If it matters to you, ask for it in the contract.
The return that no reopen rule covers
A customer reads the AI's answer in a chat, leaves, and emails support two days later because it did not work. At Fin the chat was counted as an assumed resolution 24 hours after Fin's last answer, and the email is a different conversation, so nothing is deducted. The same is true of every vendor in the table that states a rule, because every stated rule is written about the same conversation, ticket or session.
Fin's own guide, "Resolution Rate vs. Deflection Rate" on fin.ai, describes this case and treats it as decisive: if a customer "contacts support again about the same issue within 24 hours, that first conversation was not truly resolved, regardless of how the vendor's AI classified it." It tells buyers to "Always ask for reopen data alongside resolution data." Our point is narrow. The guide calls this the "reopen rate", and its test is the same customer contacting support again about the same issue. Fin's billing rule uses "reopened" for a return to the same conversation. A conversation can fail the first test and still be charged under the second.
How often that happens is not published anywhere we could find. A thread on Intercom's community forum asks exactly this. Its author says they are exploring building something in this space. The most useful reply is from a customer posting as Justin, whose team handles about 2,000 conversations a month. He says his audits find "only a handful" counted as resolved while the customer was still struggling, and that in most of those the customer either did not follow Fin's directions or "abandoned the conversation and came back in a separate channel". He adds that review almost always shows Fin gave a good answer. That is one team's account. His team puts these cases down mostly to the customer and treats the charge as the cost of doing business.
- A customer whose conversation was already counted writes again about the same problem
- Did they write in a new conversation: a new chat, an email after a chat, a call? Yes No credit stated
- Is the vendor Fin or Featurebase? Yes Charge deducted
- Is it HubSpot, with an email reply more than 72 hours after the customer's last message? Yes Reopened
- Is it Gorgias, more than 10 days later by email or 3 by chat or SMS? Yes New ticket
- Otherwise: Zendesk, Help Scout and Salesforce do not say; Freshdesk adds no charge inside its session window
How to measure the returns your vendor's rule does not see
This needs data from every channel the customer can use, including any outside your AI vendor's product, and none of the billing pages above describes a report that matches billed resolutions to later contacts. A shorter check of the billed list itself is in our piece on resolution, deflection and containment, and what these returns do to the price you really pay per resolution is in our piece on calculating cost per resolution.
- Get one month of billed resolutions. Each with the conversation, the customer's email or ID, and the date it was counted. If the vendor's reports do not show it, ask for it.
- Export every contact from every channel for the same customers. Email, chat, phone and social, from the first billed date to seven days after the last.
- Match by customer. Keep each billed resolution that the same customer followed with another contact within seven days, and note whether it was within 24 or 48 hours, the windows Fin's guide asks about.
- Read each pair. Mark it same problem, different problem or unclear, by your judgement. Report unclear separately rather than folding it in.
- Split the same-problem returns. Those in the same conversation should already be off the bill at Fin and Featurebase, so check the invoice. Those in a new conversation are not credited under any of the eight vendors' rules, so if the first was billed, the charge stands.
- Take the count to the vendor. Ask in writing what the contract says about a return in a new conversation, and whether it will credit the ones you found.
We set out how long each vendor waits before silence counts as a resolution, and which vendors bill it at all, in our piece on assumed resolutions.
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 11 November 2026), says: "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." The rule is written about the issue rather than the conversation. Whether it is the same issue is a judgement, and the page says it is recorded with the reason so that you can disagree with it. It can only credit a return Varley knows about, and the page does not say how a return on a channel Varley does not handle would be found. It has a limit the Fin and Featurebase rules do not: after 30 days the credit no longer applies, so a customer who returns to the same Fin conversation in month three is better covered at Fin.
Varley does not publish a resolution rate yet, and there is no self-serve export: the list of billed resolutions is sent on request within two working days, which is what step one of the method above needs. The early-access price for direct use is $0.50 per resolution, as of 28 September 2026 on the pricing page (read 11 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
If a customer reopens a conversation, am I billed again?
Ask first where they came back. A return to the same thread is where vendors' published rules apply, and the generous ones remove the earlier charge. A return in a new chat, email or call is a separate conversation, and none of the eight rules compared here credits the first charge. Several vendors publish nothing on either case, so get it in writing.
What if the customer comes back by email after chatting with the AI?
Then it is a new conversation, and none of the eight vendors compared here says the first charge comes off. The second contact is handled, and may be billed, on its own terms. The only way to see how often it happens is to match billed resolutions against every channel's contacts for the same customers.
Does Zendesk cancel the charge if a customer reopens within 72 hours?
Not according to its billing page. "About automated resolution tiers" sets the billed tier when the conversation ends, 72 hours after the first email or by default 2 hours after the first chat message, and says nothing about reopens. The reopen condition appears in Zendesk's marketing explainer, not on its billing page. Ask Zendesk to put any reopen credit in your contract.
Is a reopened conversation the same as a repeat contact?
No. A reopened conversation is the customer writing again in the thread that was already counted. A repeat contact is the customer coming back about the same problem in a new conversation, often on another channel. Vendors' published reopen rules cover the first. Fin's own buyer's guide treats the second as the real test of a resolution.
Changes to this piece
- 11 Nov 2026
- First published.
Sources
- Fin AI Agent outcomes, Intercom help centre, including its FAQ, updated 23 September 2026. Read 11 November 2026.
- Intercom pricing, Fin section. Read 11 November 2026.
- Fin pricing: Outcomes, Fin Help Center. Read 11 November 2026.
- Fin resolutions, Intercom help centre, Internet Archive capture of 2 December 2023. Read 11 November 2026.
- Fin AI Agent resolutions, Intercom help centre, Internet Archive capture of 6 January 2026. Read 11 November 2026.
- Resolution Rate vs. Deflection Rate, fin.ai, 10 March 2026. Read 11 November 2026.
- Fibi AI Agent resolutions, Featurebase help centre, including its FAQ. Read 11 November 2026.
- Understand the customer agent, HubSpot Knowledge Base, last updated 16 September 2026. Read 11 November 2026.
- How you're billed for using Gorgias, Gorgias help centre, no date shown. Read 11 November 2026.
- About automated resolution tiers, Zendesk help, edited 30 September 2026. Read 11 November 2026.
- Understanding outcome-based pricing, Zendesk, published 16 April 2026, updated 13 May 2026. Read 11 November 2026.
- AI Resolutions Pricing, Help Scout Docs. Read 11 November 2026.
- Salesforce Launches Agentforce Help Agent That Deploys in Minutes and Only Charges for Resolutions, Salesforce newsroom, 25 June 2026. Read 11 November 2026.
- Manage Freddy AI Add-ons, Freshdesk support, modified 4 August 2026. Read 11 November 2026.
- Does anyone track whether customers come back on a different channel after Fin marks a conversation resolved?, Intercom Community, thread 15290, reply by Justin. Read 11 November 2026.