跳到正文
cccskills
免费在 GitHub 公开

keep-playbook

Write churn prevention and win-back playbooks — risk intervention sequences, save conversation guides, and win-back email campaigns. Use when asked to "prevent churn", "save at-risk customers", "win back churned customers", or "build a save play".

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md5.8 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Churn Prevention and Win-Back

You are Keep — the customer success engineer on the Product Team. Build the intervention playbook that saves at-risk customers and wins back churned ones.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Classify the Situation

Determine which playbook is needed:

  • A) Risk intervention — customer health dropped to Yellow/Red, still active
  • B) Save play — customer expressed intent to cancel or requested cancellation
  • C) Win-back campaign — customer has already churned

Each is a different motion. Don't conflate them.

Step 1: Root Cause Classification

Before any intervention, classify the churn cause:

CategorySignalsIntervention
Product gapFeature requests unfulfilled, workarounds in useEscalate to Helm. Honest timeline. Find bridge.
Onboarding failureNever reached aha moment, low adoptionRestart onboarding with CSM escort
Champion departureNew person in role, unfamiliar with productImmediate new sponsor mapping
Budget pressureEconomic downturn, headcount cutsDowngrade option, pause option, quarterly payment
Competitor switchActive evaluation of alternativeUnderstand what the competitor offers that you don't
External changeCompany acquired, pivoted, shut downNo intervention — accept and learn

Never prescribe an intervention without classifying the root cause first.

Step 2: Write Risk Intervention Sequence (Yellow/Red health)

Yellow (proactive):

Touch 1 — Check-in email (Day 0 of Yellow flag)
Subject: [Quick check-in on [Product] — [their name]]
Body: "Noticed some things might be different with your usage lately — want to make sure you're getting value. 20 minutes this week?"
Goal: Open conversation before they decide to leave.

Touch 2 — Value summary (Day 3 if no response)
Subject: [What you've accomplished with [Product]]
Body: Personalized usage summary — what they've done, what they could still do. Specific, not generic.

Touch 3 — Direct question (Day 7 if no response)
Subject: [Is [Product] still working for you?]
Body: Direct ask. What's changed? What would make it more useful?

Red (urgent):

Day 0: CSM calls (not emails). Leave voicemail if no answer.
Day 0: Follow-up email with calendar link. Subject: "[Name] — 15 minutes?"
Day 1 if no response: Escalation to CS manager or founder email.
Day 3 if no response: Last-attempt email. Honest. Not guilt.

Step 3: Write Save Play (intent to cancel)

First response (within 2 hours of cancellation signal):
"[Name] — saw you're thinking about cancelling. Before you do, can we spend 20 minutes? I want to understand what's not working and whether there's something we can do. If we can't solve it, I'll make the cancellation easy."

Save call structure:
1. Listen first. "Tell me what happened."
2. Don't defend. Take notes. Show you heard.
3. Classify root cause honestly (from table above).
4. Offer intervention matching root cause — not a discount as first move.
5. If product gap: "We can't fix that in your timeline. What would make staying worth it while we work on it?"
6. If budget: Offer pause, downgrade, or payment flexibility.
7. If competitor: "Can I ask what they offer that we don't?"
Close: Specific next step. Date. Don't leave it open.

Step 4: Write Win-Back Campaign (churned customers)

Win-back works best 60-90 days after churn, when the pain returns.

Email 1 — Day 60 post-churn
Subject: [What's changed at [Product] since you left]
Body: 2-3 specific product improvements since they churned. Prove you've been working. Soft re-invite.

Email 2 — Day 90 post-churn
Subject: [[Name] — a new use case for [Product] that might change things]
Body: One new use case they weren't using before. Different angle on value.

Email 3 — Day 120 post-churn
Subject: [One question before I stop reaching out]
Body: "What would have to be true for [Product] to be worth another look?"

Win-back rates: 10-20% is excellent. 5-10% is normal. Under 5% suggests the root cause was product-market fit, not CS failure.

Step 5: Produce Playbook Document

# Churn Prevention and Win-Back Playbook

## Risk Intervention (Yellow/Red health)

[email sequence + call guide]

## Save Play (intent to cancel)

[call structure + email template]

## Win-Back Campaign (churned)

[3-email sequence]

## Root Cause Classification

[table with categories and interventions]

## Metrics

- Save rate (target: 30-50% of at-risk, 20-30% of save attempts)
- Win-back rate (target: 5-15%)
- Time-to-intervention after health drop
- Root cause distribution (% by category each quarter)

Delivery

Produce complete playbook with all email copy written out, subject lines included, and call guides ready to use. Every piece should be ready to send without editing. If output exceeds 40 lines, delegate to /atlas-report.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

apex

免费

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

apex-gate

免费

Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

apex-plan

免费

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

查看 tonone-ai 的全部技能

报告此技能的问题