Migrate from Chatbase to Clanker Support

Quick migration

Replace the Chatbase embed snippet with the Clanker Support script tag, then paste your knowledge base into your Clanker Support project. Everything else is configuration in the dashboard.

<script>
  window.embeddedChatbotConfig = {
    chatbotId: "XXXXXXXX",
    domain: "www.chatbase.co",
  };
</script>
<script
  src="https://www.chatbase.co/embed.min.js"
  chatbotId="XXXXXXXX"
  domain="www.chatbase.co"
  defer
></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 workspace, and add a project. Your project gets a public key (pk_live_…) used to bootstrap the widget. Set your brand color while you're here — the widget inherits it automatically.

2. 2

   Import your knowledge base

   In Chatbase, your bot is trained on uploaded files and text sources. Export or copy that content and paste it into your Clanker Support project's knowledge base / system prompt field. Keep it focused and current — this is your bot's working memory.

3. 3

   Swap the embed snippet

   Delete the Chatbase embed from your site and drop in the Clanker Support script tag. Replace the public key with your project's. The widget loads in a shadow DOM, so your page styles and the widget never interfere.

   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

Chatbase → Clanker Support

What to expect

Other migration guides