Lead Reactivation by Text: Campaign Plan, Templates, and

A lead reactivation campaign is a structured attempt to restart conversations with people who previously asked about your service but did not book. It is not permission to text every old number in your database.

A useful campaign has six parts: an eligible list, meaningful segments, honest messages, clear reply ownership, immediate opt-out handling, and measurement. Build those before you schedule a blast.

This guide gives you the full workflow and copy-paste texts. It is written for previously consented leads; it is not legal advice. Consent requirements depend on the message, technology, jurisdiction, industry, and how the lead originally opted in.

#Before you text: build an eligible reactivation list

Start with permission, not copywriting. An old inquiry does not automatically prove that you can send a new marketing campaign today.

For each record, confirm that you can answer these questions:

Where and when did the person provide the number?
What language did they agree to?
Which business did they expect to hear from?
What service or request created the relationship?
Has the person opted out, asked not to be contacted, complained, or been added to a suppression list?
Is the number still associated with the same person?
Do applicable federal, state, industry, and carrier rules allow this message and sending method?

Exclude a record when the consent trail is missing or does not cover the planned outreach. Also exclude customers whose issue was resolved, leads marked as duplicates or bad numbers, contacts with active disputes, and anyone on an applicable do-not-contact list.

For calls and texts covered by the federal rule, 47 CFR § 64.1200 recognizes several ways a person can revoke consent, including replies such as STOP, QUIT, END, REVOKE, OPT OUT, CANCEL, and UNSUBSCRIBE. It also requires reasonable natural-language requests to be recognized in covered situations. Your safer operating rule is simpler: if someone communicates that they do not want more messages, suppress the number immediately.

Have qualified counsel review the campaign when the legal basis, consent language, audience, or jurisdiction is unclear. A texting tool can enforce your workflow, but it cannot decide whether you had permission in the first place.

#Segment the list before writing the message

A person who requested a roof estimate last month should not receive the same text as someone who asked about a maintenance plan a year ago. Segmentation keeps the context recognizable and makes replies easier to route.

Use fields you can verify rather than guesses about the person:

Prior request

Group leads by the service, quote, appointment, or project they actually asked about. The message should name that context without exposing sensitive details.

Last known outcome

Separate leads who postponed, received an estimate, stopped responding, chose another provider, or never completed the first step. Each group needs a different reopening question.

Age and data quality

Newer dormant records may have clearer context. Older records deserve stricter review for stale consent, changed circumstances, and reassigned numbers. Do not use age alone as proof of either eligibility or interest.

Practical next step

Decide what a positive reply should lead to: answering a question, updating an estimate, checking availability, scheduling a call, or closing the record. Do not send the campaign until somebody owns that next step.

Keep uncertain records out of the pilot. “Maybe eligible” is not a useful segment.

Turn segments into message plans

Write one row in your campaign plan for each audience before choosing a template. For example:

Recent estimate, decision postponed: include only records with verified consent and notes that timing was the issue; ask whether the timing changed; use the timing-was-wrong template; route a positive reply to an estimate owner.
Estimate sent, outcome unknown: exclude records marked won, lost to another provider, disputed, or opted out; ask whether an update would help or the request should close; use the estimate template; route UPDATE to the estimator.
Consultation requested but never scheduled: include only records with a documented incomplete booking; offer to send current options without claiming an opening; use the unfinished-booking template; route YES to the scheduler.
Older record with weak context: do not send until the team verifies the original request, consent scope, identity, and a relevant next step. If those facts cannot be verified, exclude it rather than using a generic message.

This matrix ties service context, prior outcome, record age, fit, exclusions, next step, and message version together. Add a separate row when any of those facts changes materially.

#Build a small pilot campaign

A pilot should be small enough that your team can inspect every reply and fix a problem before more messages go out. The right size depends on staffing and normal response volume, not a universal benchmark.

Before launch, write down:

Eligible segment: the exact inclusion and exclusion rules.
Campaign objective: for example, identify people who still want an updated estimate.
Single next step: the action requested in the text.
Sender identity: the person and business the lead will recognize.
Reply owner: the employee who will handle each response type.
Stop conditions: opt-out, wrong number, negative response, booking, or manual escalation.
Sending controls: applicable hours, frequency limits, suppression checks, and any required registration or platform review.
Tracking fields: message version, delivery result, reply category, booking result, opt-out, and notes.

Send the pilot while the reply owner is available. Reactivation fails operationally when a business restarts a conversation and then leaves the response unattended.

#Lead reactivation text templates

Replace every bracketed field with verified information. Keep only claims that are true. The first message should identify the business, restore context, ask one easy question, and include the opt-out language your campaign requires.

