---
title: Configure Retention Health, Drafts, and Win-Back
description: Enable retention carefully, choose its autonomy, limit outreach, and review member-risk signals.
audience:
  - group_admin
product_area: retention
topics:
  - Retention
  - Win-back
  - Automation
  - Member health
synonyms:
  - admin
  - administrator
  - owner
  - creator
  - churn
  - at risk
routes:
  - /groups/:groupId/admin/retention
related_articles:
  - admins/creator-console-overview
  - admins/members-and-roles
  - admins/ai-tutor-practice-and-channels
  - admins/monitor-learning-and-ai-diagnostics
status: published
---

Open **Creator console → Retention**. This workspace is owner/admin gated. Its health and win-back signals help prioritize review; they are not a diagnosis or permission to message someone.

![The Retention workspace with health, drafts, win-back, MRR, autonomy, caps, and cadence.](/help/images/admins/retention.png "Start with draft-for-approval autonomy and a conservative daily cap.")

## Configure safely

1. Review **Health, Drafts, Win-back,** and **MRR** for the current community.
2. Decide who owns message review, member replies, and escalation.
3. Start with **L1 — draft for approval** so a person approves each message.
4. Set a conservative daily send cap and digest cadence.
5. Configure quiet hours, pause/mute behavior, and any higher-autonomy cap when those controls are available.
6. Turn on the engine and choose **Save**.

Higher autonomy can send without per-message approval. Use it only after L1 drafts have been reviewed across languages, member segments, and edge cases.

## Run the review loop

1. Open **Drafts** and verify recipient, evidence, tone, link, offer, locale, and unsubscribe expectations.
2. Approve, edit, or reject the draft using the available control.
3. Watch **Activity** for delivery and response outcomes.
4. Review the 30/60/90-day win-back stages and recent member activity before any nudge.
5. Pause the engine if facts, targeting, or volume look wrong.

Do not include private learning, payment, support, or memory details that the recipient did not provide for this purpose. If a metric is empty, confirm the feature is enabled and enough real activity exists; do not generate test outreach to real members merely to populate the dashboard.

## Legal

- [Privacy](/privacy)
- [Terms](/terms)
- [Data rights and deletion](/data-deletion)