Chatwoot WhatsApp Business API Setup and Costs in Kenya

WhatsApp is where Kenyan customers already are, and the free WhatsApp Business app stops working for you the moment more than one person needs to answer chats. The fix is the WhatsApp Business API connected to a shared inbox, and Chatwoot is the strongest open-source option for that inbox. This guide covers the full setup path, what Meta actually charges per message in Kenya (including the pricing change that took effect on 1 October 2026), and the points where teams usually get stuck.

Why pair Chatwoot with the WhatsApp Business API

The WhatsApp Business app is free and fine for a one-person operation. It breaks down when you need several agents answering the same number, conversation assignment, labels, SLA tracking, or an audit trail. The API has no interface of its own; it is a pipe. You connect it to an inbox platform, and that platform becomes your team's workspace.

Chatwoot gives you that workspace as open-source software. You get a shared inbox, agent assignment, canned responses, automation rules, and contact management, and you can run it yourself or pay for the hosted version. Because the API connection is native (not a third-party bridge), message delivery and status webhooks go straight from Meta to your Chatwoot instance.

Two things to know before you commit:

The API is not the app. A phone number on the API no longer works in the regular WhatsApp or WhatsApp Business app, unless you use Meta's coexistence option during embedded signup. Pick a number you are willing to dedicate.
Templates rule outbound. Outside a 24-hour customer service window, you can only send pre-approved template messages. Free-form replies are only possible inside that window.

What Meta charges per message in Kenya

Meta moved the WhatsApp Business Platform to per-message pricing on 1 July 2025. You pay for each business message that is delivered, and the rate depends on two things: the message category and the recipient's country. Incoming customer messages are never billed. Meta publishes the full mechanics in its pricing documentation.

Kenya bills under the "Rest of Africa" market pair. The rates in effect since the July 2026 rate card, in US dollars per delivered message:

Marketing: $0.0225. Promotions, offers, product announcements, re-engagement. The expensive lane by design.
Utility: $0.0040. Transactional updates tied to an action the customer took: order confirmations, delivery updates, appointment reminders, payment notifications.
Authentication: $0.0040. One-time passwords and verification codes.
Service: $0.0040 from 1 October 2026. Free-form replies your team sends inside the 24-hour window. Previously free; details in the next section.

These figures come from Meta's published rate card, mirrored in SleekFlow's pricing breakdown. Two structural points matter for budgeting. First, rates only change on 1 January, 1 April, 1 July, or 1 October, with one to six months of notice, so you can plan. Second, utility and authentication messages have volume tiers, so heavy senders pay less per message than the list rate.

The October 2026 change: service messages are no longer free

This is the part most guides have not caught up with. Until 30 September 2026, free-form replies inside the 24-hour customer service window cost nothing, and utility templates sent inside the window were also free. From 1 October 2026, per Meta's non-template message pricing notice:

Service messages become chargeable. Every free-form reply your agents send bills at the utility rate for the market: $0.0040 for Kenyan recipients.
The first 1,000 service messages per phone number per month stay free. The counter resets monthly and does not roll over. A team sending fewer than 1,000 replies a month still pays nothing for them.
Utility templates inside the window become chargeable too, at the same $0.0040 rate.
Accounts without a payment method stopped receiving service message delivery as of 30 September 2026. If your WhatsApp Business Account has no payment method attached in WhatsApp Manager, your replies simply do not go out. This is the single most urgent operational item.
The 72-hour free entry point survives. When a customer messages you from a Click-to-WhatsApp ad or a Facebook Page button, everything you send in the following 72 hours is free, templates included.

The practical effect: WhatsApp support is no longer a zero-marginal-cost channel, but at $0.0040 a reply it is close. The change punishes chatty workflows, not support itself. Consolidating three quick agent replies into one complete message now saves real money at scale.

Worked example: a Nairobi retailer with three agents

A mid-sized online retailer in Nairobi runs support on one WhatsApp number with three agents in Chatwoot. A typical month:

6,000 customer-initiated conversations. Agents send an average of 4 replies per conversation inside the window: 24,000 service messages. After the 1,000 free messages, 23,000 are billed at $0.0040. Cost: $92.00.
8,000 utility templates. Order confirmations and delivery updates. 8,000 x $0.0040. Cost: $32.00.
10,000 marketing messages. One promotional campaign to the opted-in customer list. 10,000 x $0.0225. Cost: $225.00.

Meta's invoice: $349 for the month, billed in USD to the card on the WhatsApp Business Account. Before October 2026, the same month would have cost $257, because the service messages and in-window utility templates were free.

