Local service lead response • wrong number cleanup • do-not-contact workflow

Wrong Number and Do-Not-Contact Cleanup Checklist for Local Service Leads

Fast follow-up helps local-service teams, but bad phone numbers, STOP replies, duplicate contacts, shared family phones, and angry refusals can turn automation into a liability. Use this checklist to close out unsafe records, keep CRM labels clean, and stop AI-assisted follow-up before it keeps nudging the wrong person.

Use the free AI lead response quickstart See Local Lead Rescue System

When this cleanup workflow matters

Use this page when a lead record is no longer safe to follow up automatically: the recipient says wrong number, replies STOP, asks not to be contacted, disputes the request, appears to be a shared phone, or has received the maximum number of unanswered touches.

Template 1: wrong-number apology and closeout

Use when: the recipient says this is the wrong number or the requested service is not theirs.

Sorry about that — we have marked this number as wrong for the [service/request] record and will not text it again. No reply needed. If you still receive a message from us, please reply STOP and we will review the record manually.

CRM note: wrong_number_confirmed; source=[lead source]; closed_by=[staff]; duplicate_check_needed=[yes/no].

Template 2: do-not-contact confirmation

Use when: someone explicitly asks not to be contacted, even if they do not use the word STOP.

Understood. We have marked this request as do not contact and will not follow up by text about it again. If this was connected to an active appointment, invoice, warranty, or safety issue, please call [approved phone] so a manager can review it.

CRM note: do_not_contact; channel=sms; reason=[customer request/wrong number/privacy/other]; automation_paused=true.

Template 3: unreachable lead closeout

Use when: the lead has received the approved cadence and has not replied.

Hi [First Name], we are closing the loop on your [service] request for now. If you still need help, call [phone] or submit a new request at [booking/contact link]. We will not keep texting about this request. Reply STOP if you do not want texts from us.

CRM note: closed_unreachable; touches=[count]; last_touch=[date]; next_allowed_action=[new inbound only/nurture date/manager review].

Template 4: duplicate or shared phone review

Use when: two leads share a phone number, a spouse/tenant/manager is involved, or the CRM might have merged the wrong contact.

Hi, this is [Business]. We may have multiple records tied to this number. Before sending more details, can you confirm which [service/property/request] this is about? If you prefer not to text, call [phone]. Reply STOP if this number should not receive texts.

CRM note: identity_unclear; duplicate_review_needed; do_not_send_estimate_or_private_details_until_confirmed.

CRM cleanup fields to add

AI summary prompt for cleanup decisions

Copy/paste prompt:

You are helping a local service business decide whether a lead record is safe to follow up. Use only the facts provided. Do not invent consent, customer identity, price, diagnosis, appointment status, warranty, legal rights, emergency instructions, or opt-out status. Return: contact status, consent source, last safe action, whether automation must stop, CRM labels, one approved closeout note if appropriate, and the human reviewer. If the record includes STOP, wrong number, do not contact, privacy complaint, disputed identity, abusive refusal, legal/safety/emergency issue, or unclear duplicate contacts, say STOP AUTOMATION and route to manager review.

Where this fits in the lead-response system

This cleanup workflow supports the SMS consent templates, stale lead follow-up templates, lead response SLA checklist, free speed-to-lead swipe file, and Local Lead Rescue System. The goal is not more follow-up; it is safer follow-up with clear stop conditions.