Short answer
Escalation management coordinates urgent customer issues with clear ownership, updates, and resolution criteria. Assess triage, coordination, communication, and closure within the role, not whether the underlying issue was caused or solved by that person.
About Escalation management
Structures the response to an urgent customer issue by clarifying impact, ownership, update cadence, decisions, and exit criteria until the escalation is resolved or transferred.
Use this competency for
- Roles that coordinate urgent customer issues across participants.
- Functions accountable for customer updates, response ownership, and escalation closure.
Do not use this competency for
- Roles that troubleshoot assigned technical issues but do not coordinate the escalation response.
Important distinctions
Incident management
Incident management restores a service and coordinates technical response. Escalation management coordinates customer impact, expectations, ownership, and communication around an urgent issue.
Account health assessment
Health assessment identifies emerging risks. Escalation management begins when an issue requires urgent, explicit coordination.
Expectations by level
IC1
IC1
Completes assigned escalation actions from an established process, keeps facts and owners current, and raises missed updates or blocked decisions.
Observable behaviors
- Records confirmed impact, current owner, and next update time.
- Separates verified facts from open questions in status notes.
- Raises a missed action or update through the defined path.
Examples
- Updates the record after engineering confirms what is known and still unknown.
- Alerts the coordinator when the promised customer update has no owner.
IC2
IC2
Coordinates standard escalations independently, establishes response roles and communication cadence, and closes the escalation against explicit criteria.
Observable behaviors
- Clarifies impact and urgency without claiming an unverified cause.
- Assigns actions and updates to participants with confirmed deadlines.
- Documents resolution, remaining work, and the post-escalation owner.
Examples
- Changes the update cadence after impact expands and tells participants why.
- Closes the escalation after agreed service and communication criteria are met.
IC3
IC3
Leads complex escalations with competing constraints and improves response standards through decision paths, cross-team alignment, and review of recurring coordination failures.
Observable behaviors
- Defines a decision path when authority or ownership is unclear.
- Aligns customer, technical, commercial, and leadership communication without merging their responsibilities.
- Uses post-escalation evidence to improve triggers, roles, or update practices.
Examples
- Establishes who can make a tradeoff decision when several teams own dependencies.
- Revises the escalation template after reviews show repeated ambiguity about exit criteria.