Migrate from Crisp to Clanker Support

Quick migration

Swap the Crisp loader for the Clanker Support script tag and re-enter your knowledge base. Route escalations to your team inbox and you're live.

<script type="text/javascript">
  window.$crisp = [];
  window.CRISP_WEBSITE_ID = "XXXXXXXX-xxxx-xxxx-xxxx-xxxxxxxxxxxx";
  (function() {
    var d = document;
    var s = d.createElement("script");
    s.src = "https://client.crisp.chat/l.js";
    s.async = 1;
    d.getElementsByTagName("head")[0].appendChild(s);
  })();
</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, create a project, and grab your public key. Set your brand color so the widget matches your site out of the box.

2. 2

   Re-enter your knowledge base

   Copy your Crisp Helpdesk articles and any Hugo AI instructions into your Clanker Support knowledge base / system prompt. Start with the topics customers ask about most.

3. 3

   Swap the loader script

   Remove the Crisp l.js loader and CRISP_WEBSITE_ID, then add the Clanker Support script tag. The widget loads in a shadow DOM so it won't pick up or leak page styles.

   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

Crisp → Clanker Support

What to expect

Other migration guides