Open-Source Intercom Alternatives in 2026

The reason teams start looking for an Intercom alternative is rarely the product. It's the invoice — and specifically the discovery that the invoice has three axes. You pay per seat, then per AI outcome, then per channel. Add a person and it goes up. Get busier and it goes up. Succeed at automating support and it still goes up, because the automation is metered too. As of September 2026 there is a fourth reason, and it is the one everybody is asking about first: the company is being bought.

Why do teams look for an Intercom alternative?

Because the bill scales on three axes at once. Intercom's seat plans run $29 / $85 / $132 per seat per month billed annually on Essential, Advanced and Expert — $39 / $99 / $139 monthly. On top of that, Fin costs $0.99 per AI outcome, and SMS, WhatsApp, phone and email campaigns are metered separately. Note the wording: Intercom bills per outcome rather than per resolution, charged at most once per conversation, with sales qualification priced at $9.99. Add-ons sit above that again — the Pro bundle from $99/month, Proactive Support Plus at $99/month, and Copilot per agent.

Zendesk has the same shape. Published seat prices run $19 per agent per month for Support Team, $55 for Suite Team and $115 for Suite Professional, with Enterprise quoted by sales rather than listed. Then the add-ons: Copilot at $50/agent/month and the Workforce Engagement Bundle at $50/agent/month. Stack those on Suite Professional and you are at $215 per agent per month — 87% over the base plan. AI agent usage is billed separately, per automated resolution drawn from a resolution allowance, and since 18 May 2026 resolutions arrive in three tiers: an assisted escalation costs nothing, an unverified contained resolution costs nothing, and only a verified resolution draws down the allowance. Zendesk does not publish the per-resolution rate on its pricing page — and its documentation carries no per-resolution figure — so that number arrives from a salesperson.

None of this makes them bad products. Both are mature, both have reporting a decade deep, and Zendesk has since added Forethought AI agents that run on stacks other than its own. It makes them expensive in a specific way: the more successfully you automate, the more you pay for having done it. It is the same pattern every meter in this industry has — counting something other than the work.

Is Intercom being acquired by Salesforce?

Yes, though it has not closed. Intercom renamed itself Fin in May 2026, and on 15 June 2026 Salesforce signed a definitive agreement to acquire it for approximately $3.6 billion. Salesforce says the transaction is expected to close in the fourth quarter of its fiscal year 2027, subject to regulatory clearance, and that Fin's customer agent technology will be folded into Agentforce. As of September 2026 the deal is signed but not completed, and Fin continues to operate as its own product.

Give the product its due, because the numbers behind that price are real. Fin's AI Agent runs on Apex, a model the company built specifically for customer support, and Salesforce's own release cites deployments resolving an average of 76% of support volume end to end across chat, email, WhatsApp, SMS, phone and Slack. More than 30,000 companies come with the deal. This is not a distressed sale; it is the category leader being bought at a category-leader price.

What it changes for a buyer is the planning horizon rather than today's product. An acquisition of this size means packaging, pricing and roadmap decisions will be made inside a much larger company, on a timetable nobody outside it can see, and the thing being acquired is specifically the AI agent that sits on top of your support data. If you are signing a multi-year contract this quarter, that is a fair question to put to your account executive and get in writing.

It is also a reasonable moment to ask a more durable question: how much does it cost you to leave, whoever owns the product? That answer does not depend on who signs the acquisition paperwork. It depends on whether your conversation history is something you can take with you — which is a question about export formats, and one worth checking before you need the answer.

What does Intercom actually cost at 1,000 conversations a month?

For a three-agent team on Expert seats, roughly $1,148 a month — $396 in seats plus about $752 in Fin outcomes, if Fin resolves the share Salesforce advertises. On Essential seats the same volume lands near $839. Zendesk Suite Professional with Copilot and the Workforce Engagement Bundle is $645 for three agents before a single automated resolution is counted.

The assumptions matter, so here they are in the open. Three agents, 1,000 conversations a month, annual billing, no channel add-ons. The Fin figure applies Salesforce's own published claim — an average 76% of volume resolved end to end — to those 1,000 conversations, giving 760 outcomes at $0.99. That is a vendor's marketing number being used to size a vendor's bill, which is the fairest way to read it: if Fin performs as advertised, this is what performing as advertised costs.

And note the trade that sits underneath it. A conversation Fin does not resolve costs you nothing in outcomes, but it costs you a human. So the meter runs hardest exactly when the product works best, and the only way to lower that line on the invoice is for the automation to do less. That is not a bug in Intercom's pricing; it is what pricing per outcome means. It is worth deciding whether it is the incentive you want pointed at your support team.

