Lean agency pod: separate Business Brains per client, one approval queue

Separate brains, same agent roster

Each client gets products, voice, and results isolated in its own Business Brain. Agents do not mix copy between accounts. When a strategist switches clients, the workspace label changes — not a shared doc with tabs.

• Voice examples live inside that client’s brain only.
• Product names and offers never bleed into another client’s drafts.
• Reporting summaries reference one Meta ad account at a time.

Coordinated teamwork: multiple clients, one inbox pass

In a pod with two account coordinators and one strategist: Morning triage brings support agents drafting replies from Client A’s brain, with the coordinator approving threads and escalating custom requests. Midday brings Client B’s content queue with carousel copy awaiting sign-off. Afternoon brings Client C’s campaign agent proposing ad sets tied to their seasonal catalog.

Strategist as approver, not typist

Junior coordinators and agents draft ads and content; a strategist approves in batch. Revisions teach the brain what that client accepts.

• Campaign drafts reference only that client’s Meta account.
• Content queues show client name and approval state clearly.
• Rejected drafts include a short reason so the next attempt improves.

Handoff checklist before client-facing send

Use a repeatable quality gate so speed does not trade off accuracy:

• Client name on the approval card matches the Business Brain you edited.
• Offers, dates, and disclaimers match the client’s current brief.
• Screenshots or links in the draft open correctly on mobile.
• Angry or legal-sensitive threads are marked human-only, not auto-drafted.
• Ad spend changes show paused-until-approved in the queue.

When unified inbox work spans a client’s channels

Agencies often inherit messy messaging: Instagram for one client, WhatsApp for another, Facebook Page for a third. The pod still benefits from one triage habit per client brain — even if Meta Business Suite remains the front door. Coordinators can document channel facts in the brain so drafts stay consistent across apps.

Pricing that matches a small shop

Teams on Starter or Growth plans can run a handful of client brains; Enterprise covers custom needs. Join the waitlist for access — details on pricing.

Questions agencies ask before turning on agents

Will agents mix clients? Not if each client has an isolated Business Brain and approvals are labeled by client. Who owns the send button? The agency strategist or account lead — agents prepare, humans publish. What if a client’s voice is undefined? Pause automation and capture voice examples first; otherwise approvals become rewrite marathons. Can one pod share login access? Use roles your platform supports; this example assumes clear approver identity per queue.