Live chat for PrestaShop: choose, connect and measure

What we would do

We would check the support tools you already run before adding another inbox. The right route depends on your shop's modules, theme, consent setup, integrations, customer data, markets, languages and the people answering. Keep a working channel if it meets the need; check whether its existing settings or a better handover can solve the problem.

Start with a channel you can monitor. For a team answering between other jobs, we would offer an asynchronous route with an honest reply expectation. Choose staffed website chat when someone can stay available for the purchase questions that need it. Test a second channel only when it has a clear role and someone will watch it.

Rehearse a new widget or connector change on a staging copy with your actual theme, checkout and consent module. Use a separate test workspace where available and prevent copied customer data or test messages reaching live support. Keep the previous settings and a way to disable the new loader. Switch in an agreed window after the checks below pass, with someone watching incoming messages and responsibility for unresolved conversations left in the old inbox.

If you want a chosen connector set up and its customer journey checked, use the PrestaShop Module Installation & Configuration Service.

Choose a channel and a coverage plan

List the questions that interrupt purchases or require after-sales help. Compatibility, dimensions, stock, delivery, payment, warranty and returns can all justify a conversation. Improve product specifications and FAQs where the same question repeats.

Closing a website tab ends the live interaction, but does not necessarily delete the transcript. A provider can retain inbox history and recognise a returning browser. Off-site follow-up requires a suitable contact channel and lawful processing.

Set response expectations and business hours, including the time zone. Assign responsibility for new conversations and handovers. Check demand from enquiries in each market rather than assuming every customer uses the same app.

Evaluate placement on product, category, cart and checkout pages according to actual questions and obstruction risks. Checkout chat can help with a last question or distract from completion. Test it on your store instead of applying a universal rule.

Work through the questions your customers actually ask

A customer choosing a replacement fitting asks whether it matches their existing model. Ask for the model reference, the selected product option and a relevant photo, without unrelated personal details. Check those against the specification and send the exact matching product link, explaining any condition that affects fit. A product name in the prepared message is a starting point, not proof of the chosen combination. Add a missing compatibility note to the product page afterwards.

For an after-hours delivery enquiry, an away message should state when a person will review it. Assign the case when coverage resumes, check the actual stock and delivery information, then answer with the conditions for the customer's destination. An automatic greeting is not a useful reply or a delivery promise.

If delivery questions repeatedly interrupt checkout, identify the missing carrier, cost or dispatch information and correct it there. Test whether chat still resolves a remaining doubt; otherwise the widget is making staff compensate for an unclear checkout.

Use WhatsApp links and choose the right account model

A basic WhatsApp entry point needs no API. Use a wa.me link with the full international number in digits only, excluding the plus sign, spaces, brackets and domestic dialling prefix. URL-encode any pre-filled message, following WhatsApp's click-to-chat instructions.

A theme or custom module can render the current product name into the text parameter. The following Smarty example illustrates a product-page link with an example number:

<a href="https://wa.me/447700900123?text=Hi%2C%20a%20question%20about%20{$product.name|escape:'url'}">Ask about this product</a>

Use the business's actual registered number and test the result on a phone and desktop. Confirm the decoded product name is correct. Do not include private customer data in the URL or pre-fill. A customer still chooses whether to send the message.

Choose the API from requirements such as integrations and routing, not an invented conversations-per-day threshold. Budget Meta charges separately from inbox subscriptions, seats and partner fees. The current rate card distinguishes service, utility, marketing and authentication messages by category and destination. A 24-hour service window is not a blanket exemption for marketing charges.

For back-office control of the storefront button, WhatsApp Chat Integration uses your phone number and prepares the product name and page address. Configure the message for each language, page coverage, position and mobile visibility. These button settings do not supply an API inbox or automated order lookup.

Use current Messenger entry points

Use a tested m.me link to your business Page or a currently supported service connected to Messenger. Remove old Chat Plugin SDK loaders and obsolete whitelist troubleshooting from your installation plan.

