An old estimate is not automatically a forgotten opportunity, a duplicate lead, or permission to send another message. It is a record that needs context before a team decides what to do next. The estimate may be waiting on the customer, waiting on an internal correction, outside the current service area, or related to a newer request.
The first question is not whether the estimate looks stale. It is what customer-facing event supports the next decision. A proposal that was sent is different from a proposal that was drafted. A voicemail is different from a connected call. A note that says "follow up later" is not the same as a current request to continue.
Start with the source event
For an old estimate follow-up, record the source, received date, service requested, owner, estimate date, last verified customer-facing event, and next action. Keep the evidence date visible. A two-year-old estimate may still matter if the customer reopened the request yesterday, while a recent estimate may be inappropriate for contact if there is a clear stop signal.
If the source event is missing, use Hold or Missing Context. Do not create a confident follow-up reason from a blank field. If two records share a name or phone number, compare the requested service, location, source and timing before deciding that one is a duplicate. The same customer can make a new request.
Use a small review sample
An old estimate lead cleanup checklist can start with 10 to 25 redacted rows from different owners and sources. Include a few estimates with clear next actions, a few with no recent event, and a few where the relationship to another lead is uncertain. Remove passwords, payment details, recordings, full unredacted conversations, health or legal records, and unrelated personal history.
For each row, ask:
- What event created the record?
- What customer-facing event is actually verified?
- Who owns the next decision?
- What would stop another message?
- What evidence would change the current state?
AI Cleanup Doctor can organize a redacted browser sample into Ready, Hold, Duplicate, Do Not Contact, and Missing Context. It does not send messages, change a CRM, or decide contact permission. The owner checks the evidence and decides whether a follow-up is appropriate.
The useful outcome is not a larger list of old estimates. It is a smaller list with an explainable next decision. That makes a handoff easier and reduces the chance that a tidy status field will be mistaken for a customer outcome.
Start with a bounded review: Missed Lead Recovery.
Review boundary: This article organizes supplied evidence. It does not prove consent, lead quality, customer intent, platform fault, calls, jobs, rankings, orders, ROI, revenue or AI citations.