European alternatives to Intercom.

In-app chat widgets for support and onboarding are where Intercom built its default position among a generation of SaaS companies, but the company behind the product, Intercom, Inc., headquartered in San Francisco, is US-incorporated, with sub-processors and primary infrastructure under US jurisdiction. For a European SaaS team auditing where their customer chat logs and contact data sit, or a DACH compliance officer reviewing customer-data flows for a Schrems II transfer impact assessment, that ownership profile is what prompts buyers to evaluate alternatives.

Six European customer-messaging alternatives are verified here against Intercom, checked against who legally owns the company, where the data physically sits, which sub-processors handle conversation content, and whether the platform holds a recognised European compliance framework (ISO 27001, BSI C5, EUCS, SecNumCloud).

Three names cover most of the shortlist: Crisp is the strongest French choice (EU-owned, French-hosted, CLOUD Act exposure: Material) with multi-channel reach (France, Nantes), Userlike is the most-adopted DACH option (EU-owned, German-hosted, ISO 27001 certified) with strong German enterprise references (Germany, Cologne), and LiveChat is the larger commercial product with the deepest integration marketplace (Poland, EU-hosted, publicly listed on the WSE).

• Live chat widget for your website and product (every alternative supports this).
• Conversation threading, assignees, status, tags.
• Canned responses and saved replies.
• Contact properties with custom fields.
• Email integration (most alternatives bundle email-based ticket support alongside live chat).
• API access for sending messages from your product.
• Mobile agent apps on iOS and Android.

Where do the alternatives fall short?

• Intercom Product Tours and onboarding messaging in the same product. European alternatives have lighter onboarding features; pair with a dedicated product-tour tool if essential.
• Intercom Inbox at full feature depth (custom views, conditional routing, SLA timers). European alternatives have core inbox features but the long-tail filtering is simpler.
• Intercom's third-party app marketplace. European tools have smaller integration libraries; native and Zapier-based integrations cover the top 20 enterprise SaaS.
• Intercom AI Operator and Fin AI Agent. European alternatives mostly ship without LLM-based features by default; Crisp has an opt-in AI tier with European LLM routing.

Conversation history and saved replies are the two things worth protecting in an Intercom migration. Six steps:

1. Export your Intercom data. Settings → Data → Export lets you download Contacts, Conversations, and Companies as CSV. Take the full export, including conversation transcripts. For attachments, use the API to fetch each conversation's attached files separately before cancellation; Intercom-hosted attachment URLs become inaccessible after the account closes.
2. Audit which conversation flows are live. Most teams have 5–15 saved replies, 3–8 automation rules, and 2–5 in-product message triggers. List each one explicitly. Migrate only the live set; archive old saved replies as text snippets in your knowledge base.
3. Set up the new tool's chat widget on a staging environment. Crisp, Userlike, and LiveChat all provide a JavaScript widget that drops in alongside Intercom's. Run both on staging for 1–2 weeks; verify agent UX, widget rendering, mobile behaviour, and the unread-message badge.
4. Migrate saved replies and automation rules. All European alternatives have saved-reply and basic automation features. Recreate each saved reply by hand (typically 15 minutes per reply). For automation rules (e.g. "tag conversation as 'billing' when message contains 'invoice'"), document each rule on paper, then rebuild as native automations in the new tool.
5. Cut over the widget on production with a 24-hour rollback plan. Replace the Intercom JavaScript snippet with the new vendor's snippet across your site. Test live chat from both customer-facing pages and authenticated app pages. Keep the rollback as one config change so you can revert if anything breaks.
6. Pause Intercom instead of cancelling it, for 60 days. A Slack notification still pointed at Intercom, a custom integration writing events to the Intercom API, or an old customer email containing an Intercom-hosted attachment URL are the kind of loose ends that surface weeks later. Pause the workspace and keep paying the lowest tier for 60 days before shutting it down for good.