Escalation Path Design

An alert without a clear escalation path is a notification that lands in someone's inbox and waits for them to decide what to do with it. An alert with a designed escalation path is a trigger that activates a specific response chain with defined ownership, timelines, and handoff points. The escalation path turns the alert from information into action by removing the decision latency — the CSM does not need to decide who to involve, they follow the path.

1. Define Tier-Based Escalation Tier 1: CSM-level response. The CSM investigates and intervenes independently. Most amber alerts stay at Tier 1. Tier 2: Manager-level involvement. The CSM and their manager coordinate on the response. Red alerts and persistent amber alerts escalate to Tier 2. Tier 3: Executive-level involvement. The VP of CS and potentially the CEO engage. Strategic accounts with critical alerts escalate to Tier 3.
2. Set Time-Based Escalation If a Tier 1 alert is not resolved within 5 business days, it automatically escalates to Tier 2. If a Tier 2 alert is not resolved within 10 business days, it escalates to Tier 3. Time-based escalation prevents alerts from aging in one person's queue when they need additional resources or authority to resolve.
3. Design Context Packages When an alert escalates, the receiving person needs context — not just "Account X is at risk" but the full picture: which signals fired, the account history, the current health score, recent interactions, and the CSM's assessment of root cause. Design context packages that auto-generate when escalation triggers, so the escalation recipient can act immediately rather than spending hours gathering information.