What SuperBot does on Shift4Shop
SuperBot adds a customer-support AI agent to a Shift4Shop store - grounded in your own product and policy content, answering instantly, and escalating to your team with the full conversation attached.
- One global snippet covers the whole storefront, including category and product templates.
- Answers are grounded in the policy pages you already publish, with links back to them.
- Escalation hands over the full thread, so a customer never repeats their question.
- Client-side only - no template logic to maintain and nothing to re-apply after a theme change.
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 Shift4Shop
Your theme's global header or footer HTML field, so it loads on every page. Save the template settings and reload a storefront page.
- Sign up for SuperBot (free) and create your workspace.
- Add your store URL so SuperBot can crawl products and policy pages.
- In the Shift4Shop admin, open your template settings and find the global header or footer HTML area for your theme.
- Paste the SuperBot snippet so it loads before the closing body tag on every page, then save.
- Review the agent's first answers and 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.
- A snippet added to a single template will miss category and checkout pages; use the global field.
- Changing themes clears template-level HTML, so re-add the snippet after a redesign.
- Verify on a live product page, not only the home page.
- 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.