The challenge
- Agents must never mix Client A’s promo with Client B’s thread
- Freelancers should only see one client’s conversations
- Clients ask for weekly message stats without sharing Meta passwords
- Some clients run Click-to-WhatsApp ads; others are inbox-only
How Pulse structures the account
Organization vs workspaces
Scoped team access
For a junior freelancer on Green Bowl Co only:
Owners keep Billing & Usages and API Keys (organization owner only).
Member (Chat-only) is fine for full-time client agents who don’t need Templates or Analytics.
Label restrictions: When a custom member has specific labels selected, they only see threads with those labels in Chat. Empty label selection = see all threads (use explicit toggles for freelancers).
AI Agent per brand
Each workspace gets its own AI Agent — knowledge never crosses workspaces.
Pause globally: AI Agents list → toggle Paused during client crises or menu changes.
Assign in Chat: Recipient panel → Assigned to → brain icon → pick agent.
Templates per approval cycle
Agency submits WhatsApp templates per client in Templates → My Templates. Account lead tracks Approved / Pending / Rejected before any broadcast. Never reuse Client A’s template name for Client B — Meta approval is per WABA/workspace context.Client reporting without Meta access
Weekly deliverable for Bistro 22:- Switch to Bistro 22 workspace in Settings
- Analytics → WhatsApp channel → Last 7 days → Apply
- Screenshot summary cards or Export CSV (message trend, template performance)
- Optional: Message logs filtered by Failed for ops notes
Broadcasts for client promos (Growth+ per client org)
Taco Norte’s weekend special:- Label engaged diners
Taco-VIPduring the week - Chat → template composer → Broadcast → labels
Taco-VIP→ approved template - Schedule Saturday 11:00 UTC
Co-Admin for account managers
Before a client call:- “Give me an overview of this workspace” — channels, open threads
- “List our WhatsApp channels” — confirm connected numbers
- “What plan are we on?” — billing context
Optional: API dashboard (Advanced)
Pulse’s engineering team uses API Keys to feed a TV screen: openEnterprise label thread count per workspace. Not required for day-to-day agency work.
What Pulse does not do (common mistakes)
Results agencies care about
- Zero cross-client thread leaks via workspace isolation
- Faster freelancer onboarding with Member (Custom) roles
- Client-ready reporting from Analytics exports — no Meta seat license per client
Copy-paste playbook
- Advanced plan + Settings → Organization → Workspaces — one workspace per client
- Channels catalog per workspace — WhatsApp / Instagram / Messenger as needed
- WhatsApp Support only vs Support, sales & ads per client ad strategy
- Labels per workflow:
Reservation,Catering,Complaint - One AI Agent + brand knowledge per workspace (optional)
- Member (Custom) for freelancers; owners on billing
- Weekly Analytics CSV/screenshot per client WhatsApp number
- Co-Admin for pre-call workspace snapshot