What does a WhatsApp chatbot cost for a Kenyan business?

What a WhatsApp chatbot costs in Kenya depends on the conversation flows it has to handle, the systems it connects to, whether it takes payments, how handoff to staff works, message volume, hosting, support, and Meta's current platform charges. Here is how those break down, including the running cost that rarely appears in a first quote.

The realistic ranges

Use these for a first budget. Meta's per-conversation charges sit on top and are covered below. Add one to two weeks at the start for WhatsApp Business Platform approval, and plan the project around it.

The running cost, and the 24-hour window

A real bot runs on the WhatsApp Business API, not the free Business app, and Meta charges for messaging on top of whatever you paid to build it. The exact rates change, and they vary by conversation category and country, so treat any specific figure you read anywhere as something to check against Meta's current pricing before you budget.

What does not change is the shape of the rule, and it is the thing to design around. When a customer messages you first, a service window opens for 24 hours. Inside that window you can reply freely and cheaply. Outside it, a conversation can only be restarted with a template Meta has pre-approved, at a higher rate. That rule affects running cost more than raw message volume does.

• Answer inside the window and your costs stay proportional to genuine demand.
• Sending templates to a list scales the bill with the size of the list rather than with demand.
• Design flows so the customer's own message opens the window. A "message us" button beats an outbound campaign on both cost and reception.
• Batch anything non-urgent into the next inbound conversation instead of paying to start a new one.

A worked budget

An illustrative example, not a quotation. Suppose you run a salon that fields around 400 customer conversations a month, mostly about price and availability, and roughly 90 of those turn into a booking worth KES 2,000 on average.

The number to focus on is the staff hour rather than the build cost. If answering those 400 conversations by hand takes two hours a day, the automation is returning roughly 40 hours a month. Price those hours at what you actually pay for them and compare the total against the monthly running bill rather than against the build. Where the hours saved are worth less than the monthly bill, the automation is not paying for itself, and conversation design will not change that.

Getting approved, and what holds it up

Before a single message goes out, the account has to exist properly. This is the step that surprises people, because it is administrative rather than technical and it does not move faster if you pay more.

• A Meta Business account, with your business verified. Have your registration documents to hand, and make sure the business name on them matches the name you are trying to use.
• A phone number that is not already on a personal or Business-app WhatsApp. This is the most common blocker we see, and freeing up an existing number means losing its chat history.
• A display name that follows Meta's rules. Names that read as generic categories tend to get rejected.
• An approved template for anything you want to send outside the 24-hour window.

Start this on day one of the project rather than the week before launch. The build can happen in parallel, and approval is the item most likely to sit waiting on somebody else's queue.

What to automate first

You do not have to automate everything, and automating too broadly tends to produce a flow that staff and customers work around. Take your last two weeks of WhatsApp messages and sort them into four groups: how often each question arrives, and how hard it is to answer correctly.

Most of the value sits in the top-left box, and for most businesses that is four to six questions. Build those first, confirm the answers are correct against real conversations, and extend the scope once staff and customers rely on it. Accuracy across a small set is worth more than coverage across a large one, because a wrong answer costs more trust than a missing one.

What a good bot does

• Answers the predictable questions instantly: hours, prices, stock, directions, at any hour.
• Takes orders and triggers an M-Pesa STK push so the customer pays inside the chat.
• Books appointments and sends reminders, which is usually where it earns its cost back fastest.
• Hands off cleanly to a human, with the whole conversation attached, for anything it cannot handle.

Escalation is the point to insist on. Where a customer cannot reach a person, the automation gets worked around regardless of how well it answers. Define which requests the bot answers, which it captures and passes on, and which it never attempts, before the flow is built.

When not to build one

At five enquiries a week, automation is an expensive way to answer them. Where the questions are genuinely varied and most customers need a real conversation, the automation will be worked around. The return comes from high volume and low variety, where the same handful of questions arrives repeatedly. Count how many of your last week of messages were the same question before spending anything.

WhatsApp Business Platform pricing, account requirements, and template rules are set by Meta and change periodically. Confirm the current rules and rates before budgeting.