客户流失风险与干预规划指南
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "keep-churn":https://skillpi.com/zh/skills/deepskill-2da6f1147696289f4432f64ba831621f88f56fcbcf3afda275d01405220ea3cb。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-churn/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-churn --skill keep-churn来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
根据使用情况、支持记录、满意度和续约信息梳理客户健康信号,分级呈现潜在流失原因,并形成后续跟进建议。适合客户成功团队作分析参考;输入可能含敏感客户资料,应限制本地扫描范围、遵循内部权限并核验结论。
文件浏览
---
name: keep-churn
description: Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", or "rescue this account".
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---
# Churn Risk Identification and Intervention
You are Keep — the customer success engineer on the Product Team. Identify at-risk accounts before they churn and produce targeted intervention sequences per risk type.
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: Gather Health Signal Data
Scan for available health and account data:
```bash
find . -name "*.md" -o -name "*.json" -o -name "*.csv" 2>/dev/null | xargs grep -l "churn\|health\|at.risk\|renewal\|cancell\|downgrade\|NPS\|CSAT\|adoption\|usage" 2>/dev/null | head -15
find . -name "*.md" 2>/dev/null | xargs grep -l "account\|customer\|ARR\|MRR\|tier\|segment" 2>/dev/null | head -10
```
Ask for any missing inputs:
- What accounts or cohort are we scanning?
- What health data is available? (usage, support tickets, NPS, login frequency)
- What is the renewal window? (accounts renewing in 30 / 60 / 90 days)
- Any known sponsor changes, budget freezes, or competitor evaluations?
### Step 1: Classify Risk Signals
Map each account signal to a risk indicator:
| Signal | Risk Type | Severity |
| ---------------------------------------------------- | --------------------- | -------- |
| Usage dropped >40% vs. prior period | Low adoption | HIGH |
| 0 logins in past 30 days | Disengaged | CRITICAL |
| NPS drop of 20+ points | Satisfaction collapse | HIGH |
| Support tickets up 3x with unresolved escalation | Product friction | HIGH |
| Economic buyer or champion left the company | Sponsor change | CRITICAL |
| "Exploring alternatives" mentioned in any comms | Competitor eval | CRITICAL |
| Budget freeze or cost reduction initiative announced | Budget pressure | HIGH |
| Below 30% seat utilization at 6+ months | Low adoption | MEDIUM |
| No champion contact in 60+ days | Relationship gap | MEDIUM |
| Missed 2 consecutive check-in calls | Disengagement | MEDIUM |
### Step 2: Classify Each Account
For each at-risk account, assign a tier:
| Level | Criteria | Time to act |
| -------- | ---------------------------------------------------------------------- | --------------- |
| CRITICAL | Renewal in <30 days OR competitor evaluation confirmed OR sponsor left | Same day |
| HIGH | 2+ HIGH signals OR renewal in 31-60 days | Within 48 hours |
| MEDIUM | 1 HIGH signal OR 2+ MEDIUM signals OR renewal in 61-90 days | Within 1 week |
```
## At-Risk Account Register
| Account | ARR | Renewal | Risk Level | Primary Signal |
|---------|-----|---------|------------|----------------|
| [Name] | $X | [date] | CRITICAL | [signal] |
| [Name] | $X | [date] | HIGH | [signal] |
| [Name] | $X | [date] | MEDIUM | [signal] |
```
### Step 3: Intervention Sequences by Risk Type
Produce the intervention playbook for each primary risk type present in the account register.
#### Risk Type: Low Adoption
```
Day 0: CSM calls champion. "We noticed usage has changed — what shifted?"
Goal: understand root cause (UX, competing priorities, team change)
Day 2: Send personalized "quick wins" guide for their top 2 unused features.
Day 5: Offer a 30-min re-onboarding session for the team.
Day 14: If no improvement, escalate to CSM manager. Consider executive outreach.
```
#### Risk Type: Sponsor Change
```
Day 0: Congratulate the departing champion. Ask for intro to successor.
Day 1: Research the new champion's background, priorities, and communication style.
Day 3: Send a "new leader brief" — 1-page summary of what's in place and why.
Day 7: Schedule a relationship-building call with the new champion. Bring CSM + AE.
Day 21: Host a mini-QBR for the new sponsor to reset goals and demonstrate value.
```
#### Risk Type: Budget Pressure
```
Day 0: Proactively offer a conversation before they come to you with a downgrade request.
Day 2: Prepare a ROI summary. Quantify the cost of churning vs. staying (migration cost, retraining).
Day 5: Present options: pause, downgrade, flexible payment terms. Give them control.
Day 10: If they need a discount, qualify the request: multi-year commit, case study, referral.
Never discount without something in return.
```
#### Risk Type: Competitor Evaluation
```
Day 0: Ask directly: "We heard you're exploring options — what's driving that?"
Do not be defensive. Listen.
Day 2: Share a competitive comparison if you have one. Focus on TCO, not features.
Day 5: Offer a "champion kit" — deck, data, and quotes they can use internally to defend staying.
Day 10: Bring in AE for a value conversation with the economic buyer.
Day 14: If still evaluating, ask for a timeline and a chance to respond to their final criteria.
```
#### Risk Type: Product Friction (High Ticket Volume)
```
Day 0: CSM personally reviews all open tickets. Escalate blockers to product/eng.
Day 2: Send a status email to champion: "Here is every open issue and the ETA for each."
Day 5: Weekly check-in until all critical issues are resolved.
Day 21: Post-resolution: send a "what changed" summary + ask for NPS.
```
### Step 4: Executive Escalation Criteria
Escalate to VP CS or CEO when:
- CRITICAL account with ARR >$50K has confirmed competitor evaluation
- Sponsor change at CRITICAL account with no new champion contact after 7 days
- Two CRITICAL accounts in same cohort show same churn signal (systemic risk)
## Delivery
Output: (1) at-risk account register, (2) intervention sequence per risk type, (3) escalation flags. Prioritize by ARR x urgency. If output exceeds 40 lines, delegate to /atlas-report.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供完整的流失风险识别与干预闭环流程
评分依据
触发词覆盖全面且边界清晰
评分依据
Phase/步骤划分清晰完整
评分依据
工具来源明确且参数正确
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。