Lead reactivation list hygiene

An old lead list is not a mailing list. It is a set of records collected under different forms, conversations, owners, purposes, and rules. Uploading the whole file into a campaign tool hides those differences until the bounces, complaints, wrong-party replies, and opt-outs arrive.

Clean the list before writing the sequence. The output should not be one large CSV marked ready. It should be a smaller launch segment, a suppression file, a review queue, and an audit record explaining every decision.

Start with a 100-record audit

Pull a mixed sample of 100 records. Include recent losses, old enquiries, different sources, and records from every CRM or spreadsheet that may feed the campaign.

For each record, find:

• the original source and collection date;
• the exact email address and phone number supplied;
• the disclosure or consent evidence stored at collection;
• the purpose of the original enquiry;
• the last contact, owner, and outcome;
• opt-outs, complaints, bounces, wrong-party reports, and do-not-contact notes;
• the system that currently controls the record.

Classify the record as eligible for a named channel, suppressed, or needs review. A blank opt-out field does not prove permission. A mobile number is not evidence that every kind of automated marketing text is allowed. An email that has never bounced may still belong to someone else now.

The first 100 records reveal whether the real job is campaign setup or data repair. If half the sample lacks a source, owner, or usable contact history, buying more sending volume is premature.

Keep identity and permission separate

Identity answers who the person or business appears to be. Permission answers what the business may send, through which channel, for what purpose, and under what evidence. Do not merge the two fields.

A CRM may contain three records for one person: a webinar registration, a quote request, and an imported sales contact. Deduplication can combine identity while preserving the separate source, date, disclosure, and communication history for each record.

Use a stable internal contact ID. Normalize email casing and phone format, but keep the original values. Match on more than a name. Shared mailboxes, family phone plans, company switches, and recycled mobile numbers create false matches.

When two records conflict, choose the more restrictive state until a person reviews them. An opt-out on one record should not disappear because another duplicate lacks the flag.

Build suppression before eligibility

Create the master suppression layer before selecting the campaign audience. It should include:

• email unsubscribes and SMS revocations;
• hard bounces and addresses blocked by the sending provider;
• spam complaints;
• wrong person, deceased contact, or reassigned number reports;
• legal or contractual do-not-contact instructions;
• internal test records, competitors, vendors, and employees when they are out of scope;
• records already converted or currently handled by sales, if the campaign would interfere.

Store the reason, channel, source system, event time, and scope. "Suppressed" without a reason is hard to audit. "Unsubscribed from promotional email on 2026-08-04 through provider X" is useful.

Amazon SES distinguishes hard and soft bounces and says a recipient that produces a permanent hard bounce should be removed from mailing lists immediately. Its account-level suppression list can add addresses for bounce or complaint reasons. Those provider controls help delivery, but the business still needs its own suppression record across every tool that can send.

Do not delete suppression history when cleaning the marketing list. Deletion can let the same address return during the next import.

Apply channel rules after cleanup

Email and SMS need separate eligibility fields. The record may support one and not the other.

For commercial email, the FTC's CAN-SPAM guide requires accurate routing and subject information, a valid postal address, a clear opt-out method, and honoring an opt-out within 10 business days. The business remains responsible when a vendor sends on its behalf.

For automated calls or texts covered by the TCPA, the FCC's 2024 consent order recognizes common reply words such as stop, quit, end, revoke, opt out, cancel, and unsubscribe as reasonable revocation methods. The rule also accounts for other reasonable ways a person may communicate revocation. A campaign process therefore needs to capture the person's meaning, not only one exact keyword.

These are not interchangeable checkboxes. Keep the evidence, purpose, channel, and suppression state visible. Have counsel review the proposed use when the record is incomplete, the message is automated, or state-specific rules may apply. This article is an operating checklist, not legal advice.

Check deliverability without pretending verification is consent

Email validation may catch malformed domains, obvious disposable addresses, and some undeliverable mailboxes. It does not create consent, prove identity, or show that the recipient still expects the message.

Google's current sender guidance tells senders to keep user-reported spam rates below 0.1% and avoid reaching 0.3% or higher. Marketing messages covered by its bulk-sender rules need one-click unsubscribe. A stale reactivation list can damage the domain used for ordinary customer mail, so isolate the reviewed segment and begin small.

For phone numbers, validate the format, country, and line information available from the provider. Do not treat a number labelled mobile as permission. Recycled numbers and changed ownership still require a wrong-party stop rule and human review.

Resolve ownership before launch

Every eligible record needs an owner or an explicit queue. Define what happens when the prior owner left, the territory changed, the account is duplicated, or two staff members claim the same reply.

Set the sequence to stop on reply, opt-out, complaint, hard bounce, booking, disqualification, conversion, or manual takeover. Route ambiguous messages to a person. "Not now," "wrong person," and "who is this?" are different outcomes, but none should trigger the next scheduled pitch automatically.

Test whether suppression moves between the CRM, email platform, SMS provider, sales inbox, and any automation tool. A stop request captured in one system is not useful if tomorrow's workflow sends from another.

Launch a segment the team can answer

The first segment should be small enough for staff to read and answer every reply on time. Select it from records with the strongest source evidence, clearest recent context, valid channel data, and assigned owners.

Record the list version, query or export rule, suppression version, campaign purpose, templates, sender, send time, and staff coverage. Keep a control total:

| Stage | Count to record | |---|---:| | Imported records | Raw count | | Unique identities | After documented matching | | Suppressed | By reason and channel | | Needs review | Unresolved evidence or conflict | | Eligible | By channel | | First launch segment | Limited by reply capacity |

After the send, report delivery, hard and soft bounces, complaints, opt-outs, wrong-party replies, human replies, qualified replies, bookings, and unresolved conversations. Keep raw counts beside rates. Do not claim the cleanup caused revenue when the offer, timing, source mix, or sales response also changed.

DATIK's Reactivation package starts with record review, suppression, channel rules, routing, and measurement. The pricing page lists installation and operating fees. A free diagnostic can review a 100-record sample before a campaign is configured.

Sources and review limits

• FTC: CAN-SPAM Act compliance guide
• FCC 2024 TCPA consent order
• Google: email sender guidelines FAQ
• Amazon SES: account-level suppression list
• Amazon SES: bounce and complaint notification contents

Sources were checked on October 14, 2026. Provider requirements and communications law can change. Confirm the rules that apply to the intended channel, message, location, and record with counsel and the sending provider before launch.