Reactivation Offer

Wake a dormant list segment with a single re-permission message that either restores engagement or cleanly removes dead weight.

Pro moderate Funnel-Stage Offers

What it adds

The builder reads your source files to define dormancy precisely, then produces a short re-permission sequence and landing page whose job is to make silent subscribers declare themselves one way or the other. It converts by asking for the smallest possible signal — a click, a preference, a reply — instead of a purchase, which is what a cold record can actually give. The conversion event is a recorded engagement signal plus a segment reassignment, with non-responders suppressed to protect deliverability.

What your builder is told to do

The actual instructions, in order.

1
Inspect the source files and set an explicit dormancy threshold in days since last open, click, or purchase; every downstream decision depends on this number being defined, not assumed.
2
Write a short, plain message that names the silence directly and asks one question with two or three answer buttons, each mapping to a content preference or an exit.
3
Build the landing destination for each answer so the click lands on confirmation plus one immediately useful item pulled from the source files — the click must be rewarded, not merely logged.
4
Offer a genuine exit option with equal prominence; a reactivation sequence without a clean unsubscribe path damages the sending domain more than the dormant records do.
5
Sequence exactly three sends across a short window with different angles — one asking the question, one delivering value with no ask, one stating the record will be removed — and stop the sequence the moment any engagement is recorded.
6
Define responsive behavior: email templates must render single-column at mobile widths with tap targets sized for thumbs; the landing page must present the preference choices above the fold on tablet; desktop should keep all options visible in one view without a scroll to compare.
7
Execute suppression at the end: move non-responders out of the active sending pool, record why, and exclude them from broadcast sends until they re-enter through a new opt-in.
8
Track responses by chosen preference so the reactivated portion enters the correct nurture path rather than the general list.

Edge cases it handles

The things an agent skips when you only say "build a reactivation offer".

A dormant record is also a past customer: route to a win-back path instead, since the relationship history is different.
Engagement data is incomplete or missing for older records: treat unknown as dormant and state that assumption explicitly.
A subscriber engages on the final send: cancel the suppression and reassign before removal executes.
Deliverability is already degraded: send in small batches to the most-recently-active dormant records first.
The list contains role or invalid addresses: remove them before the sequence rather than counting them as non-responders.

Definition of done

Your builder is required to check every one of these before reporting the work finished.

A numeric dormancy definition is stated and applied consistently across the sequence.
Each message asks for one low-effort signal and offers a visible exit option.
Every click destination delivers something useful drawn from the source files.
Email and landing layouts are verified at mobile, tablet, and desktop widths.
Engagement at any point halts the remaining sends immediately.
Non-responders are suppressed from broadcasts and the reason is recorded.
The builder reports which source files supplied engagement history and content, and which assumptions about dormancy remain unresolved.

Related offer files

Funnel-Stage Offers

Lead Magnet

Turn anonymous cold traffic into named subscribers by trading one narrowly useful asset for an email address in seconds.

Funnel-Stage Offers

Cart Recovery Offer

Close an abandoned checkout by returning the shopper to their exact cart and resolving the friction that stopped them.

Funnel-Stage Offers

Win-Back Offer

Recover a lapsed customer by naming what changed since they left and crediting the relationship they already built.

How it works

1

Copy the link

Grab the Markdown blueprint URL for this offer type.
2

Give it to your builder

Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.
3

It maps, then builds

Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.