The Zendesk figure is the one with a hole in it. $215 per agent per month is a published number, and $645 for three agents is arithmetic. What is not published is the rate per verified automated resolution — Zendesk's own help centre carries no per-resolution figure — so the automation line on a Zendesk quote cannot be modelled from public information at all. You get it from a salesperson, after you have shown interest.

• 01Intercom Expert — $396 in seats for three agents, plus ~$752 in Fin outcomes at 76% resolution. About $1,148 a month.
• 02Intercom Essential — $87 in seats, same outcome bill. About $839 a month, with a thinner feature set behind it.
• 03Zendesk Suite Professional — $645 for three agents with Copilot and the Workforce Engagement Bundle stacked, before automated resolutions, which are priced privately.
• 04Chatwoot Cloud Business — $117 for three agents, with 500 Captain AI credits included and further credits at $20 per 1,000. Self-hosted Community is $0 in licence.
• 05Munin Cloud Free — €0 per org for all six modules, within 5,000 MCP calls, 250 contacts and 100 MB. Cloud Premium, launching soon, is a flat €99 per org per month rather than per seat.

What is the best open-source Intercom alternative?

Chatwoot is the most mature and the default recommendation — live chat, email, social, and WhatsApp in one inbox, and the closest like-for-like replacement. Zammad is better if you need SLA management and ticketing discipline. FreeScout is the lightest. Tiledesk is the one to look at if the chatbot is the point. Munin is the pick if you want the support inbox to share one customer record with your CRM, knowledge base, and content, and to be operated by AI agents.

The honest framing: four of these five replace your inbox. One replaces the reason you had four systems. If it's the CRM side of that you're weighing rather than the inbox, the open-source CRM field compares differently — and mostly on the licence.

Is Chatwoot a good replacement for Intercom?

Yes — Chatwoot is the most mature open-source customer messaging platform available and the closest thing to a drop-in Intercom replacement. It handles live chat, email, social inboxes, and WhatsApp from one unified interface. Expect roughly 2–4 hours to stand up on a VPS, with 8 GB RAM minimum and 16 GB recommended on its own deployment page; how that footprint compares to running a whole platform on one host is its own piece.

The prices are published, which is more than Zendesk manages. Chatwoot Cloud is $0 on Hacker for up to 2 agents and 500 conversations a month, then $19, $39, and $99 per agent per month billed annually on Startups, Business, and Enterprise, with Captain AI credits included per tier — 300, 500, 800 — and further credits at $20 per 1,000. Self-hosted, the Community Edition is free forever, and the supported editions are $19 and $99 per agent per month. Worth reading the shape rather than only the number: self-hosting removes the vendor from your data path, and the paid self-hosted editions are still counted per agent.

One thing to read carefully before you commit: the community edition is MIT, but everything under the enterprise/ directory ships under a separate proprietary, source-available licence. You can read that code, but running those features in production requires a paid Chatwoot subscription and an active agreement. That's open core — a perfectly legitimate business model, and not the same thing as the MIT badge on the front page.

One more thing to check if you are in Europe: Chatwoot's own pricing FAQ states that Chatwoot Cloud runs on AWS with servers in the United States. Self-hosting puts that back under your control entirely, in whichever jurisdiction you choose — which is the answer if data residency is a hard requirement and you are happy to run the box. If you would rather someone else ran it and still needed the data to stay in Europe, that is the case Munin Cloud is built for.

Chatwoot covers WhatsApp, Instagram, and Facebook natively; Munin's four channels are email, chat widget, SMS, and voice. If most of your support arrives through social channels, take Chatwoot. If it arrives through email and chat, and the problem is that your inbox knows nothing about the customer sitting in it, that is the job Munin was built for — one record behind the inbox, MIT throughout, and no enterprise/ directory to buy back.

Chatwoot or Zammad — which should I pick?

Pick Chatwoot if your support is conversational: live chat, social, WhatsApp, people expecting a reply in the widget. Pick Zammad if your support is contractual: tickets, queues, escalation paths, and a number you have promised somebody in writing. The split is not about maturity — both are mature — it is about whether the unit of work is a conversation or a ticket.

