A Five-Step Database Reactivation Campaign Plan

A campaign needs a relevant audience, a truthful message and someone ready to handle the response. It does not need an invented return forecast or a fixed sequence across every available channel.
Use these five steps as a planning checklist. If eligibility or response handling is unresolved, stop there before scheduling anything. For definitions and measurement basics, read what database reactivation means.
Step 1: Establish Which Records Are Eligible
Record where the data came from, why it was collected, which preferences apply and whether it can be used for the proposed purpose and channel. A valid email address or mobile number is not permission by itself.
Separate duplicate, invalid, suppressed and uncertain records. Keep suppression information so a later import cannot accidentally reactivate an objection. Do not infer permission from an old purchase or an email-open event.
Your output should be a defined eligible audience with documented exclusions. It should not be a projection of how much revenue the database contains.
Step 2: Choose One Relevant Group
Recency, frequency and purchase value can help organise records, but they do not establish current interest. Choose a group for which you can explain why the message is useful now.
For example, a verified service change may be relevant to some previous customers and irrelevant to others. Check that the proposed message does not imply knowledge you do not have or reveal sensitive information.
Avoid automatic rules such as contacting everyone after six months. The normal purchase cycle and recipient preferences matter more than a generic calendar.
Step 3: Approve the Message and Its Claims
Write for a person who may have forgotten the business. Make the sender, reason for contact and proposed next step clear. Include the required preference or opt-out route.
| Copy check | What the reviewer should verify |
|---|---|
| Relevance | Why this recipient is included |
| Offer | The business has approved the scope and terms |
| Deadline | Any stated expiry is real |
| Proof | Results or testimonials have evidence and permission |
| Personalisation | Every included detail is accurate and appropriate |
| Next step | The destination works and someone owns the response |
Do not add invented social proof to make a template persuasive. Do not imply that an AI-generated recommendation reflects a personal assessment by a member of staff.
Step 4: Pilot the Complete Response Journey
Test the message, destination, reply routing and preference handling with internal test records first. Confirm that an objection prevents further marketing in the intended systems and that a failed integration creates visible work for someone to resolve.
Then choose a manageable pilot audience. Agree the review point and stopping conditions before sending. Delivery problems, complaints or unhandled replies may justify stopping, even if the planned sequence is unfinished.
Do not switch a non-responder to SMS or WhatsApp simply because another contact field exists. Assess that channel separately. More channels are not automatically better.
Step 5: Report Outcomes Without Inflating Them
| Measure | Definition to agree |
|---|---|
| Eligible recipients | The people included after exclusions |
| Successful delivery | The channel's reported delivery event, with its limitations |
| Genuine responses | Human replies separated from automatic responses |
| Qualified demand | Responses meeting the business's agreed fit criteria |
| Completed work | Fulfilled purchases or delivered services, with cancellations and refunds considered |
| Additional contribution | Money from additional sales left after delivery costs, before overheads and tax |
| Negative outcomes | Objections, complaints and unresolved handling failures |
An open or click is not a purchase. A purchase after a message is not automatically caused by it. Where appropriate, use a comparison group or matched period and explain the limits of the method.
Our reactivation definition guide includes a labelled synthetic calculation that distinguishes contribution-based ROI from revenue divided by campaign spend. There is no 7:1 minimum return or universal payback date.
Questions Before a Second Campaign
Did the audience selection make sense? Could the team handle replies? Were claims accurate? Were preferences honoured? Which outcomes were additional, and which remain uncertain?
Use those answers to decide whether another campaign is justified. Do not automatically repeat contact every quarter or increase the number of messages because the first attempt did not produce sales.
Can we run this ourselves?
Possibly, if the team can establish eligibility, prepare accurate content, operate the tools and handle responses. Specialist support can help with particular gaps; it does not guarantee a better return.
How many records do we need?
There is no universal minimum. Relevance, eligibility, economics and handling capacity determine whether a pilot is worthwhile. Small samples also limit the conclusions you can draw.
When should we expect results?
Agree a review period around the buying cycle and the purpose of the message. Do not promise a purchase window or recovery of costs before there is evidence.
Fix the Follow-Up Before Adding Volume
Check the audience against our database readiness guide. If you need support running the campaign, ReFlow brings the agreed audience, messages and response process into one scoped piece of work.
If enquiries disappear between tools or nobody owns the next step, address that first. Our automation service covers scoped workflow improvements, and the dashboard guide explains how to make unresolved work visible.
Tell us which part of the process is failing so we can discuss whether it fits our work.