SuperBot for BigCommerce

01

What SuperBot does on BigCommerce

On BigCommerce, SuperBot is a single Script Manager entry: no app to install and no Stencil theme file to edit. The agent answers pre-sale questions from the product, shipping, and returns pages you add to its knowledge, and hands anything about a specific order to your team with the conversation attached.

• Script Manager entries sit outside your Stencil theme files, so a theme update does not mean pasting the snippet again.
• The Functional consent category lets the launcher follow each shopper's cookie choice instead of loading regardless of it.
• Escalations land in one shared inbox with the whole conversation, which suits a team already answering BigCommerce order emails.
• Quote and bulk requests go to the built-in CRM or to HubSpot, Salesforce, or Pipedrive.

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 BigCommerce

Storefront → Script Manager → Create a Script, with the location set to Footer and the script applied to All pages or Storefront pages. Save the script. Script Manager output is injected through your theme's footer scripts, so there is no theme file to republish.

• Create a free SuperBot workspace and copy the embed snippet from your setup page.
• Add the URLs of your shipping, returns, and best-selling product pages so the agent learns your store's own wording.
• In the BigCommerce control panel, open Storefront → Script Manager and click Create a Script.
• Set the location to Footer, choose All pages (or Storefront pages to skip checkout), pick the Functional category and the Script type, then paste the snippet and save.
• Ask a shipping question on a live product page in a private window and review the answer before you announce it.

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.

• Storefront pages covers everything except checkout and order confirmation. Pick All pages only if you want the launcher on checkout, and note that BigCommerce only runs checkout scripts on Optimized One-Page Checkout.
• With the cookie consent banner on, a script loads only after the shopper accepts its category. Chat belongs in Functional, so a shopper who declines Functional will not see the launcher.
• On multi-storefront accounts Script Manager lives in each storefront's channel settings; add the script to every storefront that should show the agent.
• Headless Catalyst storefronts need Catalyst 1.1 or later to render Script Manager scripts, and client-side navigation can skip scripts; the snippet in the app's root layout is the simpler route.
• 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