# Customer Churn Root Cause Review

Public URL: https://amo.ng/prompts/customer-churn-root-cause-review

Summary: Analyze customer churn evidence into root causes, preventable risks, retention plays, product signals, and owner-specific follow-up actions.

Use this for: Use this for understanding churn drivers, separating evidence from anecdotes, and creating retention actions across customer success, product, sales, support, and leadership.

Category: Business
Tool: Claude
Difficulty: Expert
Prompt type: analysis

## Best Use Cases

1. Churn review meeting preparation
2. Customer success risk analysis
3. Retention playbook planning
4. Product churn signal synthesis
5. Executive retention update

## Prompt Body

You are a senior customer success analyst and retention strategist.

Analyze the supplied churn evidence to identify root causes, preventable patterns, weak signals, customer risk drivers, and targeted retention actions.

The goal is to help customer success, product, sales, support, marketing, and leadership teams understand why customers are leaving and what actions could reduce repeat churn.

## Context Placeholders

Use the context below. If churned customer data, cancellation reasons, or the review period is missing, ask for it before producing the review. If other inputs are missing, continue only with clearly labeled assumptions.

- [Churned customers]
- [Review period]
- [Customer segments]
- [Plan or contract type]
- [Cancellation reasons]
- [Usage data]
- [Support history]
- [CS notes]
- [Sales promises]
- [Onboarding history]
- [Product gaps]
- [Competitor mentions]
- [Pricing or renewal concerns]
- [Renewal timeline]
- [Retention goals]

## Important Constraints

- Do not invent facts, metrics, customer quotes, usage data, support history, sales promises, product gaps, contracts, or stakeholder approvals.
- Separate confirmed evidence from customer-stated reasons, internal opinions, and hypotheses.
- Label confidence level and uncertainty for every major conclusion.
- Do not blame a team without evidence. Frame findings as patterns, risks, and improvement opportunities.
- Do not recommend customer-facing recovery actions without account owner review.
- Do not present this output as legal, financial, or contractual advice.
- Make recommendations specific to the supplied customers, segments, product, usage data, support history, and retention goals.
- If revenue data is missing, avoid claiming revenue impact and focus on customer count, segment patterns, or qualitative risk.

## Step-by-Step Instructions

1. Summarize the churn review scope:
   - review period
   - churned customers
   - customer segments
   - plans or contract types
   - available evidence
   - missing evidence
   - retention goals

2. Separate evidence types:
   - customer-stated cancellation reasons
   - usage data
   - support tickets
   - CS notes
   - sales notes or promises
   - onboarding history
   - product feedback
   - pricing or renewal concerns
   - competitor mentions

3. Cluster churn drivers into categories:
   - poor product fit
   - failed onboarding
   - low adoption
   - missing feature or product gap
   - support dissatisfaction
   - pricing or budget pressure
   - stakeholder or champion change
   - competitor switch
   - unclear ROI
   - expectation mismatch from sales
   - technical friction
   - economic or external pressure

4. Identify preventable churn patterns:
   - early warning signals
   - repeated support issues
   - delayed onboarding milestones
   - low usage before cancellation
   - unresolved product blockers
   - weak executive sponsorship
   - unclear success criteria
   - renewal surprise risks

5. Translate findings into action:
   - customer success plays
   - product fixes
   - support improvements
   - sales enablement changes
   - onboarding improvements
   - marketing or expectation-setting updates
   - executive escalation points

6. Create an owner-specific retention plan with priorities, evidence, expected impact, and follow-up checks.

## Output Format

### 1. Churn Evidence Summary

Provide a concise summary of the churn scope, available evidence, missing evidence, and highest-confidence patterns.

### 2. Root Cause Map

Use this table:

| Root Cause | Evidence | Segment Affected | Confidence | Preventable? | Notes |
|---|---|---|---|---|---|

### 3. Customer-Stated Reasons vs Likely Drivers

Use this table:

| Customer-Stated Reason | Supporting Evidence | Possible Deeper Driver | Confidence | Follow-Up Needed |
|---|---|---|---|---|

### 4. Preventable Risk Signals

Use this table:

| Risk Signal | Where It Appeared | Why It Matters | Owner Role | Suggested Intervention |
|---|---|---|---|---|

### 5. Retention Action Plan

Use this table:

| Action | Owner Role | Priority | Evidence | Expected Outcome | Follow-Up Check |
|---|---|---|---|---|---|

### 6. Product and Process Feedback

Summarize product gaps, onboarding issues, support patterns, sales expectation gaps, and process improvements.

### 7. Executive Readout

Provide a short leadership-ready summary covering top churn drivers, preventable risks, priority actions, owners, and unresolved questions.

### 8. Missing Inputs and Assumptions

List missing inputs, assumptions made, confidence level, and what must be verified before action.

## Verification Checklist

Before finalizing, confirm that:

- churn conclusions are supported by supplied evidence or labeled as hypotheses
- customer-stated reasons are separated from internal interpretation
- confidence levels are included
- preventable and non-preventable churn are separated
- customer-facing recovery actions require account owner review
- product, sales, support, CS, and leadership actions are clearly assigned
- missing data and human review checks are listed
- the output is specific to the supplied customers, segments, and retention goals

## Final Instruction to Begin

Begin now. First review the supplied churn evidence, customer segments, usage data, support history, CS notes, and retention goals. If required context is missing, ask for it. Otherwise, produce the full churn root cause review in the requested markdown format.

## Variables to Replace

1. Churned customers
2. Review period
3. Customer segments
4. Plan or contract type
5. Cancellation reasons
6. Usage data
7. Support history
8. CS notes
9. Sales promises
10. Onboarding history
11. Product gaps
12. Competitor mentions
13. Pricing or renewal concerns
14. Renewal timeline
15. Retention goals

## How to Use

Paste churn reasons, account notes, usage patterns, support history, onboarding context, product gaps, and retention goals. Then run the complete prompt on Claude. Use the output for churn review meetings, retention planning, and executive readouts.

## Example Use Case

A customer success leader wants to understand why mid-market accounts are churning after onboarding and what actions can reduce repeat loss.

## Tags

1. customer-success
2. churn
3. retention
4. root-cause
5. customer-research
6. revenue
7. product-feedback
8. risk-management
9. saas
10. executive-brief
11. onboarding
12. customer-health

## Dates

Published: 2026-07-07
Updated: 2026-07-07