Intercom Fin is a good product, and at low support volume it is genuinely the cheapest way to deploy AI resolutions. But per-resolution pricing scales linearly with usage, and above roughly 1,500-2,000 monthly resolutions the numbers flip. This guide walks through the actual math, a capability-by-capability comparison, and a decision framework so you can pick the right option for your volume, your control needs, and your compliance posture.
Every SaaS support leader we talk to wants the same one-line answer to this question. There is no one-line answer, because the right choice depends almost entirely on your resolution volume and how much control you need. Here is the honest breakdown by volume band.
Every business is different. Do the actual math on your projected 12-month resolution volume before deciding. The table further down in this guide gives you side-by-side monthly costs at eight different volume tiers so you can pick the row that matches your business.
Intercom Fin uses a per-resolution pricing model. As of 2026, the list price is $0.99 per resolution. A resolution is defined by Intercom as a conversation where Fin answered the user's question and the user did not require a human agent to step in. If the conversation escalates to a human, it does not count as a Fin resolution and you do not pay the Fin fee for it. That definition is generous, and it is one of the reasons Fin is a strong product at low volume. You only pay when it actually worked.
Zendesk AI (branded as Zendesk Advanced AI) uses a similar per-automated-resolution model, priced closer to $1.50 per automated resolution as of 2026. Freshchat Freddy AI sits between the two. All three vendors follow the same commercial pattern.
Additional costs on top of per-resolution fees:
Volume discounts on the per-resolution price are available above certain commitment tiers, negotiated case-by-case with Intercom sales. Typical negotiated pricing lands between $0.69 and $0.85 per resolution for committed volumes above 5,000 monthly resolutions. Below that, you pay list.
A custom RAG chatbot has two cost buckets. A one-time build cost, and a monthly ops cost. Nothing in between scales per-resolution.
One-time build cost: ₹6-15 lakh (roughly $7,000-$18,000 USD) for a production RAG on your docs with in-app widget, WhatsApp, admin panel, evaluation harness, and monitoring. Simpler builds start lower, multi-channel or on-prem builds cost more. Full breakdown in our AI chatbot cost guide.
Monthly infrastructure and ops: ₹40,000-1,50,000/month ($480-$1,800 USD) depending on volume. This covers LLM API costs, vector database, compute, monitoring tools, and human time for evaluations and re-indexing. Scaling from 1,000 to 10,000 monthly resolutions typically adds only 30-60% to this bill, because the marginal cost is tokens processed by the LLM, not the resolution itself.
LLM API costs scale with tokens, not resolutions. This is the crucial difference. GPT-4o at 2026 pricing costs roughly $0.05-0.15 per resolved conversation depending on prompt length and retrieval depth. That is 10-20x cheaper per resolution than Intercom Fin's $0.99, before you even count Intercom's platform fees. This is where the break-even flips.
Managed ops adds roughly ₹40,000/month if you do not have an in-house team to operate the system. That covers re-indexing on doc updates, model drift monitoring, quality evaluations, cost alerting, and incident response. Full cost transparency, no per-resolution surprises, and no invoice spikes when you launch a big marketing campaign.
Here is the actual side-by-side monthly cost at eight different monthly resolution volumes. Custom RAG columns show both raw ops cost and ops cost amortized against a build cost of ₹12L (roughly $14,400 USD) spread over 24 months. Intercom column uses list price of $0.99 per resolution without volume discounts.
| Monthly resolutions | Intercom Fin ($0.99 each) | Custom RAG (ops only) | Custom RAG (ops + amortized build) |
|---|---|---|---|
| 100 | $99 | $1,200 | $1,700 |
| 500 | $495 | $1,200 | $1,700 |
| 1,000 | $990 | $1,300 | $1,800 |
| 2,500 | $2,475 | $1,500 | $2,000 |
| 5,000 | $4,950 | $1,800 | $2,300 |
| 10,000 | $9,900 | $2,500 | $3,000 |
| 25,000 | $24,750 | $4,500 | $5,000 |
| 50,000 | $49,500 | $8,000 | $8,500 |
Build cost of ₹12 lakh ($14,400) amortized over 24 months = ~$600/month. Ops baseline of ~$1,200/month covers vector DB, compute, monitoring, retainer for a mid-scale deployment. LLM API scales at roughly $0.10 per resolution on GPT-4o with prompt caching. Amortized-build column stops adding after 24 months, so year-3 economics of custom look even better than shown here. Intercom column is list price. Enterprise discounts would push break-even up to roughly 2,500-3,000 resolutions.
The break-even point where custom RAG starts winning even accounting for the build cost lands at roughly 1,500-2,000 monthly resolutions. Below that, Intercom is cheaper on paper. Above it, custom is meaningfully cheaper and the gap widens fast. At 10,000 monthly resolutions, custom saves you about $7,000/month. At 25,000 monthly resolutions, custom saves you about $20,000/month, which is $240,000 a year.
15-minute call. Tell us your current monthly ticket volume, what percentage you think is automatable, and your projected 12-month growth. We tell you honestly which option makes sense, with the math. If Intercom is the right call for your volume, we say so.
Book Free 15-min CallCost is not the only variable. Even if the volumes tilted the other way, there are capabilities in each direction that matter for specific use cases. Here is the honest side-by-side of what each option gives you.
| Capability | Intercom Fin | Custom RAG (Decipher) |
|---|---|---|
| Setup time | Days | 6-9 weeks |
| Pricing model | Per-resolution ($0.99+) | Flat monthly plus one-time build |
| Model choice | Vendor-locked | Any LLM (GPT, Claude, Llama, Gemini) |
| Data privacy | Intercom hosts | Your VPC, on-prem, or hybrid |
| Zero-data-retention | Depends on Intercom's ToS | Yes, signed with your chosen LLM provider |
| Multi-channel (in-app + WhatsApp + Slack + Teams) | Add-on cost per channel | Included in build |
| In-app product-state awareness | Limited | Full (reads user context via your API) |
| Custom actions (create ticket, refund, etc.) | Limited without paid connectors | Any action your product API supports |
| Fine-tuned model on your data | Not available | Available (Llama fine-tune, OpenAI fine-tune) |
| Language support | 40+ languages (auto) | Depends on chosen model, 100+ possible |
| White-label, no vendor branding | Enterprise tier only | Fully yours |
| Analytics and evaluations | Intercom dashboard only | Custom dashboards, integrates with your BI |
| Compliance (SOC 2, ISO 27001, HIPAA) | Intercom's certifications | Your certifications (we support the operational side) |
| Migration cost if you leave | High (data lock-in) | Low (your code, your models) |
We recommend Intercom Fin (or Zendesk AI) to prospects on discovery calls all the time. Some scenarios where it is clearly the right call:
The other direction. Scenarios where custom is clearly the right call and where we most often deploy it for clients:
A pattern we see with mid-to-large SaaS companies is deploying both, each for the job it is best at. Intercom Fin handles public marketing-site chat and Tier-1 support ticket deflection where volume is high and questions are basic. A custom RAG chatbot handles in-app product assistance where deep product-state awareness and custom actions matter more than any per-resolution cost.
This hybrid makes sense when your public support volume is dominated by high-volume basic questions (billing, account setup, general how-to) while your in-app volume is dominated by low-volume but high-value questions (advanced feature usage, complex workflows, integration troubleshooting). Different economics, different capability needs, different tools.
The bots do not need to know about each other. Intercom stays in your marketing site and help center. Custom RAG stays in your product UI. Handoff to human agents in both cases goes back into your Intercom ticketing system so your support team has a single inbox to work from.
Run these four questions in order. The first "yes" or "no" answer that tips you strongly in one direction is usually the right call.
We do not compete with Intercom Fin at low volume and we do not try to. If a discovery call reveals you are under 500 monthly resolutions with simple FAQ flows and no compliance constraints, we will tell you to use Intercom. Our custom RAG business is above that band, where the numbers stop making sense for per-resolution pricing and where product-state awareness starts creating real value.
The questions we hear most on Intercom-vs-custom discovery conversations.
15-minute call. Bring your monthly ticket count, your rough automation percentage, and your 12-month growth projection. We come back with a side-by-side cost model and an honest recommendation. If Intercom is the right call for your volume, we say so.