Insights · Business models
Database Reactivation Campaign Examples: Eligibility First
An older contact record can contain useful context, incomplete information or a reason the business should not make contact. Before writing a reactivation message, decide which records are suitable for review and why the proposed communication would be relevant.
A useful database reactivation plan starts with that decision. It connects record quality, a legitimate reason to reconnect, the approved communication channel and the person who will handle a response. The examples below illustrate how to design the process without treating every stored contact as an eligible audience.
Review the source and meaning of the record
Identify how the record entered the system and what interaction it represents. A customer, an unfinished inquiry, an imported contact and an unknown-source record need different evaluation.
Look for the original context, the date of the interaction, the service discussed and the latest response or status. Record uncertainty explicitly. If the source or purpose cannot be established, place the record in a review category rather than filling the gap with an assumption.
Deduplicate records before estimating the size of the audience. One person appearing in several lists should not become several unrelated communications from the same business.
Treat eligibility as a documented decision
Choose the communication channel and check the records and requirements relevant to that actual use. A stored email address or phone number is not an operating plan for contacting it.
For Twilio-based messaging, Twilio's Messaging Policy describes consent tied to the sender and message subject, proof of consent and opt-out handling. It also addresses reconfirming consent in circumstances such as a significant passage of time. Review the current provider policy and applicable requirements for the intended communication.
Assign the eligibility decision to an appropriate responsible person. Keep the basis for inclusion separate from the copywriting task so a persuasive message cannot silently override a record that needs to be excluded.
Example one: an unresolved inquiry with a known next step
Imagine a service business that has an older inquiry about a defined project. The record includes the requested work and a next step that was never resolved. This is a hypothetical example, not an actual customer record.
The review would first establish whether the record is current enough to be useful, whether contact through the selected channel is appropriate and whether the service remains available. It would also check for later interactions elsewhere in the system.
If the record is eligible, a proposed message could refer to the original subject and ask whether the customer still needs help. It should not pretend that the customer recently requested contact or create an urgency that the business cannot support.
Example two: a relevant service update for an eligible audience
Imagine a business that has changed a service in a way relevant to a clearly defined group of existing contacts. The initial decision concerns whether those people are eligible for that type of communication through the proposed channel.
The message brief should then explain what changed and why it may matter to the recipient. Avoid presenting a generic sales promotion as a necessary update to a transaction.
Define the response route before sending. A customer who asks whether the revised service fits their circumstances should reach someone who can assess suitability and explain the current scope accurately.
Example three: records that should stay out of the campaign
Unknown-source records, conflicting contact details, a recorded request to stop and duplicate entries all deserve specific handling. An exclusion can be the correct outcome of the review.
Create a reason field the team can understand. For example: source unclear, channel eligibility unresolved, duplicate, service no longer relevant or suppression applies. Keep those reasons separate from “not interested,” which describes a different kind of observation.
Do not use a reactivation campaign to test whether an uncertain address or number belongs to someone. Resolve record-quality questions through an appropriate process before considering campaign inclusion.
Build the campaign brief around one purpose
For each eligible group, write down the shared context, the reason for contact and the intended next step. If the group requires several unrelated explanations, divide it into more coherent categories or reconsider the proposed communication.
Use the following planning table:
| Decision | What to record |
|---|---|
| Audience basis | The verified context shared by included records |
| Eligibility | The approved channel and basis for inclusion |
| Reason to reconnect | A specific, accurate subject relevant to that group |
| Next step | One action the recipient can understand |
| Response owner | The person responsible for replies and exceptions |
| Stop conditions | Suppression, reply, closure and end-of-sequence rules |
Use actual information for the final brief. This table is a worksheet, not a preapproved segment or a campaign ready to send.
Test reply handling and suppression together
Use sample records to check an ordinary reply, a request to stop, a wrong recipient, a duplicate and a response that arrives through a different channel. Confirm what the team sees and whether pending messages stop as intended.
Also test what happens when a record is edited or merged while a sequence is pending. The workflow needs a reliable relationship between the current contact record, suppression state and the remaining actions.
Keep a manual pause available. Name the person who can stop the campaign and explain where unresolved replies will remain visible during an investigation.
Evaluate the full path after the message
Separate attempted messages, replies, suitable conversations, accepted work and completed delivery. A reply can reveal a wrong number or a changed situation; it is not automatically a qualified opportunity.
Include exclusions and unsuccessful outcomes in the review. They help the business understand the quality of the original records and whether the reason for reconnecting was useful.
Where records do not support an attribution or financial conclusion, report the process observations you can verify. Avoid turning message volume into a revenue claim.
Explore database reactivation planning to review one record group and its eligibility questions. For ongoing communications, examine the related SMS marketing workflow as a separately scoped process.