Win-back campaign emails: template and examples

What is a win-back campaign?

A quiet customer, not a cold one.

A win-back campaign is an automated email sequence that re-engages a past customer whose orders have stopped, using their purchase history to decide who to target and when. Klaviyo’s own win-back flow guide recommends three emails, timed against the customer’s buying cycle rather than a fixed calendar date.

This is not one blast to your whole list. It runs as a flow, triggered when a customer crosses into a segment you defined, built on data only a past buyer generates.

A welcome series works a stranger toward a first order. A win-back email works someone who already trusts you enough to buy once, then stopped. You know their order, their category, their timing. That history is the asset a welcome email never has.

How is a win-back campaign different from an abandoned cart email?

Different customer, different clock.

An abandoned cart email reaches a shopper who never finished paying, triggered within hours of the checkout they started. A win-back email reaches someone who already paid, triggered weeks or months after their last order. One recovers a broken transaction. The other reopens a relationship.

Mix these two up and the copy gets confused. A cart abandoner needs their cart back and one objection answered. They were seconds from buying. A lapsed customer needs a reason to think about you again, because the product left their mind.

Who counts as a lapsed customer?

This is the real work. Not the copy.

A lapsed customer is anyone who has gone longer than your brand’s normal repurchase cycle without a new order. Three inputs set that threshold: the median days between orders, order count per customer, and product category. A sock brand and a mattress brand will not share a number.

Most win-back guides skip straight to discount copy. That is backward. The hard part is deciding what “lapsed” means for your store, and the answer lives in your own order data, not a template.

Take Ridgeline Socks. If most repeat customers reorder every 45 to 60 days, a customer silent past 90 days is a real signal. Picture a mattress brand using that same 90-day rule. Nobody buys a second mattress at 90 days, so every customer would trip the flow right after their first order, and the segment would mean nothing.

Klaviyo’s date-based segment conditions let you filter “Placed Order is at least X days ago” once you know your own X. Pull it from your repeat buyers’ order history, not a benchmark blog post, and set the threshold a little past that median gap, not far past it.

Running win-back as one blast instead of a flow with a real threshold? The free assessment names the one recurring job worth handing off first. Eight questions, about two minutes. No pitch.

What should a win-back email sequence look like?

Three emails, each a different pitch.

A working win-back sequence is short: a check-in, a reason to look again, and a close. Klaviyo’s exit filter for this flow is “Placed Order zero times since starting this flow,” with a standard re-entry limit of 90 days, so nobody restarts the sequence twice in one quarter.

Klaviyo’s own guide to building a win-back flow recommends three emails, with the first delay set a little past your average buying cycle rather than a fixed date. The same segment logic from the last section decides the timing here.

Email 1, plain check-in. No discount. Name what they bought and ask if it worked out. This email alone recovers people who meant to reorder and forgot.

Email 2, the reason. New arrivals in the category they bought, or the thing that changed since their last order. This is where a real discount earns its place, if you use one at all.

Email 3, the close. State plainly that this is the last email in the sequence. Naming the end is not pressure. It is the only honest deadline you have.

The trigger and filter logic sits with the rest of your flows. Klaviyo flows: which to build, in what order covers the exit filter and re-entry limit that keep win-back from firing twice on the same customer.

What do good win-back email examples look like?

Two, with the reason each works.

The two win-back email examples worth copying: the plain check-in that names the exact product bought, and the reason-to-return email built on new stock or a real change. Neither opens with a discount. Both use the order history a cold email never has.

Example 1. The check-in.

Why it works: it proves you are not guessing. A generic “we miss you” email can never name the actual product.

Example 2. The reason.

Why it works: it filters the catalog for them, instead of asking them to browse a store they have half forgotten.

What should a win-back customer email template include?

Five parts, in order.

A win-back customer email template needs five parts: the exact product last bought, the time since that order, one specific reason to return, one link, and no more than one ask. Skip a part and the email reads as generic, the fastest way to lose the reopened relationship for good.

Fill this in for your own brand:

• Subject. Name the product, not the brand. “Still wearing the [product]?” beats “We miss you.”
• Opening line. State what they bought and roughly when.
• Middle. One reason to look again. New stock, a change, or an honest ask about what went wrong.
• Link. One. A reorder link or a filtered category page, never the homepage.
• Close. No pressure on email one. Save the stated deadline for the last email in the sequence.

How do you know a win-back campaign is working?

Orders back, not opens.

Judge a win-back campaign on orders placed inside a fixed window after flow entry, not on open rate. Apple’s Mail Privacy Protection pre-fetches images, so opens move for reasons unrelated to the reader. A smaller list needs a full quarter of entries before the numbers mean anything.

Two numbers carry the read:

1. Reactivation rate. Of everyone who entered the flow, how many placed one more order before the sequence ended.
2. Which email did it. Click and order data per message shows whether the check-in alone did the work, or the reason email was needed.

Clockwork holds this kind of job with your context attached: your products, your own repurchase cycle, your last correction. Anything a run is unsure about comes back held, with the reason. Nothing goes live without your yes.

FAQ: what else do people ask about win-back campaigns?

Four questions that come up before the first build.

The usual questions are what a win-back campaign is, how many emails to send, whether to lead with a discount, and how it differs from a re-engagement email. Short answers: an automated flow for past buyers, two to three, only after the check-in fails, and win-back is the case built on purchase history.

What is a win-back campaign?

An automated email sequence aimed at a past customer whose orders have stopped, built on their own purchase history rather than a generic list. A win back campaign differs from a welcome series or an abandoned cart flow because it targets someone who already bought, using what and when they bought to time the message.

How many emails should a winback email sequence have?

Two to three is enough for most Shopify brands. Klaviyo’s own win-back flow guide recommends three: a plain check-in, a reason to return, and a close that states the sequence is ending. A longer sequence past that usually repeats the same ask in different words.

Should a win-back email lead with a discount?

No. Lead with the check-in first, no offer attached. A discount in email one trains customers to wait for one every time. Save it for the second email, and only if a real reason to return is not enough on its own for your product.

How is a win-back email different from a re-engagement email?

“Re-engagement” often means an inactive email subscriber who never bought. “Win-back” specifically means a past customer, so the message can reference a real order. If the person has purchase history, write it as win-back. If they only ever joined a list, that is a different, weaker message.

Keep reading: what should you build next?

The rest of the flow system.

Win-back is the last of five core Klaviyo flows to build, and it needs order history to time correctly. The trigger and filter logic sit on the Klaviyo flows page, the flow it is often confused with sits on the abandoned cart page, and the full system sits on the hub.

• Klaviyo flows: which to build, in what order for the trigger and filter logic behind all five.
• Abandoned cart email examples and template for Shopify for the flow win-back is not.
• Ecommerce email marketing: build the flows first for where win-back sits in the whole system.