Solutions / Agencies
Run WhatsApp campaigns for clients from one control plane.
Manage multiple client WhatsApp accounts, approved templates and broadcast audiences without sharing passwords or logging into separate tools. Each client keeps ownership of their WABA while your team works inside a permissioned workspace.
The problem
Client messaging gets messy at scale
Agencies inherit a pile of numbers, spreadsheets and template screenshots. Without a shared system, approvals, consent and reporting break down.
Client assets must stay under the client's ownership.
Broadcasts must never go to contacts who opted out.
Template approvals happen in Meta, not in a spreadsheet.
Campaign results need one consistent reporting model.
How it works
A workspace per client, one team view for you
Invite your team to each client organization with the right role. Campaigns, templates and conversations stay tenant-scoped, while your agency keeps a clean operational view.
Create a client organization
Separate billing, assets and audit history for every client from day one.
Connect the client's WABA
The client completes Embedded Signup. Their business assets remain theirs; your agency never holds Meta credentials.
Build consent-first audiences
Import contacts with opt-in source and timestamp, suppress opt-outs, and preview audience size before scheduling.
Report from real events
Sent, delivered, read and failed are driven by Meta status webhooks, not optimistic assumptions.
ClickMaker ConnectCustomer-owned WABA and phone number. Meta policy, templates and delivery remain under Meta's control.
Assets stay with the customerCapabilities
What you can build on the platform.
Campaign batching
Large broadcasts are queued and dispatched in controlled batches with per-number throttling.
Template library
See approval state, category, language and rejection reason before a campaign is built.
Team roles
Owners and admins manage access; agents handle inbox work; billing managers see invoices, not credentials.
Audit trail
Sensitive actions such as connection, key creation and campaign cancellation are recorded.
Create a campaign through the API
cURLcurl -X POST https://connectapi.clickmaker.in/api/v1/campaigns \
-H "Authorization: Bearer cmc_live_..." \
-H "Content-Type: application/json" \
-d '{
"name": "Diwali offer — Mumbai salons",
"phoneNumberId": "pn_01J...",
"templateId": "tpl_01J...",
"audience": {
"tags": ["mumbai", "salon"],
"optInOnly": true
},
"scheduledAt": "2026-11-10T09:30:00+05:30"
}'Examples reflect the documented API shape. Endpoints marked as planned in the developer portal are not yet available.
FAQ
Common questions.
Can each client see only their own data?
Yes. Multi-tenancy is enforced at the application layer and reinforced at the database layer. Agency staff only see organizations they are members of.
Who pays Meta for conversations?
The client's WhatsApp Business Account is the billing relationship with Meta. ClickMaker subscription charges and Meta messaging charges are kept separate.
Can we approve messages before sending?
The platform supports draft campaigns, scheduling and role-based access. Approval workflows are being expanded; they are not claimed as generally available yet.
ClickMaker Connect
Give your agency a WhatsApp backbone
Bring your client accounts into one permissioned platform with consent-aware broadcasts.
No shared ClickMaker sender · Customers own their assets