> 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/co-pilot/use-cases/use-cases-library-co-pilot/product-subscriptions/preventing-churn-after-delivery.md).

# Preventing churn after delivery

Trigger\
Customer has received a delivery in the last 3–5 days but hasn’t taken follow-up actions (e.g. confirmed next order, clicked product tips, submitted feedback).\
Segment: “At-Risk Post-Delivery”

Action Flow Options\
Co-Pilot randomly selects and tracks the effectiveness of different actions:

* Email asking “How’s your product working?” with usage tips or reorder link
* WhatsApp message offering quick support or a satisfaction survey
* Referral incentive (“Get 15% off when a friend subscribes”)
* Wait step with no action (control group)

Co-Pilot Exploration\
Initially rotates actions randomly → learns which actions lead to repeat orders or prevent cancellations → prioritizes top-performing action for future users.

Next-Best-Action Push\
Winning action is pushed to your CRM or marketing tool (e.g. Klaviyo, HubSpot, Customer.io) with:

* Personalized content (e.g. based on last product received or frequency)
* Send time optimization (based on past behavior)
* Channel preference (email vs WhatsApp)

KPIs Tracked

* Next-order confirmation rate
* Open / Click-through rate per channel
* Referral redemptions or shares
* Retention rate after 30 days
* Churn reduction vs. control


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.churned.io/churned-docs/co-pilot/use-cases/use-cases-library-co-pilot/product-subscriptions/preventing-churn-after-delivery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.