An Intercom-team migration guide: what you gain and lose moving to Chatbase, including pricing models, ticket history, identity, routing, reporting, and Fin's standalone option.
Intercom Fin
ChatbaseIf your team already lives inside Intercom's shared inbox, this is not a "which tool is better" comparison. You are deciding whether the operational machinery you rely on every day, ticket history, routing, reporting, and in-product messaging, survives a move to a platform built around an AI agent. Some of it transfers, some of it doesn't, and one piece of Intercom's stack, Fin, can stay with you even if you leave. For the reverse perspective, see our Chatbase vs Intercom comparison.
TL;DR: For an established Intercom team, switching to Chatbase trades a seat-plus-outcome model and mature routing for a credit-metered agent platform. Chatbase's Basic plan includes an inbox, voice, and API access, but you will rebuild workflows, reporting, identity, and in-app messaging elsewhere. Fin also runs standalone on other helpdesks at $0.99 per outcome. Run a side-by-side pilot before committing.
Intercom is priced per seat with usage on top. Essential lists at $29 per seat per month on annual billing, with a promotional $19 rate for new customers shown on the pricing page (eligibility conditions are unspecified). Advanced lists at $85, and Expert at $132. Fin adds $0.99 per outcome; sales qualifications are $9.99 each. Copilot is $29 per agent per month on annual billing, or $35 monthly.
Chatbase sells blocks of message credits. Hobby is $32 per month billed annually and includes 700 subscription message credits. Basic is $120 per month billed annually and includes 4,000 credits plus the helpdesk inbox, voice, and API access. Business is $400 per month billed annually and includes 15,000 credits, advanced analytics, source suggestions, and tickets as a source. Auto-recharge adds credits at $40 per 1,000.
The catch is that these units do not convert. A Chatbase message credit is not a conversation and not a resolved ticket; consumption depends on the model you select and the workload, so 4,000 credits can mean very different volumes for different teams. An Intercom outcome is a defined event, a resolution or a procedure handoff, while a seat is a human being. You are comparing two different meters, so a price-per-unit comparison will mislead. For a broader walkthrough of these billing models, see our AI chatbot pricing guide.
Most migration risk isn't in the bot. It's in the infrastructure around it.
Ticket history and customer context. Intercom keeps a full conversation history and customer profile attached to each person. Agents see prior issues, purchase history, and the threads that led to the current ticket. When you move to Chatbase, you need a plan for what carries over. A long-time customer who has to re-explain a two-week-old problem will notice immediately. Confirm your export path and what the new agent can reference before you schedule a cutover.
Identity and agent administration. Intercom's Expert plan includes SSO and identity management, so your team already expects centralized login and persistent customer identity. None of that transfers to Chatbase automatically. You will need to re-provision agent accounts and re-verify how customer identity is linked across conversations in the new workspace. Plan for this separately from ticket export.
Routing and assignment. Intercom's Advanced plan adds multiple team inboxes, a workflows automation builder, and round-robin assignment; Expert adds SLAs, SSO, and multibrand support. Chatbase's inbox on Basic and above shows ticket status and requestor fields, but it does not advertise the same depth of routing rules, skill-based assignment, or SLA management. That isn't proof it can't handle your queue; it's a reason to test your actual workflow rather than assume parity from a feature list.
In-product messaging. Intercom's Messenger does far more than answer questions. It delivers in-app chats, banners, tooltips, and outbound campaigns (Proactive Support Plus, $99 per month for 500 messages). Chatbase positions its agent across chat, email, and voice for customer experience, but it is not a replacement for Intercom's product-engagement layer. If your team uses the Messenger to drive onboarding and announcements, plan for that gap.
Reporting. Intercom ships pre-built reports and CSAT focused on agent operations. Chatbase offers analytics on topics, sentiment, and trends oriented toward agent behavior. Neither dashboard translates to the other; you will rebuild reporting either way.
The biggest surprise for most teams: Fin is not tied to Intercom. It runs standalone on other helpdesks, including Salesforce, HubSpot, Freshworks, Dixa, Front, Zoho, Sprinklr, and Gorgias, at $0.99 per outcome with a 50-outcome monthly minimum, no seat costs, and no setup or platform fees. So if cost is the reason you're shopping Chatbase, there is a middle path: keep a helpdesk (possibly a less expensive one) and run Fin on top. You are not forced to choose between all-Intercom and all-Chatbase. Our Intercom Fin review digs into how outcome billing behaves in practice.
The video below walks through how Fin behaves as an agent in a live demo, useful for understanding what a billable "outcome" looks like before you commit to outcome-based budgeting.
Take a hypothetical team of six on Intercom Essential, annual billing.
The Chatbase route: Basic at $120 per month gives 4,000 credits, the inbox, and 3 workspace members, fewer than the six on Intercom, so member limits matter. You still have to train the agent on your sources, configure procedures, reconnect integrations, and re-verify data access.
The financial comparison only becomes meaningful once you also value the labor of migration and the features you lose.
Treat the switch as a testable hypothesis:
Then apply a simple rule: switch only if the agent answers accurately, your workflow survives in the Chatbase inbox, and the all-in cost beats your current seats plus Fin bill. Otherwise, consider the standalone Fin path or stay put.
Moving to Chatbase is defensible when your team is small and seats dominate cost, when you don't depend on Intercom's in-app messaging or advanced routing, and when you accept rebuilding agent training, identity, and reports. It's also attractive if you're effectively starting over, with no backlog of ticket history to carry.
Stay in Intercom (or evaluate the standalone Fin route) when you rely on routing rules, SLAs, workflows, multibrand support, or product messaging, when Fin costs are predictable and modest, or when the labor of migration outweighs the projected savings. For a wider field of helpdesk options, see the help desk comparison.
Does Chatbase have a helpdesk inbox? Yes. Basic and above include the Chatbase helpdesk inbox, voice, and API access. It's not a chatbot-only platform, but its inbox feature set is lighter than Intercom's routing and workflow tooling. Test your queue against it.
Can Fin be used without Intercom? Yes. Fin runs with other helpdesks including Salesforce, HubSpot, Freshworks, Dixa, Front, Zoho, Sprinklr, and Gorgias, at $0.99 per outcome with a 50-outcome monthly minimum and no seats.
What counts as a Fin outcome? A resolution (no further help requested), a procedure handoff you configured, a disqualification, or a self-serve routing, each $0.99. Qualifications are $9.99 each. Conversations handed to your team without an outcome are not charged.
How do Chatbase message credits compare to Fin outcomes? They don't convert. Credits meter model usage based on your configuration and workload; outcomes meter defined resolution events. Budget them separately and measure actual consumption.
Is Chatbase cheaper than Intercom? On sticker price, usually yes: Basic is $120 per month versus six Essential seats at $174 per month plus Fin usage. But that ignores the cost of rebuilding workflows, identity, and in-app messaging, and retraining. The real question is whether the cheaper platform handles your queue.
The migration is justified when the cheaper meter covers the actual work your team does, and you've proven it in a pilot. The standalone Fin path exists precisely because you can separate the AI agent from the helpdesk. Choose based on operational needs, not unit price alone.