Add the inbox side. Self-hosted Chatwoot Community Edition is free software; a DigitalOcean droplet with 2 GB of RAM costs $12 a month, and 4 GB at $24 gives comfortable headroom. All-in, this team spends roughly $361 to $373 a month for the whole stack. On Chatwoot's hosted Business plan, three agents cost $117 a month on top of the Meta bill, for a total of $466.

The marketing campaign is two-thirds of the Meta bill. Teams that treat WhatsApp as a support channel and keep campaigns modest will find the channel remarkably cheap; teams that blast promotions weekly will find marketing messages dominate everything else.

What Chatwoot itself costs

Chatwoot has two cost models, per its pricing page:

Cloud, hosted by Chatwoot on AWS: Startups at $19 per agent per month, Business at $39 (the tier most teams need for automation and SLAs), Enterprise at $99. A 15-day trial is included, and the Startups plan is free for open-source projects and nonprofits.
Self-hosted Community Edition: free, no per-agent fee. You pay for the server ($6 to $24 a month for a small VPS) and for the time to maintain, back up, and upgrade it.

The honest trade-off: self-hosting removes per-agent fees, which matters at 10 or 20 agents, and keeps all conversation data on infrastructure you control. It also makes you responsible for uptime, SSL, backups, and version upgrades. If nobody on your team wants to own a server, the cloud plan is the right answer. The same licence-versus-hosting math plays out across the open-source stack; we ran the numbers for scheduling in Cal.com vs Calendly. If you want the software managed for you without per-agent fees, that is exactly the gap a managed open-source stack service fills.

Setting it up, step by step

There are two routes into Chatwoot: embedded signup (the easy path) and the manual API flow (for edge cases). Both are documented in Chatwoot's embedded signup guide and manual setup article.

Before you start

A Meta business portfolio at business.facebook.com. Your personal Facebook account owns it; add your company details.
A phone number that can receive an SMS or voice call for verification, and that is not actively registered in the consumer WhatsApp or Business app (or use the coexistence option in embedded signup).
A payment method to attach in WhatsApp Manager. Without it, service messages stop delivering.

Route 1: embedded signup

In Chatwoot, go to Settings, Inboxes, Add Inbox, choose WhatsApp, then WhatsApp Cloud.
Click Connect with WhatsApp Business and complete the Facebook OAuth flow: pick your business portfolio, create or select a WhatsApp Business Account, register the number, verify it by SMS or call.
Chatwoot configures the webhook automatically. Done.

Self-hosted instances need one extra step first: a super admin sets WHATSAPP_APP_ID, WHATSAPP_CONFIGURATION_ID, and WHATSAPP_APP_SECRET in the app config, pointing at a Meta app with the WhatsApp product and Facebook Login for Business configured.

Route 2: manual flow

Use this when embedded signup is not an option, for example when a provider already manages your number. You create the Meta app yourself, generate a permanent system-user access token with whatsapp_business_messaging and whatsapp_business_management permissions, then paste the WhatsApp Business Account ID, Phone Number ID, and token into Chatwoot, and point Meta's webhook at your Chatwoot callback URL with the verify token. One warning from Chatwoot's docs: do not manually register a number that is still active in the WhatsApp Business app.

After the connection

Attach the payment method in WhatsApp Manager under Billing. Do this the same day.
Create and submit templates for your utility and marketing messages. Templates go through Meta review; a utility template stuffed with promotional language gets rejected or recategorized as marketing and billed at the higher rate.
Verify your business. This lifts your messaging limit and unlocks the approved display name.
Build the operating layer in Chatwoot: teams, assignment rules, business hours, canned responses, and automation. If you want WhatsApp events to trigger workflows elsewhere (CRM updates, alerts, escalation), wire the inbox to an automation tool like n8n as part of a broader business automation setup.

Messaging limits and business verification

New business portfolios start with a limit of 250 unique recipients per 24 hours outside customer service windows, per Meta's messaging limits documentation. The limit is portfolio-level and shared across all your numbers.

Raising it works in stages:

To 2,000: complete one scaling path: verify your business, have your onboarding partner verify it, or deliver 2,000 template messages within 30 days at a high quality rating.
To 10,000, then 100,000, then unlimited: automatic, once you hold a high quality rating and have used at least half your current limit in the last seven days.

Business verification is Meta checking that your company is real: legal name, registration documents, website, phone. For a Kenyan limited company this means your certificate of incorporation and matching details. Budget a few days for it, and start early, because a campaign that needs to reach 5,000 customers is impossible on a fresh account until the limit scales.