1. Simple context restart

Copy: “Hi [First name], this is [Name] with [Business]. You reached out about [service] in [month]. Is that still something you want help with? Reply YES and I’ll help with the next step. Reply STOP to opt out.”

Use this when the original request and date are clear, but you do not know why the conversation ended.

2. Estimate follow-up

Copy: “Hi [First name], [Name] from [Business] here. We prepared an estimate for [service] earlier. Would an updated estimate be useful, or should I close the request? Reply UPDATE or CLOSE. Reply STOP to opt out.”

This gives the lead two simple choices and helps clean the pipeline even when the answer is no.

3. Timing-was-wrong restart

Copy: “Hi [First name], it’s [Name] at [Business]. When we last spoke about [service], the timing wasn’t right. Has that changed, or would you rather we leave the request closed? Reply NOW, LATER, or CLOSE. Reply STOP to opt out.”

Use only when your notes actually say timing was the issue.

4. Unfinished booking or consultation

Copy: “Hi [First name], this is [Name] with [Business]. You had asked about a [consultation/appointment] for [service], but we never finished scheduling it. Would you like me to send the current options? Reply YES or NO. Reply STOP to opt out.”

Do not insert specific availability until it has been checked.

5. Question-led restart

Copy: “Hi [First name], [Name] from [Business]. You contacted us about [service] a while back. What would be most useful now: pricing, timing, or a quick call? Reply PRICE, TIME, CALL, or CLOSE. Reply STOP to opt out.”

Use this when your team can respond consistently to each option.

6. Seasonal service reminder

Copy: “Hi [First name], this is [Name] with [Business]. You previously asked about [service]. We’re checking whether it is back on your list for [season/time period]. Want to revisit it? Reply YES or NOT NOW. Reply STOP to opt out.”

A season is context, not manufactured urgency. Do not imply a deadline, shortage, or weather event that is not real.

7. Genuine update

Copy: “Hi [First name], [Name] at [Business]. Since your earlier [service] request, [brief factual change]. Would you like the updated details? Reply YES and I’ll send them. Reply STOP to opt out.”

Use this only for a real, relevant change—such as a verified service-area update or a newly available appointment type. Never invent a discount, price drop, nearby job, rebate, or cancellation to create a response.

8. Second touch

Copy: “Hi [First name], following up once on your earlier [service] request with [Business]. If you still want help, reply YES and [Name] will pick it up. If not, reply CLOSE. Reply STOP to opt out.”

This message should make it easy to end the conversation, not pressure the lead for ignoring the first text.

9. Final close-the-loop message

Copy: “Hi [First name], we’ll close your earlier [service] request for now. If you want to revisit it, reply REOPEN and [Business] will help. Otherwise, no reply is needed. Reply STOP to opt out.”

After this message, stop the reactivation sequence. A lead who remains silent should not roll automatically into another campaign.

#A practical three-touch sequence

You do not need a long drip to learn whether a dormant lead still wants help.

Touch 1: Send the most relevant segment-specific restart message.

Touch 2: If there is no reply, send one short follow-up after several business days. Restate the business and original context.

Touch 3: After another reasonable interval, send the close-the-loop message and end the sequence.

Pause scheduled messages as soon as a person replies. Do not make someone receive the second campaign text while an employee is already answering the first.

The sequence also ends on an opt-out, wrong-number report, negative response, booking, complaint, or manual hold. Document the reason so the record is not accidentally added to the next batch.

#Route replies instead of improvising

The message is only the opening. Decide the branch for each common reply before launch.

Interested now

Copy: “Thanks, [First name]. I can help with that. To make sure I send the right next step, are you looking for [option A] or [option B]?”

Ask one useful qualifying question, then move toward the estimate, call, or appointment your team actually supports.

Has a question

Copy: “Absolutely—send the question here. If it needs a specialist, I’ll route it to [role/name] and let you know who is following up.”

Do not force a booking before answering the question that reopened the conversation.

Interested later

Copy: “Understood. What month would be better for one check-in? I’ll note that, and we won’t keep sending this reactivation sequence.”

Record the requested timing and the basis for any future message. “Later” is not permission for unlimited reminders.

Not interested

Copy: “Thanks for letting us know. I’ll close this request and stop the campaign messages.”

Close the campaign branch. If the person also asks not to receive future texts, add the number to the appropriate suppression list.

Wrong person or reassigned number

Copy: “Thanks for telling us. We’ll remove this number from the record and stop the messages. Sorry about that.”

Suppress the number immediately and investigate the source record before using it again.

