Customer data glossary
Orchestrator agent
An orchestrator agent is an agent that routes requests to rails, holds the approval queue and tracks work to close, without reading customer records or approving anything.
By Art Kukharenko · Published · Updated
All glossary termsPart of the Learn hub and the customer data glossary.
What it means in practice
An orchestrator agent moves work, not data. On AI agent rails it is called the Orchestrator, and it runs at L4 on routing only. Its data scope is request metadata, redacted request text, the rail catalogue and queue state, with no customer tables.
Its limits matter more than its reach. It may start a run, notify people, expire a request and broadcast a pause. It must never read a customer record, approve anything or widen a scope. Routing should be a table that people change through change control. A model at most classifies free-text requests, and low confidence goes to a person.
The word means other things elsewhere. In Anthropic's orchestrator-workers workflow, a central model breaks a task into subtasks, assigns them to worker models and combines the results 1. Adobe's AEP Agent Orchestrator, generally available since 10 September 2025, interprets intent and decides which agents to activate 2. The rails version is deliberately narrower, so check what a vendor's orchestrator can read and do.
A model is often unnecessary here. A small team can use a workflow engine with a routing table and get most of the benefit. Anthropic's general advice is to start with the simplest solution 1.
The Orchestrator is a role in a vendor-neutral method, and PrivyCDP does not ship it. PrivyCDP exposes an MCP-ready interface that a router of this kind could call.
Example (life insurer, illustrative): a marketer submits new policy copy for review. The Orchestrator routes it to the Claims Checker rail, opens one correlation ID and tracks the request. A compliance reviewer signs off regulated claims. The Orchestrator sees the request, never a policyholder.
Related terms
- Correlation ID: issued once per request.
- Kill switch: the pause it broadcasts.
- Approval gate: the queue it holds but cannot clear.
- AI agent: the broader term.
Where it matters
- The Orchestrator agent: routing without giving agents the keys.
- How the three cross-cutting agents fit together: the control plane.
- Marketing claims compliance check: one routed job.
Back to the customer data glossary or the Learn hub.
Browse use casesFunction playbooksAgent roster
FAQ
Can an orchestrator agent approve work?
No. It holds the approval queue and the timeouts, never the approval right. A person approves, and a timeout expires the request.
What happens if the Orchestrator goes down?
No new work starts, and a human owner can also stop it. Rule-based controls elsewhere keep running, and people can still do the job by hand.
Sources
Further reading
- AI Marketing Claims Checker: An Agent
- AI Agents for Email Marketing
- Marketing Compliance Review With AI
- Agent rails
- AI Agent Permissions Template Download
Published: · Updated:
Editorial dates describe content changes. Confirm current sources before making legal, security or purchasing decisions.