Official skill · Customer success
Churn-risk note for an account
Writes a churn-risk note on one account: risk level with evidence, a root-cause hypothesis, a save plan with owners and dates, and what to tell the customer. Use it when usage dropped, a champion left, or a renewal is near and something feels off.
AI skill
Have your AI spot an account at risk and plan the save
14 days free · No card needed
Works in Claude, ChatGPT, and coding agents. On Team and Business, the official skill in your pod updates itself when we improve it.
When to use it
- Usage dropped, a champion left, or a renewal is near and something feels off
- Before a save call or an at-risk account review
What you give it
- Usage data, ideally 2 periods to compare
- Recent tickets
- Call notes and emails
- Plan, value, and renewal date
What you get
A one-page risk note with an evidence table, a hypothesis, a dated save plan, and a customer message.
How it works
- List the signals
- Set the risk level with our default rubric
- Write a root-cause hypothesis
- Plan the save
- Write what to tell the customer
- State the stakes
Example
What you give it
> Today: Wednesday 9 September 2026. Account: Brightwell Clinics, 25 seats, renews 30 November, 18,000 per year. Usage: weekly active users 21 → 7 (August vs May). Scheduling feature: no use since 12 August. Tickets: 2 open about calendar sync, oldest 19 business days. Call notes 2 Sept: "Our practice manager Joel left; Hana is covering." Hana asked if the plan can drop to 10 seats.
What you get back (the start of it)
Churn risk: Brightwell Clinics — 9 September
Risk: High — champion left, usage down 67%, seat downgrade asked, renewal in 82 days Renewal: 30 November · Value: 18,000 per year · Owner: [account owner]
Evidence
| Signal | Source | Detail |
|---|---|---|
| Champion left | Call, 2 Sept | "Our practice manager Joel left; Hana is covering." |
| Active users down 67% | Usage | 21 → 7 weekly, May vs August |
| Key feature unused | Usage | Scheduling: no use since 12 August |
| Stale tickets | Tickets | 2 open on calendar sync, oldest 19 business days |
| Downgrade asked | Call, 2 Sept | Hana asked about 10 seats |
Root-cause hypothesis
Joel ran scheduling; since he left, the calendar sync issue blocks Hana and nobody is driving use. Evidence: scheduling has been unused since 12 August and his exit was reported on 2 Sept [check: when Joel left]; both open tickets are on sync. Would be wrong if: usage fell before Joel left.
The rest of this output, the full steps and the checks the AI runs before it answers are in your pod once you add the skill.
Use this skill in your AIShare it with your team
Add it to an AI Skill Pod and everyone on the team, contractors included, uses the same version from their own AI. Read the best ways to share AI skills with a team
Changelog
- v1.0.1 · · Example: the input states today (Wednesday 9 September 2026) and the first save step is due Friday 11 September, not a Sunday; the hypothesis no longer dates Joel's exit, which the input doesn't give, and marks it to check.
- v1.0.0 · · First release.
Sources
- The Essential Guide to Customer Churn | Gainsight Software (read 2026-11-04)
- Customer health score: Everything you need to know [+Expert insights] (read 2026-11-04)
- CTAs, Tasks, and Playbooks Overview (read 2026-11-04)
- Customer Success Playbook: What to do When your Sponsor Leaves (read 2026-11-04)