What SuperBot does on OpenCart
SuperBot adds an always-on support agent to an OpenCart store - trained on your catalogue and policy pages, answering the questions that would otherwise sit in an inbox overnight, and capturing the leads worth following up.
- Works on OpenCart 3.x and 4.x alike, because it is a script rather than an extension tied to a version.
- Nothing to maintain through OpenCart upgrades - no extension conflicts, no vQmod or OCMod patches.
- Answers cite the information pages you already wrote, so support content and store content stay in one place.
- Captures enquiries out of hours, when most small OpenCart stores have nobody watching the inbox.
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 OpenCart
Design → Theme Editor, in your template's footer, before the closing body tag. Refresh the theme cache from Modifications or Developer Settings.
- Sign up for SuperBot (free) and create your workspace.
- Add your store URL so SuperBot can crawl products, categories, and information pages.
- In the OpenCart admin, open Design -> Theme Editor, choose your store and template, and edit the footer template.
- Paste the SuperBot snippet before the closing body tag and save.
- Refresh the theme cache from the Modifications or Developer Settings panel, 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.
- OpenCart caches compiled templates; without a refresh the old footer keeps being served.
- If you run multiple stores, the Theme Editor edits one store and template at a time.
- An OCMod or vQmod change touching the footer can override your edit.
- 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.