Choosing a WhatsApp Business API Provider in South Africa
Meta Cloud API direct, a Business Solution Provider or a local partner? Compare onboarding, costs, support, data residency and lock-in before you choose.
- Social Agent team
- 7 min read
In this article
Once you outgrow the free WhatsApp Business app, you need a way onto the WhatsApp Business Platform. You can go directly to Meta's Cloud API, work through a global Business Solution Provider (BSP) such as 360dialog, or use a local South African provider that bundles WhatsApp with support and other channels. Each route can work well, depending on your technical capacity, budget, compliance needs and appetite for vendor dependence. This guide lays out the trade-offs and the questions to ask before you sign.
Provider terms, Meta's partner programmes and pricing change often. Treat the details below as the position at the time of writing and confirm them against Meta's WhatsApp Business Platform documentation and each vendor's current terms.
The three main routes
All three routes end up in the same place: your messages travel through Meta's infrastructure, and at the time of writing the Cloud API hosted by Meta is the standard way to access the platform. The difference is who sits between you and Meta, and what they add.
Meta Cloud API direct
You create a Meta business portfolio, set up a WhatsApp Business Account (WABA), register a phone number and call the Cloud API yourself. Meta bills you directly for messages.
- Good for: teams with developers who are comfortable with webhooks, access tokens and API error handling.
- What you get: direct access to new features as soon as Meta releases them, no intermediary markup and full control of your account.
- What you give up: hands-on onboarding help and a single support contact. Support comes through Meta's business support channels, which can be slower for urgent issues than a dedicated account manager.
A global Business Solution Provider
BSPs are Meta partners that provide onboarding, hosting of your integration layer, tooling and support. Some, such as 360dialog, focus on API access with a thin layer on top. Others offer a full customer engagement suite.
- Good for: organisations that want faster onboarding and a partner to call when something breaks, without building everything themselves.
- What you get: guided setup, dashboards, help with verification and templates, and often extra tooling.
- What you give up: some independence. You depend on the BSP's API, uptime and roadmap, and new Meta features may reach you later.
A local provider
South African providers often bundle WhatsApp with SMS, USSD, voice or contact centre services, and may resell or partner with a global BSP behind the scenes.
- Good for: organisations that value local support hours, rand billing, local contracts and a single supplier for several channels.
- What you get: familiarity with local business practices, face-to-face support and often help with campaigns.
- What you give up: potentially another layer between you and Meta, which can affect feature timing, pricing transparency and portability.
Comparing the routes side by side
| Factor | Meta Cloud API direct | Global BSP | Local provider |
|---|---|---|---|
| Onboarding | Self-service, technical | Guided, often embedded signup | Guided, often done for you |
| Billing | Direct from Meta | Meta fees plus BSP fees | Usually a bundled rand invoice |
| Support | Meta business support | BSP support team | Local account management |
| Feature access | Earliest | Depends on the BSP | Depends on the provider and its upstream partner |
| Engineering effort | Highest | Medium | Lowest |
| Lock-in risk | Lowest | Medium | Medium to high, depending on contract |
Understanding cost models
Meta charges per delivered template message, with the rate set by the template category and the recipient's country. That applies whichever route you choose. What varies is what the provider adds on top. Common models include:
- Pass-through plus a platform fee: Meta charges are passed on at cost and the provider charges a fixed monthly fee per number or per account. Some API-focused BSPs, 360dialog among them, have used this kind of model.
- Per-message markup: the provider adds a margin to each message, sometimes bundled into a single rate.
- Bundles and commitments: a monthly package of messages or a minimum spend, common with local providers.
- Seat or feature licences: charges per inbox user or for automation features, on top of messaging.
Ask for an example invoice at your expected volume by category, since a low headline rate can hide other fees. Our guide to WhatsApp template categories explains how categories affect cost, and Meta's rate card is the reference for the underlying charges.
Support, features and reliability
Beyond price, look at what happens on a bad day:
- Support hours and channels: are they available during South African business hours, and is there an emergency route?
- Escalation to Meta: can the provider escalate account restrictions, verification problems or template disputes, and how quickly?
- Uptime commitments: is there a service level agreement with credits, and does it cover the provider's own layer?
- Feature parity: does the provider support interactive messages, media headers, WhatsApp Flows and newer features, or only a subset?
- Webhooks and data access: can you receive every status update and inbound message in your own systems, in real time?
Data residency and POPIA questions
Under POPIA you remain responsible for personal information you process, even when an operator processes it on your behalf. Section 72 also limits transfers of personal information outside South Africa unless certain conditions are met, such as adequate protection in the recipient country or binding agreements.
WhatsApp messages sent through the Cloud API are processed on Meta's infrastructure, which is largely outside South Africa. At the time of writing, Meta offers a local storage option for data at rest in certain regions; check its current coverage in Meta's documentation. Any provider in the middle will also store message content, contacts and logs somewhere. Questions to ask:
- Where does the provider store message content, media, contact lists and logs?
- Which sub-processors do they use, and in which countries?
- Will they sign an operator agreement that meets POPIA section 21?
- How long do they retain data, and can you set or shorten retention?
- How do they handle a data subject access or deletion request?
- How are access tokens and credentials protected, and who on their side can see them?
This is not legal advice. Involve your information officer before you finalise a provider.
Lock-in and number portability
Your WhatsApp phone number, display name, verified status and template library are valuable. Make sure you can take them with you.
- Who owns the WABA? Ideally the WhatsApp Business Account sits in your own Meta business portfolio, with the provider granted access as a partner. If the provider owns it, moving becomes harder.
- Number migration: Meta supports migrating a registered number between WhatsApp Business Accounts and providers. At the time of writing this typically requires two-step verification to be managed correctly and cooperation from the current provider. Ask how they handle outbound migrations and how long it takes.
- Templates: check whether your approved templates can move with the number or will need resubmitting.
- Conversation history: find out whether you can export message history and contacts in a usable format.
- Contract terms: look for notice periods, exit fees and data return obligations.
Why a vendor-agnostic control plane helps
Many enterprises end up with more than one WhatsApp route: an agency on one BSP, the contact centre on another, a product team on the Cloud API. Each has its own inbox, templates and logs, and nobody has a complete picture.
A control plane above the providers keeps your inbox, broadcasts, templates, approvals and audit trail in one place, so the provider becomes a connection you can swap and you choose on price and service, not migration pain.
This is the approach Social Agent takes: it connects to Meta's Cloud API directly, to 360dialog, to eCommunicate or to any vendor API, with provider credentials held in a secrets store that is never exposed to the browser or to the AI agent. The same integration model covers email, databases and HTTP APIs, so WhatsApp becomes one channel among the systems your team already runs.
Questions to ask every vendor
- Will the WhatsApp Business Account sit in our Meta business portfolio?
- What is your full cost model, including platform, seat and setup fees, based on our volume?
- Do you pass Meta charges through at cost, or add a markup?
- Which Meta features do you support today, and how quickly do you adopt new ones?
- What are your support hours, escalation routes and uptime commitments?
- Where is our data stored and processed, and who are your sub-processors?
- Will you sign a POPIA-compliant operator agreement?
- How do we migrate our number and templates away, and what does it cost?
- Can we receive all webhooks and export all data in real time?
- How are our API credentials and access tokens protected?
Key takeaways
- All routes rely on Meta's platform; the difference is who sits in the middle and what they add.
- Cloud API direct gives the most control but needs engineering capacity; BSPs and local providers add onboarding and support at the cost of some independence.
- Compare total cost using your own volumes, including platform and seat fees, and check Meta's current rate card.
- Ask hard questions about data location, sub-processors and POPIA operator agreements.
- Keep the WhatsApp Business Account in your own business portfolio and confirm your exit path before signing.
- A vendor-agnostic control plane reduces lock-in and lets you change providers without rebuilding your operations.
