Intercom Fin Pricing Explained: What Counts as an Outcome

Intercom charges $0.99 for each Fin outcome, and an outcome is a resolution (the customer asks for no further help after Fin's last answer) or a Procedure that ends in a hand-off to a person or workflow. So yes, a hand-off can be billed, but only when you configured it as part of a Procedure.

The phrase "pay only when Fin resolves it" hides the details that decide your bill: silence counts as success, a hand-off you designed is billable while an escalation Fin decides on its own is not, and you are charged once per conversation however much happens in it. The definitions below come from Intercom's own help article on Fin outcomes, and a month of illustrative conversations is run through them to show how the total builds up. Figures are list prices as of 5 November 2026; Intercom updates the definitions, so check them on the Fin pricing page before you rely on them.

Follow me on Instagram@sagnikteaches

The five outcome types and their prices

Intercom's help article on Fin outcomes lists five billable outcomes. Only one of them costs more than $0.99.

Connect on LinkedInSagnik Bhattacharya

A support-only business will see just the first two. The last three belong to Fin for Sales, which is a separate use of the product. The rule that ties them together is one outcome per conversation at most: a customer who asks four questions, or a Fin that runs two Procedures, still produces a single charge.

Subscribe on YouTube@sagnikteaches

Charges apply to Fin over chat and email when used with Intercom. Fin Voice, high-volume pricing and unusual set-ups are quoted by Intercom's sales team, so a business planning phone support should not assume the $0.99 figure.

Resolutions: confirmed, assumed and the quiet customer

A resolution is counted after Fin's last answer in two situations. A confirmed resolution is when the customer replies with something like "Ok thanks" or "That helped". An assumed resolution is when the customer exits the conversation without asking for more help. Both cost $0.99.

The assumed kind is where owners get surprised, because a customer who gave up looks the same as one who was satisfied. Intercom's help article states plainly that a customer leaving after Fin's answer without requesting further help is billed as an assumed resolution, even if they were frustrated. I could not find a fixed waiting period in the current article; it describes the customer exiting the conversation and refers to an inactivity timeout, so do not assume a particular number of hours.

Three details limit the billing:

• A resolution only counts when Fin gives an actual answer. A reply to a greeting is not an answer.
• If Fin asks a clarifying question and the customer never replies, the conversation closes after the inactivity timeout, no resolution is recorded and nothing is billed.
• If a customer comes back to the same conversation asking for more help, even in a later billing period, the earlier resolution is deducted and not charged.

One more detail if you use the chattier version of Fin: Intercom says that with Conversational Fin, Fin can follow up after a customer has been inactive for 4 minutes, and that this follow-up message is not considered an answer and does not change whether the conversation counts as resolved.

Hand-offs: the billed kind and the free kind

This is the question most small teams actually ask. Intercom separates two things that look alike from the inbox.

A Procedure handoff happens when Fin runs a Procedure you set up, such as collecting an order number and booking details, and the Procedure is configured to end by passing the conversation to a team, a teammate or a workflow. That is a billable outcome at $0.99, because Fin completed the work you gave it.

An escalation happens when Fin hands off on its own default behaviour or your workspace-level rules, for example when a customer asks for a human or shows frustration, or when you have set rules under Train, then Escalation. Intercom says you are not billed for these. A Procedure that fails to finish because of a technical error is also an escalation and also free.

There is one exception that catches teams out. Intercom's FAQ says that if a customer asks for more help or a person, but the collect information setting is on and the customer then goes quiet without giving the details Fin asked for, the conversation is still marked as resolved and charged. If Fin routinely asks for an order number before passing a complaint on, every customer who gives up at that point can become a billed outcome. Check that setting before you assume all hand-off requests are free.

The practical consequence is that the wording of your Procedure guidance decides the bill. A Procedure that says "collect these three details, then hand to the bookings team" is billable when it completes. Fin passing a conversation over because the customer typed "can I speak to someone?" is not. If you would rather pay only for conversations the customer never needed a person for, build your hand-offs as workspace-level escalation rules rather than as the final step of a Procedure, and check how Intercom classifies them in your usage screen.

One month of conversations, run through the rules

Take an illustrative dog groomer with 400 Fin conversations in a month, shared between booking changes and price questions. Sorting them by what happened:

Two readings of that table matter. First, the groomer pays for 70 per cent of the conversations Fin touched (280 of 400), and the 60 assumed resolutions are the most doubtful: about a fifth of the paid total is for conversations where nobody said the answer helped. Second, Fin itself costs nothing in a month when it is not used. Intercom says you are not billed for Fin if you are not using it, and that you can set reminders and hard limits to cap spend.

Remember what sits outside this figure: Intercom seats and any other channel usage. This sum covers Fin only; the three-seat plan cost comes on top, unless you use Fin with another helpdesk.

Scenarios from Intercom's own table, with a small-business twist

Intercom publishes a list of scenarios and whether each is billed. Here they are, restated with the kind of conversation each would be in a small business.

• Billed: a shop recommendation. A customer asks what running shoes are available under $100, Fin recommends products from a synced catalogue, and the customer browses without complaint. That is a resolution. Clicking product cards, adding to a cart and checking out afterwards carry no extra charge: still one outcome.
• Billed: a teammate closes it. Fin answers from your content, then a staff member assigns themselves or closes the conversation, and Fin had not escalated. Intercom treats it as resolved. This is why staff who jump into a conversation Fin has already answered can create a charge nobody expected.
• Not billed: Fin has no answer. Fin says it cannot answer from your content and a teammate replies. That is not a resolution.
• Not billed: an outbound message nobody replies to. If Fin sends a proactive message and the customer opens it but does not respond, the conversation is Pending, not an outcome.
• Not billed: spam. Fin routes it to the Spam view.
• Billed once: a long conversation. A driving school's customer asks about lesson prices, then test dates, then cancellation rules, and Fin answers all three. One resolution, one $0.99 charge.

The teammate scenario deserves a second look. If your staff habitually step into conversations, ask Intercom's help or your own usage report which of those conversations were billed, because the rule turns on whether the customer had asked for extra help or for a person.

Sales outcomes are priced differently

If you use Fin to talk to prospects, the arithmetic changes because a qualification costs $9.99, ten times a resolution. A qualification is counted when Fin matches a prospect to the criteria you defined and routes them, for example to book a call with your sales team or start a trial. The same routing marked as Self-serve costs $0.99 instead, because it does not book meetings or trigger sales follow-up. Existing outcomes do not switch automatically; they stay at the full rate until you change them.

An illustrative photography studio might use Fin for pre-sale questions: 60 enquiries a month, 20 of which Fin qualifies and books into a call, 15 disqualified (too far out of scope) and 10 sent to a self-serve booking page. The bill is 20 x $9.99 + 15 x $0.99 + 10 x $0.99 = $199.80 + $14.85 + $9.90 = $224.55. Move those 10 self-serve routings to the qualified outcome by mistake and the line grows by $90. The point is to read each routing outcome's type in the playbook before you switch Fin for Sales on. The tutorial on Fin for Sales covers the set-up.

Using Fin with another helpdesk

Fin can run on top of a helpdesk other than Intercom. The Fin pricing page lists Salesforce, HubSpot, Freshworks, Dixa, Front, Zoho, Sprinklr and Gorgias, and names Zendesk elsewhere on the same page. The terms are $0.99 per outcome, no seat costs and no setup or integration fees, with a floor: the Fin pricing page states a $49 monthly minimum, which includes 50 outcomes, while Intercom's main pricing page simply says a minimum monthly commitment applies, with 50 outcomes as the example. In practice a business with 20 outcomes in a month still pays $49, and one with 80 pays $49 plus 30 x $0.99 = $78.70, assuming outcomes above the included 50 are billed at the normal rate. Confirm both points in writing before you sign, because the minimum is the figure that sets your lowest bill.

Why the bill can surprise you, and what to set up

Three gaps between expectation and invoice come up repeatedly, and each has a fix inside Intercom.

1. The silent customer. Assumed resolutions include people who left unhappy. Configure escalation guidance so Fin hands off when it detects frustration. Intercom itself suggests this, and escalations are not billed.
2. Procedures that end in hand-offs. If the aim is to keep costs predictable, count your expected Procedure handoffs separately from resolutions when you budget, since both are $0.99 but only one reduces your team's workload.
3. Uncapped trials turning into uncapped bills. The 14-day trial has unlimited Fin outcomes, but once you add a card, usage is billed. Set a usage reminder and a hard limit before the first live week.

To check what you were charged for, Intercom's help article tells you where to look. In Fin AI Agent, open the relevant area (Service, Sales or Ecommerce), then the Analyze tab, then Performance, and the performance funnel lets you open the conversations behind each outcome. Make that a monthly habit: sample ten billed conversations and ask whether you would have paid $0.99 for that result.

A Procedure written so the billing is predictable

Because a Procedure that completes is billable while a default escalation is not, it helps to write the Procedure's end state deliberately. Below is a filled-in example for an illustrative driving school's rescheduling request. The wording is a sketch to adapt, not Intercom's required syntax.

Procedure: Reschedule a lesson
1. Ask for the learner's name and the lesson date they want to move.
2. Ask for two alternative dates and times.
3. Check the lesson is more than 24 hours away (read from the booking note).
4. If it is less than 24 hours away: do NOT complete the Procedure.
   Explain the late-change fee from the help article and let the
   customer choose to speak to the office (this is an escalation).
5. If it is more than 24 hours away: summarise the request and hand
   over to the Scheduling team (this is the Procedure handoff).

Read what that does to the bill. Steps 1 to 3 and 5 are the billable path, $0.99 when the Procedure completes. Step 4 deliberately ends in an escalation, so the late-change conversations that need a person cost nothing. Without step 4 a short-notice request could run through to the hand-off and be billed even though the office has to do all the work. The design question is always the same: at what point has Fin really done something worth $0.99?

Escalation rules that protect you from paying for unhappy customers

Since a quiet, unhappy customer can be billed as an assumed resolution, the cheapest protection is a rule that sends frustration to a person. Intercom says Fin's default behaviour already escalates when a customer asks for a human or shows frustration, and you can add workspace-level guidance. A sketch of wording for an illustrative café that takes catering orders:

Escalate to the catering team, without trying again, when the customer:
- mentions an allergy or dietary requirement for an event,
- disputes a charge or asks for a refund,
- has asked the same question twice in this conversation,
- writes in capital letters or uses words such as "unacceptable".

Each of those is a conversation you do not want billed as a success, and the first one is a safety matter that should never be left to an automated answer. The rule costs nothing to add and turns four likely assumed resolutions a week into four free escalations that a person handles properly. Over a month at $0.99 each that is a saving of a few dollars, but the real gain is that your resolution count stops including conversations that went badly.

A realistic month-end check, from invoice to sample

Fin is a flat $0.99 per outcome for support conversations, so the check is simple arithmetic. Suppose the month-end usage screen shows 312 outcomes. Multiply by 0.99 to get $308.88, and compare that with the figure on the invoice. Then sort a sample.

• Open the performance funnel and pull ten conversations at random from the billed list.
• For each, write one word: "fixed", "unclear" or "wrong". A conversation where the customer gave no sign either way is "unclear".
• If three or more are "unclear" or "wrong", look at those answers and at the help article each one drew on, and fix the article rather than switching Fin off.

An illustrative result: seven fixed, two unclear and one wrong. That is a 70 per cent sample accuracy on paid outcomes. The one wrong answer points to a help article that still quotes last year's opening hours, which is a five-minute correction. Treat the exercise as quality control for the knowledge base. Your help articles decide how many conversations resolve at all, and an article Fin cannot use is a conversation that ends in a free escalation or a paid failure.

Three short conversations, labelled

Sometimes the rules read more clearly as transcripts. These are invented for illustration, with the billing result written underneath.

A. Customer: What time do you open on Saturdays?
   Fin: We open at 9am on Saturdays.
   Customer: Great, thanks.
   Result: confirmed resolution, billed $0.99.

B. Customer: How much is a bath and trim?
   Fin: That depends on size. Is your dog small, medium or large?
   Customer: (no reply)
   Result: Fin's last message was a clarifying question, so no
   resolution is recorded and nothing is billed.

C. Customer: How much is a full groom?
   Fin: A full groom starts at $45 for small dogs.
   Customer: That's too expensive, let me talk to someone.
   Result: the customer asked for a person, so this is not a resolution.
   Not billed.

Transcript B is the clean version of a quiet customer. If Fin had instead offered to pass a refund request to the team and asked for a booking date, with the collect information setting on, the same silence could be billed as a resolution, as described in the hand-off section. The difference between A and C is a single sentence from the customer. That is why reading real transcripts for a fortnight tells you more about your likely bill than any calculator.

How to budget from a sample week

You can estimate a month before committing, using a week of real conversations.

1. Export or list a week of customer questions your team handles by chat or email.
2. Mark each as something Fin could answer from your help articles, something needing a Procedure with a hand-off, or something needing a person from the start.
3. Assume the first group becomes resolutions and the second Procedure handoffs; the third should not be billed if your escalation rules are set correctly.
4. Multiply the first two groups by $0.99 and scale the week to a month.

For an illustrative driving school with 90 weekly questions, say 50 are price and timetable questions, 15 are rescheduling Procedures and 25 need a person. The billable count is 65 a week, about 280 a month, or around $277. That matches the groomer's total above, which shows how little the business type matters compared with the mix of questions.

If you would like to test your own numbers without paying, the 14-day trial plan shows how to run Fin on real questions, and the Chatbase comparison shows what a credit-based alternative looks like against this per-outcome model.

Questions about Fin outcomes and billing

Is Fin billed twice if a customer asks two questions?

No. Intercom charges at most one outcome per conversation, however many questions the customer asks or Procedures Fin runs. If Fin answers three questions in one conversation and the customer leaves satisfied, that is a single $0.99 resolution.

Can I stop Fin charging me while I test?

Yes. Remove Fin from live Workflows or pause it in the Simple deploy section and it stops replying, so no outcomes occur. You can also set usage reminders and hard limits. The 14-day free trial includes unlimited Fin outcomes with no card needed.

Does a customer who comes back later cancel the charge?

Intercom's help article says that if a conversation was counted as resolved but the customer later returns to the same conversation seeking more help, even across billing periods, that resolution is deducted and not charged. A new conversation is billed on its own.

What does a sales qualification cost?

Qualifications in Fin for Sales are $9.99 each, while disqualifications and routing to a self-serve outcome are $0.99. Existing outcomes are not repriced automatically, so check how each routing outcome is marked before turning Fin for Sales on.

Further reads

• Intercom vs Fin: Do You Need the Inbox, the AI Agent or Both? — Decide whether you need the inbox, Fin or both.
• ChatGPT Chatbot for Sales: Qualify Website Leads Without Losing Them — Four qualifying questions, a handover rule, a lead log and a cost comparison of ready-made bots against a build-your-own.
• Intercom Fin Alternatives: Options Without Per-Outcome Pricing — Which Fin alternatives avoid per-outcome pricing, which quietly do not, and what 300 AI conversations cost on each.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Intercom's pricing page, Fin pricing page and the help article on Fin AI Agent outcomes (updated 23 September 2026), all read on 5 November 2026. Rates can change, so confirm them on the live pages.