Section 7 · Multi-Agent Orchestration · 5% of exam
7.2 Orchestrators and Connected Subagents
Exam objective
Explain how an orchestrator coordinates specialized agents and how subagent scope and descriptions affect delegation.
Define the coordinator’s responsibility
In Salesforce’s multi-agent pattern, an orchestrator provides a coordinating layer for connected agents, which Salesforce documentation now calls subagents. The orchestrator can serve as the initial point of contact, interpret the conversation, and route work to a specialist. The architecture determines whether the orchestrator stays responsible for the user-facing conversation or transfers control. The coordinator should have a clear purpose: recognize which capability is needed, provide the required context, and manage the result or transition. It should not duplicate every specialist’s instructions and actions, because that erodes the value of separating responsibilities. Give each subagent a bounded job
A subagent should have a well-defined area of responsibility, useful instructions, and only the actions and information it needs. Its name and description matter because the router uses the connected agents’ descriptions and the conversation context to select a match. Write descriptions that state the task, the kind of request it handles, and important boundaries. Avoid vague or overlapping labels such as “General Support” for several agents. If the subagents’ scopes overlap, refine their descriptions and instructions or redesign the division of work so the router can distinguish them reliably.
Plan context and permissions
Delegation works only if the receiving agent has enough context to perform its part. Decide which details should travel with the request, such as a record identifier, language, verified customer intent, or relevant prior result. Pass the minimum useful context and do not assume a specialist automatically has all conversation history or data available. Review each agent’s identity, permissions, connected actions, and data access separately. A handoff should not be used to bypass access controls. If an action requires verification or a particular user context, preserve that requirement through every delegated step.
Coordinate the result
The design should state who handles incomplete work, conflicting results, errors, and escalation. A specialist can return a concise result or take over the interaction, depending on the selected orchestration pattern. The orchestrator may need to request additional work, summarize the outcome, or explain that a human must continue. Keep the result format and responsibility clear enough that the receiving layer can use it correctly. Test representative requests for every subagent, ambiguous requests that could match more than one, and requests that should not be delegated. Review routing traces to see which description and action path was selected. This also supports review: administrators can verify that the intended specialist was selected and stayed within its assigned scope.
Make each subagent’s description distinct, task-focused, and explicit about what it should not handle.
A connected subagent is still subject to its configured permissions and available actions. Delegation does not grant broader access by itself.
Extra concept: A good routing description functions like a selection rule: it helps the coordinator distinguish the specialist from its neighbors.
Official references:
- Multi-Agent Orchestration https://help.salesforce.com/s/articleView?id=ai.agent_multi_orch.htm&language=en_US&type=5
- Subagent Classification and Routing https://help.salesforce.com/s/articleView?id=ai.agent_topics_routing.htm&language=en_US&type=5
- Connect an Agent as a Subagent https://help.salesforce.com/s/articleView?id=ai.agent_multi_orch_connect.htm&language=en_US&type=5
Key takeaways
- The orchestrator coordinates requests; connected agents or subagents own specialist work.
- Distinct descriptions, scoped instructions, and purposeful context help routing work reliably.
- Set permissions and escalation behavior for the delegated agent as part of the architecture.