The operational bill differs more than the feature lists suggest. Chatwoot is Docker-based and lands in a couple of hours. Zammad wants Ruby on Rails dependencies, Postgres and Elasticsearch, and around 4 GB of RAM before it is comfortable — more moving parts to patch, and a real reason to prefer it only when you need what it does. Licences differ too, and in Zammad's favour: AGPL-3.0 the whole way down with no ee/ directory, against Chatwoot's MIT core plus a proprietary enterprise/ tree.

If you are weighing these two, there is a third question worth asking before you commit to either, because it is the one that is expensive to change later: does the desk need to know who it is talking to? Chatwoot and Zammad both hold a contact record, and both hold it in their own database, separate from whatever your sales side runs. Munin's answer is that the inbox and the CRM are the same table — so a conversation arrives already attached to the customer's history, the campaign they are in, and the knowledge base your team writes. That is the axis Munin competes on, and it is orthogonal to the chat-versus-ticket choice.

What about Zammad and FreeScout?

Zammad is a help desk rather than a chat tool. It takes email, chat, phone, and social, converts them into tickets, and gives you SLA management, reporting, and a knowledge base — the things a support org with contractual obligations actually needs. Its licence is also the cleanest in the category: AGPL-3.0 throughout, with no ee/ directory and no cut-down community edition, and self-hosting needs no licence key to get the full feature set. The cost is setup: Ruby on Rails dependencies on a Linux server, a higher bar than the Docker-based options.

FreeScout is a lightweight shared inbox on PHP/Laravel, under 256 MB RAM idle, installable on any LAMP host. It's the right answer when what you want is a shared mailbox that isn't Gmail, and nothing more. Its paid modules are unusual in this field for being AGPL-3.0 as well — what you buy is a download key and support, not different terms.

One fact these self-hosted options share, worth stating precisely rather than vaguely: none of Chatwoot, Zammad, FreeScout or Tiledesk publishes an official MCP server today. Chatwoot's own extensibility for Captain is custom HTTPS tools rather than MCP, and the servers you will find on GitHub for all four are community projects with no vendor maintaining the contract. That is not a claim that an agent cannot drive them — a REST API and a community wrapper get you a long way — it is a claim about who is on the hook when the API changes underneath you. Munin's position is the inverse: the tool catalogue is the primary surface and the REST API is the thing that came second. If it is the cheaper hosted end of the market you are weighing instead, the Freshdesk comparison covers that field and the metering Freshworks has announced for its own MCP interface.

What about Tiledesk?

Tiledesk is an open-source live chat with a visual chatbot builder and human handoff — the closest structural match to what Intercom's Messenger plus Fin actually does. It is written in Node.js, self-hosts with Docker Compose or a Helm chart, and in July 2022 it relicensed from AGPL-3.0 to MIT and collapsed to a single codebase. If a bot that deflects the easy questions and passes the rest to a person is the job, this is a serious option.

Credit where it is due, and this is the interesting part: an MIT relicence with one codebase is a genuinely generous move, and it is rarer than the badges on this category's front pages suggest. Most vendors have gone the other way since, in 2025 and 2026 especially.

There is still a line to find, and it is in an unusual place. Tiledesk's own deployment repository notes that Enterprise customers request credentials to pull private, Enterprise-only Docker images. So the carve-out is not a directory you can read and not a per-file header — it is an artefact you cannot see at all. That is the third of the three hiding places worth checking on any project in this category, and Tiledesk is a clean example of it. Not a criticism of the licence, which is real; a note that the licence and the distribution are two different questions.

The scope difference against Munin is the ordinary one. Tiledesk is a conversation surface with bots behind it. Munin is a conversation surface that shares its customer record with a CRM, a knowledge base, a CMS, an outreach tool and analytics, with the whole thing driven through one MCP endpoint — and MIT applies to every part of it, including the images.

What does it actually cost to self-host a support desk?

The licence is the free part, and it is the part people quote. The real bill is three lines: a server, the model tokens your AI actually burns, and somebody's time to patch it. Chatwoot Community, Zammad, FreeScout, Tiledesk and Munin all cost $0 in licence fees self-hosted. None of them costs $0 to run.

The server is the smallest of the three and the easiest to size — a single modest VPS carries any of these at small-team volume, and every vendor above publishes its RAM floor. Check the current rate on your provider's own page rather than a comparison table; the European hosts repriced during 2026 and most third-party figures on the web are stale.

The model tokens are the line that replaces the meter you left behind, and it is worth being exact about what changes. Self-hosting does not make AI support free. It makes the AI cost yours — you pay your model provider directly, at your provider's rate, for the tokens you actually spend. What disappears is the layer between: no $0.99 per outcome, no resolution allowance, no per-1,000-action bundle, and no vendor margin on top of the inference. Whether that is cheaper depends on your volume and your model, and at low volume with heavy automation it usually is by a wide margin.

