Users need a task handled across Microsoft 365, Sales and Finance systems by specialists. What do you design?
Why B is the answer
A multi-agent solution
A task that spans several systems suits a multi-agent solution, where specialist agents handle each part.
In detail
- Specialists across several systems suit a multi-agent solution.
- Use several agents only when one agent cannot do the job well.
Use case
An illustrative scenario, not a real incident.
A customer request needs contract data, a sales record and an invoice. A coordinator sends each part to the agent that knows that system.
See it in different ways
flowchart TD A["User"] --> B["Coordinator agent"] B --> C["Sales agent"] B --> D["Finance agent"] B --> E["Service agent"]
sequenceDiagram participant U as User participant C as Coordinator participant S as Sales agent participant F as Finance agent U->>C: Request C->>S: Task and context S-->>C: Result C->>F: Task and context F-->>U: Completed work
sequenceDiagram participant P0 as User participant P1 as Coordinator participant P2 as Sales agent participant P3 as Finance agent P0->>P1: Request P1->>P2: Sales part P1->>P3: Finance part P1-->>P0: Combined answer
Key point: Multi-agent designs split work between specialists.
Why the other options are wrong
- A. One prompt with no tools or knowledge at all
- A prompt with no tools cannot reach those systems.
- C. A single report in Excel
- A report does not handle a task.
- D. A single agent with one long set of instructions for every product
- One agent with everything is hard to maintain.