A subscription cancellation survey asks one thing at the moment someone clicks cancel: why are you leaving? The answer decides which save offer the subscriber sees, which emails they get afterwards and, if you read the answers properly, what you fix in the product. This guide covers which reasons to list, how to map each one to an offer, how to get the reason into Klaviyo, how to read free text, and how to keep the whole thing on the right side of the rules.
The survey is one part of a bigger setup. For the full flow from the cancel button to the winback, read our guide to the subscription cancellation flow.
Why the survey matters more than the offer
Without a reason, every cancelling subscriber gets the same offer, and that offer is usually a discount. The subscriber with too much product at home gets 20% off more product they don't need. The one who hates the flavor gets 20% off the same flavor. Neither stays.
With a reason, you can show the offer that solves the actual problem. That's the whole point. Think of the survey as a routing question first and market research second, and give every answer somewhere to go.
Which reasons to list in a subscription cancellation survey
Five to seven options, plus "something else" with a text field. Here's the list we usually start from:
- I have too much product at home
- It's too expensive
- I don't like the product, flavor or scent
- I'm going away or need a break
- I'm not seeing results
- Delivery or shipping problems
- Something else (please tell us)
Adjust this to your product. A coffee brand will want "I'd like to try a different roast." A pet food brand might need "My pet's needs changed." A skincare brand may hear "It didn't suit my skin" often enough to give it its own line.
A few rules for the wording:
- Write it the way a subscriber would say it, in first person. "I have too much at home" works better than "Excess inventory."
- Keep each option short enough to read at a glance on a phone.
- Don't put the most common reason first just because it's convenient. Some apps let you shuffle the order, which gives you cleaner data.
- Keep the tone neutral. Nobody should feel guilty for picking an option.
If you add a new reason, ask yourself what offer it leads to. If the answer is "the same as another reason," merge them.
Map every reason to a save offer
This is where the survey earns its place. Each reason gets one first offer, and at most one backup.
| Reason | First offer | Backup | Email after cancel |
|---|---|---|---|
| Too much product | Longer interval | Skip next order | Reminder that the interval can change |
| Too expensive | Smaller size or longer interval | Discount for a set number of orders | Best offer in the winback |
| Doesn't like it | Swap product or flavor | None | New flavors when they launch |
| Going away | Pause until a chosen date | Skip | Short note when they're likely back |
| No results | Usage tips and honest timing | Swap | How to use it, from a real person |
| Delivery problems | Fix it and say so | Change date | Personal follow up on what changed |
| Something else | Skip or pause | None | Plain text email asking for a reply |
Show one offer at a time. If the subscriber declines, let them finish cancelling with one more click. A screen with five offers stacked on top of each other looks desperate, and it hides the cancel button.
And be careful with discounts. They fit one reason in that table. If your save rate comes mostly from discounts, your survey probably isn't doing its job, or the offers behind it aren't matched. Our pillar guide on how to reduce subscription churn covers discount hygiene in more detail.
Pass the reason to Klaviyo
The survey answer is only half used if it stays in the subscription app. In Klaviyo it can change the emails a subscriber gets after the cancel and the winback weeks later.
Check what your app sends
Most subscription apps send a cancellation event to Klaviyo through their integration. Many include the reason as a property on that event, and some also write it to the profile. Look at a recent cancellation event in a test profile and see what's actually there. Our guides to Recharge, Loop, Skio and Stay AI cover each integration.
Use it in the flow
In the flow triggered by the cancellation event, add a conditional split on the reason property. Each branch gets its own follow up. The "too expensive" branch can get a different winback offer than the "too much product" branch, which mostly needs a lower frequency.
Store it on the profile
Event properties are great for the flow that's triggered by the event. For segments and campaigns weeks later, you want the reason on the profile, ideally with the date. If your app doesn't write it there, check if your setup lets you copy it over, for example with a profile update step in the flow. Keep the values identical to the survey options, so "Too expensive" is always spelled the same way. Otherwise your segments miss people.
With the reason on the profile, you can do things like send a launch email for a new flavor only to people who left because they didn't like the old one. That's a much easier sell than a generic "we miss you." See our subscription winback and Klaviyo segmentation guides for the setup.
Read the free text every month
The "something else" box is where you learn what you didn't think to ask. Once a month, export the answers and go through them. It takes less time than you think.
- Sort them. Many free text answers actually fit an existing reason. Count them there.
- Keep a list of the rest. If the same new reason comes up month after month, it deserves its own option and its own offer.
- Look for fixable problems. Broken links in the portal, a courier that keeps failing in one region, packaging that leaks. These show up in free text long before anyone opens a support ticket.
- Note the exact words. How subscribers describe their problem is how your emails should describe the fix.
Share what you find with the people who can act on it. A recurring complaint about a flavor belongs with product, a courier problem with operations. The email team is often the first to see these patterns, because the cancel reason lands in Klaviyo right next to everything else you know about the subscriber.
Also look at the totals. If "too much product" climbs after you changed the default interval, you've found your cause. Our guide to subscription retention metrics shows how to track save rate per reason alongside the rest.
Keep cancelling easy
The survey must never become an obstacle course. A subscriber who wants to leave should be able to leave without hunting for the button.
Rules on this differ by country and by US state, and they keep changing. Germany, for example, requires a cancellation button for many contracts concluded online. Some places restrict how many retention steps you can put in front of the cancel, or require that cancelling online is as easy as signing up. We're not lawyers and this isn't legal advice, so have someone who knows the rules in your markets check the flow.
Apart from the law, a few practical rules:
- One question, one offer, then a clear way out.
- If the answer is required, keep it to a single tap.
- Confirm the cancellation clearly, by email, right after.
- Don't send another save offer in the confirmation email.
A subscriber who leaves easily and on good terms is a lot more likely to come back through the winback than one who had to fight their way out.
Questions we get a lot
How many reasons should a cancellation survey have?
Five to seven, plus an option for something else with a free text field. Fewer and you lump different problems together. More and subscribers pick whatever is at the top. Each reason should lead to a different save offer, or it doesn't need its own line.
Should the cancellation survey be mandatory?
Many apps let you require an answer before the cancel goes through. If you do, keep it to one quick question and make sure cancelling stays easy. Rules on how easy cancelling must be differ by country and state, so have a lawyer check whether a required question is fine where you sell.
How do I get the cancellation reason into Klaviyo?
Most subscription apps send a cancellation event to Klaviyo through their integration, and many include the reason as an event property. Check your own event data. If the reason only sits on the event, you can still branch flows on it, and you can store it on the profile so winback campaigns and segments can use it later.
What should I do with free text answers?
Read them every month. Sort them into the existing reasons, and keep a list of the ones that don't fit. If the same new reason shows up again and again, add it to the survey. Free text is also where you find fixable problems like broken links, delivery issues or a confusing portal.