What SuperBot does on Adobe Commerce (Magento 2)
SuperBot adds a customer-support AI agent to an Adobe Commerce or Magento 2 storefront - answering catalog, shipping, and returns questions from your own store content, capturing B2B leads, and escalating to your team with the full thread attached.
- Grounds answers in your real catalog content rather than a separate knowledge base nobody maintains.
- Multi-store friendly: the snippet is configured per store view, so each brand can have its own agent.
- Handles the long B2B questions Magento merchants actually get - bulk pricing, lead times, tax exemption - and captures them as leads.
- Escalation carries the whole conversation, so an agent never asks the customer to repeat themselves.
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 Adobe Commerce (Magento 2)
Content → Design → Configuration, edit the theme for the relevant store view, then HTML Head → Scripts and Style Sheets. Flush the cache under System → Cache Management, and run a static content deploy if you are in production mode.
- Sign up for SuperBot (free) and create your workspace.
- Add your storefront URL so SuperBot can crawl category pages, product pages, and CMS policy blocks.
- In the Magento admin, go to Content -> Design -> Configuration, edit the theme for your store view, and open HTML Head -> Scripts and Style Sheets.
- Paste the SuperBot snippet, save, then flush the cache under System -> Cache Management.
- Approve the agent's first answers so they become your canonical replies, then 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.
- Magento serves per store view — a snippet added to one view will not appear on another.
- Production mode caches aggressively; a missing flush is the most common reason the change seems not to apply.
- JS bundling or minification can interfere; exclude the SuperBot script if the launcher does not render.
- 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.