Severity definitions
Severity is set by impact on the customer's outcome, never by the volume of their frustration. Write that sentence into the document; it is the rule that stops the loudest account consuming the capacity a quietly failing one needed.
| Level | Definition | Owner | Response | Customer communication |
|---|---|---|---|---|
| Sev 1 | Delivery has stopped, or a committed outcome will be missed | Named senior owner | Within 1 hour | Proactive, same day, with a plan and a next update time |
| Sev 2 | Delivery degraded, or a milestone is at risk | Team lead | Same working day | Plan communicated within 2 working days |
| Sev 3 | Isolated issue with a workaround available | Standard owner | Within the standard SLA | Normal channel; no proactive escalation |
Internal triggers
The part most matrices omit. These fire without the customer saying anything, which is the whole point.
| Condition | Raises | Notify |
|---|---|---|
| Onboarding milestone missed by more than 3 days | Sev 2 | Delivery lead |
| Issue open past its severity SLA | Escalate one level | Support lead |
| Two consecutive checkpoints skipped | Sev 2 | Account owner's manager |
| Committed delivery date at risk inside 5 working days | Sev 1 | Senior owner and commercial owner |
| Customer response latency doubles over two cycles | Sev 3 review | Account owner |
Routing and continuity
- Escalations route to a role with a named fallback, never to an individual only.
- Every notification carries the context and the available options, not just an alert.
- Out-of-hours behaviour is written down, including who is genuinely reachable.
- The customer-facing owner is named at each level so the customer hears one voice.
- Every escalation is logged with cause and resolution, in structured form.
The monthly review
Escalations are data about the operating system. Once a month, review what escalated and why. Recurring causes are process defects, and fixing the top cause each month is the only mechanism that makes escalation volume fall.
Related work
The problem is described in escalations arrive too late; the surrounding system is customer success operations.
Muhammad Sameed Abid
Muhammad Sameed Abid is a business operations, automation and growth systems professional with 9+ years across operations management, workflow and CRM automation, marketing operations and customer success. He is currently Head of Customer Success at GHA Marketing and writes here about the operating layer underneath growth.