CX-301b · Module 1

Alert Priority Framework

3 min read

Not all at-risk accounts are equally urgent. An enterprise account with a six-figure annual contract and a renewal in 45 days requires a different urgency response than a startup account with a five-figure contract and a renewal in nine months. The alert priority framework layers account context onto signal urgency to produce a prioritized action queue. The CSM who sees all alerts as equally urgent responds to everything with the same intensity — which means they respond to nothing with appropriate intensity.

Do This

  • Factor account value (ARR), renewal proximity, and strategic importance into alert priority — not just signal severity
  • Implement a four-level priority system: P1 (action today), P2 (action this week), P3 (action within two weeks), P4 (monitor next cycle)
  • Review and adjust priority weightings quarterly based on which P-levels actually correlated with churn

Avoid This

  • Prioritize alerts solely by signal severity — a red alert on a small account may be less urgent than an amber alert on a strategic account
  • Treat all alerts as P1 — when everything is urgent, nothing is urgent
  • Ignore low-priority alerts indefinitely — P4 alerts that persist for multiple cycles should be escalated to P3