# Use cases library (Co-pilot)

* **What is the Co-Pilot?**

  > In subscription-based businesses, knowing what to do for retention is hard. Knowing who to target, when, and how,that’s where the real complexity lies.\
  > The **Churned Co-Pilot** turns that complexity into action.

  *Link to article:* [Co-pilot](/churned-docs/co-pilot.md)
* **Setting up the Co-Pilot**

  > Guide on activating Co-Pilot, connecting data, defining actions per flow step, and pushing outputs into downstream tools.

  *Link to article:* [How to setup the Co-Pilot](/churned-docs/co-pilot/how-to-setup-the-co-pilot.md)
* **Use Cases Library**

  > Overview of tested and recommended use cases. Each use case links to a 1-pager with:

  * Trigger moment
  * Action options
  * NBA logic
  * KPIs

*Link to the article:*&#x20;

{% content-ref url="/pages/6GvrMchWtSOPatVgTzFB" %}
[Where co-pilot brings most value](/churned-docs/co-pilot/use-cases/use-cases-library-co-pilot/where-co-pilot-brings-most-value.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.churned.io/churned-docs/co-pilot/use-cases/use-cases-library-co-pilot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