Verify that messaging is enabled for the Page and that the link reaches the correct business. Test an authenticated user and a user who is signed out. Messenger requires a Messenger account; an Instagram login is not interchangeable. Eligible European users can use a standalone Messenger account without linking Facebook information, as described in Meta's account-choice announcement.

Keep an alternative contact route for people who do not want to use Messenger. Give more than one authorised colleague access to the business inbox and define retention and export needs. Provider-hosted conversation history is not automatically part of your PrestaShop order records.

Use the supported link mode in Messenger Chat Integration, configured with your numeric Page ID. Check that the destination still belongs to your business after any Page or account change.

Compare Tawk.to, Tidio and Crisp by the actual limits

Plan comparison dated 27 October 2026. Recheck them before subscribing, including tax, billing currency, annual commitments and usage definitions. A trial can temporarily expose features absent from the lasting free plan.

Check Tawk.to add-ons and AI Assist billing, Tidio's allowances and Tidio's separate usage meters, and Crisp's plan comparison.

Tawk.to lets visitors start without registering, but that does not make the processing anonymous. Its cookies and storage recognise returning browsers. Its hosting information describes US storage at rest and selectable storage locations as future work.

Compare assignment, mobile apps, file handling, transcript access, contact profiles, exports, retention and integrations using your own support tasks. Measure each widget's performance with the actual bot, language and tracking configuration; there is no fixed weight ranking.

Before choosing a plan, ask what happens when each allowance runs out: whether live replies, automated answers or profile collection stop, what staff see, and whether an upgrade or extra usage is charged. Check the lasting plan after a trial ends and keep an alternative contact route available.

Provider-specific installation and supplied shop context differ. Check the installed release and enabled data settings against these integration help pages:

Connect chat without losing performance or messages

Use a supported module or a maintained custom integration. For custom code, displayBeforeBodyClosingTag is an appropriate storefront hook when your theme renders it. In Classic, the layout calls that hook; the footer partial does not itself contain the closing body tag.

Inventory existing module, theme and tag-manager snippets so you do not load the same widget twice. Limit loading to the pages where you need it, using only the page combinations the integration actually supports. Test each shop and language separately.

A footer hook, asynchronous script and timer do not guarantee execution after first paint. A visibility delay hides markup; it does not by itself defer downloaded assets. An interaction-triggered loader can postpone injection, but its timer fallback, network work and JavaScript still affect the page. Consent gating is a separate requirement.

1. Record representative product, category and checkout measurements without the widget.
2. Repeat with the widget and its real trigger. Check network requests, transferred bytes, long tasks, LCP and responsiveness.
3. Test opening chat on a mid-range phone, including keyboard focus and close controls. Follow an app handoff and return to the shop; confirm the cart and selected product option remain usable.
4. Check that the launcher does not cover add-to-cart, consent controls or payment buttons.
5. Test offline hours, agent notifications and the destination of a submitted offline message. Have the intended agent receive and answer it, rather than accepting a successful-looking submission as proof.
6. Test first visits, consent refusal, acceptance and withdrawal against your intended loading rules. Inspect remote requests and customer fields as well as the visible launcher.
7. Repeat after signing out, switching language and revisiting another page. A previous customer's name, the wrong workspace or duplicate welcome messages indicate a context or loader fault to resolve before launch.

A hosted widget's offline form normally sends to its provider. It does not automatically create a PrestaShop support thread. The native contact form can create threads under Customer Service → Customer Service; forwarding from another service requires an integration.

Order-aware chat requires more than a launcher. Check what the installed connector already supplies before commissioning extra access. A custom integration can read authorised PrestaShop order data through the webservice or another supported interface. Keep credentials server-side, grant minimal permissions and verify the customer's identity before revealing order details.

Handle privacy and daily operations

