workflow:technical-support-escalation
Technical Support Escalation overview
Manages the escalation of technically complex support cases to engineering — defining clear escalation criteria based on issue reproduction complexity, code-level investigation requirements, and potential bug severity, packaging escalation handoffs with structured reproduction steps, environment details, log snippets, and customer impact assessment, routing to the appropriate engineering team based on component ownership and on-call schedules, tracking engineering SLAs for acknowledging, investigating, and fixing escalated issues, managing customer communication cadence during engineering investigation periods, coordinating hotfix deployment decisions versus next-release scheduling, feeding resolution patterns back to support teams as runbooks for future self-resolution, and maintaining an escalation backlog review cadence to prevent aging issues. Produces escalation volume dashboards, engineering response SLA reports, and fix-time distribution analyses by component. Excludes L1 triage and product roadmap prioritization.
Attributes
Outgoing edges
- domain:customer-experience·DomainCustomer Experience
- domain:operations·DomainOperations
- role:bug-triager·RoleBug Triager (Bot)
- role:debugger·RoleDebugger
- role:engineering-manager·RoleEngineering Manager
- org-unit:support-team·OrgUnitSupport Team
- org-unit:engineering·OrgUnitEngineering
- skill-area:customer-success·SkillAreaCustomer Success
- skill-area:observability-pipeline·SkillAreaObservability Pipeline
- responsibility:triage-incoming-issues·ResponsibilityTriage incoming issues
- responsibility:respond-incidents·ResponsibilityRespond to production incidents
Incoming edges
- tool:medusa·ToolMedusa
- tool-server:mcp-medusa-candidate·ToolServerMedusa MCP candidate