Database Reactivation: Turning Old Leads Into New Work

Suppose a homeowner asked for an estimate, postponed the project, and never booked. Months later, the inquiry is still in your CRM. Before sending another message, you need to know whether the project is still relevant, whether you may use that channel, and who will handle a reply.

Database reactivation is a planned effort to reconnect with eligible dormant contacts. It can uncover work, but it cannot guarantee revenue this month. Some people have moved on; others should never enter the campaign. The useful outcome is a measured conversation that your team can follow through to a completed, paid job.

Define dormant before choosing an audience

Start with one service and one reason to reconnect. For example, consider estimate inquiries with no two-way conversation for 90–180 days, no booking, and a recorded reason of “timing.” That range is an illustrative business rule, not a consent-expiration rule or a recommended sending window for every company.

Separate postponed estimates from former customers due for maintenance and leads who chose another provider. Each group needs different wording. Exclude active opportunities, current jobs, unresolved complaints, and anyone already receiving a related sequence.

Record the original inquiry date, service, last meaningful interaction, lead source, owner, and outcome. An email open alone is a weak basis for deciding that someone remains interested. If the original need is unknown, do not write as though you remember it.

Make channel eligibility a separate check

A phone number, old inquiry, or “customer” tag does not establish current marketing permission. Audit the consent record: who collected it, when, through which form or interaction, what disclosure appeared, which business it named, and which channel and purpose it covered.

For this workflow, hold out purchased or rented lists, unsubscribed contacts, Do Not Disturb (DND) records, missing consent evidence, and records whose permission is stale or unclear. Do not send an otherwise unauthorized “permission check” to repair the gap.

Email and SMS have different requirements:

• U.S. commercial email needs accurate sender information and subject lines, advertising identification, a valid postal address, and a clear opt-out. The FTC’s CAN-SPAM guide requires opt-outs to be honored within 10 business days. Configure prompt suppression rather than using that limit as a waiting period.
• Provider rules can be stricter. For example, Twilio’s Email Policy requires affirmative consent for marketing and renewed consent after extended non-engagement. It prohibits purchased lists. Check the policy of the provider actually sending your email.
• For SMS, review consent for your business and the proposed message purpose, sender registration requirements, and applicable federal delivery rules and state rules before enrollment. Twilio’s Messaging Policy requires prior express consent, retained proof, sender identification, and straightforward opt-out handling. It recommends reconfirmation after a significant lapse or a change of subject.

Do not assume email permission covers texts. Have the person responsible for compliance resolve unclear records and jurisdiction-specific requirements, including sending hours and do-not-call restrictions. This checklist does not establish legal eligibility by itself.

Clean the list without losing suppression history

Normalize email addresses and phone formats, then review duplicates before merging. Shared family numbers and business addresses can belong to different people. Preserve the most restrictive applicable opt-out state and the evidence behind it; a fresh import must not reset suppression.

Remove invalid destinations and suppress hard bounces, complaints, and wrong-number reports. Email verification can help identify address problems, but a valid address does not prove consent or inbox placement.

Before a pilot, confirm sending-domain authentication and unsubscribe behavior with your email administrator. Google’s sender guidelines require SPF or DKIM for all senders to personal Gmail accounts, with additional authentication and one-click-unsubscribe requirements for bulk senders. Google also recommends increasing volume gradually while monitoring delivery. Cleaning a list does not replace those checks.

Offer a useful next step

Choose an offer your staff can fulfill: an updated estimate, a seasonal maintenance appointment, or a short consultation about the postponed work. A discount is optional. State genuine availability and expiration terms only after checking capacity.

These examples are illustrative drafts for eligible recipients. Replace every bracketed field, verify the historical detail, and add required disclosures before use.

Email example

Subject: Still planning your [service] project?

Hi [first name],

You contacted [business] about [verified service] in [month]. If you’re still considering the work, we can review what has changed and let you know whether the old estimate needs updating.

Reply with what you need, and [staff name/team] will help you choose a next step. If the project is finished, there’s no need to respond.

[Business name and monitored reply address]

Advertisement from [business]. [Valid postal address]

[Working unsubscribe link] · [Privacy policy link]

SMS alternative

Hi [first name], this is [staff name] at [business]. Still considering [verified service]? Reply if you’d like an updated estimate. Reply STOP to unsubscribe.

Use SMS only for independently eligible SMS recipients. Do not automatically text someone because they ignored the email. Match required disclosures to the actual program, and review message length and delivery charges after personalization.

Map the workflow before activating it

