Multi-client WhatsApp inbox
A single workspace where your team manages every client's WhatsApp account \u2014 with strict tenant isolation, per-client metrics and role-based access.
- Tenant isolation
- Role-based access
- Per-client metrics
- Audit logs
Key things to know
Tenant isolation
Per-client database, full RLS.
Role-based access
Agent / manager / owner per client.
Per-client metrics
Opens, replies, conversion, SLA.
Audit logs
Every action logged per client.
People also ask
Q.Tenant isolation depth?
Full RLS — clients never see each other's data.
Q.Role-based access?
Yes — owner / manager / agent per client.
Q.Per-client billing?
Yes — bills attribute to the right client tenant.
Q.Quick switch UX?
Single dropdown — under 60s switch.
Q.Audit trail?
Yes — every send / assign / export logged.
Q.Scale limit?
No technical limit — agencies run 100+ clients here.
Built for agency operations, not single-client teams
Most WhatsApp CRMs are single-tenant. Agencies need multi-tenant — one workspace, infinite clients, strict isolation.
Add role-based access (junior agents see only their assigned client; managers see all) and per-client metrics, and one ops person scales to 12+ accounts.
Built for serious growth teams
Tenant isolation
Per-client database, full RLS.
Role-based access
Agent / manager / owner per client.
Per-client metrics
Opens, replies, conversion, SLA.
Audit logs
Every action logged per client.
Quick switch
Single dropdown across all clients.
Per-client SLA
Different thresholds per retainer tier.
Get live in days, not months
- 1
Set workspace + roles
- 2
Add clients as tenants
- 3
Assign agents to clients
- 4
Configure SLA per retainer tier
What teams ship with this
Performance agency book
30+ Meta clients.
Vertical-specialist agency
All clients in one vertical.
Full-service agency
Mixed verticals + service tiers.
Consultancy + execution
Strategy + delivery teams separated.
Frequently asked questions
Why Multi-client WhatsApp inbox is the highest-leverage move for growth teams
WhatsApp is where growth teams customers actually reply. Open rates sit at 85–98% inside 15 minutes versus 18–22% on email and sub-2% on SMS, and the medium is conversational — a customer can ask a follow-up, share a photo, or pay without leaving the thread. That is the entire premise behind multi-client whatsapp inbox: stop losing the conversation to slow channels and let intent convert while it is warm.
Most growth teams teams treat WhatsApp as a broadcast megaphone. The teams that win treat it as a workflow surface — every notification is also a decision point where the customer can act. The capabilities below are wired to do exactly that: each one collapses a multi-step off-platform detour into a single in-thread reply.
The impact numbers on this page — 12+ clients per ops person, 100% tenant isolation, 0 cross-client leakage, 60s client switch time — are pulled from LandinChat customers running this workflow for at least 90 days. They are directional; your mileage depends on list quality, template approval speed, and how aggressively you route qualified conversations to a live agent.
Each capability, in plain terms
Tenant isolation
Per-client database, full RLS. In practice this means the growth teams operator running multi-client whatsapp inbox does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Role-based access
Agent / manager / owner per client. In practice this means the growth teams operator running multi-client whatsapp inbox does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Per-client metrics
Opens, replies, conversion, SLA. In practice this means the growth teams operator running multi-client whatsapp inbox does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Audit logs
Every action logged per client. In practice this means the growth teams operator running multi-client whatsapp inbox does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Quick switch
Single dropdown across all clients. In practice this means the growth teams operator running multi-client whatsapp inbox does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Per-client SLA
Different thresholds per retainer tier. In practice this means the growth teams operator running multi-client whatsapp inbox does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
How this actually rolls out
Step 1. Set workspace + roles
Set workspace + roles is the foundation of the multi-client whatsapp inbox workflow. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 2. Add clients as tenants
Add clients as tenants is the next unlock of the multi-client whatsapp inbox workflow. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 3. Assign agents to clients
Assign agents to clients is the next unlock of the multi-client whatsapp inbox workflow. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 4. Configure SLA per retainer tier
Configure SLA per retainer tier is the final lock-in of the multi-client whatsapp inbox workflow. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
How different teams put this to work
Performance agency book
30+ Meta clients. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Vertical-specialist agency
All clients in one vertical. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Full-service agency
Mixed verticals + service tiers. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Consultancy + execution
Strategy + delivery teams separated. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Buyer’s checklist
- • Official Meta Tech Partner — templates approve faster and account is not at ban risk.
- • Native growth teams data model — no glue-code to import contacts, orders, or bookings.
- • Green-tick support with a clear submission checklist and Meta-side follow-up.
- • Conversation-based pricing that matches WhatsApp’s own billing model, not per-message surcharges.
- • Human handoff with unread routing, so qualified replies never sit in a bot loop.
- • Audit log & role-based access — required for regulated enterprise buyers.
Common pitfalls
- • Broadcasting cold lists — quickest way to a quality-rating downgrade and eventually a template ban.
- • Skipping opt-in capture — makes every future utility template harder to approve.
- • Treating WhatsApp as a one-way channel — the platform penalises accounts with low reply-rate.
- • Running only one template variant — you leave 20–40% of lift on the table.
- • Not routing hot conversations to a human within 5 minutes — kills conversion by up to half.
What to measure after launching multi-client whatsapp inbox
Week 1 signal
Track template approval time, first-reply latency, delivered-rate, and the first 100 customer replies. For growth teams, the fastest warning sign is not low opens; it is customers replying with confusion because the trigger, offer, or handoff promise was not specific enough.
Month 1 signal
Compare reply quality across Tenant isolation, Role-based access, Per-client metrics, Audit logs. The best-performing growth teams teams keep the highest-intent replies visible to managers, then rewrite templates around real customer language instead of internal terminology.
Scale signal
Once Set workspace + roles → Add clients as tenants → Assign agents to clients → Configure SLA per retainer tier is stable, scale by segment rather than volume. Add new audiences only when opt-in source, template intent, agent ownership, and conversion tracking are all mapped.
Search-quality notes for this workflow
This page is intentionally built around multi-client whatsapp inbox rather than a generic WhatsApp marketing overview. The content references the actual workflow, the growth teams audience, implementation steps such as Set workspace + roles, Add clients as tenants, Assign agents to clients, Configure SLA per retainer tier, and use cases like Performance agency book, Vertical-specialist agency, Full-service agency, Consultancy + execution. That specificity helps buyers, internal teams, and search engines understand why this page deserves to exist separately from broader WhatsApp CRM, broadcast, chatbot, and automation pages.