Industries
SaaS churn risk
Empathetic cancel and risk interviews with a clear churn taxonomy field. Surfaces price, feature, competitor, and usability drivers — and openness to a save offer.
Cancel surveys that only offer five radio buttons produce a flat “price” pie chart. Real churn mixes missing integrations, a competitor’s workflow, a champion leaving, and quiet usability debt.
This template runs an empathetic AI interview in cancel flow or after a usage-drop trigger. A required churn taxonomy field keeps reporting clean; probes capture competitor names, missing features, and whether a save offer is even welcome.
Treat cancel-flow interviews as last-mile truth. Pair with relationship pulses earlier so you are not learning about churn only at the door.
Best for
- SaaS retention and CS teams
- Product managers owning cancel reasons
- Growth teams embedding in cancel flow
Outcomes
- Actionable churn reason mix
- Competitor and integration blockers
- Win-back levers tied to quotes
How it works
1
Choose cancel-flow vs risk wave
Embed or link in cancel UX for definitive reasons; API-trigger on usage drop for earlier intervention.
2
Require a churn reason field
Taxonomy might include price, missing feature, competitor, usability, champion left, company change. Allow “other” with a probe.
3
Ask about save openness carefully
Do not hard-sell. Ask whether anything would make them stay — then route willing accounts to CS with context.
4
Close the product loop weekly
Feed missing-feature and competitor themes into roadmap triage. Quotes beat anonymous cancel codes.
Sample questions
- QWhat is the main reason you are leaving or considering leaving?
- QWhich alternative are you moving to, if any — and what looks better there?
- QWas there a moment things started to feel wrong?
- QIs there anything that would make you reconsider, or is the decision already final?
Setup tips
- Keep tone respectful — participants are often frustrated. Guardrails should forbid argumentative or salesy replies.
- Separate involuntary churn (bankruptcy, acquisition) in taxonomy so product does not chase ghosts.
- Pass plan and tenure metadata; early vs late churn drivers differ.
Frequently asked questions
- Should this run inside the cancel button flow?
- Yes, when legal and UX allow a short intercept. Keep it optional and brief. Also run usage-drop waves so not every insight arrives at cancel time.
- What if someone refuses to talk?
- Allow a one-click skip to cancel. Forced interviews poison both completion quality and brand trust.
- How do we use save-offer answers?
- Only when the participant signals openness. Route those sessions to CS with the transcript summary — do not auto-discount everyone who mentions price.