AI Cleanup Doctor

Product-first field guide

When a Contractor Says the Leads Are Bad, Check the Handoff First

Reviewed July 18, 2026 | Human-reviewed workflow guidance | Main topic: contractor lead follow up.

Review boundary: This article organizes safer first-step decisions. It does not prove consent, customer intent, recoverable revenue, calls, jobs, rankings, orders, ROI, platform fault, traffic, customers, or AI citations.

Contractors often call a lead source bad when the real failure happened after the lead arrived. That does not mean vendors are always clean, and it does not mean every lead deserves another contact. It means the first review should separate demand quality from handoff quality before the business spends more money or cuts a channel too quickly.

The first question is simple: can the team show what happened to the request? A usable contractor lead follow up audit should show the source event, the first person or system that received it, the owner of the next action, the last customer event, and any reason contact should stop. If those pieces are missing, the business does not yet know whether the lead was bad, ignored, duplicated, delayed, outside service area, or waiting on a human decision.

This is where a small redacted sample helps. Instead of exporting an entire CRM or giving someone an inbox login, take 10 to 25 mixed rows: web forms, missed calls, old estimates, referral notes, and a few records marked contacted. Remove names, full phone numbers, payment data, private notes, and anything unrelated to the decision. Then sort the rows into plain outcomes: Ready, Hold, Duplicate, Do Not Contact, and Missing Context.

Ready is narrower than most teams think. A ready row has enough source, owner, context, permission, and next action for a human to approve a modest draft. Hold means a decision is missing. Duplicate means two rows may describe one person or job. Do Not Contact means a stop signal exists. Missing Context means the record is too thin to use safely. That set of labels is less exciting than a dashboard score, but it is more useful when someone has to decide what to do next.

The mistake is treating "no answer" as proof that the lead was worthless. A customer may not answer because the first call was late, the form confirmation went nowhere, the estimate owner changed, the wrong service area was selected, or the person already opted out. Those are different problems. A better review keeps those differences visible.

Use the local-only Missed Lead Recovery tool first: https://cleanup.stoga.com/missed-lead-recovery. It does not send messages or change a CRM. It only helps the owner see whether a small sample can be sorted without guessing. If the unclear rows matter enough to review with a person, the $197 AI Leak Scan can inspect up to 25 redacted records and return a bounded repair list. It does not promise recovered revenue, sales outcomes, rankings, or customer responses.

FAQ

Should a contractor cancel a lead vendor after a few bad leads?

Not before checking whether the team can prove source, owner, last event, next action, and stop reason for a small sample. Vendor quality and handoff quality are different questions.

Can this review be done without sharing a CRM login?

Yes. The first pass should use public context, screenshots, exported rows, or a small redacted CSV. Do not share passwords, recovery codes, full inbox exports, or private customer lists for an initial review.

Start small: Use public context or a small redacted sample. Do not send passwords, two-factor codes, recovery codes, recordings, payment data, broad inbox dumps, full CRM exports, or private customer lists for the first review.