Local service lead response • stale leads • CRM hygiene
A late reply can look like easy revenue, but it can also reopen stale prices, old availability, expired photos, wrong consent status, or a job that already moved on. Use this checklist before a local-service team restarts an old lead thread.
Use the free AI Lead Response Quickstart See Local Lead Rescue System
Lead/customer: [name or lead ID]
Original request date: [date/time]
Latest reply date: [date/time]
Original source: [phone / form / email / GBP / referral / marketplace / social]
Original status: [new / callback-due / quote-sent / lost-no-contact / closed / owner-review]
What changed since then: [pricing / availability / parts / service area / policy / staffing / none verified]
Consent/contact status: [call OK / text OK / email OK / unknown / do-not-contact]
Reopen owner: [person responsible]
Next safe action: [ask one detail / re-quote / schedule callback / owner review / do not reopen]
STOP AUTOMATION: Do not invent prior contact history, consent, price validity, schedule availability, diagnosis, warranty, urgency, referral quality, or customer intent.
Hi [Name] — thanks for getting back to us about [original request]. Before we reopen this, could you confirm [one current detail: address area / issue status / best callback window / photo]? We will re-check availability and details before making any promises.Review: use when the lead is still plausible but current facts are missing.
Hi [Name], we can revisit the [estimate/quote] for [job]. Because some details may have changed since [date], we need to review [scope/pricing/parts/schedule] before confirming next steps. We will follow up with the current options after review.Review: do not say an old price is still valid unless the owner has confirmed it.
Hi [Name], thanks for checking back. This request needs a quick owner review before we can reopen it because [reason: age of request / service area / schedule / policy / missing details]. We will confirm whether we can help or suggest the next safest step.Review: use this instead of inventing a referral, exception, or promise.
| Label | Use when | Required proof |
|---|---|---|
| REOPEN-REQUESTED | A stale lead replied and may need follow-up. | Latest reply timestamp and channel |
| REOPEN-NEEDS-DETAIL | The team needs one updated fact before action. | Exact missing detail requested |
| REQUOTE-REVIEW | An old estimate, quote, or price may be outdated. | Original quote date and owner review owner |
| OWNER-REVIEW | Pricing, warranty, emergency, policy, service-area, or consent risk exists. | Question for manager/owner |
| DO-NOT-REOPEN | Policy, opt-out, source rules, or current facts block follow-up. | Stop reason and reviewer |
You are helping a local service business review a late reply from an old lead. Use only the notes provided. Return: (1) original request summary, (2) latest reply, (3) prior status, (4) current unknowns, (5) consent/contact status, (6) safest next message, (7) CRM label, and (8) OWNER-REVIEW items. Do not invent prior contact attempts, consent, pricing, availability, diagnosis, warranty, emergency priority, referral options, or customer intent. If evidence is missing, write NEEDS OWNER REVIEW.
Pair this with the Stale Lead Follow-Up Templates, Lost Lead Reason Code Checklist, Callback Attempt Log Checklist, and Local Service Lead Response Resource Library.
Product signal: if late-reply reopen resources earn clicks/replies/reuse, consider adding a Local Lead Rescue worksheet for reopen status, current-fact check, re-quote review, consent status, and do-not-invent-prior-history guardrails. This run records one signal only; monitor before editing the buyer ZIP.