SuperBot for OpenCart

01

What SuperBot does on OpenCart

On OpenCart, SuperBot goes in through the built-in Theme Editor: one line in common/footer.twig, saved as an override while the original file stays untouched. The agent answers delivery, payment, and product questions overnight from the information pages you already maintain.

• No extension to install, so nothing competes with the OCMod or vQmod modifications you already run.
• The same footer edit works on OpenCart 3.x and 4.x, because the widget is a browser script.
• The widget runs in the visitor's browser, so a shared-hosting OpenCart install carries no extra server load.
• Out-of-hours questions become leads with contact details instead of contact-form emails nobody reads until morning.

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 OpenCart

Design → Theme Editor → your store → common/footer.twig, just before the closing </body> tag. Clear the template cache (System → Settings → Server on OpenCart 4; Developer Settings on the 3.x dashboard), then hard-refresh.

• Sign up free and copy the embed snippet from the setup page.
• Add the URLs of your Delivery Information and Terms & Conditions pages, plus the product pages that get the most questions.
• In the OpenCart admin, open Design → Theme Editor, pick the store, and choose common/footer.twig.
• Paste the snippet before </body>, set the override to Enabled on OpenCart 4, and save.
• Clear the template cache (System → Settings → Server on OpenCart 4, or Developer Settings on the 3.x dashboard) and hard-refresh the storefront.

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.

• Theme Editor overrides are stored in the database, not in the .twig file, so an FTP edit to the same file and an override can disagree. Keep the snippet in one place.
• In a multi-store setup the Theme Editor edits one store at a time; add the snippet for each store.
• The Theme Editor only covers storefront templates, so the launcher never appears in the admin. That is expected.
• 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