churn-prevention

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Churn Prevention

Churn预防

You are an expert in SaaS retention and churn prevention. Your goal is to help reduce both voluntary churn (customers choosing to cancel) and involuntary churn (failed payments) through well-designed cancel flows, dynamic save offers, proactive retention, and dunning strategies.

您是SaaS retention与Churn预防领域的专家。您的目标是通过精心设计的cancel flow、动态save offer、主动留存和dunning策略，帮助降低voluntary churn（客户主动选择取消）和involuntary churn（付款失败导致的流失）。

Before Starting

开始之前

Check for product marketing context first: If

.claude/product-marketing-context.md

exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

首先查看产品营销背景： 如果存在

.claude/product-marketing-context.md

文件，请在提问前先阅读。使用该背景信息，仅询问未涵盖的内容或与本次任务相关的特定信息。

收集以下背景信息（若未提供则询问）：

1. Current Churn Situation

1. 当前Churn状况

What's your monthly churn rate? (Voluntary vs. involuntary if known)
How many active subscribers?
What's the average MRR per customer?
Do you have a cancel flow today, or does cancel happen instantly?

月度Churn率是多少？（若已知，请区分voluntary和involuntary）
活跃订阅用户数量是多少？
客户平均MRR是多少？
目前是否有cancel flow，还是取消操作会立即生效？

2. Billing & Platform

2. 计费与平台

What billing provider? (Stripe, Chargebee, Paddle, Recurly, Braintree)
Monthly, annual, or both billing intervals?
Do you support plan pausing or downgrades?
Any existing retention tooling? (Churnkey, ProsperStack, Raaft)

使用的计费提供商是哪个？（Stripe、Chargebee、Paddle、Recurly、Braintree）
计费周期是月度、年度还是两者皆有？
是否支持暂停订阅或降级套餐？
现有任何留存工具吗？（Churnkey、ProsperStack、Raaft）

3. Product & Usage Data

3. 产品与使用数据

Do you track feature usage per user?
Can you identify engagement drop-offs?
Do you have cancellation reason data from past churns?
What's your activation metric? (What do retained users do that churned users don't?)

是否按用户跟踪功能使用情况？
能否识别参与度下降的节点？
是否有过往Churn的取消原因数据？
激活指标是什么？（留存用户做了哪些流失用户没做的事？）

4. Constraints

4. 约束条件

B2B or B2C? (Affects flow design)
Self-serve cancellation required? (Some regulations mandate easy cancel)
Brand tone for offboarding? (Empathetic, direct, playful)

是B2B还是B2C？（会影响流程设计）
是否要求自助取消？（部分法规要求提供便捷的取消方式）
离队流程的品牌调性是什么？（共情、直接、活泼）

How This Skill Works

此技能的工作方式

Churn has two types requiring different strategies:

Type	Cause	Solution
Voluntary	Customer chooses to cancel	Cancel flows, save offers, exit surveys
Involuntary	Payment fails	Dunning emails, smart retries, card updaters

Voluntary churn is typically 50-70% of total churn. Involuntary churn is 30-50% but is often easier to fix.

This skill supports three modes:

Build a cancel flow — Design from scratch with survey, save offers, and confirmation
Optimize an existing flow — Analyze cancel data and improve save rates
Set up dunning — Failed payment recovery with retries and email sequences

Churn分为两种类型，需要不同的策略：

类型	原因	解决方案
Voluntary	客户主动选择取消	Cancel flow、save offer、exit survey
Involuntary	付款失败	Dunning邮件、智能重试、卡片更新服务

Voluntary churn通常占总Churn的50-70%。Involuntary churn占30-50%，但通常更容易解决。

此技能支持三种模式：

搭建cancel flow — 从零开始设计，包含调研、挽回优惠和确认环节
优化现有流程 — 分析取消数据，提高挽回率
设置dunning — 通过重试和邮件序列追回失败付款

Cancel Flow Design

Cancel Flow设计

The Cancel Flow Structure

Cancel Flow结构

Every cancel flow follows this sequence:

Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel

Step 1: Trigger Customer clicks "Cancel subscription" in account settings.

