- Blog
- Retention
SaaS win-back email templates for every cancel reason
Five copy-paste win-back emails for cancelled SaaS customers, one per cancel reason, plus when to send them and when to stop.
The short version
A win-back sequence for a SaaS product is three or four emails over a few months, sent after the cancellation and timed to when the customer’s reason might have changed. Write each one to the reason they gave when they left, give them one easy way back, and stop as soon as they return, unsubscribe or reach the last email.
A customer who cancelled made a choice, so a win-back email can’t argue with it. What it can do is show up when that choice no longer fits: the budget came back, the feature they missed shipped, the busy season ended. The reason they gave on the way out tells you which of those to wait for.
Below are five templates, one for each common cancel reason, plus a short note on timing. Words in curly braces are placeholders for your own merge fields.
When to send win-back emails#
- Right after cancelling: confirm the cancellation, say when access ends and that their data is kept for a while. No offer yet. This email earns the right to send the next one.
- Two to four weeks later: the first real win-back email, written to their reason.
- Two to three months later: one more, ideally with something new to say, like a shipped feature or a new plan.
- Before their data is deleted, if you delete it: a factual reminder, so nobody loses work by surprise.
That’s the whole sequence. If none of those worked, more emails won’t either.
Start with the reason they gave#
If your cancel flow asks one question about why they’re leaving, you already know which template to send. If it doesn’t, the plain sequence still works, but it will read more generic. The reasons below match the ones in our cancellation flow examples.
Five win-back templates by cancel reason#
“Too expensive”
- When: about a month after cancelling, when a new budget period may have started.
- Subject: A smaller way back into {product}
“Hi {first name}, when you cancelled {product} you said the price didn’t fit. If things have changed, our {cheaper plan} covers {the core thing they used} for less, and your old setup is still here. You can pick it up here: {resubscribe link}. If now still isn’t the time, no reply needed. {your name}”
Why it works: it answers the objection with a real option instead of a generic discount, and it reminds them that coming back doesn’t mean starting over.
“Not using it enough”
- When: two to three months later, around the time their busy or quiet season usually turns.
- Subject: Your {product} account is right where you left it
“Hi {first name}, you left {product} because you weren’t using it much, which is a fair reason. If your {project, season, team} is picking up again, everything you set up is still here: {resubscribe link}. Next time, you can also pause instead of cancelling. {your name}”
Why it works: these customers didn’t dislike the product, the timing was off. Mentioning a pause also makes the next quiet month less likely to end in a cancellation.
“Missing a feature”
- When: only once the feature they asked for has shipped. Don’t send this one on a timer.
- Subject: {feature} is live in {product}
“Hi {first name}, when you cancelled you told us {product} was missing {feature}. It shipped this week, and here’s how it works: {short link to the announcement}. If it fixes what you needed, you can restart here: {resubscribe link}. Thanks for telling us, it helped. {your name}”
Why it works: it proves you listened. It’s the win-back email with the best reason to exist, so keep a list of who asked for what.
“Switched to another tool”
- When: around two months later, after the new tool has had time to show its gaps.
- Subject: How’s the new setup going?
“Hi {first name}, you moved from {product} a couple of months ago, and I hope the switch went smoothly. If anything is harder than it was, I’d like to hear it, even if you stay where you are. And if you want to come back, your account and data are still here: {resubscribe link}. {your name}”
Why it works: it asks a real question and doesn’t criticize the other tool. Replies here are useful product feedback even when nobody comes back.
“It didn’t work for us”
- When: after you’ve fixed what broke, or within a couple of weeks if a person can help.
- Subject: We fixed {the problem you hit}
“Hi {first name}, you cancelled after {the problem} got in the way, and I’m sorry it did. We’ve since {what changed}. If you’d like to give it another go, reply and I’ll help you set it up, or restart here: {resubscribe link}. {your name}”
Why it works: an apology and a concrete fix rebuild trust faster than an offer. Offering a person’s help matters most for this group.
When to let go#
- They unsubscribe or ask you to stop: stop everything, not just this sequence.
- They reached the last email: three or four is enough. After that you’re sending newsletters to someone who didn’t sign up for one.
- They said they closed the business or the project ended: send the confirmation and the data reminder, and skip the rest.
A short, respectful sequence also protects the next conversation. Someone who left on good terms is far more likely to come back on their own than someone you chased for six months.
ExitLoop’s win-back sequence starts when a Stripe subscription is cancelled and stops when the customer subscribes again, and you can edit each email’s wording and wait time. See how email sequences work or what’s included.
Common questions
When should I send a win-back email after a customer cancels?
Send a confirmation right away, the first win-back email two to four weeks later, and one more two to three months after cancelling, timed to when their reason might have changed.
How many win-back emails should a SaaS send?
Three or four, including the cancellation confirmation. If they haven’t come back by then, more emails rarely help.
Should a win-back email include a discount?
Only for customers who left over price, and even then a cheaper plan often works better than a coupon. For other reasons, a fix or a new feature is the stronger message.