Quality rating is the other lever. If recipients block or report your messages, the rating drops, and scaling stalls. This is Meta's spam control, and it works: unsolicited promotional blasts will throttle your account.

Kenya-specific points

Data protection. Customer conversations are personal data under the Data Protection Act 2019. Data controllers and processors register with the Office of the Data Protection Commissioner through its data portal. Where your inbox data lives is a real decision: Chatwoot cloud hosts on AWS in the US, while self-hosting lets you keep conversation data in a region you choose. For law firms, financial services, and health-adjacent businesses, that distinction often settles the cloud-versus-self-host question on its own. SACCOs face the same residency and cost trade-offs; our guide to AI for SACCOs in Kenya covers what to deploy first in that sector.

Billing. Meta bills in USD to a card on the WhatsApp Business Account. Kenyan corporate cards that handle USD subscriptions work; confirm international card payments are enabled with your bank before the billing date to avoid a failed charge and delivery interruptions.

Number choice. A Safaricom, Airtel, or Telkom number all work; the number just needs to receive the verification SMS or call. A dedicated line is better than repurposing the founder's personal number, because migrating a number to the API ends its life in the consumer app.

When this is the wrong choice

You are a solo operator with low volume. Under roughly a hundred chats a month, the free WhatsApp Business app with quick replies is enough. Do not buy infrastructure you do not need.
You only run outbound campaigns. If there is no two-way conversation, a full inbox is overkill; a campaign-focused sender may be cheaper and simpler.
Nobody will own the setup. The API, templates, quality rating, and Meta Business Suite need an owner. Without one, the channel decays within a quarter. A managed deployment solves this, but pretending the ownership question away does not.
You need voice calls on the same channel. This stack is messaging-first; if your support motion is phone-heavy, look at voice channels instead. Latency is what makes or breaks a voice agent on calls, which we break down in Voice AI latency on phone calls.

Common mistakes

Leaving the number active in the Business app and then trying a manual API registration. Migrate properly through embedded signup instead.
No payment method attached. Since 30 September 2026, that means your replies do not deliver at all.
Ignoring the 250-recipient starter limit and planning a launch campaign a fresh account cannot deliver.
Writing promotional content into utility templates. Meta recategorizes or rejects them, and repeat offenders see quality rating damage.
Designing chatty reply flows. After October 2026 every agent message bills. One complete reply beats four fragments, for cost and for readability.
Assuming self-hosted means zero cost. The software is free; the server, backups, monitoring, and upgrade time are not.

Frequently asked questions

Is the WhatsApp Business API free in Kenya? The API itself has no licence fee, but Meta charges per delivered business message: $0.0225 for marketing and $0.0040 for utility, authentication, and (since October 2026) service messages to Kenyan numbers. You also pay for the inbox platform you connect, unless you self-host open-source software like Chatwoot.

Can I keep using the WhatsApp Business app on the same number? Not in the usual setup. Moving a number to the API removes it from the app. Meta offers a coexistence option during embedded signup in some configurations that lets the app and API share a number, but treat that as the exception and plan for a dedicated API number.

How many messages can a new account send? A new business portfolio can reach 250 unique recipients per 24 hours outside customer service windows. Verifying your business (or delivering 2,000 quality messages in 30 days) raises it to 2,000, and strong quality plus usage scales it automatically to 10,000 and beyond. Replies inside the 24-hour window are not subject to this cap.

What happened on 1 October 2026? Service messages (free-form agent replies) became billable at the utility rate, with the first 1,000 per number per month free. Utility templates sent inside the service window also became billable. Accounts without a payment method stopped getting service messages delivered from 30 September 2026.

Do I need a Business Solution Provider? No. Meta's embedded signup lets you onboard directly through Chatwoot without a BSP and without BSP per-message markups. BSPs still make sense if you want them to hold the Meta relationship, but for a Chatwoot-based stack they are optional.

Is self-hosting Chatwoot worth it? At three agents, cloud is simpler and the price difference is small. At ten or more agents, or when data residency matters, self-hosting usually wins on cost and control. The break-even question is not the licence; it is whether someone owns the server.

Where to go from here

The pieces are straightforward: a Meta business portfolio, a verified number, a payment method, and an inbox your team will actually use. The fiddly part is getting the Meta app, templates, limits, and Chatwoot configuration right the first time, and keeping the instance healthy afterwards. We deploy and manage Chatwoot as part of our managed open-source stack, and if you want an AI agent answering the routine questions inside that inbox, that is exactly what our AI Employees service is built for.