Opt-out or other stop request

Use the confirmation behavior required for your platform and applicable rules, then send nothing promotional after it. Your system should recognize standard keywords and natural-language requests such as “don’t text me,” not just an exact uppercase STOP.

If a one-time confirmation is permitted or required for your workflow, keep it purely administrative:

Copy: “Opt-out confirmed. [Business] will not send more marketing texts to this number.”

Never argue with an opt-out, ask the person to explain, or make them complete another step.

#Test without muddying the result

Run the first batch as a controlled test, not a contest between five completely different campaigns.

Choose one variable:

opening question;
requested reply format;
send window permitted by your rules;
context level;
message length; or
segment definition.

Keep the audience rules, offer, reply owner, follow-up spacing, and measurement window consistent. If version A targets recent estimates and version B targets year-old general inquiries, the result cannot tell you which message was better.

Log the assigned version before sending. Do not move poor results from one version into another after replies arrive. Review reply quality and opt-outs, not just total responses: “wrong person” and “stop” are replies, but they are not campaign wins.

#Measure the campaign

Use counts and formulas your team can reproduce. Define each metric before launch.

Delivery rate: delivered messages ÷ attempted messages.
Delivery error rate: failed or undelivered attempts ÷ attempted messages. Define the delivery statuses counted as errors before launch.
Human reply rate: unique leads with a human reply ÷ delivered messages. Exclude carrier errors and automated system notices.
Positive reply rate: unique leads who indicate current or future interest ÷ delivered messages.
Booking rate: leads who complete the campaign’s target booking ÷ delivered messages. You may also calculate bookings ÷ positive replies to inspect the handoff.
Opt-out rate: unique opt-outs ÷ delivered messages.
Wrong-number rate: unique wrong-person or reassigned-number reports ÷ delivered messages.

Track raw counts next to rates. A percentage without its denominator can make a tiny test look more certain than it is.

A simple campaign scorecard needs these columns:

Scorecard fields: lead_id, segment, message_version, attempted_at, delivery_status, delivery_error_reason, reply_category, replied_at, owner, booked_at, opt_out, notes

Do not put sensitive message content into a report that does not need it. Limit access and follow your retention policy.

#Diagnose the result before scaling

Different patterns point to different problems:

Many delivery errors: pause and clean the data source. More copy changes will not fix stale numbers.
Many wrong-person replies: investigate list age, imports, and number verification before another batch.
Many opt-outs: stop scaling. Recheck consent scope, audience selection, sender recognition, frequency, and message expectations.
Delivered but few replies: inspect whether the context is recognizable and the requested action is easy. Compare results by segment before rewriting everything.
Replies but few qualified conversations: the message may be too broad or the segment may contain weak-fit records.
Positive replies but few bookings: inspect response time, ownership, qualification, availability, and the handoff—not just the opening text.
Bookings with no unresolved compliance warning: recheck eligibility, complaints, opt-outs, and wrong-number reports against thresholds approved for your campaign. If the review passes, document what stayed constant, expand gradually, and continue monitoring rather than assuming the result will hold forever.

There is no universal “good” reactivation rate that makes every list, service, and consent history comparable. Establish your own baseline from clearly defined, lawful campaigns.

#Common reactivation mistakes

Treating the database as permission. A stored phone number is data, not a complete consent record.

Blasting one generic message. Missing context makes the text look unfamiliar and makes replies harder to route.

Using fake urgency or proof. Do not claim an opening, deadline, neighborhood job, savings figure, or price change unless it is true and supportable.

Sending before assigning an owner. A positive reply loses value when nobody knows who should answer it.

Counting every reply as success. Opt-outs and wrong-number reports are operational signals, not positive demand.

Letting the sequence continue after a reply. Scheduled messages should pause while a human conversation is active.

Recycling silent leads automatically. End the sequence and require a fresh eligibility decision before any later campaign.

#Where automation helps

Once the manual pilot is sound, automation can apply repeatable timing and suppression rules while keeping replies visible to the team. SecureMyLead supports reactivation campaigns, SMS sequences, two-way replies, and automatic opt-out handling for recognized keywords. Natural-language stop requests still require human attention when they do not match a supported keyword.

The business still owns consent, campaign eligibility, message truthfulness, and lawful use. Automation should enforce a reviewed process—not make an uncertain list send faster.

For broader message strategy, see How to Follow Up With Leads Using Text Message. To diagnose the original leak, read Why Your Leads Go Cold and How to Fix It. If the conversation stalled recently rather than months ago, use What to Do When a Lead Stops Replying instead of launching a reactivation campaign.