WhatsApp Business API in Kenya: what it is for, what Meta checks, and how long it takes
Most Kenyan businesses do not need the API and are better off on the free app. Here is the line between them, and what the approval process actually involves if you cross it.
Almost every week someone asks us to "put WhatsApp automation" on their business. Most of them should not have it, and the honest version of this article is a single paragraph:
If a human is going to read and type every message anyway, you do not need the WhatsApp Business API. Use the free Business app, put a wa.me link on your website, and spend the money on something else.
If you are still reading, here is the real distinction.
Three different things called "WhatsApp for business"
The wa.me link. A link that opens a WhatsApp chat with your number and a pre-filled message. No API, no approval, no verification, no cost. It works the day your website goes live. This is what sits on every page of our own site, and for most Kenyan businesses it is the entire answer.
The WhatsApp Business app. The free app with a catalogue, quick replies and labels. One phone, one person, manual. Excellent, and genuinely sufficient up to a surprisingly high volume.
The WhatsApp Business Platform, or Cloud API. No interface at all. It is a connection between WhatsApp and your own software, so your system can send and receive messages without a person. This is the one people mean by "automation", and the one with the paperwork.
When the API is actually worth it
Four situations, in our experience:
Notifications triggered by something else. An order ships, a project moves stage, an invoice falls due — and the message goes out because your system knows, not because someone remembered. This is the most common real use.
Volume past what a person can hold. When two people are working the same inbox on one phone and losing track of who replied to whom.
Messages that must land in your records. An inbound enquiry that automatically creates a lead in your CRM, rather than living in a chat thread only one person can see.
Two-way flows. A customer replies "1" to confirm a delivery slot and your system acts on it.
Notice that none of those is "reply faster." The API does not make you faster. It makes your software able to talk, which is a different thing.
What Meta actually checks
This is the part that surprises people, so plan for it.
Business verification. Meta verifies that your business exists and that what you have submitted matches official and publicly available records. Your business name, your registration details, and often a phone number or website that can be independently checked. Mismatches are the main cause of delay — a name on a certificate that does not quite match the name on the Business Manager account will send you back to the start.
The phone number. The number you use must not be active on the regular WhatsApp or WhatsApp Business app. This catches people out constantly: you cannot take the number your business has used for three years and move it to the API without first removing it from the app, which means losing that chat history. Decide early, and if in doubt use a new number.
Every outbound template. More on this below.
Timeline: days to weeks for verification. It is the longest pole in any project that touches WhatsApp, and there is no way to hurry it. Start it first, on day one, before a line of code is written. Everything else in the project can proceed in parallel; nothing can proceed past it.
The 24-hour rule, which changes everything
This single rule shapes every WhatsApp automation project, and most people discover it late.
Within 24 hours of a customer messaging you, you can send whatever you like — free-form text, back and forth, normal conversation.
Outside that window, you may only send a pre-approved template message. Free-form text is simply rejected.
So "send the client an update when their project status changes" is not a message you write. It is a template you submit to Meta for review, with placeholders for the bits that vary. Review is usually a day or two. Templates get rejected for being too promotional, too vague, or for having placeholders where Meta cannot tell what will be substituted in.
The planning consequence: write your templates early and submit them early. Every proactive notification your system will ever send needs one, and you cannot invent them on launch day.
What this means for a Kenyan business, practically
The most honest sequence we can give you:
- Start with the wa.me link. Free, instant, no approval. Put it on every page. See how much of your problem it solves — for most businesses, it is all of it.
- Use the free Business app until an actual person is drowning. Not until it feels unprofessional, until someone is genuinely losing messages.
- Only then consider the API, and only if your problem is that software needs to send messages, not that people need to send more.
When you do cross that line, the order matters: Meta Business verification first, templates second, build third. Reversed, you get a finished system sitting idle for three weeks waiting on a verification nobody started.
The one that is worth it every time
If we had to pick a single WhatsApp automation for a Kenyan SME, it is not outbound notifications. It is inbound capture: every WhatsApp enquiry automatically becoming a record in your system, with the message, the number and the time.
Because the thing quietly costing you money is not slow replies. It is that you have no idea how many people messaged you last month, what they wanted, or how many you never got back to. A person cannot remember that. A system does not have to.
Questions people ask us
- What is the difference between WhatsApp Business app and the API?
- The free app is an inbox you open on a phone — one device, manual replies, fine for most businesses. The API has no interface at all; it connects WhatsApp to your own system so messages can be sent and received automatically, by software, at volume. If a person is going to read and type every message anyway, you do not need the API.
- How long does Meta Business verification take?
- Days to weeks, and it is the longest step by far. Meta checks that your business is real and that the details you submit match public and official records. Start it before anything else in your project, because everything downstream waits on it.
- Can I send any message I like through the API?
- No. Outside the 24-hour window after a customer last messaged you, you may only send pre-approved template messages. Free-form text is rejected. Each template is submitted to Meta and typically reviewed within a day or two.
- Do I still need the API if I just want a WhatsApp button on my website?
- No. A wa.me link opens a chat with a pre-filled message and needs no API, no verification and no approval. It works the moment your site is live. That covers most businesses entirely.
- What does WhatsApp API cost in Kenya?
- Meta charges per conversation and the rate varies by conversation type and country, so check Meta's current pricing rather than a blog figure. Beyond that you pay for whatever provider or build sits between WhatsApp and your system. The cost that catches people out is not money, it is the verification wait.