PrestaShop Chatbot Module: Free AI Chat for 1.7 and 8 (Complete Guide)

Search for "PrestaShop chatbot" or "PrestaShop live chat" today and the results tell a consistent story: integration pages from Crisp and Smartsupp, paid listings on the PrestaShop Addons marketplace, and "Top 10 PrestaShop live chat modules" listicles ranking the same handful of commercial products. What is conspicuously missing is a straightforward answer to the question most PrestaShop merchants are actually asking: how do I get a capable AI chatbot on my store without adding another monthly subscription or a marketplace purchase?

That gap exists for structural reasons. PrestaShop is self-hosted, open-source e-commerce, favored by merchants (heavily in Europe) who chose it precisely to avoid platform fees. Yet the chat ecosystem around it is dominated by per-seat SaaS pricing and one-time Addons purchases that commonly run from tens to a few hundred euros. Merchants end up with a strange choice: pay recurring per-agent fees for tools built primarily for human-staffed chat, buy a static module, or go without.

This guide covers a third route: the free, open-source Conferbot module for PrestaShop 1.7 and 8. It is a standard zip-installed module - upload, paste your Chatbot ID, flip a switch - that puts a full AI chatbot with live chat handoff on your storefront. And because PrestaShop renders pages server-side, the module does something the generic paste-a-script approach cannot: it automatically passes the logged-in customer's identity and their live cart context (total and item count) to the bot, so you and your agents see who you are talking to and what is in their basket before you type a word.

As with every Conferbot platform integration, there are two install paths, and this guide covers both:

Path 1: The module. The full experience - zip install, a two-step configure screen, per-page-type visibility controls, and automatic customer/cart context. This is the right choice for almost everyone.

Path 2: The direct template embed. Pasting the standard widget snippet into your theme's footer.tpl. Useful for developers, staging experiments, or heavily customized themes, at the cost of the context injection and the admin UI.

Everything here works on the free Conferbot plan, and you can trial the whole thing before creating an account using the public demo bot ID 691c970890527a0468f9b2c9. The quick overview lives on the Conferbot for PrestaShop channel page, and the condensed technical reference is in the developer portal's PrestaShop guide. What follows is the complete walkthrough.

Before installing, the checklist is short:

• PrestaShop 1.7 or 8.x. Both major supported branches are covered by the same module.
• PHP 7.2 or newer. Any hosting that runs a current PrestaShop already satisfies this.
• A Conferbot account with a published chatbot - or no account at all if you start with the built-in demo bot, which the configure screen offers as a one-click fill.

Notably absent from that list: API keys, workspace IDs, cron jobs, database configuration, and theme edits. The only credential the module ever needs is the Chatbot ID, the 24-character identifier of your bot. The widget resolves everything else server-side from that ID at runtime.

What the module does, mechanically

It is worth demystifying, because "chatbot module" can mean anything from a full chat backend to a glorified script tag. The Conferbot module hooks PrestaShop's displayHeader and injects the standard Conferbot loader snippet into your pages - the same two-script embed used on any website - but with a crucial addition. Because the module runs inside PrestaShop, it builds an options object at render time containing:

• The logged-in customer's identity (id, name, email) when a customer is signed in, so conversations in your Conferbot inbox arrive pre-identified.
• Store and cart context: platform (prestashop), store name and URL, the active language and currency, plus the visitor's current cart total and item count.

All of that becomes the visitor's context in Conferbot chats. When someone with a 240 euro cart asks "can I still change my shipping address?", your agent sees the name, email, and cart value alongside the conversation. That single feature changes how you prioritize and answer chats, and it is only possible because the module renders inside PrestaShop rather than being pasted on top of it.

What the module deliberately does not do

Two honest boundaries. First, the module contains no appearance settings: widget colors, position, theme, language, greetings, auto-open behavior, proactive prompts, and URL exclusions are all configured in the Conferbot dashboard under Customize and delivered to the widget at runtime. The module does not duplicate those controls, which keeps it small and means dashboard changes apply instantly without touching PrestaShop. Second, outbound webhooks - order status pushes, product sync, abandoned-cart events flowing from PrestaShop into bot flows - are not part of the current version. The context flows one way, from the storefront page into the conversation. If a module promises deep two-way order automation, check the fine print; on Conferbot's side that is roadmap, not shipped, and we prefer to say so.

