The Short Answer
A WhatsApp chatbot connected to your store is priced on what it has to do and how much outbound messaging you run, not on a flat rate. Meta charges separately for messages, but far less than most retailers expect, because replying to a customer who messaged you first is free.
That last point is the one worth understanding before you buy anything. Meta's own developer documentation is clear: when a customer messages you, a service window opens and your replies inside it cost nothing. You are charged for template messages you send to start a conversation. Get that the right way round and a support chatbot on WhatsApp is remarkably cheap to run.
For a fixed quote on what this would look like for your store, book a free discovery call at /contact.
How Meta Actually Charges
WhatsApp moved to per-message pricing on 1 July 2025, replacing the older per-conversation model, which Meta has since deprecated. Under the current rules you are charged when a template message is delivered, and the rate depends on the template category, the recipient's country calling code, and volume for some categories. Check Meta's own current rate card for the countries you actually message, since it changes and varies by market.
There are three paid categories and one that mostly is not:
- •Marketing templates are always charged. This is the promotional message, the sale announcement, the "we miss you".
- •Utility templates are charged only outside an open service window. Order confirmations, delivery updates, appointment reminders.
- •Authentication templates, such as one-time codes, are charged outside a service window.
- •Service messages, meaning ordinary replies inside an open customer service window, are free. So are all non-template messages inside that window.
Meta also documents a free entry point: conversations started from a Click-to-WhatsApp advert or a page call-to-action button carry a 72-hour free window.
The practical consequence is that the cost of a WhatsApp chatbot is almost entirely determined by how much outbound messaging you do. A bot that answers questions costs very little. A bot that chases every abandoned basket with a marketing template can run up a meaningful bill.
What This Means in Practice
| What the bot does | Who starts it | Meta charge | Practical reality |
|---|---|---|---|
| Answers "where is my order" | Customer | Free | Effectively nil |
| Answers sizing and stock questions | Customer | Free | Effectively nil |
| Sends the delivery update | You, utility template | Charged outside a service window | Small, scales with order volume |
| Sends the one-time code | You, authentication | Charged outside a service window | Small |
| Sends the sale announcement | You, marketing | Always charged | The line that grows with list size |
Rates vary by the recipient's country, so a UK-only customer base and an international one are not the same calculation. Check the current rate card for the countries you actually message rather than assuming one figure applies everywhere.
Where It Earns Its Money in Retail
Order status without a ticket. Most retail support is the same question. A bot connected to your store answers it from the live order record, in the app people already have open, and Meta charges nothing because the customer started it.
Returns inside your policy. Within rules you set, a value threshold and a returns window, the bot can start a return itself and only escalate what falls outside.
Sizing, stock and specification. The questions that stop a purchase. Answering them in the moment is worth more than answering them well tomorrow.
Delivery updates people actually read. A utility template lands where email does not, and the reply comes back to a bot rather than an inbox nobody watches.
Recovering the basket, carefully. This works, and it is the one place to be disciplined, because it is outbound and therefore charged. One well-timed message that answers the question that stopped the purchase beats three that do not.
More on the wider retail picture is at /industries/ecommerce.
What Sets the Build Cost
A WhatsApp chatbot's build cost tracks the same drivers as any of our chatbot tiers, set out in full at /services/ai-chatbot-development: whether it is answering from documents alone, or connected to your store, CRM or helpdesk, or taking multi-step actions across several systems. A WhatsApp bot for a retailer almost always sits in the middle of that range, because the value is in the connection to live order data rather than in the conversation itself. A bot that cannot see the order can only tell people to check their email. Running costs then sit on top of the build, and Meta's message fees sit on top of that again, driven by how much outbound messaging you actually send.
WhatsApp, Web Chat or Email?
Most retailers end up running more than one, so the useful question is what each is genuinely best at rather than which to pick.
Web chat catches people mid-purchase, on the product page, at the moment doubt arrives. It is the highest-intent channel you have, and no platform charges per message on it. Its weakness is that the conversation dies when the tab closes.
WhatsApp wins after the purchase. The thread persists, the customer already has the app, and the notification actually gets seen, which is why delivery updates land there and go unread in email. It is also the only one of the three where a platform charges you to start a conversation, which shapes how you should use it.
Email remains the record. It handles attachments, long explanations and anything the customer may need to produce later, such as a returns authorisation or a receipt.
The pattern that works is web chat to convert, WhatsApp to keep people informed and answer afterwards, email for anything that needs to be kept. One bot can serve all three, and should, because the alternative is three sets of answers drifting apart from each other.
What You Need Before You Start
A WhatsApp Business Platform account, which is not the same as the WhatsApp Business app on a phone. The app is fine for a small shop answering manually; the platform is what a bot connects to.
A verified business. Meta checks who you are. Start this early, because it is the step that most often delays a launch.
Templates approved in advance. Anything you send to start a conversation needs approving, and approval takes time and can be refused. Write them before you build, not after.
A number you are willing to commit. Moving a number between platforms later is possible but tedious. Decide whether you want a new one or your existing customer service line.
The Data Questions to Settle First
WhatsApp conversations are personal data, and in retail they routinely contain order details and addresses.
Decide where transcripts are stored and for how long, and make sure your privacy notice actually mentions WhatsApp as a channel, because most retailers' notices do not. If you use conversations to train or tune anything, say so. Confirm your position with whoever handles data protection for your business; the ICO's guidance on transparency and retention is the reference point, and this is not something to work out after launch.
One practical detail people miss: customers will send things you did not ask for, including photographs and occasionally card details. Decide in advance what the bot does when that happens.
Common Mistakes
Treating it as a marketing channel first. It is a support channel that happens to allow marketing. Retailers who lead with promotion get blocked, and a blocked number is hard to recover from.
Sending a template when a reply would do. If the service window is open, an ordinary message is free. Sending a template instead means paying for nothing.
No human handover. WhatsApp feels personal, so a bot that traps someone in a loop annoys them more than a web widget would. Design the escape route first.
Ignoring the quality rating. Meta scores how people respond to your messages, and a poor rating limits how many you can send. Blocks and reports are the signal, so send less and send better.
How We Build Them
We connect the bot to your actual store, so it answers from live orders, stock and your returns policy rather than from a help article. We design the human handover before the conversation flows, set the rules for what it may do alone, and keep outbound templates to the ones that earn their fee.
For the build options in general see /blog/how-to-build-an-ai-chatbot-for-your-uk-business, and for what the storefront around it involves see /blog/ecommerce-website-cost-uk.
Want to know what this would look like for your store? Book a free discovery call at /contact.
Frequently Asked Questions
Does Meta charge for every WhatsApp message the bot sends?
No. Meta's documentation states you are charged when a template message is delivered. Ordinary replies inside an open customer service window, which is what a support bot mostly sends, are free, as are utility templates sent inside that window.
What will WhatsApp cost us per month?
It depends almost entirely on outbound messaging. A bot that answers customer questions costs very little in Meta fees because customers start those conversations. A bot sending marketing templates to a large list is a different calculation, and rates vary by the recipient's country, so the honest way to plan is to model your own expected volume against Meta's current rate card rather than rely on a generic figure.
Can the bot see our orders and stock?
Yes, and that is usually the point. We connect it to Shopify, WooCommerce, Magento or your own system so it answers from the live record. Without that connection it can only tell people to check their email.
How long does it take to go live?
Typically a few weeks for a store-connected bot. The build is rarely the constraint; business verification with Meta and getting your message templates approved are what move the date, so start both early.
What happens when someone sends something sensitive?
Customers will send photographs and occasionally card details whether you ask for them or not. We decide in advance what the bot does with those, and you should settle where transcripts are stored and for how long with whoever handles data protection for your business before launch.