Migrate from Fin to Clanker Support

Quick migration

Stand up an Clanker Support project, recreate your answer content, and replace the Intercom/Fin messenger embed with the Clanker Support script tag. Your existing helpdesk data stays where it is.

<script>
  window.intercomSettings = {
    api_base: "https://api-iam.intercom.io",
    app_id: "XXXXXXXX",
  };
</script>
<script>
  // Intercom messenger loader (Fin runs inside this)
  (function(){ /* … intercom snippet … */ })();
</script>

<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 and create a project. You'll get a public key for the widget. Because Clanker Support is a standalone widget + inbox, you don't need to keep paying for the surrounding Intercom platform unless you use it for other things.

2. 2

   Recreate your answer content

   Fin draws on your help center and configured content. Copy your core help-center articles and FAQs into your Clanker Support knowledge base. You don't need to migrate everything — start with the topics that drive the most conversations.

3. 3

   Replace the messenger embed

   Remove the Intercom messenger loader (Fin lives inside it) and add the Clanker Support script tag. If you're keeping Intercom for other workflows, you can run them side by side during a transition and remove the messenger once you're confident.

   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

Fin → Clanker Support

What to expect

Other migration guides