# Reactivating Hibernating Users via Email or WhatsApp

**Reactivating Hibernating Users via Email or WhatsApp**

**Trigger**\
Users haven’t engaged (logged in, opened email, used product) in the last 45 days. Segment: "Hibernating".

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

* Email with a reactivation incentive (e.g. discount or reminder of benefits)
* WhatsApp message offering a quick survey or support touchpoint
* Wait step with no action (control group)
* Push notification (if app installed)

&#x20;**Co-Pilot Exploration**\
Initially rotates actions randomly → learns which actions lead to higher reactivation or prevent churn → prioritizes top-performing action for future users.

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

* Personalized content (based on segment or RFV score)
* Time of day optimization (based on user past engagement)
* Channel preference routing (email vs WhatsApp)

&#x20;**KPIs Tracked**

* Reactivation rate (re-engagement within 7 days)
* Open/Click-through rate per channel
* Conversion or purchase post-reactivation
* Long-term retention lift

***


---

# 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/publishers/reactivating-hibernating-users-via-email-or-whatsapp.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.
