Start with custom code access
Webflow sites usually add a third-party chat widget with custom code, placed in the site-wide or page-level code settings. Whether you can add code site-wide depends on your Webflow site plan, so check that before you pick a tool. A widget that cannot load on every page will not give you a consistent answer for visitors.
Once you know you can add code, decide where the chat should appear. A site-wide widget reaches every page. A page-level widget suits a marketing campaign or a single product section. Check how each tool lets you choose.
SuperBot can be added to Webflow sites, and any site can use its single embed snippet. Confirm the current installation steps on the vendor's page for your plan before you start, because a wrong install is a common reason a widget never appears.
Teach the bot from your real content
Webflow sites often hold a lot of useful content in CMS collections: service pages, blog posts, FAQs and product or pricing pages. A good bot should learn from the parts of that content that customers actually ask about, not only from the homepage.
Make a short list of the pages and documents you want the bot to use, then test the training. Write a help article with a unique phrase that appears nowhere else. Ask the bot that phrase. A bot that answers and cites the source is grounded in your content. A bot that guesses is not, and no amount of styling fixes that.
Be careful with order and account questions
A Webflow marketing site usually does not hold order data. If your business sells through a separate store or booking system, the chat needs a supported connection to answer order questions. The widget alone does not connect that data.
For marketing and lead-generation sites, the more useful question is different: can the bot capture a lead, book a call and send the details where your team works? SuperBot captures leads into a built-in CRM and shares booking links for Calendly or Cal.com. Ask us about any other connection you need before you rely on it.
Check handoff, reporting and languages
A website bot should hand a hard question to a person with the full conversation attached. Test that handoff at a quiet time of day, because that is when visitors are most likely to leave without an answer.
Reporting should show whether the bot is helping. Look for resolution rate, satisfaction, sentiment and the questions it could not answer. Those last ones are your content to-do list.
If your visitors use more than one language, check each tool's current language list. SuperBot answers in 35 languages. Test the languages your visitors use most, in your own copy, before you rely on a translation.
A short test plan
- Install the widget on a staging version of the site, or on one page of the live site.
- Ask 20 real visitor questions, including pricing, timelines, service areas and one question the bot should refuse.
- Check the answer, the source and the tone for each one.
- Book a test call through the bot, and confirm the lead reaches your team.
- Roll the widget out to more pages only after the test passes.
Price the plan you actually need
Compare the price on the plan that covers your real traffic, not the cheapest headline. SuperBot's free plan covers 200 conversations a month with no card, Starter is $25 a month for 2,000 conversations, and Pro is $60 a month with unlimited conversations. Every plan includes unlimited teammates, which matters when several people answer the inbox.
What to do this week
- Check your Webflow site plan and confirm that custom code is available site-wide.
- List the CMS pages, FAQs and documents the bot should learn from.
- Write one test article with a unique phrase, and check whether each tool answers from it.
- Run the 20-question test on a staging page and score the answers yourself.
- Book one test lead through the bot, and confirm it arrives where your team will see it.