Use case
Portfolio operations
Leaders running several outbound motions or client workspaces
Govern multiple Pam Pods from Pam OS with cross-workspace health, approvals, mail queues, and revenue signals for agencies and multi-brand operators.
Isolated Pam Pods, unified oversight
Each team or client motion gets its own Pam Pod with separate CRM, domains, and sending policy. Pam OS aggregates health and activity so portfolio operators prioritize across workspaces.
Approval and deliverability at scale
Pending agent approvals and mail health issues surface at the portfolio level. Operators route work to the right Pam Pod before sends or automation continue.
Reports without manual rollups
Portfolio reports connect to real Pam Pod data. Operators inspect pipeline and campaign signals per workspace instead of maintaining external dashboards.
Related
FAQ
Can client data stay isolated?
Yes. Pam Pods isolate CRM, mail, and agent state. Pam OS reads operational signals without merging records across clients.
How many Pam Pods can one organization run?
Organizations configure Pam Pods per motion or client. Portfolio access respects membership and permissions for each workspace.
See this workflow in Pamphlet
Book a demo to walk through Pam Pod setup for your team type.