WhatsApp Business API for Nigerian businesses: a practical guide
What the WhatsApp Business Platform is, how it differs from the WhatsApp Business app, what it costs to run, and the workflows that pay for themselves.
By Timothy Fadipe · · 7 min read
In Nigeria, your customers are already on WhatsApp. They'd rather send you a message than fill in a form, call a line that rings out, or download an app. The question isn't whether to use WhatsApp for business. It's whether you've outgrown doing it by hand.
That's what the WhatsApp Business Platform (usually called the WhatsApp Business API, or WABA) is for.
App vs API: what's the difference?
The WhatsApp Business app is the free app on your phone. It's good for a small business: a catalogue, quick replies, labels and an away message. But it's tied to a small number of devices, it can't connect to your systems, and everything depends on someone typing.
The WhatsApp Business Platform is an API. There's no app to install; your number is connected to software. That means:
- Many staff can work from one number through a shared inbox.
- Messages can be sent and received automatically by your own systems.
- WhatsApp connects to your website, CRM, order system or payment flow.
- You can send approved notifications (order updates, reminders, OTPs) at scale.
The rule of thumb: if conversations are getting lost, staff are sharing one phone, or you're copying details from WhatsApp into another system, it's time for the API.
How to get access
Meta offers the API in two ways:
- Directly through Meta's Cloud API, hosted by Meta. You (or your developer) build against it.
- Through a Business Solution Provider (BSP): companies such as Twilio, 360dialog and Infobip that wrap the API with their own tools and support, usually for an extra fee.
Going direct gives you the most control and the lowest platform cost. A BSP can make sense if you want a ready-made inbox and don't plan custom integrations.
Either way, you'll need:
- A Meta Business account (verification is recommended, and required for higher messaging limits).
- A phone number that can receive a verification SMS or call. A number already registered on the WhatsApp app has to be removed from it, or migrated, before it can be used with the API.
- A display name that matches your business, which Meta reviews.
The 24-hour window and templates
This is the rule everything else depends on:
- When a customer messages you, a 24-hour customer service window opens. Inside it you can reply freely with any normal message.
- To message a customer outside that window, or to start the conversation yourself, you must use a message template that Meta has pre-approved.
Templates are categorised (for example marketing, utility and authentication), and the category affects both approval and price. "Your order #4821 has shipped" is a utility template. "20% off this weekend" is marketing.
Customers must also have opted in to receive messages from you. Sending unsolicited marketing is the fastest way to get your number's quality rating lowered and your sending limits cut.
What does it cost?
Meta charges for template messages, with rates that depend on the template category and the recipient's country. Replies inside the 24-hour customer service window are currently free. Meta changes its pricing model periodically, so check the current rate card on Meta's developer site before you budget. A BSP adds its own fees on top.
The bigger cost is usually the build: the integration, the automations and the inbox your team works in. That's a one-off, and the right workflow pays for itself quickly.
Workflows that pay for themselves
These are the patterns we see deliver the most value for Nigerian businesses:
- Listings and catalogue intake. Suppliers or dealers send product details and photos by WhatsApp; the system turns them into structured listings. We built this pipeline for BuyCar, so dealers list cars from the app they already use every day.
- Order and delivery updates. Automatic confirmation, dispatch and delivery messages, which cut "where is my order?" calls sharply.
- Payment links and confirmations. Send a Paystack or Flutterwave link in chat, and confirm automatically when the webhook lands.
- Appointment reminders. Fewer no-shows for clinics, salons and service businesses.
- AI-assisted first replies. An assistant answers common questions instantly (prices, opening hours, delivery areas) and hands over to a human when it should.
- OTP and verification, as an alternative to SMS where WhatsApp delivery is more reliable for your customers.
Getting it right
A few things separate a WhatsApp integration customers like from one they mute:
- Be useful, not noisy. Utility messages build trust; constant promotions destroy it.
- Always offer a human. Automation should handle the routine and route the rest.
- Store conversations properly. Link messages to customers and orders so your team has context.
- Watch your quality rating. Meta monitors blocks and reports. A falling rating means you're over-messaging.
- Handle data responsibly. Conversations contain personal data, so they fall under the Nigeria Data Protection Act. Keep access controlled and retention sensible.
Where to start
Pick the one conversation your team handles most often, whether that's order status, new enquiries or payment confirmation, and automate that first. Measure the hours saved, then expand.
Want WhatsApp connected to your business systems? Let's talk.