Step 2: Exit Survey Ask why they're cancelling. This determines which save offer to show.

Step 3: Dynamic Save Offer Present a targeted offer based on their reason (discount, pause, downgrade, etc.)

Step 4: Confirmation If they still want to cancel, confirm clearly with end-of-billing-period messaging.

Step 5: Post-Cancel Set expectations, offer easy reactivation path, trigger win-back sequence.

每个cancel flow遵循以下流程：

Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel

步骤1：触发（Trigger） 客户在账户设置中点击“取消订阅”。

步骤2：退出调研（Exit Survey） 询问客户取消的原因。这将决定展示何种挽回优惠。

步骤3：动态挽回优惠（Dynamic Save Offer） 根据客户的原因提供针对性优惠（折扣、暂停、降级等）。

步骤4：确认（Confirmation） 如果客户仍想取消，需明确确认，并告知计费周期结束的相关信息。

步骤5：取消后（Post-Cancel） 明确后续预期，提供便捷的重新激活路径，触发win-back序列。

Exit Survey Design

退出调研设计

The exit survey is the foundation. Good reason categories:

Reason	What It Tells You
Too expensive	Price sensitivity, may respond to discount or downgrade
Not using it enough	Low engagement, may respond to pause or onboarding help
Missing a feature	Product gap, show roadmap or workaround
Switching to competitor	Competitive pressure, understand what they offer
Technical issues / bugs	Product quality, escalate to support
Temporary / seasonal need	Usage pattern, offer pause
Business closed / changed	Unavoidable, learn and let go gracefully
Other	Catch-all, include free text field

Survey best practices:

1 question, single-select with optional free text
5-8 reason options max (avoid decision fatigue)
Put most common reasons first (review data quarterly)
Don't make it feel like a guilt trip
"Help us improve" framing works better than "Why are you leaving?"

退出调研是基础。合理的原因分类：

原因	反映的问题
价格过高	价格敏感度高，可能对折扣或套餐降级有反应
使用频率过低	参与度低，可能对暂停订阅或入门指导有反应
缺少我需要的功能	产品存在缺口，展示路线图或解决方案
转向竞品	竞争压力，了解竞品的优势
技术问题/漏洞	产品质量问题，转至支持团队处理
临时/季节性需求	使用模式问题，提供暂停订阅选项
业务关闭/变更	不可避免的情况，收集信息后友好告别
其他	兜底选项，包含自由文本输入框

调研最佳实践：

仅1个问题，单选+可选自由文本
最多5-8个原因选项（避免决策疲劳）
将最常见的原因放在前面（每季度回顾数据更新）
不要让客户有负罪感
使用“帮助我们改进”的表述比“您为什么要离开？”效果更好

Dynamic Save Offers

动态挽回优惠

The key insight: match the offer to the reason. A discount won't save someone who isn't using the product. A feature roadmap won't save someone who can't afford it.

Offer-to-reason mapping:

Cancel Reason	Primary Offer	Fallback Offer
Too expensive	Discount (20-30% for 2-3 months)	Downgrade to lower plan
Not using it enough	Pause (1-3 months)	Free onboarding session
Missing feature	Roadmap preview + timeline	Workaround guide
Switching to competitor	Competitive comparison + discount	Feedback session
Technical issues	Escalate to support immediately	Credit + priority fix
Temporary / seasonal	Pause subscription	Downgrade temporarily
Business closed	Skip offer (respect the situation)	—

核心要点：根据原因匹配优惠。折扣无法挽回因“缺少功能”或“使用频率低”而取消的客户。

原因与优惠匹配：

取消原因	主要优惠	备选优惠
价格过高	折扣（2-3个月内优惠20-30%）	降级至低价套餐
使用频率过低	暂停订阅（1-3个月）	免费入门指导
缺少功能	路线图预览+时间规划	解决方案指南
转向竞品	竞品对比+折扣	反馈访谈
技术问题	立即转至支持团队处理	账户信用+优先修复
临时/季节性需求	暂停订阅	临时降级套餐
业务关闭	跳过优惠（尊重客户情况）	—

Save Offer Types

挽回优惠类型

Discount

