What SuperBot does on Spree Commerce
SuperBot adds a support agent to a Spree Commerce storefront with a single snippet in your layout - no engine to install, no Rails upgrade to plan around, and no coupling to your Spree version.
- No Spree extension means nothing to keep compatible when you upgrade Spree or Rails.
- A Deface override keeps the change out of your forked views, which suits teams running close to upstream.
- Answers are grounded in your storefront content, so they stay correct as the catalogue changes.
- Client-side only, so it adds no load to your Rails application or database.
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 Spree Commerce
Your storefront layout before the closing body tag, either directly in the view or via a Deface override. Deploy as usual and precompile assets if your pipeline requires it.
- Sign up for SuperBot (free) and create your workspace.
- Add your storefront URL so SuperBot can crawl products and content pages.
- Add the SuperBot snippet to your storefront layout before the closing body tag - either directly in your layout view or through a Deface override if you prefer not to fork the view.
- Deploy as you normally would, and precompile assets if your pipeline requires it.
- 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 Deface override keeps the change out of a forked view, which is safer across Spree upgrades.
- Headless storefronts need the snippet in whatever front end renders the HTML, not in the Rails app.
- Content-Security-Policy configured in Rails must allow superbotapp.ai.
- 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.