Customer Churn Interview Questions: A Cancellation Research Guide

A customer churn interview explores the sequence behind someone’s decision to stop using or paying for a product. Ask what they hoped to accomplish, what happened during use, what changed, and what they did after leaving. A cancellation label such as “too expensive” is a starting point for inquiry.

This guide provides an original interview script and a review worksheet. It is designed to help a product or customer success team form explanations it can investigate. Running interviews alone does not establish why every customer leaves or prove that a proposed change will improve retention.

Download the churn interview worksheet.

Define the kind of churn you are investigating

Choose the event and customer group before writing invitations. A free-trial expiry, a deliberate subscription cancellation, a payment failure, and an account that remains paid but unused need different questions.

For a first study, define a specific cohort, such as customers who deliberately cancelled after trying the product. Record when the event occurred, what experience each participant had, and how you identified the group. Avoid mixing an administrator’s billing action with an end user’s experience without preserving the distinction.

If an account has several users, one interview describes one person’s perspective. A buyer may describe budget pressure while an end user describes workflow friction. Both can matter, and their accounts may conflict.

Write an invitation that makes participation clear

Explain that the purpose is learning about the experience. Keep any win-back or support activity separate so people can understand what they are agreeing to.

Here is suggested invitation copy to adapt:

We are reviewing the experience of customers who recently stopped using our product. Would you be willing to describe what happened? Your participation is optional. We will explain how we use the conversation before you start.

Include an accurate time expectation based on a rehearsal of your own guide. If an AI agent will conduct the interview, say so. Describe any incentive and relevant data handling in the invitation. Avoid sending repeated requests to someone who has declined.

An adaptable churn interview script

1. Recover the original goal

Start before the cancellation:

• What were you trying to accomplish when you first chose the product?
• What were you doing before that?
• What made this seem worth trying at the time?
• Who else was involved in the decision?

Keep this section short, but do not skip it. A product can be usable and still solve a task that no longer matters to the customer. Understanding the original goal helps interpret what changed.

2. Reconstruct actual use

Ask for a concrete occasion:

• Walk me through a recent time you used the product for that task.
• What worked as you expected?
• Where did you have to pause, repeat something, or work around a limitation?
• What did you do when that happened?
• Were you able to reach the outcome you needed?

Allow an answer that the product worked well. The purpose is to understand the experience, including evidence against the team’s preferred explanation.

3. Explore the decision to leave

• When did you first consider stopping?
• What was happening around that time?
• Was there a particular event that led you to decide?
• What had you tried before deciding to leave?
• Who made or approved the final decision?

Distinguish a final trigger from an underlying condition. A renewal reminder might prompt action after weeks of low use. A price increase might matter because the customer’s team shrank. These are illustrative possibilities to investigate, not findings about your customers.

4. Follow ambiguous cancellation reasons

If the participant says “too expensive,” ask what they were comparing the cost with and what outcome they were getting. Avoid arguing about the price or immediately offering a discount.

If they say “missing features,” ask which task they could not complete and how they handled it. A feature request can conceal a different constraint, such as permissions or an incompatible process.

If they say “we no longer need it,” ask what changed in the work and when that change occurred. There may be no product change that would make the original job necessary again.

If they say “hard to use,” ask them to describe the step and what happened next. Their account can guide a later usability study; it does not replace observing someone attempt the task.

5. Understand the alternative and close

• What are you using or doing now?
• What trade-offs have you noticed with that approach?
• Is any part of the original task still unresolved?
• What have we missed about your decision?
• May we contact you if we need to clarify something?

Ask about permission for follow-up independently of any incentive or account status. Record a refusal without interpreting it as dissatisfaction.

Organize findings around explanations

For each completed interview, write a short record with:

1. The original job and relevant account context.
2. A useful or disappointing product experience.
3. The point at which leaving became a consideration.
4. The reported trigger and any underlying conditions.
5. The alternative chosen, including doing nothing.
6. Supporting conversation excerpts and session references.
7. Missing information and competing explanations.
8. A next action the team could test.

Keep direct statements separate from interpretation. If a participant never identified the final decision-maker, record that as unknown. Avoid filling the gap from an account’s job title or an AI summary.

Nielsen Norman Group’s thematic analysis guidance offers background on organizing qualitative evidence. Our interview analysis workflow provides a specific decision record to use with these interviews.

Check the denominator before reporting a pattern

Track how many people were invited, started, and completed the interview. Compare available cohort characteristics with your respondent group. People willing to explain a cancellation may differ from those who ignored the invitation.

If several respondents mention the same obstacle, report the finding within the interviewed group and explain its limits. Do not turn that fraction into the percentage of all churn caused by the obstacle. An interview theme suggests an explanation; operational data or a separate study may be needed to evaluate its reach.

Keep billing failures separate from deliberate departures in the analysis. Also separate an expressed willingness to return from an actual renewed subscription.

Turn the finding into a test

For an illustrative permissions problem, a decision record might read: “Some interviewed administrators described waiting for a colleague during setup. We will test clearer access instructions, and check whether the intended cohort completes setup more often.”

Specify who owns the action, which group it applies to, what you will measure, and what result would challenge the explanation. Other appropriate actions include a human follow-up interview or a usability study. You do not need to turn every theme into a feature.

Run the conversation in Stetos.co

Configure a Stetos.co AI interviewer around the cancellation research goal, with neutral follow-ups and clear completion behavior. Test it, invite the cohort you chose, and review transcripts, summaries, and configured metrics in the project.

Keep the interview distinct from account management and support promises. To experience the participant side first, try the live demo. For earlier-stage learning, use the customer discovery question guide.