Start with status definitions
An “unsold estimate” report can contain very different situations: true no-decisions, duplicate options, declined work, deferred maintenance, open opportunities, completed work under another record, and estimates that should never be recontacted. Define each status before exporting. The quality of the recovery campaign depends more on the exclusions than the message.
Export the minimum necessary fields
A useful working file typically needs a stable record identifier, customer and contact fields approved for the test, estimate date, business unit, job type, status, value, location or service area, assigned employee, last meaningful contact, and suppression indicators. Avoid exporting unrelated notes or sensitive fields simply because they are available.
Build suppression rules
Suppress active work, recently contacted customers, do-not-contact requests, complaints, unresolved warranty issues, collections matters, and records with uncertain ownership. Confirm whether other campaigns or sales teams are working the same list. A recovery sprint should not collide with normal operations.
Segment before writing copy
Replacement estimates require different context than maintenance recommendations. Financing hesitation differs from a customer who selected a competitor. Recent estimates need a continuation message; older records need an honest reintroduction. Segmenting first allows the message to be accurate without pretending to know more than the data shows.
Write outcomes back to the CRM
The recovery system should return clear disposition codes: wrong contact, not interested, project completed elsewhere, revisit later, question pending, appointment booked, appointment attended, estimate reopened, job won, and opt-out. Without write-back or a disciplined reconciliation file, the database becomes less reliable after each campaign.
Use a frozen baseline for attribution
Create a dated list of eligible records before launch. Mark which opportunities are already active, define the attribution period, and reconcile by stable ID. This allows the contractor to distinguish true incremental recovery from activity that would have occurred anyway.
What is hiding in your estimate backlog?
Request a free Pipeline Recovery Map from Gemma. No system access is needed for the first conversation.
Request the map →