Section 7 · Multi-Agent Orchestration · 5% of exam
7.3 Handoff and Supervisor Modes
Exam objective
Choose between handoff and supervisor routing based on who should own the conversation and whether the final answer needs synthesis.
Understand the control difference
Salesforce documents two main routing patterns for multi-agent solutions: handoff mode and supervisor mode. In handoff mode, the orchestrator transfers control to a connected subagent. That specialist then manages the interaction and responds directly to the user. This can avoid an extra synthesis step and suit a task where one specialist should own the rest of the conversation. In supervisor mode, the orchestrator remains responsible for the user conversation. It delegates a request to one or more subagents, receives their results, and composes the answer. The key distinction is who retains control of the conversation.
Choose handoff when one specialist should take over
Handoff is a fit when the request belongs to a specific domain and the specialist needs to lead an end-to-end exchange. Imagine a billing specialist that must ask follow-up questions, inspect invoice details, and explain next steps. The orchestrator can route the user to that agent, which handles subsequent turns directly. This pattern can reduce response steps, but the transition should feel understandable and preserve the context the specialist needs. Use clear language and a reliable fallback if routing fails or the subagent cannot complete the request. Choose supervisor when results need coordination
Supervisor mode is useful when the orchestrator should remain the single conversational owner or needs to combine results before responding. For example, a service request might need a case status from one specialist and a warranty eligibility result from another. The orchestrator can delegate these focused tasks, compare the returned information, and present one coherent response. This pattern supports synthesis and a consistent user-facing voice, but adds work for the coordinating agent. Make clear how it handles missing, delayed, or inconsistent results and when it should ask the user a follow-up question.
Read scenario clues carefully
In a question, phrases such as “the specialist should take over and continue the conversation” point to handoff. Phrases such as “the main agent remains the contact and combines specialist results” point to supervisor. A requirement for a single conversational front door also favors supervisor. A requirement for a specialist to directly manage a domain-specific dialogue favors handoff. Do not confuse these routing patterns with MCP or A2A: handoff and supervisor describe conversation control within an orchestration design, while protocols standardize how systems or agents communicate. Select the pattern that matches the required owner and result flow.
Ask: who should speak to the user after delegation, and must results be combined before the answer? Those clues identify the routing mode.
The preferred mode depends on the solution’s user experience and coordination needs; neither pattern is best for every case.
Extra concept: A supervisor can keep the conversation while delegating work; a handoff changes which agent directly manages the conversation.
Official references:
- Multi-Agent Orchestration: Handoff and Supervisor Modes https://help.salesforce.com/s/articleView?id=ai.agent_multi_orch.htm&language=en_US&type=5
- Agent Script in Multi-Agent Solutions https://help.salesforce.com/s/articleView?id=ai.agent_multi_orch_script.htm&language=en_US&type=5
- Salesforce Certified Agentforce Specialist Exam Guide https://help.salesforce.com/s/articleView?id=005298924&language=en_US&type=1
Key takeaways
- Handoff transfers control to a connected specialist that responds directly to the user.
- Supervisor keeps the orchestrator in control while it receives and synthesizes delegated results.
- Choose based on conversation ownership, need for synthesis, response flow, and failure handling.