The module itself is open source under the Academic Free License, with a test suite covering the ID parsing, page-type mapping, visibility rules, and the safety of the JSON it inlines into your pages.

Installation follows the standard PrestaShop module flow and takes about five minutes end to end.

Step 1: Get the module zip

Download the packaged conferbot.zip from the module's release page (linked from the developer portal guide). If you build from source instead, note the packaging rule that trips people up: the zip must contain a top-level conferbot/ directory, not the bare files.

Step 2: Upload it in the Module Manager

In your PrestaShop back office, go to Modules > Module Manager > Upload a module and drop in the zip. PrestaShop installs it in place. Two alternatives for other workflows: copy the conferbot/ folder into your shop's /modules/ directory and install from the Module Manager list, or use the CLI on PrestaShop 8: bin/console prestashop:module install conferbot.

Step 3: Configure - two steps, genuinely

Click Configure on the installed module. The screen asks for exactly two things:

Paste your Chatbot ID. In the Conferbot dashboard at app.conferbot.com, open your bot and go to Share > Embed into website; the Bot ID is the 24-character hex code. You can paste the bare ID, the entire embed snippet, or even the dashboard URL - the module extracts the ID from any of them, so there is no way to get this step wrong by copying "too much".

Flip the switch and save. The master toggle turns the chat on. Save, open your storefront, and the chat bubble is live. The module's demo recording clocks this at about 30 seconds once the zip is uploaded.

No Conferbot account yet? Click "Try our demo bot" on the configure screen. It fills in the public demo bot (691c970890527a0468f9b2c9), which works out of the box, so you can watch a real bot answering on your actual storefront before signing up for anything.

Step 4 (optional): The advanced settings

Behind the basic two-step flow sit a few advanced options worth knowing about:

• How the chat appears: floating chat bubble (default) or a popup window.
• Show on these pages: per-page-type visibility - home, category and search pages, product pages, cart, checkout, customer account pages, and everything else, each individually switchable. The common patterns: everything on except checkout (zero distraction at payment), or product-and-cart only (chat exactly where purchase questions happen).
• Widget script URL: leave as the Conferbot CDN unless you are pointing a staging shop at a staging widget build.

Step 5: Verify the context injection

The step most guides skip, and the one that proves the module's real value: log into your storefront as a test customer, add something to the cart, and start a chat. Then open your Conferbot inbox. The conversation should show the customer's name and email plus the store and cart context. If you see that, everything is wired correctly - your future chats arrive with the information a human agent actually needs.

Every Conferbot integration keeps a no-module escape hatch, and on PrestaShop that is pasting the standard snippet into your theme. This is the canonical embed, identical to what you would put on any website:

<script src="https://cdn.conferbot.com/dist/v1/widget.min.js" async></script>
<script>
  window.ConferbotWidget('YOUR_BOT_ID', 'live_chat');
</script>

Replace YOUR_BOT_ID with your bot's ID (or the demo bot ID 691c970890527a0468f9b2c9 for a quick test). The first tag loads the widget bundle asynchronously from the CDN so it never blocks rendering; the second boots it.

How to add it to a PrestaShop theme

Step 1: Locate your active theme's footer template: /themes/YOUR_THEME/templates/_partials/footer.tpl on 1.7/8 classic-style themes (the exact path varies with custom themes).

Step 2: Paste the snippet at the end of the file, so it lands just before the closing of the page body.

Step 3: Clear the PrestaShop cache (Advanced Parameters > Performance > Clear cache) - Smarty caches compiled templates, and skipping this step is the number-one reason a fresh embed "does not work".

Step 4: Reload the storefront and confirm the bubble appears.

What you give up versus the module

• No automatic customer or cart context. The static snippet knows nothing about PrestaShop. You can reproduce the context yourself by templating Smarty variables into a user and customData options object on the ConferbotWidget() call - the options shape is documented on the developer portal - but at that point you are hand-maintaining what the module does for free, with your own escaping bugs to find.
• No per-page-type visibility switches. You would wrap the snippet in Smarty conditionals instead.
• Theme-coupled. Update or switch your theme and the snippet vanishes with the old files. Module installations survive theme changes.
• No admin UI. Changing the bot ID means editing a template file and clearing cache again.

When the direct embed is the right call anyway

