Dormant List Revival

    12 Re-engagement Email Examples That Didn't Hurt Deliverability (and What Made Them Safe)

    By Artem KukharenkoPublished Updated 13 min read

    Updated 17 October 2026.

    Twelve envelope cards represent twelve re-engagement email examples
    Original editorial illustration of the article’s process; no third-party interface is depicted.

    What makes a re-engagement email safe for your domain

    Run every draft against this list before it goes near a dormant segment.

    Scroll for more → On small screens, choose cards for wide tables.

    Check Why it matters
    1. Sent from your usual From name and domain A new "friendly" sender to dodge filters is exactly what filters are tuned to catch, and a new domain starts with no reputation.
    2. Subject line says what the email is Gmail, Yahoo and CAN-SPAM all treat deceptive subjects as a violation; curiosity-gap subjects on a cold list produce complaints.
    3. First lines explain why they're receiving it "You signed up for X on [date/context]" reminds a reader who forgot, which is most of them.
    4. Visible unsubscribe link in the body Required by Google and Yahoo for bulk senders; the cheapest signal you can receive.
    5. One-click unsubscribe headers (List-Unsubscribe, List-Unsubscribe-Post) Required by Google for bulk marketing mail; Yahoo requires a functioning header and recommends the POST method.
    6. Light on images and links Image-heavy templates with many tracking links to a cold list raise filtering risk for no gain.
    7. A single, honest ask Stay, leave, or choose frequency. Not "stay and also buy."
    8. Physical address and real reply-to CAN-SPAM requires the address; Microsoft recommends a From or Reply-To that can receive replies.

    The four types and when to use each

    Scroll for more → On small screens, choose cards for wide tables.

    Type Send to Goal Risk if misapplied
    Re-permission Consent on file, no relationship evidence (no click or purchase) for 12+ months Documented renewed consent; remove likely complainers Low; the "wrong" outcome is an unsubscribe
    Value reminder Past clickers or customers, 6–36 months quiet Bring back readers who drifted Medium if sent as a blast; low in daily cohorts
    Preference update Readers who engage occasionally; readers who unsubscribe due to frequency Keep them at a cadence they want Low
    Win-back offer Past customers only, with purchase history Reactivate a buyer High when sent to non-customers; trains discount-waiting

    12 examples, annotated

    Each example is original copy you can adapt. Replace the bracketed fields; keep the structure.

    Example 1. The plain re-permission (newsletter)

    Type: re-permission. Safe because: names the sign-up context, one ask, visible unsubscribe, no images. Copy this: the "no action needed, we'll stop" line, which turns silence into a clean exit. Avoid: adding a "here's what you missed" list; it muddies the ask.

    Example 2. The re-permission with a date and a reason (B2B)

    Safe because: the reason is true and the deadline is real. Copy this: "we'll remove your address" as a benefit, not a threat. Avoid: fake urgency or a countdown timer.

    Type: value reminder. Safe because: one link to content, one to leave, one to reduce. Copy this: "readers shared most" as proof instead of self-praise. Avoid: three columns of back-issues.

    Example 4. The value reminder from a person (SaaS)

    Safe because: specific, short, honest about the gap, from a named person at the real domain. Copy this: "we haven't seen you since" as a plain statement. Avoid: "we miss you" to someone who used the product twice.

    Example 5. The preference email (any sender)

    Type: preference update. Safe because: every button is a win for deliverability, including the last one. Copy this: the "only the big stuff" option, which keeps many people who would otherwise leave. Avoid: requiring a login to change preferences; Yahoo specifically asks that unsubscribing not require one.

    Example 6. The "we changed" email (newsletter or brand)

    Safe because: honest, specific, and it doesn't ask for a click to stay (the default is stay). Note: use this only for tiers B and C (past engagement); for tier D use Example 1, where the default is leave.

    Example 7. The win-back for a past customer, no discount (e-commerce)

    Type: win-back, customer only. Safe because: a real reason tied to purchase history, one product, no urgency. Copy this: the purchase-cycle logic. Avoid: "we miss you, here's 20% off" as the first message; see the mistakes section.

    Example 8. The win-back with an offer, second email only (e-commerce)

    Safe because: sent only to customers who engaged with the first email, so the offer rewards a signal rather than chasing silence. Copy this: gating the offer behind engagement.

    Example 9. The "last email" (any sender)

    Type: final step of a re-permission or sunset flow. Safe because: it is literally true and it ends the sequence. Avoid: sending a "last email" and then sending more; it destroys trust and invites complaints.

    Example 10. The publisher's re-permission with a reason the reader cares about (media)

    Safe because: it states the sender's own interest honestly, which readers respond to. Copy this: "smaller list of readers than a bigger list of inboxes."

    Example 11. The agency-managed client email (multi-brand)

    Safe because: the brand, source and reply path are explicit, which matters when the same agency mails several brands and readers forget which one they joined. Copy this: "a person reads it" with a real reply-to, per Microsoft's recommendation.

    Example 12. The healthcare-safe re-engagement (clinic or provider)

    Safe because: it states that the content is general marketing, makes no reference to any individual's health information, and keeps tracking to aggregate opens and clicks. Any email referencing care must go through HIPAA-appropriate channels. Copy this: the explicit "no information about your care" line.

    30 subject lines grouped by intent

    Honest check-in (re-permission)

    1. Still want these?
    2. Should we keep emailing you?
    3. One click to stay on the list
    4. Confirm you want emails from [Brand]
    5. We're not sure you still want [Newsletter]
    6. Quick question about your subscription
    7. Do you still want [topic] updates?
    8. Keep, pause, or stop?

    Value (value reminder)

    1. The one piece worth your time this month
    2. What changed since you last looked
    3. Three things you missed (two paragraphs each)
    4. Our most-shared issue since [month]
    5. The [topic] update people asked us for
    6. A shorter [Newsletter], starting now
    7. What readers replied to most this year

    Preferences

    1. How often do you want to hear from us?
    2. Weekly, monthly, or only the big stuff?
    3. Too many emails? Pick a pace
    4. Choose what you get from [Brand]
    5. Fewer emails, same [topic]

    Deadline (final step only)

    1. Last email unless you click
    2. We'll stop after this one
    3. Removing your address on [date]
    4. Final notice: keep receiving [Newsletter]?
    5. This is goodbye, unless you say otherwise

    Customer win-back (customers only)

    1. Your [product] is probably due for [X]
    2. What's new since your last order
    3. A thank-you for coming back (second email, after engagement)
    4. Is [product] still working for you?
    5. We kept your account; here's what changed

    Avoid: fake "Re:" prefixes, "We miss you" to non-customers, emoji-stuffed lines, and anything that promises a prize.

    One email or a sequence?

    Two or three emails, never one and never five. A reasonable flow: Example 1 or 3 on day 0, Example 5 or 6 on day 7, Example 9 on day 14; a click on any of them resets the clock, and no click by day 21 means suppression. Send each email to small daily cohorts rather than to the whole dormant segment at once; the full daily-cohort schedule and stop conditions are in the reactivation playbook.

    What results to expect

    Scroll for more → On small screens, choose cards for wide tables.

    Metric Figure Source and caveat
    Win-back email read rate 12% Return Path, 33 retailers (2014)
    Recipients who read a later message 45%, average 57 days later; only 24% of them had read the win-back email Return Path (2014); causation not established
    Inactive newsletter readers recoverable "as many as 15%" Inbox Collective, Not a Newsletter (April 2023); consultant experience
    Reactivation rates quoted by list-cleaning vendors roughly 2–15% depending on list age Vendor blogs; unaudited
    Planning figure we use in the playbook's worked example 4% click-or-order reactivation Illustrative, not measured

    Measure a frozen cohort on clicks, orders and revenue at 45 and 90 days, not on opens. Apple Mail's privacy proxy accounts for roughly half or more of recorded opens in 2026, so an "open" on a dormant cohort may be a server, not a person. Before you run the program, estimate what the segment is worth with the dormant email list value calculator.

    Mistakes that turn re-engagement into a spam problem

    1. Discount-first to the never-engaged. People who have not clicked in a year did not leave over price. An offer in the first email attracts deal-seekers and complaint-prone readers and trains the rest to wait.
    2. "We miss you" to people who never opened. It reads as false. Use the plain check-in instead.
    3. Sending to the full dormant segment at once. The email can be perfect and the send still produces a bounce and complaint spike, because the list contains 15–30% invalid or risky addresses by vendor estimates.
    4. A new From name or domain to "get past" filters. Reputation is per domain; a new one starts at zero and faces Gmail's accelerated enforcement timetable.
    5. A "last email" that isn't. Readers remember.
    6. Hiding the unsubscribe. Every unsubscribe you make hard becomes a complaint you cannot afford. Gmail's limit is three per thousand.

    Two templates to copy

    Use Example 1 as the re-permission template (tier D: consent on file, no relationship evidence) and Example 3 as the value-reminder template (tiers B and C: past clickers and customers). Both are complete; replace the bracketed fields and keep the unsubscribe link and the one-click headers.

    FAQ

    What is a re-engagement email? An email sent only to subscribers who have stopped engaging, asking whether they want to keep receiving your mail, reminding them of its value, or letting them choose a frequency. Its purpose is to recover readers and remove the rest before they complain.

    How many re-engagement emails should I send? Two or three over about two weeks, sent in daily cohorts, with a defined end: readers who click stay, readers who don't are suppressed.

    Should I offer a discount in a re-engagement email? Not in the first email, and not to people who were never customers. Offer something only to past customers who engaged with the first email.

    What subject lines work for re-engagement? Plain ones that say what the email is: "Still want these?", "How often do you want to hear from us?", "Last email unless you click." Avoid curiosity gaps and fake replies.

    What open rate should I expect? Don't plan on opens; Apple Mail inflates them. The independent benchmark is Return Path's 12% read rate on the win-back email and 45% reading later messages. Plan on a few percent of the cohort clicking or buying, and measure at 45 and 90 days.

    What's the difference between re-engagement and win-back? Re-engagement targets subscribers who stopped reading. Win-back targets customers who stopped buying. The copy and the risk are different, which is why offers belong only in win-back emails to actual customers.

    Before you send, find out what's actually in the segment. The free List Health Audit scans for bounces, traps and dead domains, maps dormancy by tier and estimates recoverable revenue, within 72 hours. Get the free audit →

    Continue with these guides

    Sources

    Cite this page

    12 Re-engagement Email Examples That Didn't Hurt Deliverability (and What Made Them Safe). Artem Kukharenko. EngageMKTG. 2026-10-17. https://engagemktg.com/knowledge/re-engagement-email-examples