← All filesStatus: delivered · live
CS-02 // Dossier
Dead-Lead Reactivation Engine
A 30-day reactivation system that works a cold lead list automatically — 15 sequenced touches, AI intent detection, and hot replies handed straight to the booking bot — then cleanly sunsets the rest.
Exhibit // CS-02
R-02 · interface redrawn from the live build — zero client pixels
- Client
- R-01SEALED UNDER NDA. SPECIFICS WALK THROUGH LIVE. → BOOK
- Industry
- Local service business with a cold lead list
- System
- Dead-Lead Reactivation Engine
- Stack
- GoHighLevel · Conversation AI · SMS · Email
- Trigger
- A cold list import — hundreds of unworked leads
- Metrics
- System scope
01 // The problem
Hundreds of old, unworked leads sat dead in the CRM. Manual reactivation never happened, and there was no safe way to re-message them without colliding with live campaigns.
02 // The system
Redrawn — no client data
The system
03 // The delta
Before and after go-live
Before
- Hundreds of old, unworked leads sat dead in the CRM
- Manual reactivation never happened
- No safe way to re-message without colliding with live campaigns
With the system
- 100% of the dead list worked automatically, end to end
- Hot replies routed straight to booking, no manual triage
- Zero cross-campaign collisions, validated by an 8-scenario test plan
04 // What got done
6 entries
- B-01Built a one-shot 30-day drip — 7 SMS and 8 emails on a paced schedule — that works the entire cold list end-to-end with no manual effort
- B-02Ran AI intent detection on every reply, pulling positive-intent leads out of the drip and handing them to the AI booking concierge to close
- B-03Wired an automatic booking-exit so a booking on any calendar removes the lead from the campaign and tags the win
- B-04Added a day-30 sunset that hands non-responders off to an ongoing quarterly reactivation track instead of abandoning them
- B-05Ran a cross-pipeline isolation audit so the reactivation campaign never double-messages or fires other live workflows
- B-06Documented a tag taxonomy, a CSV import runbook, and an 8-scenario end-to-end test plan to validate the whole flow before launch
05 // Outcome
System scope — capability metrics, honestly labeled
- → Scope
of list worked automatically - 0%
- → Scope
over 30 days - 0 touches
- → Scope
cross-campaign collisions - 0
06 // The result
From the build log
- 100% of the dead list worked automatically, end to end
- Hot replies routed straight to booking with no manual triage
- Zero cross-campaign collisions, validated by an 8-scenario end-to-end test plan
- Non-responders handed off cleanly instead of abandoned
Want a system like this one?
Free · 30 min · leave with a rough scope either way