Cancellation Feedback Form Template
Learn why customers leave at the moment they go — reason-specific follow-ups, a win-back door left open, and exit notes your roadmap will thank you for.
You're leaving — we won't make it weird. Sixty seconds of honesty helps us fix what pushed you out.
Exit feedback is the highest-signal data a subscription business collects, and the worst-collected: most cancellation surveys are a wall of guilt placed between the customer and the door, so people click the first option and lie. This template takes the opposite stance — the intro promises not to make it weird, the form is six questions at most, and the reason question branches so each leaver only sees the follow-up that fits their answer.
Why these fields. The reason list covers the five exits that account for nearly all churn — price, features, under-use, a competitor, and support — plus an escape hatch. Each of the first three triggers its own targeted probe: price-leavers are asked what number would have kept them (real willingness-to-pay data, straight from the people who just proved the current price fails), switchers are asked where they are going (your competitive landscape, self-reported), and feature-leavers are asked which capability tipped it (a roadmap vote weighted by lost revenue). The experience scale separates "the product failed me" from "the product was fine but life changed", which completely changes how you read the rest. The win-back question is the quiet revenue play: choosing "if the reason gets fixed" swaps the ending to a door-stays-open message, converting a cancellation into a future reactivation lead.
What we left out. Retention offers — a feedback form that suddenly discounts is a negotiation, and it teaches customers to cancel for coupons. Multi-page interrogations, mandatory text fields, and "are you sure?" repetition are also absent; exit friction breeds chargebacks and grudges.
Who uses this. SaaS products link it from the cancellation flow's confirmation step, membership sites and box subscriptions email it after the cancellation processes, and service retainers send it when a client winds down.
Make it yours. Match the reason options to your actual churn taxonomy — if your support tickets say "too complicated" is a top exit, add it. Pipe responses to your CRM via webhook and tag the win-back "yes" cohort for a ship-announcement list. Review the CSV monthly: reason mix shifting toward "switching" is an early competitive alarm that dashboards rarely catch.
The reason with no probe. Price, features, and switching each trigger a targeted follow-up; "not using it enough" deliberately gets none, because under-use is rarely something a leaver can explain at the door — its causes live weeks earlier, in setup friction and habits that never formed. Treat that answer as a verdict on your onboarding rather than a prompt for more questions here. What you can act on is proportion: when under-use grows as a share of exits while the experience scores stay warm, you are winning hearts and losing calendars, and the retention fix is activation work, not roadmap work. The exit-note field catches whatever your reason taxonomy missed — read it before renaming any option.
Frequently asked questions
Where in the cancellation flow should this sit?
After the cancellation is confirmed, not before — feedback gated in front of the exit gets rage-clicked. A link on the confirmation screen or email gets calmer, truer answers.
How do the reason-specific questions work?
Three Logic rules show a different follow-up for price, switching, and missing features. Leavers see only the one that matches their reason, keeping the exit short.
What do we do with the win-back answers?
Export the CSV or webhook them into your CRM, tag the "if fixed" cohort by the feature or issue they named, and email exactly that list when you ship the fix.
Should the form be mandatory to cancel?
No — forced feedback is fiction. Keep it optional and short; completion above forty percent is achievable when the intro promises no retention tricks.