Before you hire someone to build a WhatsApp business chatbot

The short answer

A WhatsApp chatbot is a chatbot that lives inside a platform with strict rules. You can reply freely to a customer for 24 hours after their last message. After that, you can only send pre-approved templates, and those are charged per message. That one rule shapes the whole build: reminders, order updates and follow-ups all need templates.

Before you hire, decide what the bot answers and what it hands over, which messages you want to send first (and so need templates), and whose accounts the number, the business profile and the AI key sit on. Then test it on a real phone, including a reply that comes back after the 24 hours have passed.

The rules every WhatsApp bot works within

These come from Meta’s developer documentation, checked in October 2026. The developer will know them; you should know them well enough to understand the quote.

• The 24-hour customer service window. When a customer messages you, a 24-hour window opens. Inside it, the bot can send normal messages: text, images, answers. Meta’s pricing page says non-template messages are free within an open window.
• Templates outside the window. Outside the window, a business can send only template messages. A template is a pre-written message with blanks to fill in, such as an order number.
• Templates are reviewed. Meta reviews each template when it is created or edited, and a template must be approved before it can be sent. Approved templates get a quality rating, and templates can be paused if customers give negative feedback or rarely read them.
• Per-message pricing. Since July 2025, Meta charges per delivered template message. Categories are marketing, utility and authentication. Marketing templates are always charged; utility and authentication templates are free inside an open window. Service conversations, where you answer a customer who wrote to you, are free.

In practice, a bot that only answers incoming questions costs little in Meta fees. A bot that sends reminders, follow-ups or promotions costs more, needs templates, and depends on Meta keeping those templates approved.

What I learned from a bot on another Meta platform

I run a small bot that replies to comments on my social posts with a private message, on a different Meta platform. It is not WhatsApp, but three of its problems belong in a WhatsApp brief.

Private messages don’t always arrive where you think. A private reply from my bot could land in the person’s message requests rather than their main inbox. I added a short public reply as well, so people knew to look. Ask the developer how your first messages will look on the customer’s side, and test it on a phone that has never messaged you.

Some people cannot be reached, and the bot should notice. One reply failed for a single person six times in a row, every twenty minutes, because their account did not accept the message. Now a reply that fails twice is marked undeliverable and handled another way. A WhatsApp bot needs the same rule: a limit on retries, and a person told when a message cannot be delivered.

Access expires quietly. On a separate publishing job, a login token expired and the job kept starting on schedule for two days while doing nothing, with the error only in a log file (the full incident). Any bot connected to a platform through a token can stop this way. Ask how you will be told when the connection stops working.

Decide these before you message anyone

Items 1, 2, 3 and 5 are the same as for any chatbot, and what to give a chatbot developer before they start covers them in detail. Items 4 and 6 are specific to WhatsApp. They are also where builds tend to stall: a template that needs rewording to be approved, or a phone number registered to the developer’s account.

Whose accounts it runs on

A WhatsApp bot usually has several accounts behind it: your Meta business account, the phone number, sometimes a messaging provider that connects the number to the bot, the automation or hosting platform, and the AI provider. Each can have its own bill and its own access.

All of them should be yours. The number in particular: customers save it, and moving a number away from someone else’s account is harder than setting it up on yours from the start. Who should own the accounts and API keys explains how to give a freelancer access you can remove, and what an API key is covers the AI side.

What moves the price

I don’t have a reliable price list for WhatsApp builds. The AI agents and chatbots page shows starting prices for chatbot developers, and the price moves with:

Factor	Why it adds cost
Number of question types	Each needs an answer written and tested
Templates	Each needs writing, submitting and sometimes rewording
Actions in live systems	Orders, bookings and lookups each need a connection
Handoff to a person	Routing conversations to staff, with history, is its own piece
Languages	Each language needs its own answers and testing
Message volume	Meta fees for templates plus AI usage per reply, every month

Ask for the build price and an estimate of running cost per 100 conversations, separately. On the shortlist, Hadj H. lists WhatsApp chatbots that take orders and answer customers, which fits a bot whose main job is orders.

How to test it before you accept it

Use a real phone, and preferably two: one that has messaged the business before and one that has not.

• Your 20 most common questions, in your customers’ words. Count wrong or made-up answers, not only good ones.
• Three questions it cannot answer. It should say so and hand over.
• Three never-do questions. It should refuse every time.
• A handoff in working hours and one after hours. A person should actually receive the conversation, with its history.
• A reply sent more than 24 hours after your last message. Check what the bot or the person can still send.
• Each template, sent once, so you see exactly what customers will see.
• A broken connection: ask the developer to show what happens, and who is told, when access stops working.

The scoring method in how to test an AI chatbot before you accept it works here too: decide the pass mark before you start.

Where it goes wrong anyway

• A template is paused. Low read rates or customer complaints can pause a template, and then it cannot be sent. Ask to be alerted when a template’s status changes; Meta reports status changes by webhook.
• The handoff misses the window. Staff reply the next day, and a free-form reply is no longer possible. Plan who answers handed-over chats, and how fast.
• Answers go out of date. Prices, hours and policies change. Agree who updates the bot’s knowledge, and at what rate, before launch.

Wrap-up

A WhatsApp chatbot is a chatbot plus Meta’s rules: a 24-hour window, approved templates and per-message pricing. Decide what it answers and what it passes on, list the messages you want to send first, register every account and the phone number to yourself, and test it on a real phone across the 24-hour line. If customers mostly reach you on your website instead, the same preparation works for a website chatbot, and the voice agent guide covers the phone.