The WhatsApp API for agencies running more than one client
Every client gets their own organisation, their own wallet and their own data, all reachable from a single login. Add API keys and signed webhooks and your clients' WhatsApp activity can feed the reporting you already run.
The daily friction
Nine clients, nine logins, one shared password file
Agencies rarely arrive at WhatsApp deliberately. A retail client asks for order updates, a clinic asks for appointment reminders, and eighteen months later you are running WhatsApp for nine businesses across four different providers, each with its own login, its own invoice and its own way of doing templates.
The cost of that is not the software. It is the half hour lost every time somebody has to work out which account a conversation belongs to, the credential shared in a chat thread because it was faster, the client whose message spend you estimate at the end of the month because the bill arrived as one number. It is also the risk you carry quietly: one shared setup, and a problem on one account becomes a problem on all of them.
What an agency needs from a WhatsApp platform is unglamorous. Proper separation between clients. Money tracked per client. The ability to give a junior access to one account and not the other eight. And a way to get the data out, because your clients look at your dashboard, not ours.
Multi-client structure
What separate client organisations actually give you
Multi-tenancy is not a marketing word here, it is how the platform is built. Every one of these exists because running eight accounts is different from running one.
One organisation per client
Each client you run gets its own organisation: its own contacts, conversations, templates, campaigns and settings. Nothing leaks sideways. When a client leaves, what belongs to them is already in one boundary rather than tangled through everyone else's data.
Switch clients without switching logins
The API carries an active organisation identifier on each request, so the same account operates inside whichever client you have selected. No password manager gymnastics, no shared credentials floating around the team, no logging out to check something for another account.
Teams and departments inside each client
Within an organisation you can set up teams and departments, which is how you model the fact that two of your people cover one client, three cover another, and one covers everybody. The structure follows how your agency is actually staffed.
Roles and permissions on members
Members are added and removed per organisation with roles and permissions attached. A junior handling replies does not need the same access as the account lead, and a client contact you invite into their own organisation needs less again.
A wallet per client, not a shared pot
Each organisation carries its own prepaid wallet with a balance, an add-funds path and a transaction history. Message spend for one client is visible against that client rather than pooled into an agency bill you then have to unpick at month end.
Per-country message pricing in the product
Meta's per-message rates vary by country and template category. Those rates live inside the platform, so a client sending to three markets can be costed against the markets they actually send to instead of a single blended guess.
Dashboard stats scoped to the client
Each organisation reports its own numbers. That is what makes a monthly client review possible without exporting everything and filtering it by hand in a spreadsheet nobody trusts.
Admin controls above the client layer
There is an administrative surface above the individual organisations covering plans, coupons and organisation administration, so the operator running the account has a view and a set of levers that individual client users do not.
Client billing
Billing clients is the part that breaks first
Ask an agency what goes wrong when they resell messaging and the answer is almost never the messaging. It is the last three days of the month, working out who sent what, in which country, under which template category, from a bill that arrived as one figure.
Per-organisation wallets change the shape of that problem. Each client's balance draws down against their own sending, with a transaction history behind it, so the number you invoice is the number the platform already recorded. A client who has a heavy campaign month shows it in their own wallet rather than in your margin.
Per-country pricing matters for the same reason. Meta charges different rates in different markets and by template category, so a client messaging one country and a client messaging six are not comparable on a blended average. Having those rates in the product lets you quote a campaign against the markets it will actually reach. Our explainer on how WhatsApp API pricing is structured is worth sending to a client before their first quote, because the two-cost model surprises almost everybody the first time.
For your own systems
The API surface agencies actually reach for
Most agencies of any size already have a reporting layer clients log into. The goal is to feed it, not to replace it.
API keys
Issue keys and call the platform from whatever you already run — your own dashboard, a reporting job, an internal tool your delivery team lives in. The same operations you use in the interface are available programmatically.
Signed outbound webhooks
Register a URL with a secret and a list of events you care about. Deliveries are signed, so your endpoint can verify a payload came from us before acting on it rather than trusting anything that arrives.
Webhook delivery logs
When a client asks why something did not reach their CRM, you want an answer rather than a theory. Delivery logs record what was sent where, which turns an argument into a lookup.
Wallet and transaction data
Balances and transaction history are readable per organisation, which is the raw material for pulling message spend into whatever you already use to invoice clients.
Straight answer
About the phrase “white label”
Agencies searching for a white label WhatsApp Business API usually want one of two different things, and the difference matters. Some want operational separation: distinct client accounts, distinct data, distinct billing, one place to work from. Others want visual separation: their own domain, their own logo, a portal the client believes the agency built.
ChatSetu AI provides the first today. Separate client organisations, per-organisation wallets and pricing, role-based member access, an administrative layer above the client accounts, and an API to build on. It does not currently provide a custom-domain, custom-branded reseller portal, and we would rather say so on the page than in a sales call after you have moved clients across.
Agency terms are quoted per agency rather than published as a tier list, because the right number depends on how many client organisations you run and the volume across them. If you manage WhatsApp for several businesses, tell us how you are set up and roughly what your clients send, and we will come back with pricing that fits.
Typical setup
How an agency sets this up
Six steps, in this order. The third one is where agencies most often take a shortcut they regret.
- 1
Set your own organisation up first
Start with the account your agency operates from. Get your own team in, roles assigned, and the working pattern settled before you put a paying client behind it. Everything you learn here you will repeat eight times.
- 2
Create an organisation per client
One client, one organisation. Resist the temptation to run two small clients together because it seems tidier — separating them later means moving contacts, templates and history across a boundary, and that is a job nobody enjoys.
- 3
Connect each client's own WhatsApp number
Each client's WhatsApp Business account and number belong to that client's organisation. Their business verification, their display name, their quality rating. An agency does not want one shared number carrying the reputation risk of every account it manages.
- 4
Add your people with the right roles
Invite the account team into the organisations they cover, and only those. Set up teams and departments so conversations route to the people who know the client, rather than to whoever happens to be looking at the inbox.
- 5
Fund the wallet and check pricing per market
Load the client's wallet and look at the per-country rates for the markets they message. This is the conversation to have with a client before their first campaign, not after their first invoice.
- 6
Wire the API into your own reporting
Generate an API key, register a webhook endpoint with its secret and the events you care about, and pull what you need into the dashboard your clients already look at. Check the delivery logs the first week rather than assuming.
Where to go from here
If you are new to reselling this channel, start with what the WhatsApp Business API involves and how a business gets access in the first place, since you will walk every client through that. Day to day, most agency work happens in the shared team inbox with departments and ticketing, and in campaigns, where per-country cost estimates keep a client's spend predictable.
The retainer work usually sits in automation flows and AI chatbots grounded on each client's own documents, which is the sort of thing you build once per client and maintain. For ecommerce accounts, the Shopify integration covers order updates and cart recovery without a bespoke build.
FAQ
Agency and reseller questions
Including the ones we would rather answer here than halfway through onboarding.
Can one login manage WhatsApp for several clients?
Yes. ChatSetu AI is multi-organisation: each client is a separate organisation with its own contacts, conversations, templates, campaigns and settings, and requests carry an active organisation identifier so one account can operate across them. You switch the organisation you are working in rather than logging in and out of separate accounts.
Is ChatSetu AI a white label WhatsApp Business API platform?
That phrase means different things to different people, so here is the honest answer. What exists today is genuine multi-tenancy: separate client organisations under one operator, per-organisation wallets and pricing, role-based member access, an administrative layer above the client organisations, and a full API. What does not exist today is a reseller-branded portal with your own domain, logo and colours. If custom branding is the deciding factor for you, ask us before you commit rather than assuming it is there.
How does billing work when I run WhatsApp for multiple clients?
Each organisation has its own prepaid wallet with a balance, an add-funds path and a transaction history, so message spend sits against the client that generated it. Per-country message pricing is held in the product, which matters because Meta's rates differ by country and template category. That gives you a per-client number to work from instead of dividing one agency bill by guesswork.
Can I pull client data into my own dashboard?
Yes. There are API keys for direct calls and signed outbound webhooks, where you register a URL, a secret and the events you want. Deliveries are signed so your endpoint can verify them, and webhook delivery logs let you check what was actually sent when something looks missing.
Do my clients need their own WhatsApp Business accounts?
Yes, and they should want to. The WhatsApp Business account, the number, the display name and the quality rating belong to the client's business. That keeps their sender reputation their own, keeps you out of the middle if they ever move, and avoids one restricted number taking every client you manage offline at once.
What are the commercial terms for agencies and resellers?
Agency pricing depends on how many client organisations you run and the volume across them, so we quote per agency rather than publishing a tier list. Tell us how many accounts you manage and roughly what they send, and we will put a number to it.
Running WhatsApp for more than one client?
Tell us how many client accounts you manage and we will come back with agency pricing.