SuperBot for Shift4Shop

01

What SuperBot does on Shift4Shop

Every Shift4Shop store has a Global Footer field under Content → Header and Footer, and that field is the whole SuperBot install. The agent answers spec, shipping, and returns questions from the pages you add, and passes order questions to your team.

• One field covers every page layout, so there are no per-template edits.
• Nothing server-side is added, so your Shift4Shop hosting and checkout are unchanged.
• Answers link back to the policy page they came from.
• Quote requests go to the built-in CRM, Slack, or a connected CRM.

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 Shift4Shop

Content → Header and Footer → Global Footer, with WYSIWYG mode off and the section enabled. Click Save at the top of the page, then reload a product page.

• Sign up for a free workspace and copy the embed snippet SuperBot gives you.
• Add the URLs of your shipping, returns, and FAQ pages, plus product pages with the specs customers ask about.
• In the Shift4Shop admin, go to Content → Header and Footer and switch the Global Footer field out of WYSIWYG mode.
• Paste the snippet into the Global Footer, make sure the section is enabled, and click Save.
• Review a few answers on a live product page before you send traffic to 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.

• Turn WYSIWYG mode off before pasting; the visual editor is not meant for script tags.
• A saved but disabled Global Footer renders nothing, so check that the section is enabled.
• Use the Global Footer rather than the Global Header or banner areas: Shift4Shop recommends it for scripts because it appears on every page regardless of layout.
• 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