How to Build a Re-Engagement Email Sequence for Lapsed App Users

Most app teams spend their entire marketing budget chasing new installs while quietly hemorrhaging the users they already paid to acquire. The math rarely works in their favor. Re-engaging a dormant user costs a fraction of acquiring a new one, and a well-structured email sequence is one of the most cost-efficient tools you have for doing it.

This guide walks through how to build that sequence — segment thresholds, email copy structure, timing cadence, and what to do when someone still doesn't respond.

Define "Lapsed" Before You Write a Single Email

The word "lapsed" means different things depending on your app's natural usage frequency. A fitness app user who hasn't opened in 14 days is lapsed. A tax filing app user who hasn't opened since April is right on schedule.

Set your dormancy threshold based on your app's expected engagement cadence — not an arbitrary 30-day window you borrowed from someone else's playbook. Here's a rough framework:

App Category	Typical Session Frequency	Lapsed Threshold
Social / Community	Daily	7–10 days inactive
Fitness / Habit	3–5x per week	14 days inactive
Marketplace / Commerce	Weekly	21–30 days inactive
On-demand Services	As-needed	45–60 days inactive
B2B / Productivity	Daily (weekdays)	10–14 days inactive

Once you've set the threshold, create at least two sub-segments within your lapsed pool: recently lapsed (just crossed the threshold) and deeply lapsed (2x–3x past it). The copy and urgency level should be different for each. Treating someone who lapsed three days ago the same as someone who lapped the threshold three times is a waste of personalization capability.

Map the Sequence Structure Before Writing Copy

A re-engagement sequence isn't a single email. It's a deliberate arc with a specific job at each step. A functional sequence for most apps runs four to five emails over two to four weeks.

Here's the structural pattern we use across engagements:

Email 1 — The Low-Pressure Check-In (Day 1–2 after threshold) No offer. No urgency. Just a simple, human "we noticed you haven't been around" message. The subject line should feel personal, not promotional. The job of this email is to get an open, not a conversion.

Email 2 — The Value Reminder (Day 5–7) Remind them why they installed the app in the first place. Lead with a specific feature, outcome, or piece of content they might have missed. If your app has personalization data — their saved items, past activity, a milestone they're close to — use it here. Generic "here's what you're missing" copy underperforms by a significant margin compared to copy tied to actual user behavior.

Email 3 — The Incentive Email (Day 10–12) If they haven't re-engaged after the first two emails, this is where you introduce a reason to come back now. That could be a feature update, a time-limited offer, or early access to something. Keep the incentive proportional — don't train your user base to wait out your re-engagement emails for a discount.

Email 4 — The Feedback Ask (Day 16–18) Frame this as genuinely wanting to know why they left. A two-question survey embedded in the email (or a single-click "tell us what happened" button) does two things: it gives you actionable data, and it occasionally converts users who just needed to feel heard. Churned users who get a real feedback request sometimes re-engage out of goodwill.

Email 5 — The Sunset Email (Day 21–25) This is the most important email in the sequence and the one most teams skip. Tell them explicitly that this is your last message and you'll stop emailing them if they don't respond. Counterintuitively, sunset emails frequently have the highest re-engagement rate in a sequence. The finality creates genuine urgency in a way that fake countdown timers never do.

After Email 5, unsubscribe non-responders from your re-engagement track. Move them to a suppression list. Do not keep mailing dormant contacts — it destroys your deliverability.

Write Subject Lines That Don't Sound Like Retention Campaigns

Your subject lines are doing the hardest work. They have to compete in an inbox full of noise, and they have to do it without telegraphing that this is a "we miss you" campaign. That phrase, along with "come back," "we haven't seen you in a while," and any emoji-loaded subject line, is a strong signal to spam filters and to users that you're running a template playbook.

A few patterns that tend to perform better:

First-name + specific behavioral hook: "Marco, your [feature] is waiting" performs better than "We miss you, Marco"
Curiosity gap tied to a real update: "Something changed in [App Name] since you were last here"
Direct question: "Did something go wrong?" — this works especially well for Email 4
The sunset subject line: "This is our last email to you" — don't soften this; the directness is the point

Test subject lines across your two lapsed sub-segments. A user who lapsed 15 days ago responds to different triggers than someone who lapsed 60 days ago. What reads as "low pressure" to a recently lapsed user can read as irrelevant to a deeply dormant one.

Running re-engagement email campaigns alongside paid retargeting? Semnexus's mobile app marketing services team handles the full retention and growth stack — from email and push to paid UA — so your channels don't work against each other.

Timing and Sending Cadence

Send frequency is where most re-engagement sequences go wrong. Teams either send daily (spam behavior) or send so infrequently the user forgets they were being contacted.

The cadence above — roughly every five to seven days — is a reasonable baseline. Adjust based on your email program's health metrics:

