Deliverability Case Study: "We Miss You"
This track has no persona — it's the brand's own voice, playing a dormant subscriber's silence as heartbreak instead of a churn statistic. Every line maps to a real re-engagement (win-back) campaign: the cadence of the touches, the low-friction ask, and the internal argument over when a sender finally has to let a cold address go.
Here is the technical breakdown of the deliverability concepts detailed in the song:
Verse 1: Re-Engagement Campaigns Are Triggered by Inactivity, Not Feelings
"We haven't heard a word in ages / But silence never said you didn't care"
The Deliverability Context: A re-engagement (win-back) campaign is a scheduled send to subscribers who've gone quiet — no opens, no clicks, no site activity — for a defined window, typically 90–120 days. It exists precisely because a sender can't know why* someone stopped engaging; the campaign is the mechanism for finding out before assuming the worst.
- The Fix: Trigger these sends off measurable inactivity thresholds, not guesswork — most ESPs let you build a segment on "no open/click in N days" and automate a fixed-length win-back sequence against it.
Pre-Chorus: Why "No Goodbye" Isn't the Same as "Still Wanted"
"But you never said goodbye / Never told us it was through"
- The Deliverability Context: This is the song's one lyric that needs a technical correction. The absence of an unsubscribe is not evidence of ongoing interest — Gmail and Yahoo's engagement models don't check whether someone clicked "unsubscribe" before downgrading a sender's reputation; they read behavior. An address that never opts out but also never opens for months sends the mailbox provider's engagement model the same negative signal as one that did unsubscribe — the model has no "but they never said goodbye" exception, and continuing to mail it at normal cadence puts the sender's engagement rate at risk regardless of consent status.
- The Correction: Treat "never unsubscribed" as neutral, not as permission to keep sending indefinitely at full volume. That's the actual justification for moving inactive subscribers into a separate win-back flow instead of the regular calendar — it isolates the risk to a small, monitored segment.
Verse 2: Cadence and Frequency in a Win-Back Sequence
"We sent a little something Tuesday / ... / Then Thursday came, we tried again / ... / Maybe we came on too strong then"
- The Deliverability Context: A two-touch sequence within the same week is a fairly standard win-back cadence — one message, then a follow-up a few days later with a different subject line or offer. The lyric's own doubt ("came on too strong") is the correct instinct: over-mailing a segment that's already showing disengagement signals accelerates spam complaints from exactly the subscribers least likely to want the volume.
- The Fix: Cap win-back sequences at 2–3 sends over 1–2 weeks, space them out, and move to suppression entirely if none land.
Verse 3 & Bridge: The Sunset Policy Debate, Argued Out Loud
"They said there comes a time for moving on / I said, 'You don't know them like I do' / ... / One more knock / One more night / One more chance to get this right"
- The Deliverability Context: This is a sunset policy playing out as an argument between two people. "Somebody" arguing to let the address go is the correct deliverability position — dormant addresses risk becoming recycled spam traps, and continuing to mail them long after engagement has died drags down engagement-based reputation signals with mailbox providers. The narrator's "one more chance" is the emotional case for a final win-back attempt before that suppression happens — which is exactly how a real sunset policy should be structured: a bounded last effort, not an indefinite standoff.
- The Fix: Give a dormant segment a fixed final touch, then suppress unconditionally if it doesn't convert. The debate in the lyrics should have a deadline attached to it, even though the song never gives it one.
Breakdown & Final Chorus: The Low-Friction Ask
"We don't need forever, baby / Just something, just something / ... / Just give us a sign, give us a sign"
- The Deliverability Context: Effective win-back emails ask for the smallest possible action — a single click, a one-question preference update, a "yes, keep me" button — not a purchase or a full re-onboarding. That one click is enough to register a fresh engagement event with the mailbox provider and pull the address out of the dormant segment. Asking for more than that in a win-back send asks a cold subscriber for more than they're willing to give, which is why the song keeps lowering the ask verse over verse.
A win-back campaign is a negotiation with a deadline, dressed up here as a plea to an old flame — and the lyrics get the emotional logic and the deliverability logic pointing the same direction: ask for less, act fast, and know when "we'll keep trying" has to become "we let go."
Every list has a cold segment. What you do with it — one more well-designed ask, or an indefinite string of mail nobody opens — decides whether it becomes a growth opportunity or a reputation liability.
Define "Dormant" With a Number, Not a Feeling
- Set a concrete inactivity window — no open or click in 90–120 days is the standard baseline — and build an automated segment on it. Don't wait for a gut sense that someone's gone quiet.
- Separate this segment from your regular sending calendar. Mixing dormant addresses into normal campaigns hides their drag on your aggregate engagement rate until it's already hurt your reputation.
Design the Win-Back Sequence for a Low-Effort Yes
- Ask for one click, not a relationship. A single "keep me subscribed" button or a one-question preference update is enough to register a fresh engagement signal — don't ask a cold subscriber to browse, buy, or fill out a full profile update.
- Cap the sequence at 2–3 sends over 1–2 weeks. Space them out and vary the subject line and offer between touches; a second identical message a day later reads as pressure, not persistence.
- Track clicks and site visits, not just opens. Apple's Mail Privacy Protection (MPP) can register an "open" without a real human behind it, so treat opens alone as an unreliable signal of a genuine win-back.
Don't Let "Never Unsubscribed" Substitute for a Real Signal
- Silence is not consent to keep sending at full volume. Mailbox provider engagement models judge behavior, not opt-out status — a subscriber who never clicks "unsubscribe" but also never opens is still dragging down your engagement-based reputation with Gmail and Yahoo.
- Isolate the risk. Routing dormant addresses into a monitored win-back flow — instead of your main send — keeps their non-engagement from suppressing deliverability for your active, responsive subscribers.
Give the Sunset Policy a Deadline
- Decide the final attempt in advance, not in the moment. A bounded last touch — "if this doesn't convert, we suppress" — protects your sender reputation better than an open-ended series of "one more try" sends.
- Suppress unconditionally after the deadline. Addresses that stay dormant past your sunset window risk becoming recycled spam traps if the mailbox provider reassigns them — mailing a trap address does far more damage than losing a subscriber ever would.
Conclusion
A win-back campaign works the same whether it's dressed as a marketing email or a love song: notice the silence, ask for the smallest possible sign of life, give it a fair but limited number of chances, and then have the discipline to let go. The list that survives that process is smaller — and healthier — than the one that never made the ask.
Your Re-Engagement Checklist:
- Build a dormant segment on a hard inactivity threshold (90–120 days), not intuition.
- Route dormant addresses into a separate, monitored win-back flow.
- Limit the win-back sequence to 2–3 sends with a low-friction, single-click ask.
- Measure success by clicks and site activity, not opens alone.
- Set a final deadline for the sequence and suppress unconditionally if it fails.
Educational content. Email deliverability evolves rapidly. Platform rules (Gmail, Yahoo, etc.), engagement signals, and ESP behaviours change frequently, and real-world issues often involve conflicting signals, data quality problems, and failure modes that general best practices can’t anticipate. Content on this site is provided for informational purposes only and does not replace a thorough analysis by a qualified deliverability professional.
Terms of Use