In a multi-agent solution, a customer asks for a live person while working with a connected subagent. The request reaches an escalation flow, but every human queue is offline at that moment. What does the customer get?
id q5b730d3301
Home / Agentforce Specialist / Objective 6.1
Domain 6: Multi-Agent Orchestration · 5% of the exam · Full exam outline
Given a scenario, determine whether a Multi Agent architecture is appropriate for scalability and control.
In a multi-agent solution, a customer asks for a live person while working with a connected subagent. The request reaches an escalation flow, but every human queue is offline at that moment. What does the customer get?
id q5b730d3301
A retail service team with all its agents in one Salesforce org is adopting Single-Org Multi-Agent (SOMA). What experience does this architecture give the end users?
Choose an answer to check it. Afterward, select any option to review its explanation.
This is the situation SOMA is meant to remove: users managing conversations with several agents one by one. The orchestrator hides the specialists behind one touchpoint instead.
SOMA puts a parent orchestrator in front of the user and delegates each task to the specialist agent best suited to it, so the user keeps a single touchpoint while specialists work in the background inside the same trust boundary.
SOMA is built on delegation from a parent agent to specialists; keeping every topic in one agent is the single-agent model whose limited cognitive span SOMA is meant to work around.
Tempting because it describes a real multi-agent pattern, but delegating to agents in other orgs is MOMA. This team has every agent in one org, which is exactly the SOMA case.
id qcdd950aa74