SMBcrm’s automation tools support triggers, conditions, waits, messaging, and staff tasks. The design below is a proposed configuration to validate in your account, not a tested campaign or a claim that every field already exists.

Use a campaign identifier such as reactivation-estimates-november and an approval field or tag controlled by the reviewer. Treat those as configuration choices.

Stage	Proposed trigger, condition, or action
Entry	Reviewer approves the campaign audience; an approval tag starts the workflow. Disable repeat entry for this campaign.
Gate	Require the dormant segment, channel permission, valid destination, assigned owner, and no conflicting sequence. Otherwise exit with a recorded reason.
First contact	Send one approved message through the eligible channel during verified recipient-local sending hours.
Wait	Illustrative assumption: wait five business days, with a defined timezone and holiday policy. Verify how the account implements this timing.
Recheck	Before any follow-up, recheck permission, suppression, replies, bookings, purchases, and active-work status.
Final contact	If still eligible and silent, send one relevant reminder. Then end this campaign without automatic recycling.

Build event-driven exits alongside the timed path. Any reply pauses promotional follow-up and creates a staff handoff. A booking stops reactivation and moves the person into the appropriate appointment process. An opt-out, complaint, or wrong-number report suppresses further promotional sends as appropriate and cancels queued steps. Review plain-language requests such as “please leave me alone,” as well as keywords.

Recheck eligibility immediately before each send. A contact may opt out or book while waiting. Hold records with an unknown timezone until permitted sending hours can be established. Verify whether reply handling removes contacts from the whole workflow or only one branch; if uncertain, keep the sequence inactive until the stop behavior is demonstrated.

The assigned staff member needs the original inquiry, campaign message, reply, consent context, and next action. For the pilot, choose an internal response target your team can cover, such as the same business day, with a backup owner. Staff should confirm the current need and pricing before promising a slot.

Test without touching customer records

Start with a written decision table and fictional rows. Include an eligible lead, SMS-ineligible email subscriber, duplicate with an opt-out, booking during a wait, reply before a reminder, unknown timezone, and wrong number. Walk each row through every gate and exit on paper or in a local spreadsheet.

Treat account test controls as live operations: workflow tests can send messages and change records. For a no-send review, keep the workflow unpublished, inspect the configuration, and use offline message previews with fictional values. Do not select customer contacts, enroll anyone, or press a send/test action. This validates the plan and copy, not runtime behavior.

Before a controlled test or pilot, complete this setup checklist:

• Reconcile audience counts and document exclusion reasons.
• Confirm authentication, channel permissions, sender setup, and applicable sending hours.
• Check all merge-field fallbacks, links, offer terms, and opt-out instructions.
• Verify staff coverage, conflicting workflows, repeat-entry rules, and queued-message cancellation.
• Define test-only recipients, expected outcomes, a pause control, and who may approve launch.

An approved controlled test must demonstrate reply exits, suppression, and queued-message cancellation before customer enrollment. Start the pilot with a small audience the team can personally review and serve. Choose the size from staff capacity and sender history. Pause expansion if suppression fails, complaints appear, or replies go unanswered; investigate before resuming.

Keep AI optional

The AI Campaigns release describes Labs-based SMS outreach and optional agent handling of replies. It is a separate route, not proof that the workflow above has been tested. Confirm current account access, outbound activation, approval controls, and human handover before considering it.

Review current AI coverage and billing: Conversation AI may be billed by usage or covered by an AI Employee subscription, subject to its limits. SMS delivery is charged separately. Have staff approve audience rules and messages. AI should not decide whether missing consent is acceptable or promise work the team has not approved.

Measure through completed work and payment

Keep one campaign record with distinct counts for eligible contacts, attempted sends, delivered messages, unique replies, bookings, completed jobs, and collected revenue. Count people separately from messages, and distinguish interested replies from opt-outs or complaints. A delivery receipt does not prove that a message was read.

For example, hypothetically, 100 eligible contacts could yield 90 delivered messages, 12 replies, four bookings, and three completed jobs. If the bookings total $2,000 but payments received total $1,200, report $2,000 in booked value and $1,200 collected. These figures are arithmetic examples, not benchmarks or expected results.

Set an attribution window before launch, connect campaign IDs to opportunities and invoices, and reconcile refunds, cancellations, and pre-existing bookings. Report message costs and staff effort alongside revenue. Campaign-associated revenue alone does not prove incremental revenue; a suitable holdout group can help evaluate that question.

---

Plan a reactivation workflow your team can run

Bring your audience rules, stop conditions, and staff handoff to a workflow review.

See plans & pricing or schedule a demo.