SuperBot for Adobe Commerce (Magento 2)

01

What SuperBot does on Adobe Commerce (Magento 2)

SuperBot works with Adobe Commerce and Magento Open Source in two layers: the widget, added through the store view's HTML Head or SuperBot's Magento 2 module, and an optional read-only store connection that lets the agent answer from your catalog and look up an order by number and email.

• Configured per store view, so each brand or language view can run its own agent.
• Catalog and order data come through a read-only integration token; nothing is written back to the store.
• Order answers need the order number and the matching email, so one shopper cannot see another's order.
• Handles the long B2B questions Magento merchants actually get - bulk pricing, lead times, tax exemption - and captures them as leads.

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 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.

• Create a free SuperBot workspace and note your Site ID.
• Add the URLs of your shipping, returns, and warranty CMS pages, and connect the store at adobe.superbotapp.ai if you want catalog and order answers.
• In the Magento admin, open Content → Design → Configuration, edit the store view's theme, and paste the snippet under HTML Head → Scripts and Style Sheets (with SuperBot's module, enter the Site ID under Stores → Configuration → SuperBot instead).
• Flush the cache under System → Cache Management so the new head is served.
• Review the first answers — try a test order number with its email too — then go live.

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.

• Design Configuration is per store view: a snippet added to one view will not appear on another, and each view can point at its own SuperBot workspace.
• Adobe Commerce 2.4.7 and later enforce a restrictive Content Security Policy on payment pages, so the launcher is blocked at checkout unless superbotapp.ai is allowlisted in csp_whitelist.xml.
• The integration token you create under System → Extensions → Integrations for the store connection never expires; delete the integration in the Admin to revoke it.
• 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.

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