Cancellation Survey Questions to Reduce SaaS Churn

A customer exit survey (or cancellation survey) asks customers why they're leaving at the moment they cancel. The core is one required multiple-choice question, "What's the main reason you're cancelling?", followed by one follow-up that depends on the answer and an optional open question. Put it inside the cancel flow, not in an email afterwards, keep it under a minute, and use the answer to show a relevant alternative (a pause, a downgrade, help) and to decide who gets a win-back message later.

Why a cancellation survey is worth it

Churn dashboards tell you how many customers left and when. They don't tell you why. A short survey at cancellation is the one moment nearly every leaving customer is still in front of you, and the reasons they give fall into groups you can act on:

Fixable product problems: missing features, bugs, too hard to use.
Price and value: too expensive, not using it enough to justify it.
Circumstance: project ended, company closed, seasonal business, budget freeze.
Competition: switching to another tool.
Service: bad support experience, billing issues.

Each group needs a different response. You can't win back a company that shut down, but you can pause a seasonal business, offer a smaller plan to someone who isn't using enough, and fix the bug that sent three accounts to a competitor this month.

The core cancellation survey questions

Keep the survey to three to five questions. Here's a set that works for most SaaS and subscription businesses.

1. What's the main reason you're cancelling? (required, single choice)

Offer five to seven options, written in the customer's words, plus "Other":

It's too expensive
I'm not using it enough
It's missing a feature I need
It's too hard to use, or I couldn't get it set up
I'm switching to another tool
My project or business has changed
Technical problems or bugs
Other (please tell us)

Randomize the order so the first option doesn't get picked by default, and keep "Other" last. Ask for the main reason, not all reasons; a multi-select gives you a pile of ticked boxes and no priority.

Revise the list as answers come in. A rule of thumb ProsperStack suggests is to split any option that draws a large share of responses into more specific ones and drop options almost nobody picks.

2. One follow-up question based on the reason

This is where logic earns its keep. Show a different follow-up for each reason:

Reason	Follow-up question
Too expensive	What would a fair price be for how you use it? or Which plan would you have stayed on?
Not using it enough	What did you hope to use it for?
Missing feature	Which feature, and what were you trying to do?
Too hard to use	Where did you get stuck?
Switching tools	Which tool are you moving to, and what does it do better?
Business changed	Do you expect to need something like this again? When?
Bugs	What went wrong? (with an optional screenshot upload)
Other	Tell us more

3. What could we have done to keep you? (optional, open text)

Make it optional. Customers who are annoyed will skip a required essay or type something useless into it.

4. How likely are you to come back in the future? (optional, scale)

A simple 1-5 or "not likely / maybe / likely" answer tells you who to include in win-back campaigns and who to leave alone.

5. May we contact you about your answers? (yes/no)

Some departing customers are happy to have a 15-minute call. Those calls are often where the clearest product insight comes from.

Optional extras

How would you rate your overall experience with us? (1-5)
What did you like most?
Which plan were you on? (skip this if you pass it in automatically; see below)
How long have you been a customer? (same)

Don't ask for anything you already know. Plan, tenure, account ID and seat count belong in your data, not in questions.

Where to put the survey in the cancel flow

There are three common placements:

Placement	How it works	Pros	Cons
Before the final cancel button	Customer clicks Cancel, answers the survey, then confirms	Highest response rate; answer can trigger a relevant offer	Must not feel like a barrier
After cancellation is confirmed	Thank-you page shows the survey	No pressure, honest answers	Fewer responses; no chance to offer an alternative
Email after cancelling	Survey link sent later	Easy to set up	Low response rates; the moment has passed

Most teams put it before the final confirmation step. If you do, follow two rules:

Never block cancellation. The customer must be able to finish cancelling whether or not they answer. A survey that traps people generates complaints, chargebacks and angry reviews, and in some places it breaks the law.
Make the offer optional and clear. One relevant alternative, with an obvious "No thanks, cancel my subscription" next to it.

On the legal side: subscription cancellation rules vary by country and state, and they change. In the US, the FTC's "click-to-cancel" rule was vacated by the Eighth Circuit in July 2025 before it took full effect (summary by Arnall Golden Gregory), but state laws still apply. California's amended automatic renewal law, in effect since July 1, 2025, allows retention offers during cancellation only if the business first tells the consumer they can complete cancellation at any time, and online cancellations must show a direct cancel link or button alongside the offer (Venable summary). This isn't legal advice; check the rules where your customers are.

Using answers to win back or route customers

The survey only reduces churn if each answer leads somewhere.

Offer a relevant alternative in the moment

Match one offer to the reason. Don't stack three.

