What SuperBot does on BigCommerce
SuperBot brings AI-first customer support to BigCommerce stores — grounded in your product catalog and published policies, with real human handoff when a customer needs it.
- Reads your BigCommerce catalog (products, variants, inventory) for grounded answers.
- Handles policy-heavy ecommerce questions (returns, exchanges, warranty) from your live pages.
- Multilingual replies for cross-border BigCommerce stores across 35 widget languages.
- Operator console for handoff — your team sees the full context the moment a conversation escalates.
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 BigCommerce
Storefront → Script Manager, as a script placed in the Footer on All pages. Save the script; BigCommerce applies Script Manager changes to the storefront without a republish.
- Sign up for SuperBot free.
- Add your BigCommerce store URL — SuperBot ingests your products, categories, and policies.
- Install via the BigCommerce Script Manager — one snippet, no theme edits.
- Configure handoff rules and approve the agent's first cited replies.
- Publish — SuperBot is live across your store.
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.
- Scripts scoped to Storefront Pages only will not load on checkout; choose All pages if you want coverage there.
- A Stencil theme with an aggressive Content Security Policy may block third-party scripts — allow superbotapp.ai.
- Preview links behave differently from the live storefront; verify on the real domain.
- 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.