Dormant Customer Reactivation: Is a 5-Email Sequence Right?

The request comes back every month in the briefs we receive: "we want a 5-email reactivation sequence". The number 5 circulates a lot in templates and LinkedIn threads, much less in vendor documentation. Klaviyo, for its part, states the opposite in black and white.

This guide sets out the real framework: what the vendor recommends, what Gmail and Yahoo tolerate on a cold list, what the CNIL allows depending on whether the dormant contact is a customer or a mere prospect, and how to structure a sequence that cleans the list instead of burning it.

What Klaviyo actually recommends: three emails, not five

Two different flows are involved when we talk about "reactivation", and both are capped by the vendor.

The sunset flow, aimed at unengaged contacts (they no longer read, whether they bought or not). Klaviyo's documentation is explicit: "It is best to limit this flow to be no more than three emails because you don't want to repeatedly contact people who are unengaged" (sunset flow documentation).

The winback flow, triggered by the absence of a repeat purchase from an existing customer. Same cap: "We recommend keeping your winback flow to three emails per recipient" (winback flow documentation).

A 5-email sequence therefore goes beyond the vendor's recommendation. That does not make it illegitimate in itself, but it puts you in a position where you have to justify each additional send to an audience that, by definition, no longer reacts. On a cold list, every extra email is a lottery ticket on the complaint rate.

In practice, when a client asks us for 5 emails, we first look at what goes into them. Often, emails 4 and 5 are promotional reminders dressed up as reactivation, sent to profiles that did not open the first three. The marginal gain is small, the deliverability risk is not.

The compromise we apply at the agency

If you insist on something longer than three emails, the clean way to do it is to split into two separate flows rather than stacking five sends in a single one:

1. A winback of three emails maximum on dormant customers (they have bought, they still open sometimes).
2. A sunset of three emails maximum on genuinely unengaged profiles, with suppression on exit.

The two populations have neither the same legal status, nor the same deliverability risk profile, nor the same message. Mixing them in a single 5-email sequence is the first cause of damage we see in audits. Each flow is covered in detail in our dedicated guides: Klaviyo winback flow and Klaviyo sunset flow.

Define "dormant" before writing the first email

The word dormant means nothing until you have translated it into segment conditions. Two definitions coexist, and they do not target the same people.

Dormant on the engagement side

Klaviyo sets a simple marker: "Emails that have not engaged for over a year are generally considered unengaged" (Klaviyo reactivation guide).

For the sunset segment, the documentation details precise conditions:

Source: Klaviyo sunset flow documentation.

The logic of this segment deserves a pause: you do not exclude someone because they did not open last month, you exclude them because they received enough volume over a long window without ever reacting. That is what separates a sunset segment from a badly calibrated inactive segment.

Watch out for open metrics since Apple Mail Privacy Protection: opens are noisy, and a segment based 100% on opens can make you suppress active people. We detail the trade-off in Apple Mail Privacy Protection: which email metrics to track.

Dormant on the purchase side

This is winback territory. The official trigger documented by Klaviyo is the Placed Order event, with a flow filter that excludes those who reordered in the meantime: "Placed Order zero times since starting this flow" (winback flow documentation).

The delay before triggering is set on your average purchase cycle. If you have not calculated it, your reactivation sequence starts from an assumption and not from data. The calculation method is in RFM: segmenting by recency, frequency and monetary value.

A point of transparency: the intervals between each email of the sequence are documented nowhere by the vendor. Klaviyo documents the initial delay for entering the flow, not the intermediate delays. Any numeric cadence you read elsewhere (day 0, day 3, day 7) is an agency convention, ours included. Test it, do not treat it as a rule.

The deliverability guardrails, the part nobody reads

A reactivation sequence sends volume to people who no longer read you. It is mechanically the riskiest operation on the CRM calendar.

The complaint ceiling

Gmail gives numbers: "Keep spam rates reported in Postmaster Tools below 0.10% ... avoid ever reaching a spam rate of 0.30% or higher" (Google, sender guidelines).

Yahoo sets the same order of magnitude: "Keep your spam rate below 0.3%" (Yahoo Sender best practices).

These thresholds are your real stop indicator. If the reactivation campaign pushes the complaint rate toward 0.10%, you cut before reaching 0.30%, you do not finish the sequence "to see". Postmaster Tools is monitored daily throughout the operation, not at the end of the month.

Mandatory batching

Klaviyo states it without ambiguity: "you should not contact them all at the same time ... break them down into multiple smaller lists, and include sends to engaged profiles in between" (Klaviyo reactivation guide).

Two instructions in that sentence, and the second is the one we see forgotten most often: it is not enough to split into batches, you must interleave sends to your engaged profiles between the batches. That way you maintain a positive signal with the providers while you push content to a cold audience.

The Gmail bulk sender threshold

If your list is large, you are probably concerned: "A bulk sender is any email sender that sends close to 5,000 messages or more to personal Gmail accounts within a 24-hour period. ... Messages sent from the same primary domain count toward the 5,000 limit" (Google, sender requirements).

The technical point to remember: the count is aggregated at primary domain level, subdomains included. You do not leave bulk sender status by moving your reactivation campaign to a dedicated subdomain, nor by separating it from your transactional sends if the root domain is the same. Subdomain separation remains useful for other reasons (reputation isolation), not for this counter.

The full Gmail and Yahoo framework is detailed in Gmail and Yahoo sender requirements in 2026.

Unsubscribing

Gmail asks senders to "Process and honor unsubscribe requests within 48 hours" and to implement one-click unsubscribe "in a way that no additional user action is needed to unsubscribe" (Gmail requirements). Yahoo sets the same requirement in different wording: "Honor unsubscribes within 2 days" (Yahoo).

