Intercom is genuinely good at one thing: bundling customer messaging, knowledge bases, and support tooling into a single interface that feels refined. If you have a 5–15 person team, predictable message volume, and you're happy with their feature set, you probably should stay. But if you're here because your bill climbed 40% year-over-year without a proportional feature upgrade, or your support volume is seasonal and you're paying per resolution no matter how many tickets close quietly—you're not alone. Intercom's pricing model rewards predictability and punishes growth. How Intercom's pricing actually works Intercom charges by resolution (roughly: a support ticket that closes or a conversation that concludes). They also layer in team seats, knowledge base articles, and add-on modules. The core math is simple in theory but brutal in practice: Resolution volume is unpredictable. A seasonal business, a product launch, or a sudden influx of onboarding questions can double your monthly bill overnight. You don't control when customers close a conversation. You pay per seat, too. Unlike Slack, where one person can access one workspace, Intercom charges for each team member who needs access to conversations. This compounds fast in support-heavy organizations. Premium features cost extra. Custom attributes, advanced routing, AI reply suggestions, and API rate limits live behind higher plans. You're not just paying for volume; you're paying for capability. The result: a company that starts at $500/month for basic support can hit $3,000–5,000/month in 18 months without changing their support process, purely because they grew. What Intercom does well (and who should stay) Before you leave, be honest about whether you're running from Intercom or toward a competitor. Intercom excels at: Onboarded product tours and checklists. If in-app guidance is core to your retention strategy, Intercom's visual builder is mature and well-integrated. Public knowledge bases with good SEO. Their article tool has built-in schema, analytics, and publishing workflows that compete with dedicated knowledge base platforms. Single-window support teams. A support agent can see conversations across email, live chat, messenger, and social media in one place. If that's your workflow, switching costs real productivity. Predictable, small-volume support. If you close 50–200 conversations per month, their pricing is rational and their product is battle-tested. Stay on Intercom if: you're small, stable, and the per-resolution model doesn't sting. Leave if: you're growing, seasonal, or you need messaging features that integrate with sales (not just support). What actually costs you during migration Switching platforms sounds simple. In practice, it's not the software—it's the work. Historical data export and cleanup. Intercom lets you export conversations, but the format varies by integration. Email threads, live chat transcripts, and custom attributes may not map cleanly to another system. Budget 40–80 hours of data munging. Knowledge base rebuild. If your knowledge base is in Intercom, you'll need to migrate articles, categories, and metadata to a new platform (or an external wiki). This is usually manual. Integration reconnection. If Intercom talks to your ticketing system, CRM, or help desk via webhooks or direct integrations, you'll need to rebuild those connections. This can break during cutover if not sequenced carefully. Team retraining. Your support staff has muscle memory for Intercom's interface. Even an objectively better tool costs 1–2 weeks of productivity while they learn hotkeys and workflows. Customer-facing disruption. If you're migrating widget code, custom email addresses, or live chat embed, there's a brief window where customers see friction (widget reloads, email bounces, chat unavailability). This isn't Intercom's fault—it's inherent to support platform switching. But it's real cost, and it should factor into your ROI calculation. Data portability: what Intercom actually gives you Intercom does allow data export, but scope matters. You can export: Conversations (with timestamps and participant info), contact records, and article text. Intercom also publishes an API, so you can programmatically pull data during cutover. You cannot export: Custom attributes in their original logic (you get the data, but not the rule set that populated them). Routing rules or workflow automations don't export as templates; you rebuild them in the new system. Read-receipts and typing indicators are dropped (data only, not logic). The upshot: your conversation history and contact list are yours. Your configuration and workflows are not. This is standard across SaaS platforms, but it's worth knowing before you commit to the switch. Where to go if you're priced out Your alternative depends on what you actually use Intercom for. Be specific: If you need unified support messaging (email, chat, social in one inbox): Look at unified messaging platforms tha