What SuperBot does on Volusion
SuperBot puts an AI support agent on a Volusion store - answering shipping, returns, and product questions from your own content, and capturing the enquiries that need a human follow-up.
- Adds modern AI support to a long-running store without replatforming.
- Answers come from your existing product and article pages rather than a separate knowledge base.
- One template edit covers the whole storefront.
- No server-side component, so nothing changes about how your store is hosted.
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 Volusion
The template file that renders your site footer, before the closing body tag. Save the file and reload a storefront page in a private window.
- Sign up for SuperBot (free) and create your workspace.
- Add your store URL so SuperBot can crawl products and article pages.
- In the Volusion admin, open the design or file editor and locate the template file that renders the site footer.
- Paste the SuperBot snippet before the closing body tag and save.
- Check a live product page to confirm the launcher appears, then go live.
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.
- Volusion's editable areas vary by store age and template; if you cannot find the footer file, add the snippet to the shared template your pages include.
- Some older Volusion templates strip unknown tags from certain fields — verify the snippet survived the save.
- Check a product page as well as the home page, since they can use different templates.
- 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.