What SuperBot does on PrestaShop
SuperBot puts a multilingual customer-support AI agent on a PrestaShop storefront - trained on your own product and policy pages, answering in the shopper's language, and handing off to your team when a human is genuinely needed.
- Multilingual by default, which matters on PrestaShop: most shops run several language versions of the same catalogue.
- Reads your CMS pages, so shipping and returns answers stay correct when you edit the page rather than drifting out of date.
- One snippet covers every page and every language version - no per-template work.
- Lead capture routes wholesale and stock enquiries to email, Slack, or a connected CRM.
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 PrestaShop
Before the closing body tag of your child theme's footer template, or inside a custom-code module you already use. Clear the cache under Advanced Parameters → Performance.
- Sign up for SuperBot (free) and create your workspace.
- Add your shop URL so SuperBot can crawl your categories, products, and CMS pages.
- Add the SuperBot snippet before the closing body tag of your theme - either in your child theme's footer template, or through any custom-code module you already use.
- Clear the PrestaShop cache under Advanced Parameters -> Performance so the change is served.
- Review the agent's first answers, 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.
- Editing the parent theme rather than a child theme means an update can remove your snippet.
- Smarty template caching and combined JS can both hide the change until the cache is cleared.
- Confirm the snippet is on every language version, not only the default one.
- 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.