Three legitimate cases: a developer testing widget behavior on a staging theme without touching the module list; a store whose deploy process forbids third-party modules but permits theme code; and heavily customized or headless-ish setups where the theme is already the integration point for all third-party tags. For everyone else, the module is strictly better. The general technique - and equivalents for other platforms - is covered in how to add a chatbot to any website.

A chatbot on a PrestaShop store can run the standard e-commerce playbook - FAQ deflection, order-status triage, lead capture - but the module's automatic context unlocks a few patterns that generic embeds cannot match. Start with these.

1. Agent-side triage by cart value

The quiet superpower. Every incoming chat in your Conferbot inbox carries the visitor's cart total and item count. When three chats arrive at once, the one from a signed-in customer with a 300 euro basket is not the same priority as an empty-cart policy question - and now you can see the difference before opening either. For small teams staffing chat between other tasks, context-based triage is worth more than any bot feature.

2. Checkout-hesitation rescue on cart and product pages

Use the per-page-type visibility to make chat unmissable exactly where hesitation happens: product, cart, and (if you choose) checkout pages. Pair it with a dashboard-configured proactive prompt on the cart page - "Questions about shipping or payment? Ask here" - and the bot fields the classic pre-purchase blockers: delivery time to a specific country, payment methods, voucher problems, size and compatibility doubts. These are the conversations that convert directly, and the agent answering them already sees what is in the basket.

3. Order questions without the identity dance

When a signed-in customer asks about an order, the conversation already carries their name and email - no "can you confirm the email on the account?" round-trip. The bot flow asks only for the order reference, and a human picking up the thread has everything needed to check the back office in one step. For guests, the bot falls back to asking for order reference plus email, which doubles as verification.

4. Multilingual and multi-currency stores

PrestaShop's international strength carries into the context: the module passes the active store language and currency with every conversation. Route flows by language, answer in the visitor's language, and let agents see which storefront locale the customer was browsing - useful for stores serving several EU markets from one installation.

5. FAQ and policy deflection, trained on your content

The unglamorous volume-eater. Feed the bot your delivery, returns, and payment pages so it answers routine questions in your voice around the clock. European shops especially see heavy "do you deliver to X and what does it cost" traffic that a knowledge-trained bot clears completely. The broader flow-design playbook is in our e-commerce chatbot guide.

6. After-hours capture

Outside business hours the bot answers what it can and captures email plus question for the rest, so mornings start with structured, answerable messages instead of missed chats. If the same bot also runs on your WhatsApp or Messenger channels, all of it lands in one inbox - the multichannel angle is covered in WhatsApp chatbots for e-commerce.

The Conferbot PrestaShop integration splits configuration between two places by design, and knowing which is which saves you from hunting for settings that are deliberately not where you expect.

In the PrestaShop module (placement and wiring)

• Chatbot ID - which bot runs on the store.
• Master on/off switch.
• Bubble vs popup presentation mode.
• Per-page-type visibility - home, category/search, product, cart, checkout, customer account, all other pages. This is PrestaShop-aware logic (it maps PrestaShop controllers to page types), which is why it lives in the module.
• Widget script URL for staging or self-hosted widget builds.

In the Conferbot dashboard (everything the visitor sees)

Under Customize at app.conferbot.com:

• Appearance: brand color, light/dark theme, widget position and offsets, launcher style, avatar and header. Match your theme's accent color so the widget reads as part of the store.
• Conversation: welcome message, quick-reply buttons, and the flows themselves in the visual builder. For a store, a concrete greeting outperforms a generic one: "Hi! Ask about delivery, returns, or your order."
• Behavior: auto-open rules, proactive prompts, load delay, language, and disabled URLs. Note the overlap with the module's page-type switches: the module controls where the snippet renders by PrestaShop page type, while dashboard URL rules filter where the widget activates by URL pattern. Use the module switches as your primary control on PrestaShop - they are aware of the store's structure - and the dashboard rules for one-off exclusions like a specific landing page.
• Availability and handoff: business hours, away messages, and live-agent takeover settings, plus notifications so a high-value chat pings you immediately.

The practical benefit of this split: dashboard changes propagate to the storefront at runtime with no PrestaShop cache clearing, no module updates, and no theme edits. You will touch the module configure screen roughly twice in its lifetime (initial setup, and if you ever change bots); you will touch the dashboard whenever you refine the experience.

A note on performance

