Manage WhatsApp for all your clients from one place.
Keep your clients' WhatsApp Business Accounts, phone numbers, templates, messages and events organized without managing every environment separately.
Starting at ₹499/WABA/month
Meta WhatsApp messaging charges billed separately.
Every new client adds another WhatsApp environment to manage.
One client is simple. Five clients means five sets of accounts, numbers, templates, message history and credentials — and a team that has to keep them straight.
- WABA
- Phone numbers
- Templates
- Messages
- Events
- Credentials
- WABA
- Phone numbers
- Templates
- Messages
- Events
- Credentials
- WABA
- Phone numbers
- Templates
- Messages
- Events
- Credentials
The work isn't any one of these. It's that the same six things multiply by every client you take on.
One operational layer for every client.
There are two ways to organise a client portfolio, and both work today. Pick the one that matches how your team operates.
One organisation, many clients
Every client WABA lives in one organisation. You see them all in one list, and each gets its own API key.
Best when your team operates the accounts day to day.
An organisation per client
Each client is its own organisation and you switch between them, which re-issues an org-scoped token.
Best when client data should stay in separate workspaces.
See every client environment in one list.
The console lists every WhatsApp Business Account in the organisation you're working in, with the numbers and templates that belong to each.
Keep client environments clearly separated.
Everything WhatsApp-specific stays attached to the client's own account, and an API key reaches exactly one of them.
- WhatsApp Business Account
- Phone numbers, per account
- Templates, per account
- Message history, per account
- Webhook events, queried per account
- API keys — one key reaches one account
- Organisation members and their roles
- The console your team signs in to
Know what happened, for the client who asked.
Events are read for one account at a time, so a question about one client's message has an answer without touching anyone else's data.
GET /webhooks/events?wabaId=…&page=1&limit=20Make your client onboarding repeatable.
The same six steps for every client, so the tenth onboarding looks like the first.
- 01
New client
They bring their own WhatsApp Business Account.
- 02
Connect the WABA
Meta Embedded Signup, completed once per client.
- 03
Sync phone numbers
Numbers are pulled from Meta and registered.
- 04
Sync templates
Approved templates come across with their status.
- 05
Issue an API key
Scoped to that client’s account and nothing else.
- 06
Operate
Send, watch events, and read failures with Meta’s reason.
Connect client applications without crossing the wires.
The same endpoints across every client environment, with a key that reaches exactly one account — so a credential issued for one client can never act on another.
POST /messages HTTP/1.1Host: wa.draskenapis.comContent-Type: application/jsonx-access-key: ak_…x-secret-key: sk_… { "phoneNumberId": "123456789012345", "to": "919876543210", "type": "template", "templateName": "order_update", "templateLanguage": "en_US"}ak_…11ak_…22ak_…33One key per client account. The account a key belongs to is fixed when it's created, and a key with no account attached is refused at authentication.
Add clients without adding another disconnected system.
The operating model doesn't change as the portfolio grows — another client is another account in the same console, billed at the same per-WABA price.
Agencies that run WhatsApp for other people.
Different practices, same operational problem underneath.
Marketing agencies
Manage the WhatsApp infrastructure behind your clients’ communication workflows.
Technology agencies
Integrate WhatsApp into client applications through the API and event history.
CRM / ERP partners
Connect the customer workflows you already implement to WhatsApp messaging.
Implementation partners
Run the same WhatsApp setup process across every client environment.
Start with the WABAs you manage.
Each client account is billed per WABA per month, so the portfolio scales one plan price at a time. Running a larger portfolio? Agency pricing is quoted against your volume and requirements.
Agency FAQ
Can I manage multiple client WABAs?
+
Yes. An organisation can hold many WhatsApp Business Accounts, and the console lists every account in the organisation you are currently in. Multiple WABAs are available on Growth and above, and each is billed per WABA per month.
Can each client have their own WhatsApp Business Account?
+
Yes — each client brings their own account, connected once through Meta’s Embedded Signup. Phone numbers, templates, message history and webhook events all stay attached to that account.
Can I switch between client environments?
+
Yes, at the organisation level. You can list the organisations you belong to and switch into one, which re-issues an org-scoped token. So you can either keep every client in one organisation and work across them, or give each client its own organisation and switch between them.
Can I connect client applications through the API?
+
Yes. Each API key is scoped to a single WABA, so you issue one key per client and that key cannot act on any other client’s account. The messaging endpoints are the same across every environment.
Can I see webhook events per client?
+
Yes. Events are queried for a specific WABA, so you read one client’s activity at a time. Note that WA Console receives events from Meta and stores them — it does not forward them on to your own server.
Can I add more WABAs as my agency grows?
+
Yes. Pricing is per WABA per month, so adding a client adds one plan price. For larger portfolios, Agency pricing is quoted against your volume and requirements.
Does WA Console provide white-labelling?
+
No. There is no white-label dashboard, agency branding, reseller account or client-facing subaccount today. WA Console is the operational platform your team uses to run client WhatsApp environments; your clients are not billed through it and do not see an agency-branded product.
Can I give team members different permissions per client?
+
Not per client. Members belong to an organisation and carry a role there, so access is organisation-wide rather than scoped to individual client accounts. If you need harder separation between clients, use a separate organisation per client.
Manage your clients' WhatsApp infrastructure from one place.
Give your team a consistent way to connect, monitor and operate WhatsApp environments across your customer portfolio.
Starting at ₹499/WABA/month.