One line of footer custom code, then a widget you colour-match to your style guide. It answers from your own pages and CMS content, in 95+ languages, citing where each answer came from.
Crawl the site
Paste the domain, pick the pages
Style the widget
Your hex values, your corner
Paste the footer code
Project Settings → Custom Code
Publish
Live on every published page
<script src="https://customerbot.co/script.js" data-bot-id="YOUR_BOT_ID"></script>Project Settings → Custom Code → Footer Code
The usual choice. The tag is injected before the closing body tag on every published page, including CMS template pages and the 404.
Publishing site-wide custom code requires a paid Site plan on Webflow.
Page Settings → Custom Code → Before </body> tag
Use this when the assistant belongs on the pricing page and nowhere else, or while you are testing on a staging page before rolling it out.
Page-level code also needs a paid Site plan to publish.
An Embed element on the canvas
Rarely the right call for a launcher, but useful if you want the widget to load only when a specific component is on the page.
Embed elements are available on paid Site plans and in the Designer preview.
Webflow sites are usually built by people who care about the details, and a default-blue bubble in the corner undoes a lot of that care. All four of these take a minute in bot settings.
Set the primary, secondary and background colours to the same hex values as your Webflow style guide swatches. The widget is not trying to look like a third-party bolt-on and it should not read as one.
Launcher position and size are configurable. If your site has a bottom-right cookie bar or a floating CTA, move the launcher rather than stacking two floating elements on top of each other.
The widget has its own light and dark setting. On a site with a fixed dark palette, pin it to dark rather than letting it follow the visitor’s system preference and clash.
Bubble messages fire after a delay you set. On a design-led site the wrong tone here is more jarring than the wrong colour — write them the way the rest of the page is written.
Point the crawler at a collection list page and it follows through to the item pages, the same way a visitor would.
Services
What each service includes, and what it does not
Case studies
Sector experience questions before someone enquires
Team
Who to ask about what
Help articles
The support content you already write
Pricing page
Rates, retainers, what triggers a quote
FAQ page
Already written to stop the same questions
Custom code only runs on published pages, so the canvas and Designer preview will both look unchanged. Publish to your webflow.io staging domain and check there — this trips people up far more often than the tag itself ever does.
To publish custom code on a Webflow site, yes — custom code in Project Settings and Page Settings requires a paid Site plan. That is a Webflow constraint rather than a CustomerBot one. On a free staging site you can still build and test the assistant; you just cannot publish the tag.
No. Custom code runs on published pages and in preview of the published site, not on the Designer canvas. Publish to your webflow.io staging domain to see it.
It reads the pages your CMS renders. Point the crawler at your collection list pages and it will pick up the item pages linked from them, exactly as a visitor would. When you publish a new item, re-train that URL.
No. The widget mounts its own container at the end of the body and does not touch your DOM, so IX2 interactions, sliders and scroll animations are unaffected.
Colours, light or dark, position, size, launch animation, avatar, header title and subtitle, placeholder and welcome copy are all configurable on every plan. The CustomerBot watermark is removed on the Pro plan.
The assistant detects the language of each message and answers in it across 95+ languages, whether or not you run Webflow Localization. Your source content can stay in one language.
Crawl your staging site on the free plan and get the colours right before the tag ever reaches production.
Start free