20-30% off for 2-3 months is the sweet spot
Avoid 50%+ discounts (trains customers to cancel for deals)
Time-limit the offer ("This offer expires when you leave this page")
Show the dollar amount saved, not just the percentage

Pause subscription

1-3 month pause maximum (longer pauses rarely reactivate)
60-80% of pausers eventually return to active
Auto-reactivation with advance notice email
Keep their data and settings intact

Plan downgrade

Offer a lower tier instead of full cancellation
Show what they keep vs. what they lose
Position as "right-size your plan" not "downgrade"
Easy path back up when ready

Feature unlock / extension

Unlock a premium feature they haven't tried
Extend trial of a higher tier
Works best for "not getting enough value" reasons

Personal outreach

For high-value accounts (top 10-20% by MRR)
Route to customer success for a call
Personal email from founder for smaller companies

折扣

2-3个月内优惠20-30%是最佳区间
避免50%以上的折扣（会让客户养成为了优惠而取消的习惯）
为优惠设置时间限制（“此优惠在您离开本页面后失效”）
展示节省的具体金额，而非仅百分比

暂停订阅

最多暂停1-3个月（暂停时间过长的用户很少重新激活）
60-80%的暂停用户最终会重新激活
自动重新激活，并提前发送通知邮件
保留用户的数据和设置

套餐降级

提供低级别套餐选项，而非直接取消
展示用户将保留和失去的功能
定位为“调整至合适套餐”而非“降级”
提供便捷的升级路径

功能解锁/延长

解锁用户未尝试过的高级功能
延长高级套餐的试用时间
最适合“未获得足够价值”的取消原因

个性化触达

针对高价值客户（MRR排名前10-20%）
转至客户成功团队进行电话沟通
小公司可由创始人发送个性化邮件

Cancel Flow UI Patterns

Cancel Flow UI示例

┌─────────────────────────────────────┐
│  We're sorry to see you go          │
│                                     │
│  What's the main reason you're      │
│  cancelling?                        │
│                                     │
│  ○ Too expensive                    │
│  ○ Not using it enough              │
│  ○ Missing a feature I need         │
│  ○ Switching to another tool        │
│  ○ Technical issues                 │
│  ○ Temporary / don't need right now │
│  ○ Other: [____________]            │
│                                     │
│  [Continue]                         │
│  [Never mind, keep my subscription] │
└─────────────────────────────────────┘
         ↓ (selects "Too expensive")
┌─────────────────────────────────────┐
│  What if we could help?             │
│                                     │
│  We'd love to keep you. Here's a    │
│  special offer:                     │
│                                     │
│  ┌───────────────────────────────┐  │
│  │  25% off for the next 3 months│  │
│  │  Save $XX/month               │  │
│  │                               │  │
│  │  [Accept Offer]               │  │
│  └───────────────────────────────┘  │
│                                     │
│  Or switch to [Basic Plan] at       │
│  $X/month →                         │
│                                     │
│  [No thanks, continue cancelling]   │
└─────────────────────────────────────┘

UI principles:

Keep the "continue cancelling" option visible (no dark patterns)
One primary offer + one fallback, not a wall of options
Show specific dollar savings, not abstract percentages
Use the customer's name and account data when possible
Mobile-friendly (many cancellations happen on mobile)

For detailed cancel flow patterns by industry and billing provider, see references/cancel-flow-patterns.md.

┌─────────────────────────────────────┐
│  很遗憾您要离开                     │
│                                     │
│  您取消订阅的主要原因是什么？        │
│                                     │
│  ○ 价格过高                         │
│  ○ 使用频率过低                     │
│  ○ 缺少我需要的功能                 │
│  ○ 转向其他工具                     │
│  ○ 技术问题                         │
│  ○ 临时不需要                       │
│  ○ 其他: [____________]            │
│                                     │
│  [继续]                             │
│  [算了，保留我的订阅]               │
└─────────────────────────────────────┘
         ↓（选择“价格过高”）
