AgentforceIntermediateescalationomni-supervisorhandoffservice-cloud
Escalate agent sessions to Omni Supervisor with structured context packets
Real World Scenario
Human agents complain that bot escalations arrive with no summary, forcing customers to repeat information and increasing handle time.
Expected Answer
• Generate structured handoff payload: intent, entities collected, actions attempted, failure reason, sentiment estimate
• Attach transcript summary—not full raw log—to Case and Omni routing record
• Pass customer verification status so human does not re-authenticate unnecessarily
• Route to skilled queue based on agent classification and failed action type
• Preserve chat session continuity where channel supports warm transfer
• Track escalation quality via human agent feedback scoring on handoff usefulness
• Define SLAs for escalation queue pickup after agent exit
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Security first: Generate structured handoff payload: intent, entities collected, actions attempted, failure reason, sentiment estimate. Enforce CRUD/FLS explicitly — `with sharing` alone is not enough. Attach transcript summary—not full raw log—to Case and Omni routing record. Escalation without context destroys containment ROI. Balance speed of delivery with maintainability.
Architect Perspective
Escalation without context destroys containment ROI. Treat handoff packets as a first-class API contract between agent and human workflows.