On a reactivation sequence, this point is structural. You are sending to people who have forgotten who you are. A fast, frictionless unsubscribe is your best release valve: every unsubscribe is a neutral signal, every spam complaint is a negative one. Making the unsubscribe visible in the body of the email, not only in the footer, brings complaints down.

One last point of method: Yahoo explicitly recommends "sending a reconfirmation email to inactive subscribers periodically" (Yahoo). The very principle of the reactivation sequence is therefore endorsed by a provider. It is the volume and the cadence that cause problems, not the intent.

The CNIL framework: two populations, two regimes

For companies operating in France, this is the worst-handled point in reactivation sequences, because the answer depends on the contact's status.

The dormant contact who is already a customer. The CNIL, the French data protection authority, specifies that consent is not required when the person is already a customer and the prospecting concerns products or services similar to those already purchased, supplied by the same company, provided they were informed of this use and given an easy way to object at the time of collection and with each communication (CNIL, electronic communication rules, in French).

Your winback on a dormant customer therefore holds, subject to two cumulative conditions: similar products, and easy objection with every send.

The dormant contact who has never bought. Here the regime changes: the CNIL states that sending commercial prospecting by electronic means to individuals rests, in principle, on obtaining prior consent (CNIL).

A prospect who subscribed to the newsletter and then went silent for two years is still covered by their initial consent, as long as that consent is traceable. A contact imported without proof of opt-in is not, and no reactivation sequence fixes that. On the retention periods applicable to non-customer prospects, the CNIL refers to its dedicated page on commercial prospecting: check the period in force there rather than copying a figure found in a blog post.

The full compliance checklist is in GDPR email marketing 2026.

Exiting the sequence: suppressing, and understanding what it implies

A reactivation sequence without an exit is not a reactivation sequence, it is just one more campaign.

At the end of the sunset, profiles that neither opened nor clicked are suppressed. Two documented consequences, to know before clicking.

Effect on the invoice. Klaviyo states that "suppressed profiles do not contribute towards your billing plan's profile count" (suppression documentation). Suppressing your dormant contacts therefore takes those profiles out of the billed base. How the tiers work is detailed in Klaviyo pricing.

Irreversible effect on the marketing side. This is the point few teams anticipate: "Once a profile is suppressed, even if that contact starts a checkout on your website or makes a purchase, they will remain suppressed and ineligible to receive any marketing emails" (Klaviyo).

A suppressed contact who buys again six months later on your site does not automatically rejoin your marketing flows. They buy, and they receive nothing: no post-purchase, no cross-sell, no winback. That changes the conversation with a client hesitating to "purge" their list: suppression is not archiving, it is a commercial decision.

Our position at the agency: we suppress profiles that never engaged, we are far more cautious with buyers, and we document the suppressed list before the operation. The full cleaning mechanics are in Klaviyo list hygiene.

Checklist before launching

• [ ] Dormant segment built on explicit conditions (profile age, received volume, absence of opens and clicks), not on an approximate "has not opened in 6 months"
• [ ] Populations separated: dormant customers on one side, unengaged prospects on the other
• [ ] Sending base authenticated and clean on the DNS side before the first cold campaign (SPF, DKIM and DMARC)
• [ ] Split into batches, with sends to engaged profiles interleaved between batches
• [ ] Postmaster Tools opened daily, stop threshold set in advance under 0.10%
• [ ] One-click unsubscribe working and unsubscribes processed within 48 hours
• [ ] Consent status checked for the prospect population
• [ ] Suppression decision documented and validated internally before execution
• [ ] Exit flow configured: what happens to those who reopen, those who click, those who do nothing

If you want the operation framed with support, it is exactly the kind of project our Klaviyo agency takes on.

What nobody will tell you about expected performance

A reactivation sequence is judged on three things: the volume of profiles brought back to engagement, the volume of profiles cleanly removed from the list, and the absence of degradation in sending reputation. The last two count as much as the first.

On expected recovery rates, no vendor publishes a reference benchmark for this type of flow. The figures that circulate come from private panels, with definitions of "reactivated" that vary from one report to the next. Take your own baseline before the operation, measure the delta, and stop comparing your sequence to averages whose scope and method you do not know. The measurement framework on the KPI side is set out in CRM KPIs: the 12 lifecycle metrics to track.

FAQ

Is a 5-email reactivation sequence forbidden?

No, but it exceeds what Klaviyo recommends. The vendor explicitly caps the sunset flow and the winback flow at three emails each. If you want more touchpoints, separate the two flows rather than lengthening a single sequence to an unengaged audience.

How long between each email of the sequence?

There is no recommended delay published by the vendor for the intermediate sends. Klaviyo documents the delay for entering the flow (set on the average purchase cycle, with a 180-day marker for the dormant segment), not the following intervals. Set a cadence, measure, adjust.

Can I re-contact a former customer without new consent in France?

Yes, if the prospecting concerns products or services similar to those already purchased from you, and if the person was informed and can easily object to each communication. For a prospect who has never bought, prior consent remains the rule. Reference: CNIL, electronic communication rules.

What happens if I suppress a dormant contact who buys again later?

They stay suppressed. Klaviyo specifies that a suppressed profile remains ineligible for marketing emails even if they start a checkout or place an order. Anticipate this case before launching a mass purge, especially on buyers.

How do I know if my reactivation campaign is damaging my deliverability?

Watch the complaint rate in Postmaster Tools every day of the operation. Gmail asks you to stay under 0.10% and never reach 0.30%, Yahoo sets a ceiling at 0.3%. If the curve climbs, you stop the sequence, you do not finish it.

Want the operation framed before your next cold send? Talk to the Deliver team.