What SuperBot does on Framer
SuperBot drops a polished, brand-matched customer-support AI agent onto your Framer site. Train on your live pages, answer visitors instantly, and capture qualified leads — all without breaking the visual integrity of your Framer design.
- Visually polished widget that respects modern Framer aesthetics out of the box.
- Lightweight install (one snippet) — no impact on Framer's strong performance.
- Lead capture can notify Slack or sync to a supported CRM or webhook.
- Multilingual native phrasing for portfolios and indie sites going global.
Before you install
The quality of the first answers depends on what a visitor can already read on your site, so publish your current shipping, returns, and contact information before training the agent. Have your site URL and one test page ready.
- Use the site that should be connected to this SuperBot workspace, not a staging copy.
- Check that your policy and product pages are written for customers rather than internal staff.
- Decide where escalations should land: the SuperBot inbox, Slack, or your existing support process.
- Copy the exact snippet from your SuperBot dashboard so the site ID routes conversations to the right workspace.
Install SuperBot on Framer
Site Settings → General → Custom Code, in the End of <body> tag field. Publish the site; custom code does not run in the Framer canvas or in preview.
- Sign up for SuperBot free.
- Add your Framer site URL — SuperBot crawls your pages and any linked policies.
- In Framer, add the SuperBot snippet via Site Settings → General → Custom Code → End of <body>.
- Tune the widget colors, radius, and avatar to match your Framer design system.
- Publish — SuperBot is live on every page.
Check that it is live
Open your site in a private window rather than the editor or preview, because most platforms only serve custom code on the published site. The launcher should appear in the lower corner within a second or two.
- Load a real published URL, not an editor preview or a password-protected page.
- Open the launcher and send a question you know the answer to, then confirm the reply cites your own content.
- Check one product or interior page as well as the home page, since templates can differ.
- If you run several languages or store views, check one page in each.
If the widget does not appear
Almost every failed install is one of four things: the change was never published, a cache is still serving the old page, the snippet carries the wrong site ID, or another script is stripping it.
- Custom code requires a published Framer site on a paid plan.
- Framer's page transitions keep the widget mounted between pages, which is expected behaviour.
- If the launcher overlaps a fixed Framer element, adjust the widget position in your SuperBot settings.
- Open your browser console and look for a blocked request to superbotapp.ai, which points at a Content-Security-Policy or an ad blocker.
- Confirm the site ID in the snippet matches the workspace you are looking at in the dashboard.
Train and test before you send traffic
Approve a small, representative set of answers before the widget meets real customers. Test the questions that normally create tickets or stop a purchase, and correct the wording once so every later answer inherits it.
- Start with the ten questions your team answers most often.
- Check that policy answers link to the live page that supports them.
- Add a trained answer for anything the agent gets wrong rather than editing the source page twice.
- Decide what should escalate immediately — refunds, complaints, anything account-specific.