Customers who cancelled and returned
Win Back Customer Comeback Story Requests
A customer who left and came back has seen your weak spot and chosen you anyway. That is a story no first time buyer can tell. It is also a delicate ask: you are inviting them to say in public that they once walked away. The templates below time the ask to when the return has proved itself, and let the customer decide how much of the leaving to mention.
- Emails for the first weeks back and for later
- Questions about leaving, returning and staying
- Wording that lets them skip the awkward part
Request builder
Write the ask for a customer who came back
Pick how long they have been back. Each template names the return plainly and makes mentioning the cancellation optional.
- Welcome back, and a promise to ask later
Too early for a testimonial. This plants the question without asking it.
Subject: Good to have you back, [Dana]
Hi [Dana], You were away for [about six months], and we are glad you came back to [Ledgerly]. We would love to hear, in a couple of months, whether [the new reporting screens] made the difference you hoped for. No need to reply now. We will check in once you have had time to see for yourself. If anything is not right in the meantime, reply to this email and it comes straight to me. [Marcus]
Templates fill in inside your browser. Nothing you enter is stored or sent.
The problem, solved
Why comeback stories go uncollected, and how StoryProof helps
- Problem 1
We do not know who came back
Reactivations look like ordinary sign ups, so the people with the best story are mixed in with everyone else.
How StoryProof solves it
Add returning customers to a contact list when they reactivate, so the request goes to them alone. Contacts and smart lists are on every plan, so requests can go to people you have added.
- Problem 2
Asking in week one feels presumptuous
They have not yet seen whether the fix holds. An early ask gets a polite nothing, or a story that later turns out wrong.
How StoryProof solves it
Send the welcome note now and the real request a few months on, by email. StoryProof sends review requests by email, not SMS.
- Problem 3
They do not want to relive leaving
Writing down why they cancelled feels like a complaint, and some customers would rather not have it public.
How StoryProof solves it
The collection link lets them answer in whatever form feels easiest: a video, an audio note or a few written lines. The template makes the leaving optional.
- Problem 4
The story names what used to be broken
A frank comeback testimonial may describe the old problem in detail, and you want to read it before it goes on a page.
How StoryProof solves it
Every submission stays private until you approve it, so you can read the frank version first and choose where it fits.
- Problem 5
One email gets lost in the inbox
Returning customers are busy catching up on a product they once dropped, and the first request slides past.
How StoryProof solves it
From Pro, follow ups send a reminder three days after the request and a last email four days later, stopping as soon as they reply.
Prompts
Questions that draw out a comeback story
Pick two or three. The point is the change, so ask about before and after, not about the competitor.
About leaving (optional)
- What were you hoping for that you did not get the first time?
- What would have kept you then?
Leave out
- Why did you cancel? (feels like an exit survey)
- Asking them to criticise whoever they used in between
About returning
- What made you look at us again?
- What did you check before deciding to come back?
About staying
- What is different now, in your day to day?
- What would you tell someone who left for the same reason you did?
Leave out
- Promising the old problem will never come back
In StoryProof
Run comeback requests
Step 1 of 4
List returning customers
Add each reactivated customer as a contact and tag them as returned, with the month they came back.
Step 2 of 4
Send the welcome note now
Use the first template by hand from your own email. It asks for nothing yet.
Step 3 of 4
Request the story after a few months
Send the comeback request with the collection link to the tagged contacts, with follow ups if your plan has automations.
Step 4 of 4
Approve and thank
Read each story before approving it. From Pro, two hours after a testimonial is approved the customer can get a thank-you email with a link to it.
Before you start
What to know before you send
StoryProof does not detect returns
It does not read billing or know when someone reactivates. You add returning customers yourself.
Email only
Requests go out by email. If the customer came back through a phone call, still follow up by email.
No “customer since” field
This page relies on no field that records a first start date and a return date. Use a tag, or let the customer say it in their own words.
Not every return is a story
Some customers come back only on price. A testimonial that says “it got cheaper” helps nobody; skip those and ask the ones who returned for a change.
FAQ
Questions people ask
Short answers to what usually comes up next.
When should I ask a returning customer for a testimonial?
Once the return has held, often a few months in. Ask too early and they have nothing new to say, or they say it before finding out whether the fix lasts.
Should the testimonial mention that they left?
Only if they want it to. A story that admits the first try did not work is very persuasive, but it is the customer’s call. The templates make it optional.
Is this different from asking repeat customers?
Yes. A repeat customer never stopped. A returning customer cancelled, used something else or nothing, and then chose you again, so their story is about what changed.
Can I ask them to compare us with the provider they tried?
You can let them, but do not push. Asking customers to criticise a competitor makes the testimonial read as a set up. Ask about their own experience instead.
Still have a question? Ask the StoryProof team or book a demo.
Turn a return into proof
Send the comeback request, collect video, audio or text, and approve every story before it is shown.
Last updated 2026-11-12.