┌─────────────────────────────────────┐
│  我们能帮到您吗？                   │
│                                     │
│  我们非常希望留住您。这是为您准备的  │
│  专属优惠：                         │
│                                     │
│  ┌───────────────────────────────┐  │
│  │  未来3个月享受25%折扣          │  │
│  │  每月节省$XX美元               │  │
│  │                               │  │
│  │  [接受优惠]                   │  │
│  └───────────────────────────────┘  │
│                                     │
│  或切换至[基础套餐]，每月仅$X美元 →  │
│                                     │
│  [不用了，继续取消]                 │
└─────────────────────────────────────┘

UI设计原则：

始终显示“继续取消”选项（不使用暗模式）
仅提供1个主要优惠+1个备选优惠，而非大量选项
展示具体的节省金额，而非抽象的百分比
尽可能使用客户姓名和账户数据
适配移动端（许多取消操作发生在移动端）

有关按行业和计费提供商划分的详细cancel flow模式，请查看references/cancel-flow-patterns.md。

Churn Prediction & Proactive Retention

Churn预测与主动留存

The best save happens before the customer ever clicks "Cancel."

最好的挽回是在客户点击“取消”之前就完成。

Risk Signals

风险信号

Track these leading indicators of churn:

Signal	Risk Level	Timeframe
Login frequency drops 50%+	High	2-4 weeks before cancel
Key feature usage stops	High	1-3 weeks before cancel
Support tickets spike then stop	High	1-2 weeks before cancel
Email open rates decline	Medium	2-6 weeks before cancel
Billing page visits increase	High	Days before cancel
Team seats removed	High	1-2 weeks before cancel
Data export initiated	Critical	Days before cancel
NPS score drops below 6	Medium	1-3 months before cancel

跟踪这些Churn的先行指标：

信号	风险等级	时间范围
登录频率下降50%以上	高	取消前2-4周
核心功能使用停止	高	取消前1-3周
支持工单激增后停止	高	取消前1-2周
邮件打开率下降	中	取消前2-6周
计费页面访问量增加	高	取消前几天
团队席位减少	高	取消前1-2周
发起数据导出	极高	取消前几天
NPS评分降至6以下	中	取消前1-3个月

Health Score Model

健康评分模型

Build a simple health score (0-100) from weighted signals:

Health Score = (
  Login frequency score × 0.30 +
  Feature usage score   × 0.25 +
  Support sentiment     × 0.15 +
  Billing health        × 0.15 +
  Engagement score      × 0.15
)

Score	Status	Action
80-100	Healthy	Upsell opportunities
60-79	Needs attention	Proactive check-in
40-59	At risk	Intervention campaign
0-39	Critical	Personal outreach

基于加权信号构建简单的健康评分（0-100）：

健康评分 = (
  登录频率评分 × 0.30 +
  功能使用评分 × 0.25 +
  支持反馈评分 × 0.15 +
  计费健康评分 × 0.15 +
  参与度评分 × 0.15
)

分数	状态	行动
80-100	健康	交叉销售机会
60-79	需要关注	主动沟通
40-59	高风险	干预活动
0-39	极高风险	个性化触达

Proactive Interventions

主动干预措施

Before they think about cancelling:

Trigger	Intervention
Usage drop >50% for 2 weeks	"We noticed you haven't used [feature]. Need help?" email
Approaching plan limit	Upgrade nudge (not a wall — paywall-upgrade-cro handles this)
No login for 14 days	Re-engagement email with recent product updates
NPS detractor (0-6)	Personal follow-up within 24 hours
Support ticket unresolved >48h	Escalation + proactive status update
Annual renewal in 30 days	Value recap email + renewal confirmation

在客户考虑取消之前：

触发条件	干预措施
2周内使用量下降超过50%	发送邮件：“我们注意到您近期未使用[功能]，需要帮助吗？”
即将达到套餐限制	升级提示（非付费墙，paywall-upgrade-cro技能负责此部分）
14天未登录	发送重新激活邮件，包含近期产品更新
NPS贬损者（0-6分）	24小时内进行个性化跟进
支持工单超过48小时未解决	升级处理+主动状态更新
年度续订还有30天	发送价值回顾邮件+续订确认

Involuntary Churn: Payment Recovery

非自愿流失：付款追回

Failed payments cause 30-50% of all churn but are the most recoverable.

失败付款导致30-50%的Churn，但也是最容易追回的部分。

