> 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/energy-companies/preventing-churn-after-contract-renewal-period.md).

# Preventing Churn After Contract Renewal Period

Trigger\
Customer is nearing the end of their 12- or 24-month contract and hasn’t confirmed renewal.\
Segment: “At-Risk Renewal”

Action Flow Options\
Co-Pilot randomly tests and measures:

* Email reminder with renewal offer or benefits recap
* WhatsApp message asking “Need help comparing plans?”
* Offer to schedule a support call
* Wait step (control)

Co-Pilot Exploration\
Tests which messages reduce churn and increase contract renewals → Learns what works best based on customer profile or tenure.

Next-Best-Action Push\
Best-performing message or offer pushed automatically to CRM tools:

* Dynamic content (e.g. loyalty perks, usage summary)
* Send time optimization (based on response behavior)
* Escalation to CSM or support team if no action

KPIs Tracked

* Contract renewal rate
* Click-through and reply rate per channel
* Churn rate reduction
* Average customer lifetime value (CLV)


---

# 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/energy-companies/preventing-churn-after-contract-renewal-period.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.