Dead Lead Reactivation with iMessage
The short answer
Reactivate dormant leads via iMessage. Texts open 98%, read in three minutes. Already paid for; reactivation is cheapest. Segment by age and stage, pace capacity, write naturally.
4 use cases in this category
Trigger
Event in your CRM
Under 60s
Send iMessage
Result
Reply in the thread
Key takeaways
- A dormant list costs twice: acquisition spend you already paid (ad clicks, referral fees, SDR time), plus depreciation while it sits unused.
- Segment on two axes: when the contact went quiet, and where they stopped.
- The play runs in four moves: pull and clean, pilot, read replies, then ramp.
- Pacing protects your team's ability to answer: your campaign's actual cap.
- The message to someone who ghosted months ago has one job: make reply easier than ignoring it.
- CRM setup for a reactivation run has three parts: the segment queries, the send trigger, and where replies land.
Reply rate by outbound channel
What does a dormant list actually cost you?
A dormant list costs twice: acquisition spend you already paid (ad clicks, referral fees, SDR time), plus depreciation while it sits unused. Reactivation is the only motion where acquisition cost is zero.
- Lists stay dead because reactivation runs on the failed channel: email. Opens at 27.7%, 85% flagged as spam, cold replies at 0.45% (Belkins, 7.5M+ sends, 2025). A fifth email isn't a plan.
- Texting changes it: under 3% get flagged as spam, iMessage drives 2-3x the reply rate of email. At $249/mo with unlimited iMessages paced at 50 opted-in / 30 cold new conversations a day, re-approaching 12,000 records costs one line.
- Records depreciate quietly. Nobody schedules a meeting about the contacts that went cold last spring.
- Reactivation gets handed to whoever has spare time, which means it gets run as a single blast.
- A past customer and a never-engaged form fill end up receiving the same message.
- Reply volume outruns the team on day one, answers slip two days, and the list gets burned for real.
How should you segment a dormant list?
Segment on two axes: when the contact went quiet, and where they stopped. Age tells you how much context to rebuild. Last stage tells you what to ask for. A proposal ghost and a form fill are different audiences.
- Send warmest first, always. Highest reply rate is exactly when your team learns to handle inbound. By the time you reach colder slices, your responses are sharp and objection handling is written down.
Proposal ghosts
- Time since last activity
- 1 to 6 months
- Last stage reached
- Quote or proposal sent, no decision
- Opening angle
- Name the document you sent and ask if it's dead
No-shows
- Time since last activity
- 1 to 9 months
- Last stage reached
- Booked, never attended
- Opening angle
- Name the date once, no guilt, then two time options
Replied then vanished
- Time since last activity
- 3 to 12 months
- Last stage reached
- Real two-way thread, then silence
- Opening angle
- Pick the thread back up mid-conversation
Closed lost on budget
- Time since last activity
- 6 to 18 months
- Last stage reached
- Passed on price or timing
- Opening angle
- Lead with what changed on your side
Closed lost to a competitor
- Time since last activity
- 9 to 18 months
- Last stage reached
- Chose someone else
- Opening angle
- Ask how that decision worked out
Former customers
- Time since last activity
- 6 to 24 months
- Last stage reached
- Bought, then churned
- Opening angle
- Reference what they bought, not a pitch
Never responded
- Time since last activity
- Any age
- Last stage reached
- Form fill or import, zero engagement
- Opening angle
- Treat as cold, send last, in small batches
How the reactivation play runs, step by step
The play runs in four moves: pull and clean, pilot, read replies, then ramp. Sending spans three weeks. Every send lands in the recipient's local window to avoid reading as automation.
- Days 1 to 2, pull and clean. Build the segment queries, dedupe, drop records with no mobile number, and run availability checking so you know your blue, RCS, and SMS split before launch. Suppress anyone who already opted out anywhere else in your stack.
- Day 3, pilot batch. Send 150 to 300 contacts from your single warmest segment. One message, one send window, nothing else that day.
- Days 4 to 5, read what came back. Reply rate matters less than what the replies say. If three people ask which company you're with, the opener is broken and you fix it before another contact sees it.
- Days 6 to 20, ramp one segment at a time. Widen daily volume in steps, watching opt-out rate as the brake and booked calls as the scoreboard.
- Follow-up fires on its own. Three touches is the right shape here: the opener, a short nudge on day 4, a close-the-loop message on day 11, then stop. Sequences support 1 to 12 steps with delays from 15 minutes to 90 days, so longer is available and reactivation isn't where you spend it.
How do you pace it without torching the list?
Pacing protects your team's ability to answer: your campaign's actual cap. A delayed reply teaches the prospect you don't respond. Start at volume your team clears inside an hour, raise only when they have time.
- Never send a full segment in one day. Split across three to five days so a bad opener costs 400 contacts instead of 4,000, and opt-out rate has time to surface. The table counts from day 3 overall once cleaning is done.
Send day 1
- What's sending
- Warmest segment: proposal ghosts and no-shows
- New contacts that day
- 150 to 300
- What you're watching
- Reply sentiment and how fast your team answers
Send day 2
- What's sending
- Nothing new, work the inbound
- New contacts that day
- 0
- What you're watching
- Whether every reply got a same-day answer
Send days 3 to 5
- What's sending
- Rest of the warmest segment
- New contacts that day
- 400 to 600
- What you're watching
- Opt-out rate and whether reply quality held
Send days 6 to 10
- What's sending
- Replied then vanished, closed lost
- New contacts that day
- 800 to 1,200
- What you're watching
- Booked calls, not replies
Send days 11 to 18
- What's sending
- Former customers, then never-responded
- New contacts that day
- 1,200 to 2,000
- What you're watching
- Cost per booked call by segment
4 days after each batch
- What's sending
- Nudge step fires on that batch only
- New contacts that day
- 0
- What you're watching
- Second-touch reply lift
11 days after each batch
- What's sending
- Close-the-loop step, then that sequence ends
- New contacts that day
- 0
- What you're watching
- Cumulative opt-outs across the run
Everything above describes the mechanism. The Blue Funnel Map marks the stages where your own funnel is losing replies, and you keep the map whether or not you buy.
Map this against your funnelWhat do you actually say to someone who ghosted you?
What do you actually say to someone who ghosted you?
The message to someone who ghosted months ago has one job: make reply easier than ignoring it. Two or three lines, one question. No reintroduction, no offer stack, no 'just checking in.' Lowercase reads as human.
- Opt-out language stays out of the message body. STOP and plain-language opt-outs are handled account-wide.
- Each example names the specific thing that happened: that's the trick. Generic copy fails because the recipient has to remember who you are. Hand them the date, document, or call, and replying gets cheap.
- Proposal ghost, four months quiet: "hey marcus, dan here. we sent that proposal over in march and i never chased it. totally fine either way, is that still live or should i close it out?"
- No-show, seven months quiet: "hi dana, you had a slot with us back in january and life clearly happened. no worries at all. i've got tuesday 11 or thursday 2 open if you still want to see it."
- Closed lost on budget, eleven months quiet: "hey priya, you passed last august on price, which was fair at the time. our pricing changed since then and i think it lands where you needed it. worth ten minutes?"
How to set it up in your CRM
How to set it up in your CRM
CRM setup for a reactivation run has three parts: the segment queries, the send trigger, and where replies land. Get the queries right and the rest is wiring.
- GoHighLevel is native: build a smart list per segment, attach a workflow to your line. Other CRMs connect via REST API and webhooks: pull the segment, post the send, subscribe to delivery states, write status back.
- Availability checking before send shows which contacts get a blue bubble and which fall through to RCS, then SMS.
- Scheduled sends fire inside each recipient's local window, which matters on any national list.
- STOP and plain-language opt-out handling is enforced account-wide, so a suppression here applies to everything else you run.
- Read receipts separate read-and-ignored from never-read, which are two different follow-up problems and want two different second touches.
- Old records often carry an email and no mobile, and those rows drop out at the cleaning step. The mobile-validated B2B leads add-on is a separate source of contacts at $0.03 each from a 700M+ database, billed monthly with the line.
How do you know whether it worked?
How do you know whether it worked?
Measurement on reactivation shouldn't lead with reply rate. Reply rate tells you whether the opener works. Recovered pipeline tells you whether the campaign was worth running; on old lists these diverge constantly.
- Run each segment as its own campaign so numbers stay attributable. A single blast across 12,000 records teaches you nothing about which part deserves another pass next quarter.
- Recovered pipeline value per 1,000 contacts messaged, broken out by segment. That number decides whether you re-run the play next quarter.
- Cost per booked call. A line is $249 a month, or about $162.50 on the annual plan, with unlimited messages, so the spend is flat and the only thing moving is how many calls you book. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered.
- Reply-to-booked conversion per segment. High replies with low bookings is a copy problem. Low replies with high bookings deserves more volume.
- Opt-out rate per segment, checked daily. A rising number on one slice means the consent story or the targeting is off for that slice, not for the list.
- Median time from inbound reply to your first response. Keep it under an hour or the pacing table is fiction.
What about consent on a list this old?
What about consent on a list this old?
Consent matters before first send: age doesn't erase or create it. TCPA governs texting on every channel. FCC consent-revocation rules took effect 11 April 2025; revoke-all extends to 31 January 2027 (DA 26-12).
- A2P 10DLC governs carrier SMS routes. iMessage is not carrier SMS, so no A2P registration is required. That's a registration distinction, not a consent exemption.
- Document where each segment's consent came from before you message it. A past customer and an imported list carry different obligations, and segmentation keeps them apart.
Frequently asked questions
How old is too old to reactivate a lead?
Age matters less than what the contact did before going quiet. A proposal ghost from 18 months ago is a better message than a form fill from six weeks ago that never engaged. Use age to decide how much context to rebuild in the opener, and use last stage to decide what to ask for.
Won't texting someone who ghosted eight months ago annoy them?
No, when it's short and specific. Ghosting is usually about timing, not rejection. A text that names the exact thing you sent reads as courteous. What annoys people is a reintroduction paragraph or a fourth follow-up after they said no.
Do I need consent to text a lead who only gave me an email address?
Yes. Consent follows the contact record, and TCPA governs business texting regardless of which app the message arrives in, so the question is what that person agreed to when they entered your database. Audit each segment's consent source before it sends, which is one more reason to run segments as separate campaigns.
How many contacts should go out on day one?
Day one should be 150 to 300 contacts from your single warmest segment and nothing else. The pilot exists to test the opener and time your team's response speed, not to produce pipeline. If every reply gets answered inside an hour and the copy holds, widen to 400 to 600 a day, then higher as colder segments come in.
What reply rate should I expect from a dormant list?
Reply rate depends on your segments, offer, and record age, so pilot first. The known gap: iMessage drives 2-3x the reply rate of cold email (0.45% across 7.5M sends, Belkins 2025). Run 300 contacts and build from the real number.
Do I need A2P 10DLC registration to run a reactivation campaign?
No A2P registration is required. A2P 10DLC governs US carrier SMS routes, and iMessage is not carrier SMS, so there's no brand submission, no campaign vetting, and no waiting period before a reactivation campaign goes live. Consent obligations under TCPA apply exactly as they would anywhere else.
What happens to contacts on my list who aren't on iPhone?
Non-iPhone contacts receive via RCS, then SMS fallback. Availability checking before send shows your blue, RCS, and SMS split. iPhone households sit near $85k median income, 40% above Android; the blue-bubble slice is worth protecting.
How many follow-ups before I stop?
Three touches is the right shape: opener, nudge at day 4, close-the-loop at day 11. Sequences support 1-12 steps with 15-minute to 90-day delays, so longer is possible. On a dormant list, longer mostly buys opt-outs. Someone ignoring three texts is telling you something.
Wake the list you already paid for
Pick your warmest dormant segment, 300 contacts, one dedicated line, and run the pilot this week. Setup is white-glove and managed for you, activation is waived on annual billing, and a line runs $249 a month with unlimited iMessages and no per-message fees. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered. Book a walkthrough and we'll segment your database on the call.