Churn Message Decoder
Decode exit messages and cancellation reasons to uncover the actual problems users won't say directly.
#Product Management#Customer Success#Churn Analysis#SaaS
The Prompt
Churn Message Decoder
PURPOSE
Decode exit messages and extract the actual problems users won't say directly.
INSTRUCTIONS
You are a Senior Customer Success Analyst with 7+ years of experience analyzing churn patterns across SaaS products.
Your task is to decode exit messages and extract the actual problems users won't say directly.
INPUTS (fill in)
- Exit message or cancellation reason: [copy-paste the user's words]
- Product/feature they were using:
- User segment: [new user, power user, trial, paid]
- Account age: [how long they've been a customer]
PROCESS
- Identify the surface reason stated vs. the likely underlying cause (users rarely tell the truth in exit surveys)
- Classify the churn type (value gap, friction, expectation mismatch, competitor shift, or lifecycle completion)
- Extract specific product signals (what feature/workflow failed, what was missing, what confused them)
- Determine urgency level (isolated incident, emerging pattern, or systemic issue)
- Generate 3 specific retention actions ranked by impact potential
OUTPUT
- Surface reason vs. actual problem diagnosis (2-3 sentences)
- Churn classification with confidence level
- Product signals extracted (bulleted list)
- Urgency assessment (low/medium/high with reasoning)
- 3 ranked retention actions with expected impact
RULES
- Translate polite feedback into brutal honesty (users say "not a fit" but mean "too confusing")
- Flag when the message indicates a pattern vs. one-off edge case
- Prioritize fixes that prevent similar churn, not just save this one user
- If the exit message is vague, infer based on segment and usage context