WhatsApp chatbot for e-commerce: you're writing inside someone's phone
The widget on your site and the assistant on WhatsApp look like the same thing with two different skins. They aren't. On your site the customer came to you and knows where they are. On WhatsApp you walked into the app where that person hears from their family, and that changes three concrete things — one of which, from August 2026, is a legal obligation.
TL;DR
- From 2 August 2026, Article 50 of the AI Act requires telling people they're talking to an AI system. On WhatsApp that's the most visible obligation you have.
- A disclosure done well is said once per conversation, not stapled to every message like a legal footer.
- On WhatsApp you can't message first whenever you like: outside the conversation window you need pre-approved messages.
- Human handover isn't one feature among others: on WhatsApp the customer expects a person, and they can tell.
1. You have to say it's an AI
This isn't a matter of style, it's Article 50 of the European AI regulation, applicable from 2 August 2026: people interacting with an AI system must be informed of it, unless it's obvious. On your site, inside a little window labelled "assistant", what counts as obvious is arguable. Inside WhatsApp, in a chat identical to the one with your sister, nothing is obvious.
The wrong way to comply is to staple "AI-generated reply" onto every single message: it becomes noise, people stop reading it, and the conversation reads like it was written by a legal department. The right way is to say it once, at the start of the conversation, and then behave accordingly — which means not pretending to be a person if someone asks.
If you're evaluating a vendor, ask to see it: is the disclosure there, on by default, and impossible to switch off from the panel? If that switch exists, someone has built the button that puts you out of compliance.
I've written about it in full here: what changes on 2 August 2026 and the transparency obligation for chatbots.
2. You can't message first whenever you like
This is the rule that surprises anyone coming from email and SMS. On WhatsApp, once enough time has passed since the customer's last message, you can no longer write to them freely: you need messages whose text was approved in advance, and each send has a cost.
Two practical consequences, and they matter:
- Cart recovery isn't free. Every deck puts it in the feature list; few mention that each out-of-window message is paid for and has to be approved first.
- Replying fast is worth double. While the conversation is open you can write freely. That's an excellent reason to answer quickly, and a terrible reason to answer badly.
3. On WhatsApp, handover is the main feature
On your site, if the assistant doesn't understand, the customer closes it and opens their email. On WhatsApp they stay there, and rephrase the same thing, and get annoyed — because they're using the app where answers come from people.
So the question to ask isn't "is there a handover?", it's:
- Does the operator see the whole conversation or start from nothing?
- Does the customer notice that they're now talking to someone else?
- When the operator is done, does the assistant resume, or is the chat manual forever?
Those three answers together separate a product built for WhatsApp from a widget with a phone number bolted on.
What you need to switch it on
- A number on WhatsApp Business — preferably not the one you use for family photos, for the same reasons you wouldn't use your personal email for support.
- The catalogue connected: without it, the assistant speaks in generalities, and on "do you have it?" generalities are invention.
- The disclosure enabled before going live, not after.
- A written rule for when it hands over to a human: which words, which topics, which hours.
FAQ
Do I need a dedicated number?
You need a number on WhatsApp Business. It can be the one you already use for the shop, but bear in mind it becomes a support channel, with hours and expectations attached.
Are stock and prices up to date?
Up to date as of the last catalogue sync, not in real time. I've explained why, and how to choose the frequency, in the WooCommerce guide: it holds identically on WhatsApp.
Do I really have to say it's an AI?
Yes, from 2 August 2026 — and in a channel like WhatsApp it's also the sensible thing: a customer who works out on their own that they've spent ten minutes talking to a machine doesn't come back.
Can I use the same assistant on my site and on Telegram?
Yes, if there's a single knowledge base. On Telegram, though, quite a lot changes under the bonnet: I've written about it here.
ShopBrain answers on your site, WhatsApp and Telegram from a single knowledge base, says it's an AI on the first reply of each conversation, and hands over to an operator who sees the whole history. If you're still choosing, continue with how not to get fooled by fake AI chatbots.
Related articles
- When the posting and the interview describe different rolesA hiring process produces four documents — the posting, the technical exercise, the final interview, the rejection email — and each says something different about the real role. How to read them before investing weeks.
- When the interview measures a conflict that isn’t yoursIt wasn't the first time I'd seen this pattern at a large, well-run company: whoever writes the posting wants one thing, whoever evaluates you needs another. How to spot it before you sign.
- The worst bug does not break the feature. It breaks the view26 tools connected and working in production, the dashboard showed zero. The bug had been there for months for another product too, and nobody had seen it because whoever could notice had admin permissions.