The Dunning Stack

Dunning流程

Pre-dunning → Smart retry → Dunning emails → Grace period → Hard cancel

预催缴（Pre-dunning）→ 智能重试（Smart retry）→ Dunning邮件 → 宽限期 → 强制取消（Hard cancel）

Pre-Dunning (Prevent Failures)

预催缴（预防失败）

Card expiry alerts: Email 30, 15, and 7 days before card expires
Backup payment method: Prompt for a second payment method at signup
Card updater services: Visa/Mastercard auto-update programs (reduces hard declines 30-50%)
Pre-billing notification: Email 3-5 days before charge for annual plans

卡片到期提醒：在卡片到期前30、15和7天发送邮件提醒
备用付款方式：在注册时提示提供第二种付款方式
卡片更新服务：Visa/Mastercard自动更新程序（可减少30-50%的硬拒绝）
预计费通知：年度计划计费前3-5天发送邮件通知

Smart Retry Logic

智能重试逻辑

Not all failures are the same. Retry strategy by decline type:

Decline Type	Examples	Retry Strategy
Soft decline (temporary)	Insufficient funds, processor timeout	Retry 3-5 times over 7-10 days
Hard decline (permanent)	Card stolen, account closed	Don't retry — ask for new card
Authentication required	3D Secure, SCA	Send customer to update payment

Retry timing best practices:

Retry 1: 24 hours after failure
Retry 2: 3 days after failure
Retry 3: 5 days after failure
Retry 4: 7 days after failure (with dunning email escalation)
After 4 retries: Hard cancel with reactivation path

Smart retry tip: Retry on the day of the month the payment originally succeeded (if Day 1 worked before, retry on Day 1). Stripe Smart Retries handles this automatically.

并非所有失败情况都相同。根据拒绝类型制定重试策略：

拒绝类型	示例	重试策略
软拒绝（临时）	余额不足、处理器超时	7-10天内重试3-5次
硬拒绝（永久）	卡片被盗、账户关闭	不重试 — 要求客户提供新卡片
需要验证	3D Secure、SCA	引导客户更新付款信息

重试时间最佳实践：

第一次重试：失败后24小时
第二次重试：失败后3天
第三次重试：失败后5天
第四次重试：失败后7天（搭配升级的Dunning邮件）
4次重试后：强制取消，并提供重新激活路径

智能重试小贴士： 在每月原付款成功的日期重试（如果1号付款成功过，就在1号重试）。Stripe Smart Retries会自动处理此逻辑。

Dunning Email Sequence

Dunning邮件序列

Email	Timing	Tone	Content
1	Day 0 (failure)	Friendly alert	"Your payment didn't go through. Update your card."
2	Day 3	Helpful reminder	"Quick reminder — update your payment to keep access."
3	Day 7	Urgency	"Your account will be paused in 3 days. Update now."
4	Day 10	Final warning	"Last chance to keep your account active."

Dunning email best practices:

Direct link to payment update page (no login required if possible)
Show what they'll lose (their data, their team's access)
Don't blame ("your payment failed" not "you failed to pay")
Include support contact for help
Plain text performs better than designed emails for dunning

邮件	发送时间	语气	内容
1	失败当天（Day 0）	友好提醒	“您的付款未成功，请更新您的卡片信息。”
2	失败后3天（Day3）	贴心提醒	“温馨提示 — 请更新付款信息以继续使用服务。”
3	失败后7天（Day7）	紧急	“您的账户将在3天后暂停，请立即更新。”
4	失败后10天（Day10）	最终警告	“最后机会 — 请更新信息以保持账户活跃。”

Dunning邮件最佳实践：

直接链接至付款更新页面（尽可能无需登录）
告知用户将失去的内容（数据、团队访问权限）
不要指责用户（使用“您的付款未成功”而非“您未付款”）
包含支持联系方式
纯文本邮件比设计复杂的邮件效果更好

Recovery Benchmarks

追回基准

Metric	Poor	Average	Good
Soft decline recovery	<40%	50-60%	70%+
Hard decline recovery	<10%	20-30%	40%+
Overall payment recovery	<30%	40-50%	60%+
Pre-dunning prevention	None	10-15%	20-30%

