> For the complete documentation index, see [llms.txt](https://docs.churned.io/churned-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.churned.io/churned-docs/models.md).

# Models

The seven models behind Churned, what each predicts, what it needs and where it surfaces

Churned runs seven kinds of models. Each is described on its own page with the same structure: what it predicts, what data it needs, how it works, how often it runs, how to read the output, and where it surfaces in the journey.

| Model                                                                    | Predicts                                                                                                                    | Surfaces in                                       |
| ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| [Health scoring](/churned-docs/models/health-scoring-model.md)           | The probability that a customer with a subscription churns, expressed as a health score, risk score and level, with drivers | Understand health, Build audiences                |
| [RFM](/churned-docs/models/rfm-model.md)                                 | Segments of one-off buyers or donors by recency, frequency and monetary value                                               | Understand health, Build audiences                |
| [RFV](/churned-docs/models/rfv-model.md)                                 | Segments of users by recency, frequency and volume of product usage                                                         | Understand health (SaaS users)                    |
| [Audience clustering](/churned-docs/models/audience-clustering-model.md) | Groups of customers that share a retention, reactivation, upsell or engagement opportunity                                  | Build audiences                                   |
| [Sentiment](/churned-docs/models/sentiment-model.md)                     | The sentiment of contact moments such as support tickets and emails                                                         | Understand health, Measure impact                 |
| [Co-pilot](/churned-docs/models/co-pilot-model.md)                       | The next best action per customer, learning from outcomes                                                                   | Automate with workflows, Optimise, Measure impact |
| [Reactivation](/churned-docs/models/reactivation-model.md)               | The probability that a churned customer comes back                                                                          | Build audiences, Measure impact                   |

## What they have in common

* **Trained on your data only.** Every model is trained per organisation on the history delivered by your integrations; nothing is pooled across customers.
* **Refreshed daily, retrained periodically.** Scores are recomputed every day from the latest data; the models themselves are retrained on a schedule and after data changes, with a check that the new model is at least as good as the current one before it replaces it.
* **Explained, not just scored.** Health, reactivation and Co-pilot outputs come with drivers or per-segment results, shown on the customer page and on Model Insights.
* **Only as good as the connected data.** Engagement, sentiment and RFV need behavioural or communication sources; without them those models and their metrics are hidden.