Feature
Pam OS
Operate multiple Pam Pods from a portfolio command center with cross-workspace health, approvals, mail queues, and pipeline signals without losing Pam Pod isolation.
Portfolio visibility without tenant bleed
Pam OS aggregates open conversations, pending approvals, mail health, and top campaigns across Pam Pods. Operators prioritize work at the portfolio level, then drill into a specific Pam Pod for execution.
Cross-Pam Pod alerts and routing
Alerts surface agent run failures, deliverability issues, and approval backlogs across workspaces. Portfolio operators decide, approve, and route work before execution continues inside individual Pam Pods.
Orchestration, not a second CRM
Pam OS does not duplicate CRM records. It reads operational state from each Pam Pod so portfolio teams observe and govern outbound motion without merging data across isolated workspaces.
Related
FAQ
When do I need Pam OS instead of a single Pam Pod?
Pam OS helps when your organization runs multiple Pam Pods for different teams, clients, or motions. Single-Pam Pod teams use the workspace directly without portfolio overhead.
Can Pam OS change CRM records in a Pam Pod?
Pam OS is a portfolio control layer. CRM changes happen inside each Pam Pod. Pam OS surfaces state and approvals so operators act in the right workspace.
How does Pam OS relate to permissions?
Portfolio access respects organization membership and Pam Pod permissions. Operators see only the Pam Pods their role allows.
See this in your workspace
Book a demo to walk through this capability with your team.