SuperBot for Volusion

01

What SuperBot does on Volusion

On a Volusion V1 store, SuperBot goes into your theme's template file through Design → File Editor: one line before </body>. The agent answers shipping, returns, and product questions from pages you choose, so a long-running store gets AI support without replatforming.

• Adds AI support without migrating the catalogue, URLs, or checkout you already have.
• One File Editor change covers every page that uses the theme template.
• Nothing runs on Volusion's servers; the widget loads in the shopper's browser.
• Escalations arrive in the shared inbox with the whole conversation, not a one-line form.

02

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.

03

Install SuperBot on Volusion

Design → File Editor → your theme's template_x.html, on the line just before </body>. Click Save, then reload a storefront page in a private window.

• Sign up free and copy the SuperBot embed snippet.
• Add the URLs of your shipping, returns, and article pages, and paste answers to the emails you send most often.
• In the Volusion admin, open Design → File Editor and select your theme's template_x.html file (x is your theme's name or number).
• Copy the file's contents to a text file as a backup, paste the snippet on the line before </body>, and click Save.
• Load a product page and a category page in a private window to confirm the launcher shows on both.

04

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.

05

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.

• These steps are for Volusion V1, which has the File Editor. On other Volusion versions without template access, email [email protected] before you start.
• The template file belongs to the theme. Switch themes and the new theme's template_x.html needs the snippet again.
• Volusion asks you to back up a file before editing it and will not repair custom-code changes, so keep that copy.
• 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.

06

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.

Common questions