Win back the customers you already earned, before you pay to replace them.
Every store quietly loses customers who simply stopped coming back. A win-back flow reaches them at the moment their next order is overdue and gives them a reason to return, which is almost always cheaper than acquiring someone new to take their place. Here is a sequence that works, and how to size what those customers are worth.
A second chance at a customer you already won
A win-back flow targets customers who bought before but have gone quiet: their usual reorder is overdue and they are drifting toward lapsed. It reminds them why they chose you, shows what is new, and gives them a reason to come back before that relationship ends. The economics are the whole point. You already paid to acquire these people once, so bringing even a fraction of them back costs far less than finding new customers to replace the ones you are losing without noticing.
The setting most win-back flows get wrong
The whole flow hinges on one decision: when is a customer actually lapsing? Set the window too short and you nag people who were going to reorder anyway; too long and you reach them after they have already moved on. A fixed number of days since last order works if your customers buy on a predictable cycle. If they do not, Klaviyo's expected date of next order lets the trigger adapt per customer, so a monthly reorder and a once-a-year purchase are each caught at the right moment instead of forcing everyone through one blanket window. Getting this timing right matters more than any single line of copy in the emails.
A win-back flow that works
Three to four emails, escalating from a soft reminder to an incentive to a last call. Adapt the timing to your reorder cycle.
We miss you, no discount
At the lapse point (their reorder is overdue)
A warm reminder that leads with value, not a coupon. Reintroduce a best-seller or the product they bought, one line on what makes it worth coming back for, and a single button to shop. You are re-opening the relationship, not firing a markdown.
Give them a reason to return
About 4 to 7 days later
Add news and proof: what is new since they last ordered, a top-rated pick, a short review or two. For consumables, a you-may-be-running-low nudge fits here. Still holding the incentive back.
The win-back offer
About a week later, if still quiet
Now bring the incentive. A modest, time-bound offer (a percentage, free shipping, or a bundle, whichever protects your margin) with a clear reason it exists (we would love to have you back). One offer, one deadline, one button.
Last call, then let go
1 to 2 days before the offer expires
A short final reminder that the offer is ending. If they still do not re-engage, let them exit cleanly and fall through to your sunset flow, so a permanently lapsed contact is not mailed forever.
The rules that keep it working
A win-back flow touches your existing customers, so the guardrails protect both revenue and the relationship.
Set the lapse window to your buying cycle
A coffee brand and a mattress brand have very different reorder rhythms. Base the trigger on your median time between orders, or use Klaviyo's expected date of next order so each customer is caught when their own reorder is genuinely overdue.
Exclude anyone already active
Filter out customers who ordered recently or who are moving through another flow, so win-back never talks over a post-purchase series or nudges someone who just bought.
Hold the discount, then protect the margin
Leading with a coupon trains good customers to lapse on purpose. Delay any incentive to later in the series, and when you do offer one, prefer free shipping or a bundle over a deep percentage if your margins are tight.
Segment high-value customers for a softer touch
Your best past customers often need a personal, no-discount nudge more than a markdown. Consider a separate, gentler path for high lifetime-value buyers so you are not discounting the people most likely to return anyway.
Bridge to sunset, do not mail forever
If a customer never re-engages, hand them to your sunset flow rather than keeping them in rotation. Repeatedly mailing the permanently gone erodes the sending reputation that gets your other emails delivered.
How to size the revenue before you build it
The economics are different from a peak-intent flow: a win-back tends to earn less per recipient than your welcome series or abandoned cart, because it is reaching people whose intent has gone cold. That is exactly why you lead with value and hold the discount, and why its payoff comes from re-earning a segment your other flows are not built to catch, rather than from a high value on each individual send. What it is worth overall depends on how many customers lapse each month and how much a returning customer is worth to you over time. A store with a large base of one-time and lapsing buyers has real recoverable revenue sitting idle; a young store with few repeat customers may get more from its welcome and post-purchase flows first. That is a revenue question specific to your account, not a generic benchmark. Once it is live, the signals that tell you it is working are its revenue per recipient and the share of lapsed customers who place another order, watched against the unsubscribe rate as a ceiling. A free Klaviyo audit reads your repeat-purchase and lapse patterns and estimates what a win-back flow is worth on your store, ranked against every other email you are not sending yet, so you build the one that pays first.
Is it safe to connect Klaviyo?
- Read-only. It can read your campaign and flow performance. It cannot send, edit, or delete anything in your account.
- No customer data stored. It works from your metrics, not your subscriber list. Names, emails, and phone numbers are never stored.
- Nothing ships without you. Built emails land as drafts for your review; nothing is pushed to Klaviyo on its own.
- Built by an operator. David Refaeli-Berman ran enterprise email at Chewy, Amazon, Overstock, and Bed Bath & Beyond.
Questions
What is a win-back flow in Klaviyo?
It is an automated email series aimed at customers who have gone quiet: people who bought before but have not ordered again within their usual cycle. It reminds them why they liked you, and gives them a reason to come back before they lapse for good. Re-engaging an existing customer is almost always cheaper than acquiring a new one.
When should a win-back flow trigger?
When a customer crosses their lapse point: the gap after which a repeat purchase is overdue. A simple version uses a fixed number of days since last order tuned to your buying cycle. A smarter version uses Klaviyo's expected date of next order, so a monthly-reorder customer and a once-a-year buyer are each caught at the right time instead of one blanket window for everyone.
How many emails should a win-back flow have?
Usually three to four. A gentle we-miss-you reminder, a second email that adds a reason to return (what is new, a best-seller, social proof), then an incentive if they still have not come back, and often a final last-call. Keep it tight; someone drifting away does not need a long series.
Should a win-back email include a discount?
Not in the first email, and not always at all. Lead by reminding them of the value and what is new. Hold any incentive for later in the sequence, once a softer nudge has not worked, so you are not training loyal customers to wait for a coupon. If your margins are thin, a free-shipping or bundle offer can work better than a percentage off.
What is the difference between a win-back flow and a sunset flow?
A win-back flow targets lapsed customers by purchase behavior and tries to earn another order. A sunset flow targets chronically unengaged email subscribers by open and click behavior and, if they stay silent, suppresses them to protect deliverability. Win-back is about revenue; sunset is about list hygiene. Many stores run a win-back first and let the still-silent contacts fall through to a sunset.
Find out what winning back lapsed customers is worth on your store.
A free audit sizes the revenue a win-back flow would recover for your account, then ranks it against the other flows you're missing.
Size my win-back flow free