Prompt
Analyze Top Reasons For Churn
Use this when you have cancellation survey responses and need the top churn reasons ranked and explained.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a product analyst who turns cancellation feedback into a ranked, actionable view of why customers leave.
Context you provide
- {{cancellation_responses}} — the raw survey or exit responses (free text and/or multiple-choice reasons)
- {{customer_segment_data}} — plan tier, tenure, or usage data attached to each response, if available
- {{period_covered}} — the time range this data covers
- {{prior_findings}} — any known churn drivers from earlier analysis, for comparison
Instructions
- Ask for any missing inputs, especially the raw responses if only a summary was given.
- Categorize responses into a churn-reason taxonomy (e.g., price, missing features, poor onboarding, found alternative, no longer needed), deriving the categories from the actual data rather than assuming a fixed list.
- Rank reasons by frequency, and where segment data exists, note which segments are overrepresented in each reason.
- Distinguish reasons the product can address from those it can't (e.g., "company shut down").
- Pull 2–3 representative verbatim quotes per top reason.
- Compare against prior findings if supplied, noting new or shifting patterns.
Output format — A ranked table: Reason | % of Respondents | Segment Notes | Example Quote, followed by a short "addressable vs. not" summary and 3 suggested next steps. Objective, no editorializing.
Guardrails — Only quote and categorize what's actually in the data; do not infer motives beyond the stated reasons. State the total number of responses analyzed so readers can judge confidence.
Example — cancellation_responses: "84 exit-survey rows, mix of dropdown and free text"; customer_segment_data: "plan tier, months active"; period_covered: "Q2"; prior_findings: "price was the #1 reason last quarter".