When you're trying to re-engage users who've gone quiet, start with a question most teams skip: is the problem awareness, or is it activation? Dormancy usually means the user never got the value they were supposed to get — the fix isn't to remind them you exist, it's to fix the value gap. This article walks through the two plays to choose between.

The Appcues App is in beta and rolling out gradually. If you don't see it yet at app.appcues.com, it hasn't been enabled for your account. See Introducing the Appcues App for more.

Two plays, depending on the signal

Distinguish between users who are slipping and users who are already gone — the channel strategy is completely different.

Play A — Trending toward dormancy (early intervention)

When this applies: the user is still logging in, but behavioral signals show they're slipping. Login frequency dropping, core actions declining, engaging with surface features but ignoring deeper ones.

What to build:

1. In-product contextual Tooltip on the user's next session, anchored to the core action they've been skipping — not a generic "welcome back," but a nudge toward the specific value they're drifting from.
2. Email follow-up if they don't return within their normal cadence.

Why early matters: act on behavioral signals, not just absence of login. The prerequisite is that your team has defined what "expected behavior" looks like at each lifecycle stage — without that, every dormancy intervention is too late.

Play B — Already dormant (recovery)

When this applies: the user hasn't been in the product long enough that in-product experiences can't reach them.

What to build:

1. Email re-engagement with a deep link that drops the user back into the product at a meaningful spot — not the homepage, but the place where their next action lives.
2. In-product Tooltip or Embed when they return — "you left off here" content. Embeds work well here because they sit inline and don't gate the user on return.
3. Event tracking for users who don't engage with the email, so you can plan a deeper investigation or accept the loss.

The strongest single play for dormancy is a Workflow with an email to bring the user back, paired with re-onboarding content when they return. If Workflows isn't an option, use deep links in email pointing to pages with in-product experiences.

The core rule: you can't fix in-product if they're not in-product

Never rely on in-product-only plays for users who are already gone. If someone hasn't logged in for weeks, a Tooltip they'll never see isn't a strategy. Email is the right channel for recovery; in-product is for the return.

What to avoid for re-engagement

• A Modal on first return. The user just walked back in — don't gate them.
• The same content as the original onboarding. They've seen it. Use re-entry copy, not first-touch copy.
• In-product only for dormant users. Email first, in-product on return.
• Generic "we miss you" messaging. Reference the specific value or action the user was on track for, not a vague sentiment.

Defining expected behaviors by lifecycle stage

Re-engagement works best when your team has defined what "engaged" looks like at each stage — what steps a user should take during onboarding, what cadence indicates healthy adoption, what signals readiness for expansion.

Without these definitions, you can still build re-engagement campaigns, but you'll need to define the triggers as you go. If users haven't taken expected steps at a given stage, re-engage them with different messaging — not a repeat of what already didn't land.

Every re-engagement campaign gets a recovery path

This applies to all campaigns, but it's especially important for re-engagement — always include:

1. An opt-out path — users can dismiss without penalty
2. Event tracking on the dismissed cohort — so you know who chose not to engage
3. A way to come back voluntarily — typically a Launchpad item or a persistent Embed