The third line is the honest one: somebody has to own the box. Backups, upgrades, TLS, the Postgres that fills up. If nobody on your team wants that job, hosted is the right answer and the licence was never the point. That is why Munin ships both from the same repository — Munin Cloud is EU-hosted with a free tier, self-hosting is docker compose up under MIT, and the code is identical either way, so the decision is reversible in both directions.

How do I migrate off Intercom?

Contacts and companies move easily; conversation transcripts are the hard part. Intercom's CSV and dataset exports are explicitly reporting metadata only — its own help centre states that conversation and message content is not included. The bulk UI export gives you PDF or text, 200–300 conversations at a time. For real transcripts at volume you have to go through the Conversations API, and the Export API caps each request at a 90-day window.

The practical shape of that, in the order that saves you the afternoon:

1. Contacts and companies first, via CSV or the API. These are the records everything else points at, and loading them first means every foreign key resolves on the way in.
2. Help centre articles next. These export cleanly and are the easiest win — they become your new knowledge base on day one.
3. Conversations last, and decide the depth before you start. Metadata-only via dataset export is fast and gives you volumes, tags and timestamps. Full transcripts mean iterating the Conversations API, 90 days per request, or an S3 JSON export — and note that Intercom's documentation says the S3 export does not contain a transcript either.
4. Decide what history is actually worth moving. Data is available for up to two years. Most teams need the last quarter searchable and the rest archived, and discover that after paying to move all of it.

Into Munin that sequence is crm_import for contacts and companies, kb_import for the help centre, and conv_import for the conversations, in that order — and every one of those has a matching export tool, so the same sequence runs in reverse on the day you want to leave. The HubSpot runbook walks the identical pattern command by command; only the shape of the source export changes.

One detail from Intercom's documentation that is worth sitting with, whichever vendor you pick next: exported conversation data cannot be imported back into a new Intercom workspace. An export you cannot re-import is a backup of a report, not a backup of your data. Ask any vendor — us included — to show you the round trip before you need it.

How is Munin different from a self-hosted help desk?

Munin isn't a help desk with a CRM bolted on. Conversations, CRM, knowledge base, CMS, outreach, and analytics are six modules over one database, and the customer exists in it exactly once. When an email arrives, the sender resolves against the record your outreach campaigns and knowledge base already use. No sync job, no second version of the truth.

That matters most in the moment a support conversation needs to know something. The agent answering it can search the knowledge base, read the customer's history, and check what campaign they're in — not through integrations, but because the six modules were designed against one schema from the start, where the tenant boundary is a database policy rather than something every query has to remember. It also runs backwards: a closed conversation is where the CRM record gets filled in, without anyone retyping what the customer just said. And what your team answered once becomes a knowledge-base article the next person finds instead of another ticket.

The second difference is who operates it. Munin exposes more than 200 MCP tools at one endpoint, alongside a REST API and around 50 bundled skills, so Claude, ChatGPT, Cursor, or a runner you wrote yourself does the triage, the tagging, the contact extraction, and the knowledge-base drafting directly. Not as a chatbot bolted to the front — as the thing running the desk, with humans approving what matters. Agents propose, humans decide.

And Munin is MIT throughout. No enterprise/ directory, no per-file licence headers, no private images. Leaving is supposed to be easy.

Self-hosted Intercom alternatives compared

Pricing and licence packaging change frequently — confirm on each vendor's own site, including ours. Figures here are indicative and were read off each vendor's own page on 2 September 2026; Chatwoot's deployment requirements were re-checked on 4 September 2026.

Frequently asked questions

What is the best free open-source alternative to Intercom? Chatwoot for a like-for-like replacement — it's the most mature open-source customer messaging platform and covers chat, email, social, and WhatsApp. Tiledesk if a chatbot with human handoff is the main job. Munin if you want the inbox to share one customer record with your CRM, knowledge base, and content, and to be run by AI agents rather than clicked through.

Is Intercom owned by Salesforce? Not yet. Intercom renamed itself Fin in May 2026, and Salesforce signed a definitive agreement on 15 June 2026 to acquire it for approximately $3.6 billion. Salesforce expects the deal to close in the fourth quarter of its fiscal year 2027, subject to regulatory clearance, and says Fin's customer agent technology will be folded into Agentforce. As of September 2026 it had not closed.

