Why does this guide refuse to print a price table?
Key Takeaways
For busy support leads: the number that decides whether Intercom is expensive for you is not the seat price. It is the price per AI resolution multiplied by how many conversations you expect to receive eighteen months from now, plus the contract language defining what counts as a resolution. Two companies paying identical list prices can end up with invoices that differ by a factor of five, purely because one of them has a free tier and the other sells only to paying accounts.
- 1Three layers, not three plans. Seats, AI usage and add-ons bill separately, and at high volume the plan tier you agonised over barely moves the total.
- 2The resolution definition is the contract. Ask in writing what counts, what happens on a reopen, and whether an unhelpful answer is still billable.
- 3Per-seat scales with headcount, per-usage scales with signups. If you run a free tier, usage pricing turns your worst-monetising users into a direct cost of goods.
- 4Compute your own break-even. Automation saves money only while a resolution costs less than the human minutes it replaced.
- 5Negotiate the pool, not the list price. Committed bundles, rollover and a capped overage rate move your bill far more than a seat discount.
Because price tables are what make most pricing articles actively harmful. Vendors change list prices, rename plans, re-tier features and adjust usage rates on their own schedule. A table published in March is quietly wrong by June while still ranking in search, and readers walk into a sales call anchored to a number that no longer exists.
There is a second reason, and it matters more. The list price is not what you pay. What you pay is a function of your conversation volume, your free-to-paid ratio, your seat count, how aggressively you switch on outbound messaging, and whatever procurement manages to negotiate. Two teams on the identical plan routinely pay amounts that are not in the same neighbourhood. A table cannot tell you that. A formula can.
So open Intercom's pricing page in another tab. Write down the seat price for the tier you actually need and the price per AI resolution. Keep those two numbers beside you. Everything below is built to accept your inputs rather than mine.
What are the three layers of an Intercom bill?
Layer one is the platform fee, charged per seat per month and tiered by feature set. Everyone with a login counts. That includes managers, the engineer who answers three tickets a week, and the analyst who only reads dashboards.
Layer two is AI usage. Intercom's AI agent is billed per resolved conversation rather than being bundled into the seat price. This is the layer that surprises people, because it is the only line on the invoice that grows when the product works well. One dated data point rather than a table: on 2 August 2026 Intercom's pricing page listed Fin at $0.99 per outcome with no additional seat costs. Check it yourself before you model anything, because that is exactly the number most likely to have moved by the time you read this.
Layer three is metered add-ons: outbound messaging beyond your plan's included audience, WhatsApp and SMS pass-through, voice minutes, product tours. Individually small. Collectively, this is the layer that makes the real invoice land above the spreadsheet estimate.
The structural point survives every repricing, which is why it is worth internalising instead of memorising numbers.
| Layer | Billed on | Grows with | Forecastable? |
|---|---|---|---|
| Platform | Seats per month | Your headcount | Yes, you control hiring |
| AI agent | Resolved conversations | Your customer count | Poorly, and worst in bad months |
| Add-ons | Messages, minutes, audience | Your marketing ambition | Only if someone owns the switches |
What actually counts as a resolution?
This is the single most valuable question in the whole evaluation, and almost nobody asks it before signing. "Resolution" is a defined term with money attached, and the definition varies by vendor and by contract revision.
Get written answers to all five of these before the commercial conversation goes any further:
- If a customer asks a follow-up an hour later in the same thread, is that one resolution or two?
- If the AI answers, the customer replies "that did not help", and a human takes over, is the AI resolution still billed?
- Does a conversation the AI started, proactively or via outbound, count the same as one the customer started?
- Who marks a conversation resolved: the model's own confidence score, an explicit customer confirmation, or a timeout with no reply?
- Is there a cap, and what happens in the month a failed deploy or a shipping delay triples your contact volume?
Two of those five already have published answers, and both are worth reading before the call. On question four, Intercom's own billing documentation defines an "Assumed Resolution": "If a customer disengages from the conversation for 24 hours after Fin's last answer, it is considered an assumed resolution". Silence is scored as success and billed as one. On question two, the same page states that "if a customer asks for a human or shows frustration, Fin escalates based on its default logic. You are not billed for these escalations", and says the same of failed procedures and abandoned conversations. Both are the vendor describing its own commercial policy rather than an independently audited fact, so get the version in your contract in writing.
That published definition is also why the marketed resolution rate needs reading carefully. Intercom advertises Fin as "averaging 76% across 12,000+ customers, with many seeing over 85%", with no methodology on the page and with the 24-hour silence rule sitting underneath it. Do not put that figure into your automation-share assumption. Measure your own.
The cap question deserves more weight than it usually gets. Usage pricing has no natural ceiling. An outage, a viral post or a botched migration can triple contacts inside a week, and the invoice follows without asking permission.
How do you calculate your real monthly cost?
Use one formula and your own quoted numbers:
Monthly cost = (seats x seat price) + (expected conversations x automation share x price per resolution) + add-ons
Here is a worked example with illustrative inputs. Every number is a placeholder you should replace before drawing conclusions.
A team of six. Three thousand inbound conversations a month. Assume the AI handles half of them, a round number chosen for the arithmetic rather than a claim about what any product achieves, giving 1,500 billable resolutions. Call the quoted seat price S and the quoted resolution price R. The bill is (6 x S) + (1,500 x R) + add-ons.
Now put illustrative values in, purely to see the shape: at S = 85 and R = 1, seats cost 510 and AI costs 1,500. The AI line is roughly three times the seat line, and the plan tier you spent the sales call debating accounts for around a quarter of the invoice. Those inputs are made up for demonstration and are not quoted prices. Substitute your own and the ratio usually holds anyway, because seat counts grow slowly while conversation counts grow with your customer base.
One more step that almost nobody takes. The forecast that matters is not this month, it is month eighteen. Pull your conversation volume from twelve months ago, compare it to today, and apply that growth rate forward twice. That is the number to put in front of finance, and it is the number a two-year commitment is actually pricing.
At what point does per-resolution AI stop saving money?
Automation is worth paying for only while a resolution costs less than the human time it replaced. That break-even is computable, and computing it is a fairer way to evaluate usage pricing than complaining about it.
Human cost per contact = average handle time x fully loaded hourly cost.
The table below uses illustrative handle times and loaded costs. Find your row, and you have the ceiling above which a per-resolution price stops being a bargain.
| Avg handle time (illustrative) | At $28/hr loaded | At $36/hr loaded | At $50/hr loaded |
|---|---|---|---|
| 4 minutes | $1.87 | $2.40 | $3.33 |
| 8 minutes | $3.73 | $4.80 | $6.67 |
| 15 minutes | $7.00 | $9.00 | $12.50 |
The honest conclusion is one that flat-rate vendors, us included, tend to skip: for simple contacts, per-resolution pricing is usually still cheaper per unit than a human, and the customer gets an answer in seconds rather than four hours. The real objection is not unit value. It is that the line is unbounded, unforecastable, and charges you most in exactly the months you can least afford it.
Why does usage pricing punish the wrong business model?
Per-seat pricing couples your bill to headcount, which you control. Per-resolution pricing couples your bill to contact volume, which you do not.
If you sell to a few hundred paying business accounts, usage pricing is fine and may well be cheaper than anything flat. If you run a free tier, a marketplace, a consumer app, or anything where non-paying users can open a conversation, usage pricing quietly converts your least profitable users into a metered expense. Free-tier support stops being a fixed cost and starts being cost of goods sold.
It is also worth knowing that the category has not settled on one meter. As fetched on 2 August 2026, Zendesk's own explainer states it "charges $1.50 per automated resolution", Gorgias quotes "$0.90 on most plans" per resolved conversation, Help Scout lists $0.75 per resolution, Front bills its Autopilot "Starting at $0.05 /conversation" rather than per resolution, and Freshdesk sells AI capacity at "$49/100 sessions", a session being consumed whether or not anything is solved. Sierra goes furthest, saying customers "pay only when the software achieves specific, valuable outcomes" and that "if a case needs to be escalated, in most cases, there's no charge", while publishing no dollar figure at all. Compare units before you compare prices.
Watch what teams do next, because the incentive is stronger than the policy. They tune the AI to answer less. They restrict the widget to logged-in paying users. They bury the contact link. Every one of those is a rational response to the pricing model and a worse experience for customers. If that trade sounds theoretical, ask anyone who has run support under a usage contract during a growth quarter.
Which plan features are the real upgrade triggers?
Most teams do not choose a tier so much as get dragged up one by a single feature. Knowing which feature, before you buy, prevents a mid-year renegotiation from a position of no leverage.
| Trigger | Why it appears | When it usually bites |
|---|---|---|
| SLA rules and business hours | First contract with response-time commitments | Your first enterprise customer |
| CRM sync to Salesforce or HubSpot | Sales wants conversation context on the account | Once support and sales share accounts |
| Granular roles and SSO enforcement | Security questionnaire, or contractors in the inbox | First serious procurement review |
| HIPAA or equivalent compliance | Regulated data lands in a conversation | Any health, benefits or insurance customer |
| Workload and assignment controls | Manual assignment stops scaling | Somewhere past a dozen agents |
The pricing consequence is the part that stings: a tier upgrade multiplies across every seat simultaneously, not just the seats that needed the feature. Verify which tier each of these sits in on the pricing page today, because feature-to-tier mapping gets repackaged more often than headline prices change.
What is actually negotiable?
Considerably more than reps volunteer, and almost none of it is the seat list price. Ask for these by name:
- A committed resolution bundle at a lower effective unit rate, rather than pure pay-as-you-go.
- Rollover of unused resolutions into the following month or quarter.
- A capped overage rate, so a single bad month cannot run unbounded.
- A ramped commitment that steps up across the year instead of starting at your projected peak.
- Removal of auto-renewal, plus a notice period your calendar can realistically meet.
- Pilot pricing on the AI layer specifically, billed on actuals.
That last one is the highest-value ask in the list. Run the AI layer for sixty days on actuals, measure your true automation share, and only then set the commitment. Nobody can forecast their automation share before measuring it, and every volume commitment signed before that measurement is a guess you pay for monthly. If you want the same three-layer test applied to a different vendor's packaging, our Zendesk comparison walks through where their AI charges sit.
Where flat-rate pricing is the wrong answer
Flat rate is not automatically cheaper, and pretending otherwise is how vendors lose trust. Corebee charges $99 a month flat, with no per-seat and no per-resolution line. If you are two people handling a low volume of conversations, a usage-priced plan may genuinely cost you less, and you should take it.
Flat rate also buys a narrower product. Corebee does not do in-product tours, lifecycle marketing messages, phone support or HIPAA. If product messaging is central to how you activate users, Intercom's integrated approach is hard to replicate, and the bill is buying something real. Teams that switch on price alone and then rebuild tours, in-app announcements and segmentation across three other vendors frequently end up spending more in total and managing more contracts.
What flat rate actually buys is a forecast. You know your month-eighteen number today. For some finance teams that is worth a premium. For others it is worth nothing, and they should optimise unit cost instead. Our pricing page exists mainly so you can check that claim against your own volumes.
Where this breaks
Below a few hundred conversations a month, none of this arithmetic justifies an afternoon. Pick the tool your team likes using and revisit the maths when volume forces it.
If your contract is already signed with nine months left, the calculation you need is a switching-cost calculation, not a pricing one. Rebuilding workflows, retraining agents and swapping the widget has a real cost that frequently exceeds the remaining term.
If your volume is seasonal by nature, retail peaks, tax deadlines, event businesses, annual averages will mislead you badly. Model your peak month and ask what the contract does to you in it.
And if the evaluation is really about answer quality rather than price, no spreadsheet settles it. Take fifty genuine past questions, run them through every candidate, and read the answers yourself.
What should you do in the next hour?
Open the vendor pricing page and write down today's seat price for the tier you need, plus today's per-resolution price. Count everyone who will need a login, including read-only people. Pull last month's inbound conversation total and the same month a year ago.
Put those into the formula, then run it again with your projected volume two years out. Email your rep the five resolution-definition questions and insist on written answers. Finally, compute your own human break-even per contact so you know what a resolution is genuinely worth to you.
If the total comes back higher than expected, that alone is not a reason to switch. It is a reason to negotiate the usage layer, because that is where the money is. If predictable billing is the thing you actually want, you can start a free trial and measure your real automation share on your own conversations before anyone asks you to commit to a volume.