The injected loader is a single async script from the Conferbot CDN. Async means the browser does not pause page rendering to fetch it, so the impact on your storefront's paint metrics is negligible - a relevant point for PrestaShop shops that have invested in performance tuning. If you run aggressive front-end optimization modules that combine or defer JavaScript, see the troubleshooting section for the one interaction worth checking.

The PrestaShop chat landscape has two camps: one-time-purchase modules on the PrestaShop Addons marketplace, and SaaS chat platforms (Crisp, Smartsupp, Tidio and peers) with official PrestaShop integrations and free tiers. Here is where the Conferbot module genuinely stands relative to both - including where it loses.

Versus paid Addons modules

Commercial chat and WhatsApp-button modules on Addons typically cost a one-time fee in the tens-to-low-hundreds of euros, often with paid yearly support renewals. Their strength is that you own the license outright. Their structural weakness is that a static module cannot ship an AI backend: most are chat buttons, contact-form hybrids, or connectors to some SaaS anyway. The Conferbot module is free and open source, and the intelligence lives in the continuously updated platform behind the widget. The trade-off is the opposite of the Addons model: the module costs nothing, and the service behind it has free and paid plans depending on your volume and feature needs. If your requirement is literally "a WhatsApp click-to-chat button, no backend", a five-euro button module is honestly all you need - that is not what this guide is about.

Versus Crisp, Smartsupp, and Tidio free tiers

These are capable products with official PrestaShop modules, and their free tiers are real. The honest comparison is about where each free tier stops:

(Vendor free-tier boundaries move; treat the table as the shape of the trade-off and check current pricing pages before deciding.)

Where the incumbents win: if your store staffs chat with a human team all day, Crisp and Tidio have deeper agent workspaces, mature mobile agent apps, and years of polish on operator workflows. Smartsupp's session recordings are a genuinely useful extra. If you already pay for one of them across other sites, consolidation is a fair argument.

Where Conferbot wins: the free tier includes the thing PrestaShop merchants actually search for - a working AI chatbot - rather than gating it behind the first paywall. The module passes customer and cart context without a plan requirement. And one bot build serves your storefront and your messaging channels together. For the typical PrestaShop shop where one or two people answer chats between everything else, automation-first is the pragmatic fit.

The zero-risk test: the module installs in five minutes and the demo bot works without an account. Run it alongside a Crisp or Tidio trial for a week and keep what resolves more of your real messages. For the wider market view, see free chatbots for websites.

Between the module's test suite and real-world installs, the failure modes are well mapped. Work through these in order.

1. Upload fails or the module will not install

Check the zip structure. The zip must contain a top-level conferbot/ directory; a zip of the bare files fails PrestaShop's validation. Re-zip the folder itself, or use the pre-packaged release zip. Also confirm PHP 7.2+ and that your hosting allows module uploads (some managed PrestaShop hosts restrict the uploader - use the /modules/ folder copy method there).

2. Module installed and enabled, but no chat bubble

Run this checklist, which resolves the overwhelming majority of cases:

• Is the master switch on in the module configure screen, and is a Chatbot ID saved?
• Is the bot published? A draft or disabled bot in the Conferbot dashboard renders nothing. Test with the demo bot ID 691c970890527a0468f9b2c9: if the demo appears and your bot does not, the issue is the bot's state, not the module.
• Is the current page type enabled under "Show on these pages"? Testing on the homepage with only product pages enabled is a classic self-own.
• Did you clear the PrestaShop cache? Advanced Parameters > Performance > Clear cache. Smarty template caching is the single most common culprit after configuration changes.
• Dashboard-side rules: disabled URLs or a load delay configured under Customize apply wherever the widget runs - check them if the module side all looks right.

3. Widget appears but customer/cart context is missing in the inbox

Confirm you are testing as a logged-in customer - guests intentionally produce no user object, only the store context. If a logged-in test still shows nothing, check for a front-end optimization module (JS combination/deferral) rewriting inline scripts; whitelist the Conferbot snippet in that module's exclusions.

4. Two chat bubbles

The module plus a leftover footer.tpl snippet, or a second chat vendor's module still enabled. Pick one path; grep your theme for conferbot and check the Module Manager for old chat modules.

5. Broken layout or JS errors after install