How much does Intercom actually cost? Seats are $29, $85 and $132 per seat per month billed annually on Essential, Advanced and Expert — $39, $99 and $139 monthly. Fin AI adds $0.99 per outcome, or $9.99 if the outcome is a sales qualification, and SMS, WhatsApp, phone and email campaigns are metered on top. Add-ons start at $99/month. Budget well above the headline seat price.

What does Intercom cost for a small team at 1,000 conversations a month? On a worked example — three agents, annual billing, no channel add-ons — Expert seats come to $396 and Fin outcomes to about $752 if Fin resolves the 76% of volume Salesforce advertises, so roughly $1,148 a month. Essential seats put the same volume near $839. Your figure moves with your resolution rate.

How much does Chatwoot cost? Cloud is $0 on Hacker for 2 agents and 500 conversations a month, then $19, $39, and $99 per agent per month billed annually on Startups, Business, and Enterprise. Self-hosted, the Community Edition is free forever and the supported editions are $19 and $99 per agent per month. Captain AI credits are included per tier, with extra credits at $20 per 1,000.

Is Chatwoot really open source? The community edition is MIT-licensed, so yes for the core. But everything under the enterprise/ directory is proprietary source-available and requires a paid subscription to run in production. That's an open-core model. Munin has no equivalent directory — the whole suite is MIT.

Should I choose Chatwoot or Zammad? Chatwoot if the unit of work is a conversation — live chat, social, WhatsApp, replies expected in the widget. Zammad if it is a ticket with an SLA attached, and you need queues, escalation and reporting. Zammad's licence is cleaner (AGPL-3.0 throughout, no ee/ directory); Chatwoot is markedly easier to stand up and run.

Can I export my conversations out of Intercom? Partly, and the detail matters. CSV and dataset exports are reporting metadata only — Intercom's own documentation states message content is not included. Bulk UI exports give PDF or text, 200–300 conversations at a time. Full transcripts at volume require the Conversations API, with the Export API capped at a 90-day window per request. Data is available for up to two years.

What counts as an automated resolution at Zendesk? Since 18 May 2026, resolutions are tiered. An assisted escalation, where the AI helped but a human finished, is free. A contained resolution that fails verification is also free. Only a verified resolution — no customer follow-up for 72 hours, then confirmed by a language model reading the transcript — draws down your resolution allowance. Zendesk does not publish the rate per resolution — its help centre carries no per-resolution figure — so you get the real one from sales.

Which of these has an official MCP server? Intercom does, at mcp.intercom.com, and so does Munin. Chatwoot, Zammad, FreeScout and Tiledesk do not — the servers on GitHub for those four are community-maintained. Zendesk publishes an MCP client rather than a server; the app named "MCP Server" in its marketplace is built by a third-party partner, not by Zendesk.

Is there an EU-hosted alternative to Intercom? Yes. Munin Cloud is EU-hosted, and self-hosting puts any of these options in whichever jurisdiction you choose. Worth checking before you assume: Chatwoot's pricing FAQ states that Chatwoot Cloud runs on AWS in the United States, so with Chatwoot the EU answer is the self-hosted one.

Does self-hosting make AI support free? No — it makes the AI cost yours rather than your help-desk vendor's. You pay your model provider directly for the tokens you spend, with no $0.99 per outcome, no resolution allowance and no margin stacked on the inference. At small-team volume with heavy automation that is usually much cheaper; the trade is that somebody has to run the server.

Can I self-host a help desk with AI support agents? Yes. Munin self-hosts with docker compose up — three containers, Postgres with pgvector plus a backend and a dashboard — and exposes its whole surface as MCP tools, so you point any model at it and the AI cost is whatever your provider charges, not a per-resolution fee to your help-desk vendor.

Which open-source help desk has SLA management? Zammad, and it's the right pick if you're measured on contractual response times. Munin covers a different job: one customer record shared across conversations, CRM, knowledge, and outreach, operated by agents through MCP tools.

Do I need to self-host to escape per-seat pricing? No. Munin Cloud is EU-hosted with a free tier, and the paid plan — a flat €99/month per org rather than per seat — is launching soon. Self-hosting is free forever under MIT if you'd rather run it yourself — same code either way.

If what actually annoys you is that support, sales, and content each hold a different version of the same customer — and that you're metered on automation you could be running yourself — start on Munin Cloud in the EU, or clone the repository and run it on your own machine.

You shouldn't pay more for support the better you get at it.