Too expensive: a cheaper plan, an annual plan with a lower monthly price, or a time-limited discount.
Not using it enough: a pause instead of a cancel, or a downgrade to the free or smallest plan.
Hard to use or couldn't set up: a setup call or a direct link to help.
Missing feature: if it's on your roadmap, say so honestly and offer to notify them. If not, let them go gracefully.
Business changed or seasonal: a pause for one to three months.
Switching tools: usually let them go, but ask what the other tool does better.

Route the response to the right people

Product team: missing features and usability problems, with the customer's own words.
Support or success: customers who reported bugs or bad service and agreed to be contacted. A same-day reply from a person can still change their mind.
Finance or billing: billing errors and payment problems, which are often involuntary churn rather than a decision to leave.
Marketing: customers who said they might come back, with the reason, for a win-back email when something relevant changes (the feature ships, a new lower plan).

Review the numbers monthly

Count reasons by month, by plan and by tenure. Patterns to look for: new customers leaving because of setup (an onboarding problem), long-time customers leaving on price (a value or packaging problem), and a spike in "switching tools" naming the same competitor.

Retention survey questions: before customers decide to cancel

A cancellation survey catches people on the way out. A retention survey, sent to active customers, catches the same problems earlier. Useful questions:

How likely are you to recommend us to a friend or colleague? (0-10)
How would you feel if you could no longer use the product? (very disappointed, somewhat disappointed, not disappointed)
What's the main thing you use it for?
How easy is it to get done what you need? (1-5)
Is there anything you expected to do with it that you can't?
How well does the price match the value you get? (1-5)
How likely are you to renew? (1-5)
What one change would make you more likely to stay?

Send it at moments that predict churn: a drop in usage, a few weeks before renewal, after a support ticket, or after onboarding ends. For more question ideas, see our guides to customer loyalty survey questions and NPS questions, and our post on in-app surveys for asking inside the product.

If you're looking for the HR version (why employees leave), that's a different survey: see employee exit survey questions.

How to do this in FlowyForm

FlowyForm gives you the survey and the routing. It isn't a billing tool, so it doesn't cancel subscriptions, pause plans or apply discounts itself; those happen in your billing system (Stripe, Paddle, Chargebee or your own backend).

Start from a template. The membership cancellation form template has the cancellation reason, an optional "tell us more", a "would one of these suit you better?" offer of a pause or downgrade, an effective date and an experience rating. For a lighter post-cancel survey, adapt the customer feedback form template.
Add reason-based logic. Rules like "if reason is It's too expensive, go to Which plan would you have stayed on?" give each customer the right follow-up. Turn on randomize for the reason options and keep "Other".
Pass account data in with hidden fields. Link to the form from your cancel page with values such as ?account_id=123&plan=pro&tenure=14 so you don't have to ask. The values are stored with each response and can be used in logic, for example to show an annual-plan offer only to monthly customers.
Show the alternative on an ending. Use different endings for each reason, with the offer explained in plain words. On Premium, an ending can redirect to a URL, such as your downgrade page, a discounted checkout link or your booking page for a setup call. Always include a plain way to finish cancelling.
Embed it in your cancel flow with the iframe snippet, inline or full page, or open it as a link. Use your product's colours and fonts so it feels like part of your app.
Route responses. Post every cancellation to a Slack channel, log them to a Google Sheet for the monthly review, and send them by webhook to your backend or to Zapier, Make or n8n to update your CRM, tag the customer for win-back, or open a support ticket.
Measure. The response table and CSV export show reasons over time. Premium adds per-question breakdowns and partial responses, so you can see customers who started the survey but stopped.

When a dedicated tool fits better: if you want the save offer applied automatically in your billing system the moment the customer accepts it, with churn and save-rate reporting built in, retention tools such as ProsperStack or Chargebee Retention connect directly to billing. FlowyForm suits teams who want a flexible, branded survey and handle the billing step in their own app or automation.

FAQ

What questions should a cancellation survey ask?

The main reason for cancelling (single choice with "Other"), one follow-up that depends on the reason, an optional "what could we have done to keep you?", how likely they are to come back, and permission to contact them.

Should a cancellation survey be required?

The main-reason question can be required within the survey, but the survey itself shouldn't block cancellation. Customers must be able to finish cancelling either way.

How many questions should a churn survey have?

Three to five. It should take under a minute, because the customer has already decided to leave.

What's the difference between a customer exit survey and a retention survey?

An exit survey runs at cancellation and asks why they're leaving. A retention survey goes to active customers and looks for signs they might leave, such as low satisfaction, low usage or poor value for money.

Should I show a discount in the cancel flow?

Only when the reason is price, and only one offer. Showing discounts to everyone trains customers to start cancelling to get a deal.

What do I do with cancellation survey results?

Count reasons monthly by plan and tenure, send product issues to the product team, follow up personally with customers who agreed to it, and use "might come back" answers for targeted win-back messages.

Cancellation Survey Questions: Reduce SaaS Churn With Exit Surveys