Renewal | risk early warning
Composite risk score from usage, sentiment, and payment latency. Drafted save email and call prep land in Slack before renewal becomes a fire drill.
Three signals that lead the obvious one
Renewal risk does not announce itself with a cancellation email. It announces itself with three signals nobody is watching together: product usage drops over the trailing fourteen days, support ticket sentiment turns negative, and invoice payment latency stretches. Each one alone is noise. All three together is the beginning of a churn conversation, and the platform that surfaces them as a composite is the platform that catches the conversation while there is still time to save the account.
What the composite score is built from
Product usage delta over the trailing fourteen days, weighted by the customer's primary use case. Ticket sentiment over the same window from Zendesk or Intercom or Front. Invoice payment latency over the trailing two cycles. Health score from Gainsight or ChurnZero where the customer has one. Account-level signals from the CRM (champion changing roles, key contact going dark on email).
What the CSM gets
A Slack DM with the composite score, the breakdown by signal, the drafted save email tuned to the specific risk pattern, and the talking points for a save call. The CSM reviews, sends the email, schedules the call, and the agent prep moves into QBR auto-pack mode for the call itself. The whole cycle compresses to a single morning rather than a quarter of triage.
Frequently asked
How early does the warning fire?
Sixty to ninety days before renewal in the typical case. Earlier if the signals shift fast. The whole point is to catch the conversation before the account hits the renewal cliff.
Can the agent send the save email itself?
Drafts only. The CSM reviews and sends. The agent does not auto-send customer-facing email.
Related use cases
QBR auto | pack
One deck per account, drafted from product analytics plus support plus CRM plus billing. The CSM reviews, edits, and walks into the QBR ready.
Contract renewal radar with auto | renewal trap detection
Ninety, sixty, thirty day alerts plus usage data plus a drafted negotiation memo per renewal. Auto-renewal traps surfaced before the cancellation window closes.
Tier-one ticket triage
Classify, try the runbook, escalate only with full context. The bulk of identity tickets close themselves rather than queueing for a human.