Churn Research: Methods, Exit Interviews & Examples

Churn research investigates why customers end a defined relationship and what the business should change. Combine product and billing records with exit interviews, including contrasting customers who stayed. Define the departure and account first, then investigate the sequence behind a reason before choosing a product repair, service change or new offer.

Sessionlane is hypothetical. Tutors publish availability and students request appointments. The team must distinguish first-booking problems, later service failures and changed needs. A cancellation answer such as “too expensive” cannot choose the remedy alone. This walkthrough reports no collected churn findings.

Example: churn in a tutor-booking service

For Sessionlane's investigation, count a paying tutor account as churned when its subscription actually ends. Record the date the tutor asked to cancel as a separate field. An account that will remain paid until the end of its term has made a decision, but it has not yet left under this definition.

Separate an explicit cancellation from a failed renewal payment, a pause, a duplicate account and a trial that never became paid. Those records can all matter, but they do not describe the same event. A payment failure needs investigation before being labeled a decision to reject the product.

Use the account as the unit, not each staff or contact record. Fix the period and starting group. New accounts have had less time to leave. Compare equal follow-up instead of mistaking shorter history for better retention.

Then divide the investigation by meaningful prior experience. Examine tutors who left before receiving a first appointment request, tutors who used the service regularly and then stopped, and tutors whose usage continued until cancellation. These are starting contrasts, not explanations. Low recorded use cannot by itself tell you whether the tutor lacked students, met a technical problem or moved bookings elsewhere.

An exit reason needs a dated episode

Build a dated sequence from product, billing and support records: availability, requests, failures, support and cancellation. Check tracking changes and missing events. A request does not prove a lesson occurred.

An exit interview adds the customer's account of that sequence. Start with the last period when the service was useful, then follow what happened before the decision to leave. Ask what they tried, who else was involved, which alternatives they considered and what they now do instead.

For example, ask a tutor to describe the last appointment they arranged through Sessionlane and the first one they arranged another way. With permission, calendar entries or messages can help pin down the order of events, though they won't confirm everything the tutor remembers.

Use open questions and follow the episode before proposing a rescue. “What happened after that request?” leaves room for a problem the team has not imagined. “Would a cheaper plan have kept you?” introduces a proposed solution before explaining the original decision. GOV.UK's interview guidance recommends neutral questions, follow-ups and concrete stories rather than general accounts of how things should work.

Responsive former customers are only part of the audience

Invite people across the relevant usage and departure groups. Do not rely only on cancellation-survey respondents, recent support callers or people the account team still knows well. Each route makes some experiences easier to hear than others.

Include customers who faced a similar problem and stayed. A workaround or different consequence may explain the contrast. This challenges an easy explanation without turning selected interviews into a causal experiment.

Record who was invited, reachable, eligible, interviewed or unavailable. Where appropriate, compare known tenure and usage characteristics of participants with the invited groups. If heavily disengaged tutors rarely reply, say which experience remains thin. Silence is not an answer to the reason question.

AAPOR's Standard Definitions distinguishes coverage and nonresponse error and cautions that a response rate alone cannot determine whether nonresponse error exists. More interviews from the same responsive group do not necessarily address the missing experience.

Report interview themes against the people who supplied them. “Mentioned in these interviews” is different from “caused this share of all churn.” Measuring the prevalence of reasons requires a suitable population, question and response design, with its missing coverage preserved.

Similar exit reasons can have different explanations

Suppose the team is investigating a tutor who reports that Sessionlane became too expensive after appointment requests stopped. There are several plausible sequences. A product failure may have prevented students from requesting lessons. The tutor may have reduced teaching hours, leaving less work for the service. They may have moved regular students to direct messages and no longer needed online booking.

Look for the evidence that distinguishes them. A reproducible failure and affected request records support a product investigation. A changed schedule can explain why the previous offer no longer fits. A switch to messages invites questions about which part of booking remains useful and what the alternative handles better.

Price can still matter. Ask what the tutor paid for, what value they expected and what they compared with the subscription. Avoid forcing every explanation into a single primary reason when several conditions interacted. Keep the original account and any uncertainty about their order.

Our customer needs analysis guide helps separate the desired outcome from a requested solution. “Give me a discount” may be one proposed response. Dependable access to suitable appointments is the outcome the business still has to serve.

The evidence determines the repair to evaluate

If tutors cannot complete a first booking task, reproduce the problem and test the repaired experience with relevant users. If established users no longer receive the service they expected, investigate delivery before changing the cancellation message. If the need has ended, a retention prompt may be the wrong intervention.

Name who owns the change and an outcome beyond stopping a cancellation. For a booking repair, can target tutors receive and manage requests? For a new offer, do the intended customers choose it and continue using it through a suitable period?

A discount accepted at the cancellation screen does not show that the original problem was solved. Keep later service use, repeat cancellation, support problems and payment outcomes visible. Before a live comparison, specify the eligible group, allocation, primary outcome and consequences to monitor. Microsoft's experimentation guidance explains why these choices belong in the design before results are read. A before-and-after change alone may also reflect seasonality or a different mix of tutors.

A revised booking offer can be compared with Sapien

Sapien can compare simulated reactions to feasible alternatives and explore the reasons behind differences across audience groups. Our team builds the simulated population and runs the agreed research; customer data and past research can add context. Our market research services guide explains the engagement and the offer comparison that can follow an investigation.

For Sessionlane, that could mean exploring how different tutor situations interpret a revised service or commitment. It won't tell you why a particular tutor left, stand in for people who never answered, or prove that a repair reduces churn. Generated explanations must remain hypotheses alongside real customer accounts and event evidence.

Choose the response source according to the remaining question, as we explain in our synthetic versus human respondents guide. Actual exit interviews concern what happened. A simulated comparison explores how a defined audience might respond. A real service evaluation tests whether the change helps.

Book a demo to compare the revised tutor offer once the investigation identifies a feasible change. Bring the tutor situations, service commitments and alternatives to test; keep the explanation of actual departures tied to their accounts and records.