What is a WhatsApp chatbot for business, and which Dutch businesses need one?
A WhatsApp chatbot for business is software connected to your company's WhatsApp number that replies automatically, fetches information from your systems and passes conversations to staff when needed. You need one when the same questions arrive on WhatsApp every day and answering them by hand costs hours.
Dutch customers are comfortable messaging businesses. They ask a webshop where their parcel is, a garage when the car is ready, a physiotherapist whether Thursday is free. Many small firms answer from a single phone. That works until it does not: messages get missed at weekends, two colleagues answer the same customer, nobody can see what was promised.
A bot handles the predictable part. Order status, delivery tracking, opening hours, booking and cancelling, return instructions, simple product questions. People handle the rest, with the conversation history in front of them.
- Webshops with frequent “where is my order?” messages.
- Clinics, salons and studios that book by appointment.
- Installers and repair firms that coordinate visits.
- Restaurants and takeaways handling reservations or reorders.
- Rental, events and hospitality businesses with seasonal peaks.
A real chatbot needs the WhatsApp Business Platform, Meta's API for businesses; the free WhatsApp Business app only offers greeting messages, away messages and quick replies. Which one you need depends on volume, integrations and how many people answer.
The Business app is a phone app for small teams. It is excellent for a sole trader and costs nothing. The Business Platform, usually through Meta's Cloud API, is what lets software send and receive messages, connect to your shop or calendar, and let several staff members share one number through an inbox.
Stay on the app when
You receive a manageable number of messages, one or two people answer, and no live data from other systems is needed.
Move to the platform when
You want automatic order or booking flows, several staff on one number, template notifications at scale, or reporting on response times.
Our India-focused comparison of the WhatsApp Business app and API explains the same trade-off in more depth; the platform rules are identical in the Netherlands.
How do you set up a WhatsApp chatbot for business on Meta's platform?
Set-up has four parts: a Meta Business portfolio for your company, a phone number registered to the WhatsApp Business Platform, a verified display name, and the bot software connected through the Cloud API. We guide you through the parts that need your company documents and do the technical steps ourselves.
Everything is created under your ownership. Your company owns the Meta Business portfolio, the WhatsApp Business account and the number; we are added as a partner or user and can be removed at any time. The bot itself runs in your cloud account, usually in an EU region.
- Create or confirm the Meta Business portfolio in your company's name.
- Start business verification with your company details.
- Choose a number: a new one, or migrate the one customers already know.
- Register the display name customers will see.
- Connect the Cloud API to the bot and set up webhooks.
- Submit your first template messages for approval.
If customers already know a number from the Business app, decide early whether the bot should use that number or a new one. Meta's options for existing numbers change from time to time, so we check the current rules with you before touching anything.
How does Meta charge for a WhatsApp chatbot for business?
Since 1 July 2025 Meta charges per delivered template message rather than per conversation, with rates set by message category and the recipient's country. Replies inside the customer service window are free.
According to Meta's pricing documentation, when a customer messages you a 24-hour customer service window opens; during that window non-template messages are free, and utility templates sent within it are also free. Template categories are marketing, utility and authentication. When someone reaches you through a Click to WhatsApp ad or a Facebook call-to-action, a free entry point window stays open for 72 hours in which all message types are free.
Meta publishes rate cards in 15 billing currencies, including EUR, so a Dutch business can budget in euros. The amounts change from time to time, so we link you to Meta's current rate card rather than quoting figures. You can read the model in Meta's WhatsApp pricing documentation.
- Customer asks “where is my order?” and the bot answers: free, inside the window.
- Shipping update sent as a utility template outside any window: charged.
- Promotional message about a sale: marketing template, charged.
- Login code: authentication template, charged.
Design choices move this bill. A bot that answers customer questions costs very little in Meta fees; a bot that pushes many marketing templates costs more. We model your expected volume in the quote so there are no surprises.
What opt-in does WhatsApp require, and how does it fit the AVG?
Before you send someone template messages, Meta requires that they have given their number and opted in to messages from your business, with the business name stated clearly. For a Dutch company that opt-in also has to fit the AVG, the Dutch term for the GDPR.
Meta's opt-in guidance says businesses must clearly state that a person is opting in to receive communication and must name the business they will hear from. Opt-in can be collected on a website, by SMS, through a phone system or on paper, as long as those conditions and local law are met.
In practice we add an unticked checkbox at checkout or booking, with plain text such as “Send me order updates on WhatsApp from [your shop]”. The system stores the wording, the time and the source. Marketing messages get a separate opt-in, because customers who want tracking updates have not necessarily agreed to promotions.
- Separate opt-ins for service updates and for marketing.
- A stop keyword that works in Dutch and English.
- Opt-outs synced back to your shop or CRM.
- No purchased or scraped number lists, ever.
How you describe this in your privacy statement, and which legal basis you rely on, is for you and your adviser. Our job is to make the technical side match what you promise customers.
How should a WhatsApp chatbot handle personal data under the AVG?
Collect only what each flow needs, keep chat data in your own systems for a defined period, and restrict who can read it. The bot should know an order number and a postcode, not a customer's full history.
WhatsApp messages pass through Meta; that is unavoidable on the platform, and you should mention it in your privacy statement. What you control is everything on your side: where the bot stores conversation logs, how long, who has access, and what is sent to other services such as an AI model.
- Bot and logs hosted in an EU region in your cloud account.
- Automatic deletion of conversation logs after a period you choose.
- Staff access through named accounts, not a shared login.
- No medical, financial or ID details requested in chat unless you have decided how to protect them.
- Any AI provider listed as a processor, with data kept to the minimum needed.
Compliance stays your responsibility, confirmed by your own counsel; we build the controls. For broader privacy work on your website, see GDPR-compliant website development.
How does a WhatsApp chatbot for business handle order status and PostNL tracking?
The customer sends a message, the bot asks for an order number and postcode, looks up the order in your shop, and replies with the status and the carrier's tracking link. For shops shipping with PostNL, DHL or DPD, the tracking information comes from the carrier or your shipping tool.
This single flow often removes a large share of repetitive messages for a webshop, because “where is my order?” is the question customers ask most after buying. It also runs mostly inside the free customer service window, since the customer starts the conversation.
Shop connection
Shopify and WooCommerce both expose order data through APIs. The bot reads status, items and shipment details; it never changes an order without staff approval.
Tracking data
If your shipping tool already stores the tracking code, the bot builds the link. Where you need live scan events, we connect to the carrier's API.
Proactive updates
With opt-in, the shop can send a utility template when the parcel ships and again when it is out for delivery.
Returns fit the same pattern: check eligibility, send return instructions or a label link, and log the request for staff. The shop side of this is covered on our Shopify developer page for Dutch brands.
Can a WhatsApp chatbot for business book appointments?
Yes. The bot offers services, shows available slots from your calendar or booking system, confirms the appointment and sends a reminder, all inside the chat. Customers can move or cancel with a message instead of calling.
Service businesses in the Netherlands, from hair salons in Haarlem to physiotherapists in Nijmegen, lose time to phone tag and no-shows. A booking flow on WhatsApp shortens both. The bot reads availability live, so it never offers a slot that was just taken on the website.
- Choose a service and, if relevant, a staff member.
- See the next available slots, then pick one.
- Confirm with name and phone number, nothing more.
- Reminder template the day before, with reschedule and cancel buttons.
- Staff see bookings in the calendar they already use.
Where no booking system exists yet, we can build a small scheduling back-end as part of the project, quoted separately from the chatbot. For clinics handling health information, keep clinical questions out of the chat and route them to staff.
When should a WhatsApp chatbot for business hand over to a human?
Hand over whenever the customer asks for a person, when the bot has failed to understand twice, when a complaint or payment dispute appears, and whenever a decision needs judgement. A bot that traps customers in loops does more damage than no bot at all.
The handover must be visible and complete. Staff receive the conversation with its history in a shared inbox, the bot stops replying, and the customer is told a colleague will answer and roughly when. Outside business hours the bot says so honestly and collects details for the next morning.
Customer triggers
Typing “medewerker”, “mens”, “agent” or “human”, or tapping a “talk to a person” button.
Bot triggers
Two failed attempts to understand, low confidence in an AI answer, or a topic on your always-escalate list.
Staff controls
Take over, hand back to the bot, add an internal note, and tag the conversation for reporting.
We write your handover rules down before building, together with you, because they are really service policy rather than code.
Can a WhatsApp chatbot use AI, and what do Meta and the EU AI Act allow?
Yes, as long as the AI serves your business's own customer service or sales tasks. Meta's WhatsApp Business Solution Terms, changed in October 2025, bar general-purpose AI assistants from the platform from 15 January 2026, while task-specific bots such as customer support, order enquiries and appointment handling remain allowed.
So a bot that answers questions about your products, delivery and returns, drawing on your own FAQ and policies, is fine. A bot that will chat about anything, write poems or answer questions unrelated to your business is not what the platform is for.
In the EU there is a second rule to design for. Article 50(1) of the EU AI Act says people must be informed that they are interacting with an AI system unless that is obvious from the context. We label AI answers clearly in the first message and keep a human route available at every step.
- Answers grounded in your own content, not the open internet.
- A topic boundary: off-topic questions get a polite redirect.
- Logging of AI answers so you can review and correct them.
- A spending cap on model usage.
AI-powered bots start from US$600. Wider automation, such as triaging email and tickets, is covered on our AI automation page for the Netherlands.
How do template messages and Dutch-language flows work?
Template messages are pre-approved message formats you send outside the 24-hour window, such as a shipping update or appointment reminder; each is submitted to Meta with a category and a language. For a Dutch business, you usually need each template in Dutch and English.
We draft template structures and variables, you supply or approve the Dutch wording, and we submit them. The bot detects the customer's preferred language from their first message or a menu choice and stays in it. We do not write native Dutch copy ourselves; a Dutch speaker on your team should approve every customer-facing line.
- Keep utility templates purely informational; promotional wording can push them into the marketing category.
- Use variables for order numbers, dates and names rather than many near-identical templates.
- Add quick-reply buttons for the next likely action.
- Review templates when your delivery or return policy changes.
What drives the cost of a WhatsApp chatbot for business?
Our builds start from US$600; the quote grows with the number of flows, the systems the bot must read from, AI features and the inbox set-up. Meta's per-message charges are separate and depend on how many templates you send.
Quotes for WhatsApp chatbots vary widely between SaaS tools, local bureaus and freelancers. The honest differences are integration depth, whether a monthly per-seat fee applies, and who owns the data and the number.
- Number of conversation flows (order status, booking, returns, FAQ).
- Integrations: shop, carrier, calendar, CRM, helpdesk.
- Rule-based menus only, or AI answers on top.
- Shared inbox for staff and reporting needs.
- Languages and the number of templates.
- Expected message volume, which affects Meta's charges and hosting.
A narrow first version with one or two flows is usually the right start. You see real questions in the logs within weeks and can add flows based on evidence rather than guesses.
How does a team in India build a WhatsApp chatbot for business owners in the Netherlands?
A WhatsApp chatbot for business is built remotely, in English, with calls during your morning and early afternoon, which is our afternoon and evening in India. The time difference is three and a half hours in Dutch summer and four and a half in winter.
Because the product is itself a messaging tool, it suits remote work well. You test every flow on your own phone from the first week, send feedback in the same WhatsApp group we use for the project, and see changes the same or next day.
Accounts and ownership
Meta Business portfolio, WhatsApp number, cloud account and code are yours. We work as added users you can remove.
Payment
USD quote, paid in milestones by Wise, bank wire or PayPal, invoiced from India. Meta bills you directly for messages.
Terms
Scope and milestones sit in the written quote; wider terms are on our terms page, and anything else is agreed in writing.
First two weeks
Days 1–2: call and quote. Days 3–6: Meta set-up and verification started, flows drawn as diagrams. Days 7–14: first flow working on a test number, templates submitted.
We do not visit premises, install hardware or run your customer service. If you need someone to answer chats for you, that is a staffing question, not a development one.
What are the common mistakes with a WhatsApp chatbot for business?
The biggest mistakes are building too many flows at once, hiding the human option, and sending marketing templates to people who only agreed to order updates. All three are avoidable.
- Launching ten flows at once instead of the two that cover most questions.
- No clear way to reach a person, which frustrates customers quickly.
- Mixing service and marketing opt-ins, risking complaints and quality ratings.
- Templates written in a promotional tone, so they are categorised as marketing.
- Bot hosted on a vendor's or developer's account instead of yours.
- No monitoring, so a broken shop API silently stops order replies.
- AI answers without logging, so wrong answers go unnoticed.
Meta also rates the quality of your messaging. If many customers block or report you, sending limits can suffer, which is another reason to keep marketing volume modest and opt-ins clean.
Example: a WhatsApp chatbot for a bike webshop in Utrecht
Take a hypothetical Utrecht webshop selling bike parts and accessories through WooCommerce, shipping with PostNL. Two staff members answer WhatsApp on one phone, and most messages ask where an order is or how to return a wrong size.
Version one would have two flows. Order status: the customer sends an order number and postcode, the bot replies with status and the PostNL tracking link. Returns: the bot checks the order date against the return period, sends instructions and logs the request. Everything else goes to a shared inbox where both staff members see the history. Opt-in for shipping updates is added at checkout; marketing is left out for now.
That scope fits the build range from US$600 with a two to three week timeline. Meta charges would be limited mostly to shipping-update templates, since customer-initiated questions fall inside the free service window.
This is an illustrative scenario, not a real client. A restaurant would swap returns for reorders; the ordering side is covered in our guide to an online ordering system for restaurants.
WhatsApp chatbot for business: launch checklist
Use this before your WhatsApp chatbot for business goes live. Each item is quick to check and expensive to skip.
- Meta Business portfolio and WhatsApp account owned by your company.
- Business verification started or completed; display name approved.
- Separate opt-ins for service updates and marketing, with stored wording.
- Stop keyword tested in Dutch and English.
- Human handover tested from every flow, including out-of-hours behaviour.
- Templates approved in both languages and correctly categorised.
- Bot hosted in your cloud account in an EU region, with log retention set.
- Monitoring alerts if the shop, carrier or calendar connection fails.
- AI answers labelled and logged, with a spending cap.
- Privacy statement updated to mention WhatsApp and any AI processor.