Reactivation email template
A specific reason to come back, sent to the segment that might — and a clean exit for the rest.
- HubSpot
- Customer.io
- Klaviyo
- Loops
Build a reactivation sequence for users who have not logged in for 90 days.
- Segmented dormancy3,100 dormant: 1,850 never activated, 1,250 lapsed-active
- Pulled recent changes2 releases matter to lapsed-active; neither helps never-activated
- Wrote per-segment reasonsNever-activated: the setup blocker they hit. Lapsed: what shipped
- Set the cap and suppression3 sends, final one an explicit opt-out
Two segments need different emails: 1,850 never-activated users stalled at account connection and do not care what shipped, while 1,250 lapsed-active users left before the two releases that address their reason for leaving. Roughly 400 addresses have not opened anything in a year and are suppressed now rather than mailed.
A reactivation email template only works if something has actually changed. This one finds the specific reason a dormant user should return — what shipped, what they never reached, what their peers now do — and pairs the sequence with list hygiene rules so non-responders get suppressed instead of emailed forever.
What is a reactivation email template?
A short sequence for users who have gone quiet. It segments dormancy by how far they got before stopping, gives each segment a concrete reason to return, and ends with a suppression rule for the ones who do not respond.
Segment the dormant list
- Split by how far the user got before going quiet
- Separate never-activated from lapsed-active
- Identify who is already unreachable and should be suppressed now
Find a real reason
- Pull what shipped since their last session
- Name the step they never reached
- Offer relevance before discount
Close the loop cleanly
- Cap the sequence at two or three sends
- Write the final email as an explicit opt-out
- Suppress non-responders to protect deliverability
What should a win back email template say?
What changed since they left, in one sentence, and what it lets them do now. "We miss you" is not a reason, and a discount without a reason mainly teaches the list to wait for discounts.
How should you segment dormant user email sends?
By where they stopped. Someone who never completed setup needs the blocker removed; someone who used the product for months and left needs to hear what improved. Sending both the same email means one of them is being ignored.
How does reactivation relate to list hygiene?
It is the last step before suppression. Two or three attempts is the honest limit; after that, continuing to send depresses your engagement rates, which lowers inbox placement for the users who do want your email.
How the reactivation email template works across your stack
The agent reads last-activity and engagement data from your ESP or CRM to build dormancy segments, and takes recent shipped changes from your changelog or Knowledge to source the reason to return. Sequences export to HubSpot, Customer.io, or Klaviyo with suppression rules written per segment.
- HubSpot
- Customer.io
- Klaviyo
- Loops
Who uses this reactivation email template
- Lifecycle marketers
- Reactivate the segment that can return and suppress the rest.
- Growth teams
- Convert a dead list into a small number of real second chances.
- Email operators
- Fix engagement rates by ending sends that never had a chance.
How to run this reactivation email template in Metaflow
Connect the list
Last activity and engagement history define the dormancy segments.
Supply what changed
Changelog or release notes give the agent a real reason to write about.
Review segments and reasons
Each segment shows why it stopped and what it is being offered.
Ship with suppression
Two or three sends, then suppress non-responders automatically.
What you provide
- Last-activity and engagement data
- Recent product changes or changelog
- Any offer you are willing to make
What you get back
- Dormancy segments with counts
- Reason-to-return per segment
- Two to three email drafts per segment
- Suppression rules
Why use this reactivation email template?
Segments by where the user stopped, so the reason fits
Reasons come from real shipped changes, not sentiment
Capped at two or three sends by design
Suppression is part of the sequence, not an afterthought
Reactivation email template FAQs
What is a good reactivation email?
One that names something specific that changed and what it now lets the reader do. Discounts work occasionally but train the list to wait, so lead with relevance and hold the offer in reserve.
How many reactivation emails should you send?
Two or three. Beyond that, response rates approach zero while the damage to your engagement metrics keeps accumulating.
When should you consider a user dormant?
Relative to your natural usage cycle — a weekly-use product has dormant users at 30 days, a quarterly workflow does not. Fixed 90-day rules mislabel healthy users in low-frequency products.
Should you delete unengaged subscribers?
Suppress rather than delete, so you keep the record without sending. Continuing to email people who never open lowers inbox placement for everyone else on the list.
Similar email sequence templates
Key takeaways
- Segment by where they stopped, not just how long ago
- Give a real reason; a discount is not a reason
- Cap at two or three sends, then suppress