> 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/b2b-saas/re-engaging-inactive-business-accounts.md).

# Re-engaging Inactive Business Accounts

Trigger\
Business account with no product usage (e.g. API calls, login, user sessions) in the past 30+ days.\
Segment: “Dormant Business Accounts”

Action Flow Options\
Co-Pilot explores effectiveness of:

* Email to account admin with usage summary + value reminder
* WhatsApp or message offering help to re-engage users
* Educational content: webinar invite, product tips
* Wait (control)

Co-Pilot Exploration\
Tests which content reactivates accounts (via admin or users) → focuses on what drives usage resumption.

Next-Best-Action Push\
CRM or marketing tool triggers reactivation actions via best-fit channel:

* Personalized by usage type or industry
* Send time optimized per previous engagement
* Admin vs. team-level routing (if applicable)

KPIs Tracked

* Account reactivation rate (e.g. new user sessions)
* Admin-level response or clicks
* Feature engagement (post-reactivation)
* Churn rate reduction


---

# 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/b2b-saas/re-engaging-inactive-business-accounts.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.