Open rate below 10% on Email 1: Your subject lines need work, or your list hygiene is poor. Fix that before building out the rest of the sequence.
High open rate but no clicks: The email body isn't earning the conversion. Revisit your value framing and CTA placement.
Unsubscribe spikes on Email 3: Your incentive email is hitting people too hard. Either the offer feels mismatched or the email feels desperate.

Send timing within the day matters less than most people think for re-engagement specifically. These users aren't in your app's habit loop yet — there's no "right moment" tied to their routine. That said, avoiding Monday mornings and Friday afternoons is reasonable practice for most consumer apps.

For B2B and productivity apps, Tuesday through Thursday between 9 AM and 11 AM local time is the conventional window, and in our engagements it holds up.

Clean Your List or Your Deliverability Pays for It

Re-engagement sequences create temporary spikes in unsubscribes and spam complaints. This is expected and, to a point, healthy — you're flushing contacts who were never going to re-engage anyway.

What you can't afford is letting that spike damage your sender reputation with Gmail and Apple Mail. A few operational rules:

Honor unsubscribes immediately. Not within 10 business days — immediately.
Suppress hard bounces before the sequence starts. Run your lapsed segment against your bounce list before the first send.
Don't re-add sunset contacts to a new sequence. Once someone has been through the full arc and didn't engage, they're done. Mailing them again from a different list is a spam complaint waiting to happen.
Authenticate your sending domain. SPF, DKIM, and DMARC records should be in place before you run any re-engagement campaign. This is table stakes.

The tradeoff here is real: a clean, engaged list of 10,000 users outperforms a bloated list of 50,000 dormant ones every time, both in deliverability metrics and in actual revenue generated.

For a broader look at how email fits into a complete app user acquisition and retention strategy, that post breaks down the full channel mix.

Connect Email to Your In-App Re-Onboarding

Email gets them to tap the notification. What happens inside the app when they do is a separate problem — and one most teams don't solve before launching the re-engagement sequence.

If a lapsed user clicks through to your app and lands on the same home screen they left, you've wasted the email. A re-engaged user needs a brief re-onboarding moment: a contextual tooltip, a "welcome back" state, or a direct deep-link into whatever you used as your email hook.

Deep linking is non-negotiable for re-engagement email. An email that mentions a specific feature needs to land on that feature, not the app's root URL. Set up Universal Links (iOS) and App Links (Android) before your sequence goes live. This is one of those implementation details that's easy to overlook when the marketing team is running the project — but it has a measurable impact on post-click conversion.

Also worth noting: re-engagement email and push notifications are not the same channel. Users who've disabled push notifications are often reachable via email but not vice versa. Run the channels in parallel, not as substitutes for each other. The 5 app marketing strategies for user retention post covers the push and in-app side of this in more detail.

FAQ

How many emails should a re-engagement sequence have?

Four to five emails is the right range for most apps. Fewer than four and you haven't given the sequence enough surface area to work. More than five and you're past the point of diminishing returns — the contacts who haven't responded by Email 5 are unlikely to respond to a sixth.

When should I send the sunset email?

Approximately three to four weeks after the first email in the sequence, depending on your cadence. The sunset email should feel like a natural end of the arc, not an abrupt cutoff. Give users enough time to have seen at least three previous emails before you send it.

Should I offer a discount in a re-engagement email?

Only if it's proportional to what your app normally offers and if you're prepared to make that the expectation for future churn cycles. Incentives work, but discount-trained users will churn again and wait for the next offer. A feature reminder or personalized value hook is a better first lever; use the incentive as a fallback.

What's the difference between a re-engagement sequence and a win-back sequence?

They're often used interchangeably, but there's a useful distinction: re-engagement typically applies to users who've gone dormant but not canceled (relevant for free or freemium apps), while win-back applies to users who've explicitly churned or canceled a paid subscription. The copy framing and incentive logic differ between them.

How do I measure whether the sequence is working?

Track re-engagement rate (users who open the app within 7 days of clicking an email), not just email open rate. Email opens that don't lead to a session inside the app aren't a win. Also monitor your 30-day retention rate for re-engaged users — if they churn again within a month, the sequence is masking a product problem, not solving it.

What if my app doesn't collect email addresses during onboarding?

That's the root problem. Fix onboarding first. Re-engagement email only works if you captured the address — ideally with explicit permission — during the initial sign-up flow. If you're collecting emails but they're low quality (fake addresses, typos), invest in real-time email validation at the point of capture before building out any retention email program.

If you're building a re-engagement strategy from scratch or your current sequences aren't moving the needle, the Semnexus mobile app marketing services team can audit what you have and build a retention program that works across email, push, and paid retargeting. Book a 30-minute call and we'll tell you exactly where your lapsed user problem is coming from.