For the complete dunning playbook with provider-specific setup, see references/dunning-playbook.md.

指标	较差	平均	良好
软拒绝追回率	<40%	50-60%	70%+
硬拒绝追回率	<10%	20-30%	40%+
整体付款追回率	<30%	40-50%	60%+
预催缴预防率	无	10-15%	20-30%

有关包含提供商特定设置的完整Dunning手册，请查看references/dunning-playbook.md。

Metrics & Measurement

指标与衡量

Key Churn Metrics

核心Churn指标

Metric	Formula	Target
Monthly churn rate	Churned customers / Start-of-month customers	<5% B2C, <2% B2B
Revenue churn (net)	(Lost MRR - Expansion MRR) / Start MRR	Negative (net expansion)
Cancel flow save rate	Saved / Total cancel sessions	25-35%
Offer acceptance rate	Accepted offers / Shown offers	15-25%
Pause reactivation rate	Reactivated / Total paused	60-80%
Dunning recovery rate	Recovered / Total failed payments	50-60%
Time to cancel	Days from first churn signal to cancel	Track trend

指标	计算公式	目标
月度Churn率	流失客户数 / 月初客户数	B2C<5%，B2B<2%
收入流失率（净）	(流失MRR - 扩展MRR) / 月初MRR	负值（净增长）
Cancel Flow挽回率	挽回客户数 / 总取消会话数	25-35%
优惠接受率	接受优惠数 / 展示优惠数	15-25%
暂停重新激活率	重新激活数 / 总暂停数	60-80%
Dunning追回率	追回付款数 / 总失败付款数	50-60%
取消时长	从第一个流失信号到取消的天数	跟踪趋势

Cohort Analysis

同期群分析

Segment churn by:

Acquisition channel — Which channels bring stickier customers?
Plan type — Which plans churn most?
Tenure — When do most cancellations happen? (30, 60, 90 days?)
Cancel reason — Which reasons are growing?
Save offer type — Which offers work best for which segments?

按以下维度细分Churn：

获客渠道 — 哪些渠道带来的客户更具粘性？
套餐类型 — 哪些套餐的Churn率最高？
使用时长** — 大多数取消发生在何时？（30、60、90天？）
取消原因 — 哪些原因的占比在增长？
挽回优惠类型 — 哪些优惠对哪些细分群体最有效？

Cancel Flow A/B Tests

Cancel Flow A/B测试

Test one variable at a time:

Test	Hypothesis	Metric
Discount % (20% vs 30%)	Higher discount saves more	Save rate, LTV impact
Pause duration (1 vs 3 months)	Longer pause increases return rate	Reactivation rate
Survey placement (before vs after offer)	Survey-first personalizes offers	Save rate
Offer presentation (modal vs full page)	Full page gets more attention	Save rate
Copy tone (empathetic vs direct)	Empathetic reduces friction	Save rate

How to run cancel flow experiments: Use the ab-test-setup skill to design statistically rigorous tests. PostHog is a good fit for cancel flow experiments — its feature flags can split users into different flows server-side, and its funnel analytics track each step of the cancel flow (survey → offer → accept/decline → confirm). See the PostHog integration guide for setup.

每次仅测试一个变量：

测试内容	假设	衡量指标
折扣比例（20% vs 30%）	更高的折扣能挽回更多客户	挽回率、LTV影响
暂停时长（1个月 vs 3个月）	更长的暂停时间能提高重新激活率	重新激活率
调研位置（优惠前 vs 优惠后）	先调研能个性化优惠，提高挽回率	挽回率
优惠展示方式（弹窗 vs 整页）	整页展示更受关注，提高挽回率	挽回率
文案语气（共情 vs 直接）	共情文案能减少摩擦，提高挽回率	挽回率

如何开展Cancel Flow实验： 使用ab-test-setup技能设计统计严谨的测试。PostHog非常适合Cancel Flow实验 — 其功能标志可在服务器端将用户分流至不同流程，漏斗分析可跟踪Cancel Flow的每个步骤（调研→优惠→接受/拒绝→确认）。有关设置，请查看PostHog集成指南。

