Storm Lead Follow-Up: Fix the CRM Graveyard

Picture the week after a hail event: 642 names in the CRM, 117 with no owner, three versions of “inspection scheduled,” duplicate spouses in different stages, and follow-up tasks created by an automation nobody trusts. Another seven-message cadence will not rescue that queue. It will amplify the bad records.

A storm-lead graveyard is a data cleanup and ownership job before it is a persuasion job. Preserve permission, remove duplicates, rebuild the stage from actual activity, assign one owner, and write one useful next action. This page starts after the lead exists; the roofing lead-channel guide owns acquisition.

Define the graveyard before touching it

Do not let “old lead” become the only filter. Build a rescue view from verifiable activity:

• no owner;
• no next action or overdue next action;
• stage unsupported by the activity record;
• appointment scheduled without confirmation;
• inspection completed without a documented customer update;
• duplicate or conflicting record;
• missing source or contact-permission evidence;
• paused record without a customer-selected future date; or
• opt-out, wrong party, invalid data, or closed project still receiving messages.

The last group is not a re-engagement queue. It is a suppression and correction queue.

Create a minimum trusted storm-lead record

Do not buy, enrich, call, text, or email a list merely because a vendor labels it “storm leads.” Verify provenance and permitted use for the actual channel. The FTC’s Telemarketing Sales Rule guidance and the FCC’s consent-revocation order and guidance illustrate why source, permission, opt-out, and suppression controls belong in the operating record. Federal and state requirements vary by workflow; qualified counsel should review the program.

Restage every lead from customer reality

“Follow-up” is not a stage. It describes an activity. Stages should answer what has happened and what decision is pending.

1. New permitted inquiry: awaiting the first allowed response.
2. Connected: customer need clarified; next option not selected.
3. Appointment proposed: specific options sent; none accepted.
4. Appointment scheduled: date, time, location, and owner recorded.
5. Inspection completed: observations exist; customer update pending or complete.
6. Scope or estimate review: controlling document delivered; questions or decision pending.
7. Customer-selected pause: reason and future date recorded.
8. Project moving forward: next operational handoff documented.
9. Closed: completed, declined, duplicate, invalid, no-contact, or another specific outcome.

The sales pipeline template can turn those stages into explicit entry evidence, exit evidence, owners, and aging rules.

Five records on the rescue board

This board prevents a common mistake: ranking every dormant record by potential revenue before determining whether the company may or should contact it.

Send one message that advances one decision

New inquiry

“Hi [name], this is [rep] with [company]. You contacted us on [date/source] about [customer-stated issue]. The next available step is [accurate option]. Would [option one] or [option two] work better? [Required channel-specific identification and opt-out language].”

Appointment not confirmed

“We have [appointment type] listed for [date/time/time zone] at [location]. Reply CONFIRM, CHANGE, or [approved stop method]. We will not inspect or access the property without the agreed permission.”

The appointment-confirmation tool creates a factual draft from verified logistics.

Inspection update overdue

“We completed the [date] inspection and owe you an update. [Owner] is reviewing [documented observations or scope] and will contact you by [time]. This update will describe contractor observations; policy and coverage decisions remain with the insurer.”

Customer-selected pause

“You asked us to pause until [date/reason]. Should we close the record, contact you after [selected date], or help with [truthful next option]? If your preference changed, tell us and we will update the record.”

Do not imply claim deadlines, material scarcity, neighborhood eligibility, or storm damage unless the statement is current, verified, applicable, and approved.

Use the cadence page for timing—not this rescue page

The right timing depends on the request, channel, permission, local rules, project urgency, staffing, and previous response. The roofing follow-up cadence guide owns maximum attempts, quiet hours, channel sequencing, and stop conditions. This page owns record repair and queue recovery.

A record cannot become contactable merely because time passed. Before adding it to a sequence, confirm that the purpose, channel, permission, and data remain valid.

Run a 20-minute exception review

1. Suppress first: opt-outs, wrong parties, invalid contacts, and duplicates.
2. Protect promises: customer updates and appointments due today.
3. Assign ownership: no record leaves the review with two owners or none.
4. Restage from evidence: correct unsupported statuses.
5. Write the next action: one action, one owner, one due time.
6. Escalate system failures: automation after opt-out, missing permission record, or repeated broken handoffs.

The remote sales-management guide provides the broader dashboard and manager cadence. The lead-qualification checklist keeps fit and routing separate from follow-up pressure.

Measure recovery without hiding the denominator

Segment by storm event, source, channel, stage, and cohort. Do not compare a fresh inbound web inquiry with a purchased record of unclear provenance and call the difference “rep performance.”

Frequently asked questions

How many times should a roofer follow up with a storm lead?

There is no universal number. The company needs a reviewed cadence by source and channel, supported permission, maximum attempts, quiet hours, and stop rules.

Should old storm leads be reactivated automatically?

No. Verify purpose, provenance, contact permission, current data, suppression status, and the customer’s last instruction before any re-engagement decision.

What is the first step when the CRM has hundreds of stale leads?

Separate suppression and invalid-data work from contactable records. Then repair stage, owner, and next action before prioritizing outreach.

A clean queue beats another cadence

The storm lead graveyard is not fixed by asking reps to “follow up harder.” Build a trusted record, honor permission and stop states, restage from customer reality, assign one dated action, and work exceptions every day. Recovery begins when the CRM tells the truth.