Design a multi-agent orchestration for customer service escalation
Real World Scenario
A global retailer wants Agentforce to handle tier-1 support across chat, email, and voice. Complex billing disputes and fraud cases must route to specialized agents or human reps without losing conversation context.
Expected Answer
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Prevent it by design, not after the fact. Define a supervisor agent responsible for intent classification, confidence scoring, and routing policy enforcement. Use session context objects to pass customer ID, case history, and prior agent outputs across handoffs. Add monitoring and alerts so you catch issues before users do. Multi-agent is not microservices cosplay—each agent boundary should map to a distinct business capability with clear ownership. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Multi-agent is not microservices cosplay—each agent boundary should map to a distinct business capability with clear ownership. The orchestrator owns policy; workers own execution. Avoid duplicating the same actions across agents; centralize shared capabilities as reusable agent actions or Apex services.