What SuperBot does on Salesforce Commerce Cloud
SuperBot adds a grounded AI support agent to a Salesforce Commerce Cloud storefront - answering from your own published content, escalating with full context, and leaving your order and customer systems untouched.
- Read-only by design: the agent answers from published content and never needs write access to orders or customer records.
- Fits an existing release process - it is a template change, not a cartridge with its own upgrade cycle.
- Escalation carries the whole conversation into your support queue rather than a disconnected form.
- Per-site configuration suits multi-site realms where each brand needs its own voice.
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 Salesforce Commerce Cloud
Your SFRA base template, or a content asset injected site-wide, so every page inherits it. Deploy through your normal release process and invalidate page cache for the affected site.
- Sign up for SuperBot and create your workspace.
- Add your storefront URL so SuperBot can crawl published category, product, and content-asset pages.
- Add the SuperBot snippet to your SFRA storefront - typically in the base template your pages extend, or as a content asset injected site-wide.
- Deploy through your normal release process and verify on a sandbox before production.
- Review the agent's answers with your support team, then enable on production.
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.
- Verify on a sandbox before production; Commerce Cloud releases are not trivially reversible.
- Multi-site realms need the snippet per site, with a separate SuperBot workspace for each brand.
- A restrictive CSP in Business Manager will block the script until superbotapp.ai is allowed.
- 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.