Chatbase vs Intercom: Website Agent or Shared Support Operation?
Chatbase vs Intercom: compare a website agent billed by message credits (Hobby $32/mo, 700) against a seat-based shared inbox with Fin at $0.99/outcome, and learn when each fits your support operation.
ChatbasevsIntercom Fin
Chatbase and Intercom both put a chat window on your website, which is why they get compared. The shared interface hides a structural difference. Chatbase is an AI agent platform billed in message credits; it treats support as conversations the AI can own. Intercom is a helpdesk platform billed per seat, with Fin, its AI agent, priced separately per outcome. The real question is not “which chatbot should I pick” but “do I need an agent, or an inbox that agents and humans share?”
That framing drives the rest of this comparison. If you start from a website-agent problem, meaning you have support content and want an AI to answer most questions inside a chat widget, Chatbase is the leaner fit. If you need a queue, ticket assignment, escalation rules, multiple channels, and reporting across a human team, Intercom’s seats are the justification. Fin can operate on either side of that line, which changes the math.
The two products solve different jobs
Chatbase is agent-first. You train it on your website, documents, or FAQs; deploy it with a widget; and attach actions. Basic and up open the deeper set: Stripe, Salesforce, Zendesk, and API access. Hobby keeps the channel integrations, including Shopify, Slack, WhatsApp, Messenger, Instagram, Calendly, and WordPress. Chatbase’s pricing page describes the product in terms of message credits, agents, and procedures. A helpdesk inbox exists, but it appears on the Basic plan and up, not as the core product.
Intercom is platform-first. The Essential plan includes the Messenger, a shared inbox and ticketing system, prebuilt reports, and a public help center. The Essential plan includes access to Fin, but Fin is billed separately at $0.99 per outcome. The difference matters when a conversation needs more than an accurate answer: someone has to own it, assign it, and follow up.
The overlap is simple web chat. If your support volume is mostly “where is my order” and “what is your return policy,” both products can handle it. The decision moves to operations: who answers when the AI cannot, and what tool do they already live in?
Chatbase pricing: agent credits, not seats
Chatbase’s current plans, on yearly billing, are Hobby, Basic, and Business. The monthly equivalents are higher, and auto-recharge is available when credits run low.
3 members, helpdesk inbox, voice, API access, advanced integrations
Business
$400/mo
$500/mo
15,000 message credits
5 members, advanced analytics, sources suggestions, tickets as a source
Two points matter before you pick a tier. First, a message credit is not a conversation. Credit consumption varies by model, response length, and whether the agent calls functions, so the same question can cost different amounts depending on how the agent is configured. Second, Hobby is not a FAQ-only tier: it ships with Shopify, Slack, WhatsApp, Messenger, Instagram, Calendly, and WordPress integrations, and can be set to hand off to a human. The Basic upgrade adds the helpdesk inbox, voice, and API access, which is what you need if the agent’s escalations need a home inside Chatbase.
Intercom pricing: seats plus outcomes
Intercom sells seats, and Fin is usage-based on top. The current Essential page shows a promotional $19 per seat per month with a struck-through $29, labeled for new customers saving 35%. The conditions behind that promotion are not fully documented on the page, so treat it as a current promotional rate rather than a permanent price. Advanced is $85 per seat per month and Expert $132, both annual. Channels and add-ons, such as Copilot at $29 per agent per month annually, are separate from the seat price.
Fin itself is $0.99 per outcome. An outcome is counted once per conversation, even if Fin answers several questions. According to Intercom’s FAQ, an outcome occurs when a customer confirms their issue is resolved, when they do not ask for more help after Fin responds, or when Fin completes a configured Procedure, including a handoff. That means an outcome is not always an independent end-to-end resolution; a completed handoff to a human counts. Sales qualification outcomes are priced separately at $9.99 each.
Fin can also run without Intercom seats. On the standalone path, Fin works with an existing helpdesk such as Salesforce, with a 50-outcome monthly minimum, no seat cost, and no setup or platform fee. If you already have a helpdesk, adding Fin there is cheaper than buying Intercom seats just to get Fin.
The same request through both stacks
Take a refund question: “I want to return the jacket I bought, can you help?”
On Chatbase, you train the agent on your return policy and connect a store or payment action. The agent can confirm eligibility and explain the window. Identity matters at this point: an order number or email is a lookup key, not proof of identity. Completing the return requires an authenticated customer session or a secure verification flow. For guests, the safe pattern is to send a secure verification link to the stored contact address rather than exposing order records in chat. If the customer is signed in, the agent can complete the return action; otherwise it routes to a human. On Hobby, there is no inbox, so escalations need a destination outside Chatbase: email, Slack, or the widget’s human-handoff setting. On Basic, the conversation can become a ticket in Chatbase’s own inbox.
On Intercom, Fin answers from your help center and can run a Procedure that, for example, collects the order number and confirms the return request. The same identity rule applies: confirming a request is not the same as executing it, and the actual return action belongs in an authenticated session. If the customer needs a human, Fin hands off inside the inbox. The key difference is not that Fin is smarter; it is that the handoff lands in the same system where your team already works, with context attached.
This is why the chatbot-versus-helpdesk framing is a trap. A refund question is resolved by whichever tool owns the follow-up when the AI cannot finish the job. If no human is scheduled to look at Chatbase, the escalations pile up. If your team already has an inbox, Fin plugs into it without requiring Intercom seats.
Cost comparison, worked
These figures are illustrative, not vendor quotes. Assume a small team that wants an AI agent plus a human fallback, and about 200 AI-handled support outcomes per month.
Chatbase path: Hobby at $32/mo annually includes 700 credits. Assuming the 200 outcomes consume roughly 1,400 to 2,100 credits under a mid-tier model, you would need one to two $40 recharges on top of the included credits, bringing the month to about $72 or $112. The human fallback lives wherever you point it, which may be an existing shared inbox or a separate tool. If you instead need Chatbase’s own inbox, you step up to Basic at $120/mo.
Intercom path: One Essential seat at the promotional $19/mo, plus 200 Fin outcomes at $0.99 each, is $217 before add-ons, messaging channels, or any $9.99 qualification outcomes. That assumes the promotional rate applies to you and that no paid channel costs are incurred.
The Chatbase option is cheaper on paper, but it is a different operation. The Intercom figure buys an inbox, assignment, reporting, and a help center in the same system; the Chatbase figure buys an agent with a modest inbox only if you move to Basic. Compare the operations, not just the numbers.
When Chatbase is the right start
Choose Chatbase when you are solving a website-agent problem: you have content, you want a trained AI in front of customers, and no one’s job is running a support queue yet. Hobby is a small monthly commitment, and you can cap auto-recharge before the widget goes public. This is also the moment to look at other agent-first platforms; if you are comparing website agents, our Chatbase vs YourGPT breakdown covers that category directly.
The failure condition is when customers start needing a human. If the agent’s handoff lands nowhere, you have created a second channel with no owner. At that point you either adopt Chatbase’s Basic inbox or route escalations into a helpdesk you already run.
When Intercom earns its seat
Intercom earns its cost when a team already works in an inbox and needs the operational layer: ticket assignment, collision detection, team inboxes, workflows, SLAs, and reporting. Fin then sits on top of that operation rather than replacing it. If your team already has a helpdesk, do not buy Intercom seats just so Fin can answer a website. The standalone Fin path with a 50-outcome minimum is the cheaper way to add an agent to the desk you already use.
If you are evaluating a full helpdesk rather than a website agent, our helpdesk comparison covers the seat-based options in more depth.
WatchFin by Intercom: customer service agent demoYouTube
This Intercom demo shows how Fin handles a customer conversation and hands off when needed; it illustrates the outcome model described above, not a measured performance benchmark.
Moving between them
The direction of migration matters. Leaving Chatbase usually means the team outgrew the agent-only model and needs a queue, assignment, and collision detection, the core of an inbox suite. If you are leaving Intercom, the question is whether you would be buying the first seat only so Fin can answer a website. In that case the agent-first product is the smaller commitment, and a list of Intercom alternatives can help you map the options.
One caution: moving from Intercom to Chatbase does not remove the need for a human fallback. It changes where that fallback lives. Plan the handoff destination before you cancel the seats.
Limits of the evidence
This comparison is based on public documentation from Chatbase and Intercom as of 26 October 2026; we did not run hands-on tests or measure vendor outcomes independently. Resolution percentages and customer quotes on vendor pages are marketing claims, not benchmarks. The Intercom Essential $19 rate is a labeled promotion with unknown conditions, so verify it before budgeting. Chatbase’s credit-to-conversation ratio depends on your workload and model choices, so the only reliable test is measuring your own usage.
FAQ
Do I need Intercom seats to use Fin? No. Fin can run standalone on another helpdesk, including Salesforce, at $0.99 per outcome with a 50-outcome monthly minimum and no seat cost. Intercom seats are only required for the Intercom helpdesk bundle.
What does a Chatbase message credit buy? A credit is a unit of model usage, not one conversation. The cost per conversation varies by the model you select, message length, and whether the agent uses actions or procedures. Set an auto-recharge threshold and measure your actual consumption before scaling.
Which Chatbase plan includes an inbox? The Basic plan adds the Chatbase helpdesk inbox, voice, and API access, along with 4,000 message credits. Hobby does not include the inbox but does include Shopify and basic channel integrations.
How is a Fin outcome counted? An outcome is billed once per conversation when the customer confirms resolution, does not ask for more help after Fin responds, or Fin completes a configured Procedure, including a handoff. Sales qualification outcomes are billed separately at $9.99 each.
Is Intercom Essential really $19? The current page shows a promotional $19 per seat per month with a struck-through $29, labeled as a 35% saving for new customers. The promotion’s conditions are not fully documented, so treat it as a promotional rate and confirm the terms before committing.
When should I leave Chatbase? Leave Chatbase when you need collision detection, ticket assignment, a queue, and team-wide reporting, the operational core of an inbox suite. If those needs are real, a helpdesk platform is the right home; if they are not, the agent-first plan remains the cheaper option.
Conclusion
The practical answer is positional. If your operation is a website agent with no human queue behind it, Chatbase is the smaller, cheaper, and more honest commitment. If your operation is a shared inbox where agents triage, assign, and escalate, Intercom’s seats are the product, and Fin is the automation layered on top. And if you already have a helpdesk, Fin’s standalone path gives you the agent without buying seats you do not need. Compare the operation you actually run, not just the chat widget.