Clanker Support
Docs/Migrate · Intercom
~30 minutes

Migrate from Intercom to Clanker Support

Intercom is a full platform — support, sales, and marketing. If you only use it for the support widget, Clanker Support replaces that piece at a fraction of the cost. If you rely on Intercom's CRM, campaigns, or product tours, plan to keep those or find replacements; Clanker Support is support-only by design.

Quick migration

Create an Clanker Support project, recreate your help content, and swap the Intercom messenger embed for the Clanker Support script tag. Move your team to the Clanker Support inbox for support conversations.

Remove the Intercom messenger
<script>
  window.intercomSettings = { app_id: "XXXXXXXX" };
</script>
<script>
  (function(){
    var w=window;var ic=w.Intercom;
    // … standard Intercom loader …
  })();
</script>
↓ replace with ↓
Add the Clanker Support widget
<script
  src="https://api.clankersupport.com/widget.js"
  data-project="pk_live_xxxxxxxxxxxx"
  data-brand="#111827"
  defer
></script>

Step by step

  1. 1

    Create your Clanker Support project

    Sign up, create a project, and grab your public key. Decide up front whether you're fully replacing Intercom or just the support widget — that determines what else you need to keep.

  2. 2

    Move your help content over

    Copy your Intercom Articles / help-center content into your Clanker Support knowledge base. Start with the highest-traffic topics so the bot is useful on day one, then expand.

  3. 3

    Swap the messenger embed

    Remove the Intercom messenger loader and add the Clanker Support script tag. The widget loads in a shadow DOM and inherits your brand color, so it fits your site without extra CSS work.

    Add the Clanker Support widget
    <script
      src="https://api.clankersupport.com/widget.js"
      data-project="pk_live_xxxxxxxxxxxx"
      data-brand="#111827"
      defer
    ></script>
  4. 4

    Configure escalation and your notify email

    In project settings, set the escalation threshold (how many exchanges before the bot hands off) and the notify email where escalations should land. This is your team inbox or a shared support address. When the bot can't help, the full conversation arrives there with context intact.

  5. 5

    Set up email threading (optional)

    If you want customer email replies to thread back into the widget conversation, point an inbound domain at Clanker Support and set your inbound email local in project settings. Replies then flow both ways — your team answers from the inbox, the customer sees it in the widget. No separate helpdesk required.

  6. 6

    Test, then go live

    Open your site, start a test conversation, and trigger an escalation to confirm it reaches your inbox. Once it looks right, you're done — the widget is already live for every visitor.

Concept mapping

Intercom → Clanker Support

Messenger widgetClanker Support widget (shadow DOM)
Articles / help centerKnowledge base / system prompt
Fin AIAny model via LLM Gateway
Intercom InboxClanker Support inbox
Per-seat pricingUsage-based — from $0

What to expect

Carries over

  • Help-center / Articles content (paste it in)
  • Brand color and basic widget look
  • Support conversation workflow (now in the Clanker Support inbox)

Needs a separate plan

  • CRM, contacts, and customer data
  • Outbound campaigns, product tours, proactive messaging
  • Conversation history and reporting

Want the full feature comparison first?

See exactly how Clanker Support and Intercom stack up across setup, AI, channels, and pricing before you switch.

Clanker Support vs. Intercom
Start your migration free →

Other migration guides