Analyze Customer Cancellation Reasons to Surface Preventable Churn Fixes
Get a structured churn analysis table separating controllable from uncontrollable cancellations, with exact counts, root causes, and one retention fix per category.
You getSummary Table and top 3 Priorities
Prompt
Act as a customer retention analyst. I will paste raw customer cancellation reasons, exit survey notes, or support tickets right after this prompt. Analyze the data to separate preventable churn from uncontrollable churn and surface concrete fixes.
Rules:
- Count every cancellation entry and group them into clear, mutually exclusive categories.
- Classify each category as Controllable (product gaps, onboarding, support, pricing) or Uncontrollable (business closed, seasonal pause, acquired).
- Identify the specific root cause behind each category using only the pasted data; do not invent reasons or statistics.
- Propose exactly one actionable retention fix per controllable category that a support or product team can test within 30 days.
Output format:
1. Summary Table: Columns for Category, Type (Controllable or Uncontrollable), Exact Count, Root Cause, and 30-Day Retention Fix.
2. Top 3 Priorities: A short numbered list of the highest-impact controllable categories to tackle first, with one sentence explaining why.
End with one line noting any ambiguous entries, missing context, or assumptions made while grouping the data.Example output
Tips and common edits
Why this works
- Forces mutually exclusive categories and exact counts so high-volume churn drivers stand out immediately.
- Separates controllable from uncontrollable churn to stop teams from wasting time on unpreventable losses.
- Requires one 30-day retention fix per category, keeping recommendations practical for support and product teams.
Use this monthly or quarterly after exporting exit survey responses or cancellation tickets. Paste 20 to 200 raw customer reasons right after the prompt in ChatGPT, Claude, or Gemini.
Common edits
- Add account MRR or plan tier to the pasted data and ask the model to sort the table by lost revenue instead of count.
- Change the 30-day fix constraint to focus only on help-center articles or automated in-app messages.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Draft a Feature Deprecation Notice for Your Customers
Get a clear, empathetic customer notice that explains a feature sunset, provides alternative workflows, and outlines migration steps to minimize user friction.
Draft Professional SLA Breach Notification Emails
Generate a clear, transparent SLA breach notification email that includes incident details, the root cause, and a concrete calculation for service credits.
Write Executive Escalation Email for At-Risk Customers
Generate a professional, high-impact email from a VP to retain a churn-risk customer by offering ownership, a concrete fix, and direct communication.
Write Proactive Renewal Check-In Emails for At-Risk Accounts
Generate a three-part email sequence to re-engage quiet customers at risk of churn by highlighting unused value and offering a workflow audit.
Write an Honest Offboarding Email with Data Export Deadlines
Generates a clean subscription cancellation confirmation email featuring hard data retention timelines and a neutral exit survey.
Explain a prorated bill or plan change clearly
Turn confusing mid-cycle invoice numbers into a calm, line-by-line explanation a customer can read in two minutes. Perfect for diffuse billing tickets.
- Turn Around Negative CSAT Scores with a Calm Follow-Up Email
- Analyze customer sentiment beneath translated tickets
- Explain browser console logs to everyday users
- Respond quickly to an unexpected VIP cancellation notice
- Confirm an order cancellation with clear refund timing
- Turn customer call notes into action items