How to reactivate a dormant email list, step by step.

A practical guide for email operations and lifecycle teams: assess permission, establish a baseline, suppress ineligible contacts, and test reactivation before expanding volume.

Updated 2026-09-15

Get Free List Audit Explore the List Revival Calculator

The problem this solves

An inactive address is not automatically eligible for another campaign. Revival starts by separating contacts you may responsibly approach from records that must remain suppressed. A useful pilot measures whether a permissioned cohort responds without putting the established sending program at avoidable risk.

What your team gets

A documented eligible cohort and a record of exclusions
A baseline that separates observed results from estimates
A staged sending plan with an owner and stop conditions
A measurement sheet for recovery, complaints, bounces, and revenue

1. Establish eligibility before planning a send

Gather the acquisition source, signup date, brand relationship, permission record, last meaningful interaction, and current subscription state. When an input is missing, mark it unknown and hold that record for review. Do not treat deliverability validation as evidence of permission.

Confirm the recipient requested the type of message and recognizes the sending brand. Keep unrelated brands and acquisition sources separate.
Exclude unsubscribed contacts, prior complainants, hard bounces, and contacts without a usable permission record. An old export must not override current suppression state.
Review the current requirements of your email provider and destination mailbox providers. The source links below explain authentication, subscription, and sending practices; they do not approve a particular list.

2. Freeze the baseline and define dormant

Write down the cohort definition and observation window before the pilot. Choose the inactivity window to match your normal customer cycle. Keep the original cohort identifiers so later reports compare the same people instead of a changing mix of contacts.

Export counts for the original list, duplicate records, excluded contacts, and eligible dormant contacts. Record the snapshot date and the reason for every exclusion.
Use meaningful clicks, purchases, declared preferences, or other verified activity where available. Treat opens as a supporting signal because image loading and privacy features can distort them.
Record recent sends, bounces, complaints, unsubscribes, and measured revenue using the same definitions and time window. Missing history stays unknown; it is not zero.
Separate a calculator estimate from a measured baseline. Assumed recoverability and revenue per subscriber describe a scenario, not a forecast or a promised result.

3. Reconcile identity and suppressions

Deduplicate the working cohort against your customer records without merging away brand-specific subscriptions. Reconcile the email platform, CRM, and suppression sources before the first send, then check eligibility again before each later batch.

Keep unsubscribe, complaint, and bounce states attached to the recipient record. Removal from one campaign must not let that recipient re-enter through another export.
Check suppression ingestion and processing with test records before launch. Assign an owner to investigate delayed or conflicting updates.
Document consent gaps, malformed addresses, dead domains, and conflicting identities for review. Do not try to recover a record by inventing missing information.

4. Segment by evidence of an existing relationship

Create small, interpretable groups using acquisition source, recency of meaningful activity, customer relationship, and mailbox provider. Keep consent eligibility separate from engagement likelihood: a promising score does not override a suppression.

Begin with eligible contacts whose relationship and recent activity are best documented. Hold older or less certain groups until the first results have been reviewed.
Use a relevant message that explains the relationship, offers a useful next step, and makes opting out easy. Avoid misleading urgency or a subject line that suggests a conversation that never happened.
Assign one owner to reconcile the segments and prevent overlap with regular campaigns. Include existing campaign volume in the recipient's frequency checks.

5. Run a staged reactivation pilot

Set an initial batch size and pace based on the established sending history, available monitoring, and provider limits. There is no universal safe batch size for a dormant list. Record who can approve a change to the pilot and when the next review happens.

Verify the sending identity, SPF, DKIM, DMARC alignment, unsubscribe handling, and message links before sending. Check the mailbox-provider guidance for the requirements that apply to your volume.
Send the first eligible segment, wait for the agreed observation window, and review delivery responses and human engagement before adding another segment.
Increase volume only when the prior batch supports that decision. Keep the established program's health visible alongside revival results.
A provider accepting a message is not proof of inbox placement. Record acceptance, observable engagement, and downstream outcomes as separate facts.

6. Define stop conditions before launch

Agree on explicit limits with the sending owner before the pilot begins. Set operational thresholds using the current provider requirements and your own baseline; do not treat a provider's maximum complaint rate as a target to approach.

Pause the affected sending stream when authentication or unsubscribe processing fails, a provider blocks or materially defers traffic, or the agreed bounce or complaint threshold is crossed.
Investigate negative changes in the active program as well as the revival cohort. Do not expand a cohort while its health or permission status is unresolved.
Record the trigger, time, affected segment, and decision owner. Resume only after the cause is addressed and the owner approves a bounded next step.
Set a maximum number of attempts and a sunset rule for nonresponders. Repeated silence is not a reason to send indefinitely.

7. Measure recovery using the original cohort

Choose a reactivation event before launch, such as a verified purchase, a qualified click, or a submitted preference. Report both the number of people who meet it and the denominator. Compare compatible windows and keep automated activity out where it can be identified reliably.

Report eligible contacts, attempted recipients, accepted messages, hard bounces, complaints, unsubscribes, and reactivated people. State each rate's denominator instead of combining incompatible provider reports.
For revenue, document the order source, attribution window, refunds, and deduplication method. Label attributed revenue separately from incremental revenue.
If you need to estimate incremental lift, agree on a comparable holdout before launch. Without that comparison, describe observed or attributed results rather than claiming the pilot caused every conversion.
Keep costs and net contribution separate from gross revenue. Use the agreed commercial terms when evaluating the program; this playbook does not change those terms.

Worked example: cohort arithmetic, not a performance forecast

Illustrative numbers only: a snapshot has 10,000 dormant records. After deduplication and eligibility review, 2,000 are excluded, leaving 8,000 eligible contacts. The owner selects 1,000 of those contacts for an initial pilot; 40 later meet the predefined reactivation event.

The pilot reactivation rate is 40 / 1,000 = 4% of attempted recipients. The other 7,000 eligible contacts have not yet been tested.
If 10 of those reactivated people generate $50 each in verified attributed revenue during the agreed window, gross attributed revenue is $500 before costs and refunds.
Neither figure establishes expected results for the rest of the list. Without a suitable comparison group, the $500 is not a measured incremental lift.

Sources and further reading

Check provider guidance before each pilot; requirements can change.

Start with a measurable lifecycle problem.

Prove one application first, then expand the same profile and decision infrastructure as the business case becomes clear.

Get Free List Audit