SuperBot for PrestaShop

01

What SuperBot does on PrestaShop

PrestaShop shops often sell in several languages, which is where SuperBot earns its place: it replies in the shopper's language from the same approved answers. The snippet goes into a child theme or a small hook-based module, so a parent theme update never wipes it.

• Replies follow the shopper's language, so a French, Spanish, and German catalogue does not need three chat setups.
• A child theme or hook-based module keeps the snippet out of the parent theme, so theme updates leave it alone.
• No SuperBot module to keep compatible across PrestaShop 1.7, 8, and 9 — the widget is a browser script.
• Wholesale and stock enquiries become leads in the built-in CRM, or go to Slack or a connected CRM.

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 PrestaShop

Just before the closing </body> tag in your child theme's layout template, or from a small module on the displayBeforeBodyClosingTag hook. Clear the cache under Advanced Parameters → Performance.

• Create a free SuperBot workspace and copy your embed snippet.
• Add the URLs of your delivery, returns, and terms of sale CMS pages — one per language version where the wording differs.
• Paste the snippet just before </body> in your child theme's layout template, or output it from a module hooked to displayBeforeBodyClosingTag.
• Go to Advanced Parameters → Performance and click Clear cache so the recompiled template is served.
• Load a product page in two languages, ask the same question in each, and review the replies.

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.

• Edit a child theme, not the parent: a child theme inherits every template and survives parent theme updates, while an edit to the parent is overwritten.
• With template compilation set to Never recompile template files, PrestaShop keeps serving the old layout; Recompile templates if the files have been updated is the safer production setting.
• The layout is shared by every language, so one edit covers them all. Knowledge sources are per page, so add the translated policy pages as well.
• If a third-party minify or defer module strips the launcher, exclude superbotapp.ai from it.
• 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