Updated · 8 min read
Sunset sequences: how to say goodbye without burning the list
Picture the bottom slice of your email list — the names that haven't opened a thing in six months. Every send to them costs you twice: you pay the per-message fee, and you pay deliverability tax because mailbox providers (Gmail, Outlook, Yahoo) read low engagement as low quality and route the rest of your sends accordingly. The hygiene policy says suppress. Most programs flinch and don't, because the list shrinks on the dashboard and someone notices. The sunset sequence is the compromise that actually works: three messages, escalating clarity, with a clean exit for anyone who doesn't want to be there.
By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
When the list is quietly dragging you down
Dormancy — the period a user has shown zero engagement, no opens, no clicks, no product activity — is the trigger. The right threshold depends on how often your product earns a check-in. Most consumer programs land at 180 days. A daily-use app might trip at 90. Annual-renewal products like tax software, where six months of silence is genuinely normal, push it out to 365 or more.
The list hygiene policy covers picking the right number for your product. Sunset runs after that threshold trips, immediately before permanent suppression — the database flag that stops marketing sends to a given address.
Sunset is not about winning users back. That's the win-back sequence, which runs earlier. Sunset gives users who are already gone a clean way to say so — or a final, specific nudge if they want to stay.
Day zero — ask the question, plainly
Timing: day 0. The day the dormancy threshold trips.
Subject: "Still want to hear from us?" or "Should we keep sending?"
Content: honest acknowledgement that they haven't been engaging. A clear yes/no ask. Two buttons: "Yes, keep me on the list" and "No, unsubscribe me." Optionally a frequency-reduction middle path ("Monthly only") — some users aren't leaving, they're drowning.
The honesty is the whole trick. Don't dress it up as a promotion. Don't lead with a "we miss you" guilt trip. "You haven't opened an email from us in six months. We're going to stop sending unless you tell us otherwise" outperforms every cleverness anyone has tried to layer on top.
Two weeks later — name the deadline
Timing: day 14, only if the user ignored message 1.
Subject: "Last chance to stay on the list" or "One more try".
Content: shorter than message 1, same two-button structure. Explicit date deadline ("We'll stop sending on [date] unless we hear from you"). Specificity makes the consequence concrete — vague deadlines get ignored, dated deadlines get acted on.
,
The goodbye that brings some of them back
Timing: day 21, at the end of the sunset window.
Subject: "This is our last email to you" or "Removing you from the list today".
Content: clear statement that this is the last marketing email they'll receive. One final "actually, keep me" button as a parachute. Link to the preference centre — the page where users pick which categories they want and at what frequency — for users who want to customise rather than leave entirely.
Counterintuitively, this is often the highest-response message in the sequence. Finality flips the frame — users who ignored the first two realise they're about to lose the option, and a small percentage come back. Typical response: 3–5% of message-3 recipients click "keep me." Loss aversion doing what loss aversion does.
What you do once the dust settles
Users who clicked "keep me" go back to the active list with an engagement reset — their dormancy clock starts over. Treat them gently for the next 30 days. Reduced frequency, high-quality sends only. They've given you a second chance; give it a real shot.
Users who didn't respond move to permanent marketing suppression. They stay in the database for transactional use (order confirmations, password resets), for analytics, for potential future re-subscription via an explicit consented moment. They stop receiving marketing. Never re-add them later without a new opt-in — that's the exact behaviour the sunset was designed to prevent.
,
Why a smaller list is the better list
Sunsetting is unpopular with stakeholders because the list shrinks, which reads as loss. It isn't. An engaged list of 50,000 outperforms an unengaged list of 500,000 on revenue, on deliverability, on send cost. All three move the same direction when you remove the dead weight.
The retention economics guide has the math. Short version: users who haven't engaged in six months have roughly a 95% probability of never engaging again. Keeping them means paying to mail phantom addresses while damaging your sender reputation — the score mailbox providers assign your sending domain — with the real ones. Lovely business model.
On the mechanics: no, don't offer a discount to keep unengaged users. Discounts teach the audience that disengagement is rewarded, which is the opposite lesson. The honest ask ("still want to hear from us?") outperforms the bribe ("here's 20% off to stay") on long-term engagement quality. A modest discount in message three as a last-ditch nudge is defensible; leading with one isn't.
And yes, you still need sunset even if you have a win-back program — the earlier sequence aimed at recently lapsed users who might still be persuaded. The two play different roles. Win-back runs earlier (60–90 days) and tries to re-activate still-interested users. Sunset runs later (180+) and gives a clean exit. Win-back is sales pitch; sunset is hygiene. A program with both, in sequence, handles dormancy cleanly. A program with only one of them handles it badly.
The Deliverability Management skilltreats sunset as a standing quarterly run, not a one-time cleanup. Automate the trigger. Run the sequence. Let the suppression happen. Quarterly audit confirms the mechanism is still firing and the retention rate hasn't drifted.
Read to the end
Scroll to the bottom of the guide — we'll tick it on your reading path automatically.
This guide is backed by an Orbit skill
Related guides
Browse allWin-back flows: 12 patterns that earn their place
Win-back is the highest-ROI program most lifecycle teams underbuild. Twelve patterns that work, when each one fits, and the sunset policy that stops the program quietly eating your sender reputation.
List hygiene: the six-rule policy
List hygiene isn't cleanup; it's a continuous policy that runs automatically. Here's the six-rule policy every lifecycle program should have written down, each tied to a specific deliverability outcome.
Trial-to-paid: the seven-email sequence that converts 20%+ of free users
Trial conversion is the most financially leveraged flow in SaaS — every percentage point compounds directly against CAC. Here's the seven-email sequence that reliably moves trial conversion from 5% to 20%+.
Product launch email sequence: the five emails that actually sell a new product
A product launch with one big announcement email captures a fraction of the addressable audience. A proper five-email sequence catches multiple attention windows, builds anticipation, and converts the users who needed a second or third touch. Here's the structure that reliably outperforms the single-send version.
Email deliverability — the practitioner's guide
Deliverability isn't a setting. It's the running total of every send decision you've made since you bought the domain. Four pillars hold it up. Break one and the whole program starts leaking.
The unsubscribe page is the most important page in your lifecycle program
The page every lifecycle team ignores is the one quietly deciding sender reputation, suppression-list quality, and the fate of next quarter's deliverability. A short defence of why it deserves the ten-minute rebuild.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 63 lifecycle methodologies, 91 MCP tools, native Braze integration. Free for everyone.