A locally rendered plain link does not itself load a third-party chat tracker. Clicking it takes the customer to another service. Incoming conversations already involve personal data, so disclose the channel, purposes, lawful basis, recipients and retention from the start.

Do not describe a customer-initiated message as automatic GDPR consent. Requested support or a pre-contract enquiry can have another appropriate basis. Assess marketing rules and WhatsApp opt-in requirements separately from service replies, and follow WhatsApp's business policy.

For embedded services, identify cookies, local storage and remote requests. Obtain prior consent for nonessential trackers. Strictly necessary storage for a service explicitly requested by the visitor can qualify for an exemption; assess its actual purpose under applicable rules. CNIL's cookie guidance explains the distinction. A loader alone does not make the whole channel compliant.

Check provider roles, processing agreements, subprocessors, international transfers, access controls, deletion and export. Define a justified retention period instead of keeping every conversation indefinitely. See the GDPR guide.

Prepare accurate saved answers for shipping, returns, payments, stock and compatibility. State when you will reply outside coverage hours. Assign unresolved cases and review missed messages, outdated replies and bot escalations. Keep a human route for questions that automation cannot answer. Give saved answers an owner and check them after changes to prices, shipping rules or returns policy. Test a bot with an unknown product option and an exception to the usual policy; it should hand over rather than invent an answer.

Measure service quality and incremental value

Track conversations started, first useful reply time, unresolved cases, satisfaction, staff time and orders associated with support. Choose response targets your team can meet. No universal minute limit or order-value threshold determines whether chat is worthwhile.

UTM-tagged product links can help identify returning traffic, for example ?utm_source=whatsapp&utm_medium=chat&utm_campaign=support. They do not guarantee purchase attribution when measurement is blocked, consent is denied or the customer changes device. Reconcile analytics with an order-linked helpdesk or a careful manual tally.

Chat users choose to engage, so comparing their conversion rate with nonusers does not show how many extra sales chat caused. Use those assisted metrics to find useful topics and service problems. For causal impact, randomise chat availability or invitations across eligible visitors and compare the assigned groups, including people who never open chat.

Measure orders, contribution margin, staffing and software costs together. Include time spent checking unanswered messages and completing follow-up, not only time typing in chat. An assisted sale that would have happened anyway cannot fund an extra shift. Compare incremental contribution after product, delivery and return costs with the full cost of running the channel. Run long enough to collect a suitable sample and account for trading patterns; a fixed 30 days does not guarantee a reliable result. Keep changes to placement, invitations and staffing documented during the test.

Agree the launch and handover

Keep evidence of the tested pages, devices, languages, consent states and message destinations with the final settings. During the switch, disable the old storefront entry point without abandoning its outstanding cases. Verify a new live enquiry reaches the intended team and record who can restore the previous setup if messages go missing.

What to ask your developer or agency

• Where is the loader installed, which release was tested, and which shop and page rules decide whether it runs?
• Which customer fields leave the shop, when are they sent, and what happens after logout or consent withdrawal?
• Which account owns the number, Page or workspace, and can an authorised colleague recover access without the installer?
• Where do offline and escalated messages arrive, who checks failed notifications, and how does the next agent find an unresolved case?
• What remains in the provider after disabling or uninstalling the connector, and where are the reversal steps and settings?

Questions owners ask

Will changing providers bring the old conversation history across?

Check export and import separately before switching. Test that the destination can use the records and attachments you need. If it cannot, agree how authorised staff will access the retained history and finish outstanding cases within your retention policy.

What if customers want a call and I cannot stay on chat?

Offer a callback window you can meet. Callback Requests collects product and combination context with the requested time and keeps a shared staff queue tied to that promise.

Can agreeing a refund or delivery change in chat update the order?

Only an integration designed for that action can perform it. Otherwise assign the authorised staff workflow, record the agreement against the case or order and check the resulting refund or delivery change before confirming completion to the customer.