Salesforce Decode
Salesforcedecode
Back to questions
AgentforceArchitect (Hardest)multi-agentorchestrationescalationservice-cloud

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

• Define a supervisor agent responsible for intent classification, confidence scoring, and routing policy enforcement • Create domain-specific worker agents (billing, fraud, returns) with scoped topics, actions, and knowledge bases • Use session context objects to pass customer ID, case history, and prior agent outputs across handoffs • Implement human-in-the-loop triggers when confidence falls below threshold or sensitive PII/fraud keywords appear • Apply guardrails at orchestration layer: action allowlists, rate limits, and audit logging for every agent decision • Design fallback paths when a worker agent fails or times out—default to human queue with summarized transcript • Measure per-agent containment rate, escalation rate, and average handle time to tune routing rules

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.