Quick answer
A white-label WhatsApp platform is messaging software that an agency offers to its clients under the agency's own brand, logo and often its own domain, while another company builds and runs the technology. Agencies use it to sell WhatsApp inboxes, chatbots and broadcasts as their own service. Each client still needs its own Meta business verification, and should own its WhatsApp account.
Key takeaways
- White-label means your brand on the product; the platform company still runs the servers, updates and Meta connection.
- There are three common models: full white-label, reselling the vendor's brand, and running clients' messaging yourself as a managed service.
- Every client business needs its own Meta business verification and WhatsApp number; white-label does not change Meta's rules.
- Clients should own their Meta business portfolio and WhatsApp account, so they can leave without losing their number.
- Under Kenya's Data Protection Act your client is usually the data controller and your agency a processor, so put it in a written agreement.
A white-label messaging platform is software built by one company and sold or operated by another under its own name. For digital and marketing agencies in Kenya, it is a way to offer clients WhatsApp inboxes, chatbots, broadcasts and SMS without building the technology themselves.
This explainer covers what white-label actually includes, how it differs from reselling or simply managing clients' chats, who owns what on the WhatsApp side, and the questions to ask before you put your agency's name on someone else's product.
What does "white-label" mean for a messaging platform?
In a white-label arrangement, your clients see your agency's brand rather than the software vendor's. Typically that covers some or all of the following:
- Your logo, colours and product name in the dashboard.
- A custom domain, such as inbox.youragency.co.ke, for logins.
- Emails and notifications sent in your name.
- Your own pricing and invoices to clients.
- First-line support provided by your agency.
What stays with the vendor is the hard part: hosting, security, uptime, feature development and the technical connection to Meta's WhatsApp Business Platform. Offerings vary widely, so treat "white-label" as a starting point for questions, not a guarantee of any specific feature.
What are the ways an agency can offer messaging to clients?
There are three common models. Many agencies start with the simplest and move up as their client base grows.
| Managed service | Reseller or referral | Full white-label | |
|---|---|---|---|
| Who the client sees | Your agency's team; the tool sits in the background | The vendor's brand, recommended by you | Your brand on the software |
| Who logs in | Your agency staff, and optionally the client | The client | The client, on your branded platform |
| Who bills the client | You, for the service | Usually the vendor, sometimes you | You |
| Set-up effort for the agency | Low | Lowest | Highest |
| Agency's responsibility | The work: replies, campaigns, flows | Advice and onboarding | Product support and the client relationship |
| Best for | Agencies selling outcomes, such as lead handling | Agencies that want a commission or simple referral | Agencies building a software line of business |
A managed service is often underrated. Clients usually care about results, such as leads answered within minutes or a monthly broadcast that sells, more than whose logo is on the dashboard.
Who owns the WhatsApp account when an agency is involved?
The client should. Each business that sends WhatsApp messages needs its own verified Meta business portfolio, its own WhatsApp Business Account and its own phone number, with its own display name approved by Meta.
Meta's WhatsApp Business Platform documentation describes how businesses, Tech Providers and Solution Partners fit together. Platforms like chat.or.ke are Meta Tech Providers, which means they connect businesses to the platform; our explainer on what a Meta Tech Provider is goes into the roles.
For an agency, the practical rules are:
- Register each client's number under the client's own Meta business, not the agency's.
- Give the agency access as a partner, rather than holding the only admin login.
- Use the client's documents for business verification; Meta checks that the business is real.
- Agree in writing what happens to the number, templates and contact data if the contract ends.
An agency that registers every client under its own business account may find it convenient at first, but it creates disputes when a client leaves and puts all clients at risk if that one account has a problem.
How does pricing work in a white-label or agency model?
Meta charges per message, by message category and the recipient's country, and its rates change over time. Somebody pays those charges, plus the platform's fees, and the agency adds its margin or service fee.
Before quoting a client, find out whether the platform's prices include Meta's WhatsApp charges or bill them separately, whether there is a monthly fee per client workspace, and what currency you are billed in. On chat.or.ke, for example, per-message prices include Meta's charges and are paid in shillings from an M-Pesa wallet, with no monthly fee; the pricing page shows the current rates. Explain to clients that marketing messages cost more than replies, so their campaign plans drive their bill.
What about data protection?
Your client is usually the data controller for its customers' information, and your agency, along with the platform, processes it on the client's behalf. That relationship should be written down.
Under Kenya's Data Protection Act, 2019, sign a data processing agreement with each client, limit staff access to what each person needs, and check whether your agency must register with the Office of the Data Protection Commissioner as a data processor. Make sure the platform keeps each client's data separate and lets you export or delete it on request.
How does this look in practice? A worked example
A Nairobi digital agency manages social media and ads for eight clients: two restaurants, a Westlands boutique, a Kisumu clinic, three property developers and a car dealer. Clients keep asking the agency to handle the WhatsApp leads its ads generate.
The agency chooses a managed service first. Each client gets its own verified WhatsApp number under its own Meta business. Inside one messaging workspace, the agency sets up a brand per client, limits each account manager to their clients, and gives every client its own auto-replies and AI knowledge. Reports are filtered per client for the monthly review. Before committing, the agency confirms with its platform how numbers registered under different clients' Meta businesses are connected and billed.
This is the pattern chat.or.ke's multi-brand feature supports, and agencies managing customer chats for different clients are one of the use cases it lists. Each brand can have its own channels, team access and replies, with reports per brand. The step-by-step guide to managing multiple brands shows the set-up. If the agency later wants clients to log in to a platform carrying its own name and domain, that is a separate white-label question to put to any vendor, including us through the contact page.
What should you check before choosing a platform?
Ask every vendor the same questions and get the answers in writing:
- Branding: Which parts carry your brand: dashboard, login domain, emails, mobile apps?
- Ownership: Can each client's number sit under the client's own Meta business, and can you still manage it from your workspace?
- Separation: Is each client's data isolated, with per-client access control?
- Pricing: Are Meta charges included? Is there a fee per client workspace? Which currency?
- Channels: WhatsApp only, or also email, SMS, Instagram, Facebook and website chat?
- Support: Who handles Meta verification issues, template rejections and outages?
- Exit: How do you, or a client, export data and move the number if you leave?
Comparing providers more broadly? Start with the best WhatsApp Business API providers in Kenya.
Published 20 October 2026 Updated 20 October 2026 Plain-text version
