What to ask a customer who cancelled before offering a discount

Ask what changed or what did not work. A discount only addresses price. It will not repair a missing feature, resolve a support problem, or create a need that no longer exists.

Complete the cancellation through your normal process. Feedback should be optional and should not become another hurdle someone has to clear to leave.

Start with an open question

If the customer has already given a reason, acknowledge it instead of asking them to repeat it. If they have not, a short message can give them room to explain:

Hi Ethan,

If you're willing to share, what made you decide to stop using the booking tool? I'd like to understand what didn't fit.

Maya

This is a fictional example. It is not presented as a tested retention message. Send it only when the contact is appropriate to the relationship and the customer's preferences.

Do not write “your cancellation is confirmed” unless it is. Account status and billing details should come from the relevant record, not from a convenient email template.

Distinguish the problem before choosing an offer

What the customer says	A useful follow-up	What not to assume
“The staff never got used to it.”	“Which part was hardest to fit into the day?”	A lower price will make adoption easier.
“We're closing that location.”	“Thanks for explaining. Is there anything outstanding we need to help you finish?”	They need another product instead.
“It couldn't handle our deposits.”	Check the precise requirement against current capability.	A workaround exists because another customer uses deposits.
“We couldn't get an answer from support.”	Route the unresolved issue to its owner.	A sales call is the right response to a support failure.
“The price no longer makes sense.”	Ask what changed, if they want to discuss it.	Every price concern should receive the same discount.

The goal is to understand their experience, including reasons you cannot change.

Follow one answer far enough to make it useful

Ethan replies: “The staff never got used to it. We went back to the paper diary.” A useful next question might be:

Was there a particular step that slowed them down, or was there no time to learn the new process?

If he says nobody had time to learn it, you can record an onboarding obstacle. You cannot conclude that he would return after a walkthrough. Ask whether he wants to discuss that possibility before offering a call.

If he wants to stay with paper, accept the answer. The feedback remains useful even when it does not lead to another sale.

Keep a feedback report separate from a return offer

The feedback record should contain the original words, a working theme, and any unresolved question. A commercial record can separately track whether the customer asked about returning and which offer was approved.

Use the feedback worksheet to retain quotes alongside interpretations. Count respondents consistently and include the people who did not reply when describing the response set. The inactive-user feedback guide explains that reporting method in more detail.

If you change the product in response to a recurring problem, explain what changed to customers who welcome an update. Do not tell someone their issue is fixed until you have checked their actual requirement.

Know when the conversation is finished

Stop when the customer declines further discussion or asks not to be contacted. Route unresolved account issues to someone who can resolve them. Do not quietly switch a feedback request into an automated sales sequence.

A useful outcome can be a clearer cancellation reason, a support handoff, or a product question to investigate. Customer feedback with OutreachGuy shows how to specify those outcomes in a brief.