Cancellation survey questions that tell you why people leave

A cancellation survey (also called a churn survey) is shown during the cancel flow, usually between the Cancel button and the confirmation. Its job is to capture the reason while the customer is still in the product. A customer exit survey is typically sent after the account has closed, by email, and can go deeper because nothing is at stake for the customer any more.

The in-flow survey does most of the work. A post-cancellation email reaches people who have already moved on, while the in-flow question is seen by everyone who cancels through your product. Keep the in-flow version to one or two questions and save longer questions (ratings of support, pricing, reliability) for the email follow-up.

Both are different from an employee exit interview. If that is what you need, Zunoform has a separate exit-interview template.

A pile of reasons is not an insight. The analysis only works if each response can be joined to the account it came from.

Pass the account ID, plan and signup month into the survey as hidden fields in the URL, so the customer never has to type them. Then you can split reasons by plan, tenure and acquisition channel. "Too expensive" from month-one customers on the cheapest plan is a different problem from the same answer on a three-year Business account.

Report each reason as a share of all cancellations per month, next to the number of cancellations. If "missing feature" goes from 20% to 35% after a pricing change, that tells you something. A raw count moves with signups and tells you much less. Keep failed-payment (involuntary) churn out of the survey data entirely, because those customers never saw the survey.

Tag them by hand into your reason categories plus any new theme, once a month. When a new theme keeps appearing, add it to the options list and note the date you changed the survey, so the trend line has a known break.

Give each reason an owner (the last column of the table above). Where the customer agreed to be contacted, tell them when you ship the thing they left over.

Generally yes, provided it doesn't obstruct cancellation. The rules have moved, so here is where they stand as of 28 September 2026. This is a summary, not legal advice.

The FTC's 2024 "click-to-cancel" amendments to its Negative Option Rule would have required cancelling to be as easy as signing up. The Eighth Circuit Court of Appeals vacated them on 8 July 2025, days before most provisions were due to apply, on procedural grounds rather than on the substance. The FTC restarted the process with an advance notice of proposed rulemaking, announced on 11 March 2026 and published in the Federal Register on 13 March, with comments due by 13 April 2026. As of today the FTC's rule page lists no proposed or final rule after that notice, so there is no federal click-to-cancel rule in force.

That does not leave a gap. The Restore Online Shoppers' Confidence Act (ROSCA, 2010) still requires online sellers of recurring charges to provide "simple mechanisms" to stop them, and the FTC continues to bring cases under ROSCA and Section 5 of the FTC Act. For consumer subscriptions, many states have their own automatic-renewal laws. California's, as amended by AB 2863 from 1 July 2025, requires cancellation in the same medium used to sign up (so online signups must be cancellable online), and allows a discount or retention offer only if the consumer remains able to cancel.

The practical reading for a cancellation survey: make it skippable, keep the cancel button on the same screen as any offer, don't require a phone call or chat to finish, and process the cancellation when the customer asks for it. If you sell to consumers in several states, or your flow is more elaborate than one question and one offer, have a lawyer review it.

Three placements are common: an in-app page shown when someone clicks Cancel, a hosted form linked from the cancel page, or an email after cancellation, which allows longer questions.

For the hosted-form approach, link to the survey from your cancel button with the account details in the URL, then redirect back to your own confirmation page after submit. If someone closes the survey, your app should still cancel. The survey is a side door, not a gate.

Zunoform works for the hosted-form approach. Hidden fields read the account ID, plan and signup month from the URL. Conditional logic sends each reason to its own follow-up. Redirect after submit (with a 0–60 second delay, and answers carried in the URL if you want them) returns people to your confirmation page. Partial responses are saved as people go, so you keep the reason even when someone skips the follow-up. Responses can go to Google Sheets or your own webhook on the Free plan, which allows 500 responses a month. Hidden-field values go along with each delivery: the Sheets row gets a column per hidden field and the webhook payload carries them in a hidden object, so the account ID lands next to the reason and you can join answers to account data without an export.

It does not cancel the subscription. Your billing system or app still has to do that, and it should not wait on the survey. Zunoform is also not an in-app retention tool: it won't show a modal inside your product, test different offers, or apply a discount in Stripe or Paddle. Dedicated cancellation-flow tools do those things. Note that the Churn Survey and Customer Exit Survey templates include an NPS question, which needs Pro to publish. Delete it, or swap it for a rating question, to stay on Free.