Every dead lead in your Lawmatics account already cost you money. The firm paid for the ad click, the directory listing, the referral relationship, or the staff hours that produced the inquiry. When the lead went quiet, that spend did not come back. The record just sits in an open stage and ages.
Reactivation is the discipline of working that list on purpose instead of letting it rot. This guide defines a dead lead in concrete Lawmatics terms, explains where the value in a cold list comes from, and walks through segmentation, sequence anatomy, list hygiene, and cadence. Everything here can be built by hand with pipelines, automations, and email templates. The point is to build it correctly, because a sloppy reactivation run burns the very list it was supposed to recover.
What counts as a dead lead in Lawmatics
A dead lead is not a lost lead. Lost is a recorded decision: the prospect hired another firm, the matter went away, or your team declined it and logged the reason. Dead is the absence of a decision. Nobody closed the record, and nobody is working it either.
In Lawmatics terms, a dead lead shows three markers. It is stage-aged: it has sat in the same open pipeline stage well past your normal intake rhythm. It has no recent activity: no replies, no form submissions, no notes, nothing new on the timeline. And it never reached the next commitment, usually a booked consultation. A record with all three markers is dormant whether or not anyone has admitted it.
Automations need a working definition, which means a threshold. A sound default is 14 days of inactivity in an open stage. That is the dormant default we install, and firms tune it against their own stage-aging data: urgent practice areas justify a shorter window, slow-deciding matters a longer one. The rule must be explicit, because staleness triggers act on rules, not feelings.
The threshold only means something if your stages do. If leads, active clients, and closed files share loose stages, inactivity cannot be measured. The Lawmatics intake pipeline guide covers stage design; get that right before wiring reactivation on top of it.
Why dead leads are worth working
The value of a dead-lead list comes from a plain accounting fact: the acquisition cost is already sunk. Every record on the list represents marketing money and intake labor that left the building long ago. A new lead requires new spend before it exists. A dormant lead requires a short sequence of plain emails that cost almost nothing to send. When one of them books, the revenue attaches to spend you had already written off. That is the entire premise, and it is why the product page for this system describes the outcome as recovering revenue you already paid to acquire.
Notice what the argument does not include: a recovery percentage. How much of a given list will respond depends on how old it is, why the leads stalled, which practice areas they came from, and how the firm handled them the first time around. None of that is knowable from the outside, so distrust anyone who quotes a recovery rate without seeing your list. The honest claim is qualitative. The downside of a disciplined pass is a handful of unsubscribes from people who were never coming back. The upside is consultations from leads you already paid for.
If you would rather buy this as an installed system than run it as a project, that is what the Ghost Revival Engine is. The rest of this guide teaches the mechanics, so you can build the sequence yourself or judge a packaged one with clear eyes.
Segment before you write a single email
A reactivation blast that treats every dormant lead the same reads like a newsletter, and these people already ignored your newsletters. The reason a lead went quiet dictates the message it should receive, so the first real work is splitting the list. Three segments cover most law firm pipelines.
- Went quiet before a consult. They inquired, maybe traded one email, and never booked. The obstacle was commitment or timing. The message asks one thing: is this still a problem you need solved? Make booking trivial and make no an acceptable answer.
- No-showed and never rebooked. They wanted the consultation enough to book it, then life interfered and rebooking felt awkward. The message removes the awkwardness: no scolding, just an open door and a scheduling link. If no-shows are a recurring leak rather than a one-time accident, fix the forward-looking side as well; the guide to cutting no-shows in Lawmatics covers reminder cascades and reschedule paths.
- Quoted but never signed. They sat the consult and received a fee quote or an engagement letter, then went silent. Highest intent, most delicate. The message asks plainly whether the sticking point was price, timing, or another firm, and it accepts any answer without a rebuttal.
Segmentation has a mirror image: suppression. Before anything sends, exclude active matters and current clients, anyone who unsubscribed or asked to stop, anyone with a recorded no, and anything flagged for conflicts. In Lawmatics this is filtering by pipeline stage, matter status, and tags, and it is not optional. One reactivation email asking a current client whether they still need a lawyer costs more trust than the whole sequence will earn back.
Anatomy of a sequence that gets replies
A working reactivation sequence is short, plain, and wired with exits. The version we install runs five messages; the exact count matters less than the properties below.
Plain text, from a person. No header image, no button, no campaign styling. A short email from a named attorney or intake manager, written the way that person actually writes. Done right, it reads as a personal check-in, which is what it is: someone at the firm reviewing open files.
A tone that permits an easy no. The goal of each message is an answer, not a yes. A line like "If you have handled this another way, reply and I will close your file" works because it lowers the cost of responding. A clear no is a win: it cleans the pipeline and ends the sequence for someone who was never going to convert.
One ask per message. Book a call, or answer one question, or confirm the file can close. Never two of those in the same email. Stacked asks read as marketing. A single ask reads as a person with a specific reason to write.
Widening spacing. The messages start close together, while the lead still remembers the previous one, and spread out as the sequence progresses. Early messages are a nudge; later messages are a quiet confirmation that the door remains open. A fixed daily drumbeat feels like collections. Widening gaps feel like patience.
Hard exits on any reply. The moment a lead replies, books, changes stage, or opts out, the automation must pull it from the sequence. Any reply means any: a no, an out-of-office, an angry one. Nothing kills the personal framing faster than message four arriving after the lead answered message two. Wire the exits into the Lawmatics automation itself; do not trust anyone to remember.
A test lead before launch. Run a test contact past the dormant threshold and watch it enter. Reply to one email and confirm the exit fires. Book the test appointment and confirm that exits it too. No sequence should touch real leads until a test lead has walked the full path in and out.
All of this is buildable by hand with Lawmatics automations and email templates. Whether you should build it by hand is a separate question, and the consultant alternative comparison weighs it properly.
List hygiene and unsubscribe honesty
Reactivation email goes to people who stopped engaging, which makes it the riskiest email a firm sends for deliverability. Hygiene comes first. Before the sequence turns on, drop hard bounces, generic role addresses, and records so old or so thin that the person could not reasonably remember the firm. A scrubbed list protects the sending reputation of the same domain your active matters rely on.
Unsubscribe handling is where reactivation programs show their character. Every message needs a working opt-out, and honesty runs deeper than the link. Treat a reply that says stop, in any wording, as an unsubscribe even though no link was clicked. Suppress opt-outs permanently, not per campaign, so a lead who left the sequence never resurfaces in a future one.
Honesty applies to content as well. The check-in framing works because it is true: the firm really is reviewing its open files. Do not invent urgency, fake a deadline, or imply the lead asked to be contacted. A law firm sells judgment, and every reactivation email is a sample of it.
None of this is special to reactivation. Every system documented in the LexLabs guides library assumes the same baseline: clean lists, honest opt-outs, and automations that respect a no.
Run it quarterly, not as a blast
A one-off blast treats reactivation as an event: export the cold list, hit it once, absorb the unsubscribes, forget about it for a year. A system treats reactivation as maintenance, with two layers running on different clocks.
The automation layer runs continuously. Staleness triggers watch for inactivity, and any lead that crosses the dormant threshold enters the sequence on its own, whether it went cold this week or last quarter. Non-responders are not recycled through the same messages; they exit to a lost-lead long-term nurture, a low-frequency campaign that keeps the firm findable, because legal problems resurface on their own schedule and dead today is not dead forever.
The review layer is quarterly and human. Open the stuck-leads report and read what the system did: what entered, what replied, what exited to nurture. Look for patterns, not records. One practice area stalling disproportionately points upstream to its intake. Leads dying repeatedly in one stage point to a mislabeled stage or a broken handoff. A sequence that only ever touches ancient records points to a threshold set too loose. Flag the few high-value files that deserve a phone call instead of another automated email.
When the same stall appears quarter after quarter, it stops being a reactivation problem and becomes a systems problem, and someone has to fix it. The consultant versus productized install guide maps that decision.
The list is already paid for. Keep the sequence short, keep the exits strict, keep the cadence quarterly, and work the list like the asset it is.