Rare, and almost always an interaction with an aggressive optimizer or a very old customized theme. The module inlines a JSON options object that is escaped defensively (this is covered by its test suite), so the first suspect is a minifier mangling inline scripts. Exclude the snippet from combination/minification and retest.

6. Multistore setups

Configure the module per shop context as you would any PrestaShop module - select the shop in the back-office context switcher before saving, and use a different Chatbot ID per shop if you want separate bots and inbox routing per storefront (the store name and URL in the context will differentiate them in the inbox either way).

7. Uninstalling

Uninstall from the Module Manager; the hook and settings are removed cleanly. Your bot and conversation history live in your Conferbot account and are unaffected. If you used the footer.tpl path, delete the snippet and clear cache.

Still stuck? The developer portal guide tracks current known issues, and support is reachable from the dashboard.

A structural advantage of installing a platform-agnostic bot rather than a PrestaShop-only chat module: the bot you configure for your storefront is not welded to it. The Chatbot ID you pasted into the module points at a bot that lives in your Conferbot workspace, and that same bot - same flows, same knowledge base, same inbox - can be connected to your other customer channels without rebuilding anything.

Why this matters for a PrestaShop shop specifically

PrestaShop's merchant base is heavily European, and in most of those markets the customer's preferred support channel is not website chat - it is WhatsApp, with Messenger and Instagram DMs close behind for consumer brands. A store that answers well on its website but lets WhatsApp messages pile up in someone's personal phone has automated the smaller half of its support volume. Connecting the same bot to a WhatsApp Business number means the delivery-cost flow you built on day two answers identically whether the question arrives from the storefront widget or a saved contact, and every conversation lands in the one shared inbox your team already watches.

What carries over and what does not

Being precise about the seams:

• Carries over: flows, knowledge-base answers, quick replies (rendered natively per channel), business-hours behavior, live-agent takeover, and the unified inbox with channel attribution on every conversation.
• Does not carry over: the PrestaShop context injection. Customer identity and cart totals come from the module rendering inside your storefront pages; a WhatsApp conversation arrives with the messaging profile (name, number) instead. Design shared flows so they do not silently depend on cart data existing - the order-status flow, for example, should always be able to ask for the order reference.

A sensible rollout order

Get the storefront bot genuinely useful first - a bot that fumbles on your website will fumble identically on WhatsApp, but in a channel where customers expect conversational quality. Once transcripts look healthy for a couple of weeks, add WhatsApp (the highest-volume win for most European shops), then Messenger or Instagram if your audience lives there. Channel connections are configured from the dashboard at app.conferbot.com; the WhatsApp-for-commerce patterns, including proactive messaging rules and template constraints, are covered in depth in our WhatsApp e-commerce chatbot guide.

The strategic point: the module is the cheapest possible entry into a multichannel setup. Nothing about starting on PrestaShop commits you to it, and nothing about expanding later requires touching the module again.

The module gets you a live widget in five minutes; the value shows up in how you spend the following week.

Day 1: Install, demo, claim

Upload the module, verify with the demo bot, then create your free account at app.conferbot.com, build your own bot, and swap the ID. First version: greeting plus three quick replies (delivery, returns, my order) and an email-capture fallback.

Day 2: Train it on your store's reality

Feed the knowledge base your delivery-costs page, return policy, payment methods page, and the ten questions you answer most by email. Ask the bot those ten questions yourself and patch what it fumbles. This hour of work determines most of the bot's eventual deflection rate.

Day 3: Place it deliberately

Set the per-page-type visibility to your strategy (a common one: everywhere except checkout), match the widget color to your theme, and add one proactive prompt on the cart page. Set business hours honestly so the away message never over-promises.

Days 4-7: Read transcripts, tune triage

Read every conversation this week. Note where the bot dead-ended, where visitors ignored the buttons, and - the module-specific habit worth building - how the cart context correlates with the questions you get. Most stores discover that a small set of product-page questions accounts for a large share of high-cart-value chats; write flows for exactly those.

What success looks like after a month

Three numbers: routine questions resolved without you (time back), chats from carts above your average order value answered within minutes (revenue protected), and emails captured after hours (pipeline). If those move, the module has paid for itself - which, being free, it did on day one; the real question is whether it pays for your attention, and a month of transcripts answers that concretely.

Next reads when you are ready to go deeper: the e-commerce chatbot playbook for flow patterns, and the WooCommerce guide if you run mixed platforms and want the same bot across both.