Churn Survey

Every customer who cancels knows something you do not. A churn survey captures that knowledge at the exact moment it is most accessible: when the customer has decided to leave and has a clear reason in mind.

Acquiring a new customer costs five to 25 times more than retaining an existing one. Churn surveys do not just explain why people leave. They surface the patterns that, once addressed, prevent the next wave of cancellations.

When to deploy a churn survey

The survey should appear at the moment of cancellation, not after. Once a customer has left, response rates drop dramatically. In-product surveys triggered during the cancellation flow consistently outperform post-cancellation emails.

Deploy churn surveys in these scenarios:

• Subscription cancellation. The highest-priority use case. Display the survey as a step in the cancellation flow before the account is fully closed.
• Plan downgrade. A downgrade is a partial churn. Capturing why someone is moving to a lower plan reveals whether you have a pricing problem, a feature gap, or a value communication issue.
• Trial expiration without conversion. Users who try your product and decide not to pay are a distinct churn segment. Their reasons are different from paying customers who leave.
• Contract non-renewal. For annual or enterprise contracts, send the survey when a customer declines to renew.

Churn survey questions

Keep the survey to four or five questions. The customer is already leaving. A long survey will not change their mind, and it will reduce your response rate.

1. What was the primary reason for canceling? | Multiple choice (Too expensive, Missing features I need, Switched to a different tool, No longer need this type of product, Too difficult to use, Poor customer support, Other) | Required
2. What did you like most about [product]? | Open text | Optional
3. Is there anything we could have done differently to keep you? | Open text | Optional
4. Would you consider using [product] again in the future? | Yes / Maybe / No | Optional
5. Is there anything else you would like us to know? | Open text | Optional

Question one gives you categorical data you can aggregate and trend over time. Question two surfaces what is working (useful for marketing even though this customer left). Question three reveals whether the churn was preventable.

Some teams add a "Would you like us to reach out?" option at the end. This identifies customers who are open to a save conversation.

Designing the cancellation flow

Where the survey sits in the flow matters as much as the questions themselves.

No skip button. Making the survey mandatory (but keeping it short) dramatically increases response rates. A single required multiple-choice question with an optional text field is the right balance between data collection and respect for the customer's time.

Show the survey before confirming cancellation. If the survey appears after the account is already closed, response rates drop by 60% or more.

Personalize when possible. Including the customer's name, plan type, and tenure makes the survey feel considered rather than generic. "You have been on the Pro plan for 14 months" is context that helps the customer reflect.

Consider a save offer. Based on the reason selected, you can present a targeted retention offer. Selected "too expensive"? Offer a discount or a plan pause. Selected "missing features"? Share your roadmap. This is not manipulative. It is addressing the customer's stated concern.

How to analyze churn survey data

Track reason categories over time. The distribution of cancellation reasons is more useful than any individual response. If "too expensive" was 15% of cancellations last quarter and is 30% this quarter, you have a pricing problem that is getting worse.

Segment by customer type. Early churners (first 30 days) leave for different reasons than long-term customers. Segment by tenure, plan type, company size, and acquisition channel. Each segment tells a different story.

Read the open-ended responses. Categorical data tells you what. Open text tells you why. Schedule a weekly review of churn verbatims with your product team.

Connect to usage data. A customer who says "missing features" but never used the features you already have does not have a feature problem. They have an onboarding problem. Cross-reference survey responses with actual product usage for the full picture.

Calculate preventable churn. Not all churn is fixable. A customer who no longer needs your category of product is gone regardless. But a customer who left because of a specific bug, a missing integration, or a support failure represents preventable churn. Quantify that number and track it.

Common mistakes

Asking too many questions. Four to five questions maximum. Every additional question reduces completion rates, and you are surveying people who have already decided to leave.

Only surveying cancellations. Downgrades are churn signals too. A customer moving from Pro to Free is telling you something important about the value gap between tiers.

Not acting on the data. If "difficult to use" appears in 25% of churn surveys for three consecutive months and nothing changes, the survey is a waste of everyone's time.

Ignoring positive feedback. Question two ("what did you like most") often surfaces your strongest differentiators. Churned customers who liked specific things are giving you positioning data.

Using email surveys instead of in-product. Email churn surveys get 1-2% response rates. In-product surveys at the point of cancellation get 30% or higher.

Set up this survey in Formbricks

Formbricks lets you embed a churn survey directly in your cancellation flow. Trigger the survey when a user initiates cancellation, and the questions appear before the account is closed.

The template includes conditional logic that adjusts follow-up questions based on the cancellation reason selected. If someone selects "too expensive," the follow-up asks about pricing expectations. If someone selects "missing features," the follow-up asks which features they needed.

All responses are tagged with user attributes, so you can segment churn reasons by plan type, tenure, and any custom data you track. Set up alerts to notify your team when specific churn reasons spike.