Common Mistakes

常见错误

No cancel flow at all — Instant cancel leaves money on the table. Even a simple survey + one offer saves 10-15%
Making cancellation hard to find — Hidden cancel buttons breed resentment and bad reviews. Many jurisdictions require easy cancellation (FTC Click-to-Cancel rule)
Same offer for every reason — A blanket discount doesn't address "missing feature" or "not using it"
Discounts too deep — 50%+ discounts train customers to cancel-and-return for deals
Ignoring involuntary churn — Often 30-50% of total churn and the easiest to fix
No dunning emails — Letting payment failures silently cancel accounts
Guilt-trip copy — "Are you sure you want to abandon us?" damages brand trust
Not tracking save offer LTV — A "saved" customer who churns 30 days later wasn't really saved
Pausing too long — Pauses beyond 3 months rarely reactivate. Set limits.
No post-cancel path — Always make reactivation easy and trigger win-back emails

完全没有Cancel Flow — 立即取消会损失收入。即使是简单的调研+一个优惠也能挽回10-15%的客户
隐藏取消按钮 — 隐藏的取消按钮会引发不满和差评。许多地区的法规要求提供便捷的取消方式（FTC点击取消规则）
对所有原因使用相同优惠 — 通用折扣无法解决“缺少功能”或“使用频率低”的问题
折扣力度过大 — 50%以上的折扣会让客户养成为了优惠而取消的习惯
忽略非自愿流失 — 通常占总Churn的30-50%，且最容易解决
未设置Dunning邮件 — 让付款失败自动取消账户
负罪感文案 — “您确定要抛弃我们吗？”会损害品牌信任
未跟踪挽回优惠的LTV — 挽回后30天内又流失的客户并非真正被挽回
暂停时间过长 — 暂停超过3个月的用户很少重新激活，需设置限制
无取消后路径 — 始终提供便捷的重新激活路径，并触发win-back邮件

Tool Integrations

工具集成

For implementation, see the tools registry.

有关实现，请查看工具注册表。

Retention Platforms

留存平台

Tool	Best For	Key Feature
Churnkey	Full cancel flow + dunning	AI-powered adaptive offers, 34% avg save rate
ProsperStack	Cancel flows with analytics	Advanced rules engine, Stripe/Chargebee integration
Raaft	Simple cancel flow builder	Easy setup, good for early-stage
Chargebee Retention	Chargebee customers	Native integration, was Brightback

工具	最佳适用场景	核心功能
Churnkey	完整Cancel Flow + Dunning	AI驱动的自适应优惠，平均挽回率34%
ProsperStack	带分析功能的Cancel Flow	高级规则引擎，Stripe/Chargebee集成
Raaft	简单Cancel Flow构建器	易于设置，适合早期阶段
Chargebee Retention	Chargebee客户	原生集成，原Brightback

Billing Providers (Dunning)

计费提供商（Dunning）

Provider	Smart Retries	Dunning Emails	Card Updater
Stripe	Built-in (Smart Retries)	Built-in	Automatic
Chargebee	Built-in	Built-in	Via gateway
Paddle	Built-in	Built-in	Managed
Recurly	Built-in	Built-in	Built-in
Braintree	Manual config	Manual	Via gateway

提供商	智能重试	Dunning邮件	卡片更新
Stripe	内置（Smart Retries）	内置	自动
Chargebee	内置	内置	通过网关
Paddle	内置	内置	托管
Recurly	内置	内置	内置
Braintree	手动配置	手动	通过网关

Tool	Use For
`stripe`	Subscription management, dunning config, payment retries
`customer-io`	Dunning email sequences, retention campaigns
`posthog`	Cancel flow A/B tests via feature flags, funnel analytics
`mixpanel` / `ga4`	Usage tracking, churn signal analysis
`segment`	Event routing for health scoring

工具	用途
`stripe`	订阅管理、Dunning配置、付款重试
`customer-io`	Dunning邮件序列、留存活动
`posthog`	通过功能标志进行Cancel Flow A/B测试、漏斗分析
`mixpanel` / `ga4`	使用情况跟踪、流失信号分析
`segment`	健康评分的事件路由