Skip to main content

Churn Risk Prediction

Windback continuously scores every customer in your project to predict how likely they are to churn. Scores update daily so you can intervene before a cancellation happens.

How It Works

The scoring algorithm analyzes 13 negative signals and 5 positive signals drawn from billing data, product usage, and support activity. Each signal carries a configurable weight, and the final score is normalized to a 0-100 scale where higher means more risk.

Negative Signals

Positive Signals

Positive signals reduce the overall risk score:

Risk Levels

Scores map to four risk levels:
Focus your team’s energy on Critical and High customers. Medium-risk customers often recover on their own once a product issue is resolved.

Auto-Email Delivery Modes

When a customer crosses a risk threshold, Windback can notify them (or you) automatically. Choose one of two delivery modes.
Windback sends the email to the customer on your behalf using your configured sender domain. No code required.
  • Emails are generated by Windback AI and match the tone you select (friendly, professional, urgent).
  • You can preview and edit templates in the dashboard before they go out.
Direct mode requires a verified sender domain. Go to Settings > Email to configure one.

Configuration API

Manage churn-risk settings programmatically with the configuration endpoints.

Get Current Config

Response:

Update Config

Changing delivery_mode takes effect immediately. Any in-flight emails for the previous mode will still be delivered.

Dashboard Features

The Churn Risk page in your project dashboard gives you a real-time view of your customer base.

Risk Distribution

A breakdown of how many customers fall into each risk level, updated daily.

Customer List

Filterable table of all customers with their current score, top signals, and last activity date.

Score History

A per-customer timeline showing how their risk score has changed over the past 90 days.

Alert Log

A record of every auto-email or webhook delivery, including delivery status and timestamps.
Churn risk scoring requires at least 7 days of event data before scores become meaningful. New projects will see scores populate after the initial data collection period.