Use this when: a lead has missing contact details, copied text, odd service-area information, duplicate submissions, suspicious links, mismatched ZIP codes, or a message that looks bot-generated.
Human-review rule: never let AI mark a lead as spam or do-not-contact from one weak signal. A human should verify source, consent/contact status, duplicate records, active jobs, estimates, invoices, warranty notes, and safety issues first.
1. Five-minute spam lead triage worksheet
Lead source: [web form / chat / marketplace / voicemail / email / ad]
Received at: [date/time]
Customer name shown: [exact value]
Phone/email shown: [exact value]
Service requested: [exact wording]
Service area / ZIP: [provided or missing]
Source proof: [form id, call log, chat transcript, marketplace URL, CRM record]
Duplicate check: [new / duplicate / possible duplicate of CRM id]
Risk signals: [links, copied text, irrelevant service, bad contact info, abusive content, mismatched area]
Real-customer signals: [local details, specific problem, valid callback path, prior customer, photo/form evidence]
Triage decision: [reply / verify / merge duplicate / owner review / hold / mark spam]
Owner/reviewer: [name]
Next safe action: [one concrete action]
2. Safe labels for CRM cleanup
- NEEDS-VERIFY: not enough proof to reply or delete yet.
- POSSIBLE-DUPLICATE: same phone, email, address, or job details as another record.
- OUT-OF-SERVICE-AREA: location appears outside the real service area; use a polite decline script only after review.
- LOW-DETAIL-LEAD: real contact path but missing enough detail to quote, schedule, or dispatch.
- SPAM-HOLD: likely junk, but held for owner review before deletion or do-not-contact changes.
- OWNER-REVIEW: touches pricing, diagnosis, warranty, refund, emergency, safety, legal/privacy, or active-customer history.
STOP AUTOMATION: do not let AI change do-not-contact status, delete a lead, mark a warranty/customer issue as spam, or send a price/diagnosis/emergency reply without human approval.
3. Copy/paste verification replies
Low-detail but possibly real
Hi [Name], thanks for reaching out to [Business]. To make sure we route this correctly, can you reply with [one missing detail: service address / photos / best callback number / preferred time]? We will review it before scheduling or quoting.
Review: only ask for details needed for the service request. Do not ask for payment data, access codes, or private documents by text.
Possible duplicate
Thanks, [Name]. It looks like we may already have this request under [phone/email/job reference]. We are checking the record now so we do not miss or duplicate the next step.
Review: confirm the CRM match before merging records.
Likely out of area
Thanks for contacting [Business]. Before we promise availability, can you confirm the service address or ZIP code? We want to make sure we do not route you to the wrong team.
Review: do not invent referrals or exceptions.
4. AI assist prompt for triage summaries
You are helping a local service business summarize a possible spam or low-quality lead.
Use only the details below. Do not invent customer identity, contact consent, job history, service area, price, urgency, diagnosis, warranty status, payment status, emergency status, availability, or prior contact.
Return:
1. One-line neutral summary.
2. Risk signals present.
3. Real-customer signals present.
4. Missing details to verify.
5. Suggested CRM label from: NEEDS-VERIFY, POSSIBLE-DUPLICATE, OUT-OF-SERVICE-AREA, LOW-DETAIL-LEAD, SPAM-HOLD, OWNER-REVIEW.
6. One safe next action for a human reviewer.
Lead details:
[paste anonymized lead details here]
5. Weekly review questions
- Which sources created the most spam holds this week?
- Which real customers almost got ignored because the first message looked suspicious?
- Do form fields need clearer service-area, phone, photo, or job-type questions?
- Are duplicate records causing slow replies or accidental repeat messages?
- Does the team have a safe owner-review path before deleting leads?