A website chatbot catches a visitor who is already on the page. A WhatsApp chatbot reaches a customer who has opted in and may return later. They look similar in a demo and behave very differently in production.
The channel decides the consent rules, the message format and the cost.
Channel intent
Website chat is usually a research or support moment. The visitor is comparing, reading or stuck. The bot has the page context and can answer immediately.
WhatsApp is a relationship channel. The customer has opted in, often after a purchase or an enquiry. The bot can send order updates, reminders and follow-ups, but it has to respect template rules and opt-out requests.
Opt-in and templates
WhatsApp business messaging requires consent and approved templates for messages outside the 24-hour service window. That changes the design: you cannot treat it like an open chat window.
A website bot has no template approval, but it still needs a privacy notice and a clear escalation path.
Handoff
Both channels need a handoff to a person, but the mechanics differ. On the website, the transcript can move into a helpdesk ticket. On WhatsApp, the agent needs access to the same conversation thread without asking the customer to repeat everything.
The handoff should include the customer identity, the intent, the order or booking reference and the bot’s attempted steps.
Cost
Website chat cost is mostly platform, model usage and integration. WhatsApp adds conversation-based messaging charges, template approval and a business number.
The cheaper channel per message is not always the cheaper channel per resolved issue. A WhatsApp conversation that returns a week later may need more context and more agent time.
Which to build first
Start with the channel where the customer already asks questions. A service business with a busy website usually benefits from website chat first. A business that already handles orders and updates on WhatsApp should start there.
Do not build both at once with the same flow. The consent rules, message formats and success metrics are different.
A shared brain, separate channels
The intent model and the knowledge base can be shared. The channel layer should stay separate: templates, opt-in status, session windows and handoff rules.
That separation lets you add a channel later without rebuilding the logic.
A launch checklist
Before launch, confirm the business number, the opt-in source, the approved templates and the 24-hour service window rules. A WhatsApp bot that ignores the window will fail at the first outbound message.
Map the handoff to a queue with a named owner. A bot that transfers to an unattended inbox is worse than a bot that collects a callback request.
Write the fallback for a failed template or a blocked number. The customer should still be able to reach a person.
Track channel-specific metrics: opt-out rate, template delivery, response time and resolution. A shared dashboard that hides the channel difference will mislead the team.
Choosing the first flow
For a first WhatsApp flow, order status and appointment reminders are safer than open-ended sales chat. They have a clear trigger, a known answer and a measurable outcome.
For a first website flow, start with the question that fills the contact form: pricing, service scope, availability or location. It is the moment the visitor is deciding whether to enquire.
Do not launch both channels with the same flow. The consent, template and handoff rules are different enough to create confusion.
A pilot should run for four weeks with one flow and one owner. Compare the resolution rate, the handoff time and the opt-out rate with the current channel. A channel that looks busy but creates more agent work is not a win.
FAQ
Can one chatbot run on both WhatsApp and a website?
The knowledge and intent layer can be shared, but the messaging rules and user experience should be designed per channel.
Do we need template approval for WhatsApp?
Yes for messages outside the service window. Plan the templates before launch; approval takes time.
Which channel has better conversion?
It depends on the buying journey. Website chat captures active research; WhatsApp works better for follow-up and repeat contact.
The product overview is on AI Chatbot, with pricing on AI chatbot app development cost. For WhatsApp setup, see WhatsApp Business API integration cost.
