risk-flag

To generate a customer escalation memo, aggregate churn signals and health alerts into a structured brief with risk severity, root-cause hypothesis, and escalation routing. This risk memo provides leadership with the specific fields needed to act on at-risk accounts.

Triage churn signals by classifying risk severity based on aggregated account health alerts and configured constraints. This churn-prevention triage process produces an evidence-based signal inventory and a recommended CSM intervention plan for at-risk accounts.

Yes, you can generate an escalation-ready summary output for managers or CROs that includes only the specific actable fields required. This escalation memo format hides internal health-model details while enforcing review and approval expectations before distribution.

Yes, risk-flag requires loading customer-success configuration from CSM CLAUDE.md and company-profile.md. These configuration files define the escalation matrix, SLA, contact routing, and governance constraints needed to classify account risk accurately.

You need an escalation matrix for renewal risk preparation when multiple health signals must be aggregated into severity tiers and quick leadership involvement is necessary. It enforces SLA, contact, and channel routing to guide CSM intervention plans.

A risk memo relies on pre-configured escalation matrices and loaded customer-success context, meaning it cannot classify risk or route escalations accurately without CSM CLAUDE.md and company-profile.md present. It functions best for health-alert-driven triage rather than real-time monitoring.