Documentation
Build with Clanker Support
Everything you need to drop in the widget, train it on your content, route escalations to your team, and migrate cleanly from your current support tool.
Quickstart
5 minDrop one script tag and go live in under five minutes.
Jump ↓Train your bot
ConfigPaste your knowledge base and system prompt to keep answers on-topic.
Jump ↓Escalation
ConfigHand off to your team with full context when the bot can't help.
Jump ↓Quickstart
Create a project in the dashboard to get your public key, then add a single script tag to your site — anywhere before the closing </body> tag. That's the whole integration.
<script
src="https://api.clankersupport.com/widget.js"
data-project="pk_live_xxxxxxxxxxxx"
data-brand="#111827"
defer
></script>data-project— your project's public key (starts with pk_live_).data-brand— a hex color for the widget header and primary button.shadow DOM— the widget mounts in isolation, so styles never bleed either way.
Train your bot
Your bot answers from a knowledge base you control. In project settings, paste your docs, FAQ answers, and a system prompt that sets the bot's tone and boundaries. Keep it focused — a tight, current knowledge base produces better answers than a sprawling one.
Because Clanker Support is built on LLM Gateway, you choose which model runs per project and can swap it with a config change — no code edits. Run a cost-efficient model for routine questions and a more capable one where it matters.
Escalation & inbox
Set an escalation threshold — how many exchanges before the bot hands off — and a notify email. When the bot can't resolve something, the full conversation lands in your inbox with context intact, and an alert goes to your notify address.
Your team picks it up from the unified inbox, replies, and the customer sees the response in the same widget conversation.
Email threading
Point an inbound domain at Clanker Support and set your inbound email local in project settings. Customer replies to escalation emails thread back into the widget conversation automatically, and replies you send from the inbox reach the customer by email — no separate helpdesk required.
Migrate to Clanker Support
Already running a support tool? These guides walk through the embed swap, knowledge-base re-import, and what does and doesn't carry over — step by step.
From Chatbase
~20 minutesFrom the Chatbase embed to a single Clanker Support script tag
Read the guide →From Fin
~30 minutesFrom Fin (inside Intercom) to a standalone Clanker Support widget
Read the guide →From Intercom
~30 minutesFrom the Intercom platform to a focused Clanker Support widget
Read the guide →From Chatwoot
~25 minutesFrom a self-hosted Rails stack to serverless Clanker Support
Read the guide →From Crisp
~20 minutesFrom the all-in-one Crisp platform to a focused Clanker Support widget
Read the guide →Ready to build?