Friction

Intercom alternatives: where its users went, and why they left

Intercom (intercom.com) has 16 sourced reports on Friction, drawn from 64 public source threads (as of 2026-10-15), 18 of them describing a move away. This page reads them for one question: if you are leaving Intercom, what do its users say they moved to, and what pushed them out?

Get started free with your email Open Intercom on Friction

Where Intercom users say they went

Switching reports that name a destination. A count is the number of reports naming it, not a market share: Friction only holds what people say in public.

Named alternativeReports naming itNewest report
Opencom22026
Their own platform, tiny.help12026
Opencom-dev12026
AWS Connect12025
Chatwoot (compare)12022
HelpScout12022
A self-built or in-house tool12020 (over 5 years old)
Papercups12020 (over 5 years old)

In their words

Powered-by branding makes customer messages feel impersonal → An unspecified alternative

“Personal communications between me and MY customers don't sound personal when they have "Powered by X SaaS Marketing Platform”

Built a replacement after frustration with support tools → Their own platform, tiny.help

“I got so fed up with my support system, and after years of using tools like Intercom, I built my own platform”

Switched to an open-source Intercom alternative over pricing → Opencom-dev

“I made a free open-source version of Intercom at the start of the year called Opencom-dev after I got sick of paying what felt like”

Complex, expensive pricing prompted an open-source alternative → Opencom

“I started working on it after years of frustration using Intercom. I love the selection of tools they offer, but not their complex and expensive”

What pushes people away from Intercom

The most-reported open problems, worst severity first. Each links to the item with its source.

Intercom is expensive and difficult to integrate · Integrations · Blocks work

“They are horrible to try to integrate into an established product development cycle (I've tried)”

Individual emails divert support requests from the team inbox · Collaboration · Blocks work

“customers start emailing us on our individual emails for support, and we have to manually nudge them back to the team inboxes”

Risk of agents accidentally replying through Intercom MCP · Permissions & security · Annoyance

“I don't want someone using the Intercom MCP to accidentally reply to a customer with an agent”

High cost and constant upselling · Pricing & plans · Annoyance

“It’s also very expensive and constantly upsold, despite being rubbish”

Intercom chat bubble adds distracting website clutter · UI & usability · Annoyance

“all things present in a website's "gadget layer" - that place where all 3rd party add-ons go that actually hurt the user's experience”

See all 15 themes for Intercom

Other customer support and messaging tools on Friction, and what their users struggle with

Switching trades one set of problems for another. The same evidence, for each tool Friction covers in this category:

Zendesk

17 reports · 55 source threads · most-discussed area: Pricing & plans

Intercom vs Zendesk: side by side · Zendesk alternatives

Chatwoot

14 reports · 66 source threads · most-discussed area: Integrations

Intercom vs Chatwoot: side by side · Chatwoot alternatives

Counts and reports reflect people who post in public (developers and technical buyers are over-represented). A tool with fewer reports is not a better tool; it may only be discussed less. How the data is built.