Local service lead response • dispatcher handoff • field crew updates
A lead is not truly handled until the field technician, dispatcher, or owner has the right facts. Use this checklist when a lead moves from inbox or phone call into a route, quote, diagnostic visit, or follow-up task.
Use the free AI Lead Response Quickstart See Local Lead Rescue System
Lead/customer: [name, phone/email, preferred contact method]
Source: [missed call / web form / inbound text / repeat customer / referral / marketplace]
Job type: [requested service, issue summary, property type]
Address/access: [address verified? access notes? gate/pet/tenant/lockbox?]
Photos/files: [attached / requested / missing / not needed]
Customer expectation: [callback / estimate / diagnostic visit / emergency review / reschedule / closeout]
Known constraints: [budget, timing, warranty, HOA/permit, owner approval, safety risk]
Current promise made: [none / callback window / arrival window / quote review / owner will verify]
Technician next action: [call first / review photos / confirm access / inspect / quote / escalate]
STOP AUTOMATION: Do not invent customer history, consent, arrival time, price, diagnosis, warranty coverage, safety priority, payment status, permit/HOA approval, parts availability, or job completion.
Thanks, [Name]. I’m routing this to the right person now. Before we confirm schedule, price, diagnosis, warranty, or next steps, we’ll review the current details and make sure the technician has the correct address/access notes.Hi [Name] — the technician can review this faster with one detail: [photo/access note/model number/best callback window]. Once we have that, we’ll confirm the safest next step instead of guessing.Thanks for the details. This needs owner/manager review before we promise [price/timing/warranty/emergency priority/payment/refund/completion]. We’ll check the current record and follow up with the verified next step.| Label | Use when | Required proof |
|---|---|---|
| TECH-HANDOFF-READY | Lead has enough facts for a technician or estimator. | Address/access, job type, customer expectation, owner |
| TECH-NEEDS-DETAIL | Photos, model number, gate code, tenant contact, or quote ID is missing. | Exact detail requested and customer-safe script |
| TECH-OWNER-REVIEW | Pricing, diagnosis, warranty, safety, payment, refund, or policy risk exists. | Reviewer and unresolved question |
| TECH-STOP | Wrong number, opt-out, unsafe request, out-of-scope work, or consent issue blocks follow-up. | Stop reason and reviewer |
You are summarizing a local-service lead for technician handoff. Use only the provided notes. Return: customer/source, requested job, verified facts, missing details, access/safety constraints, current promise made, technician next action, customer-safe update, CRM label, and owner-review risks. If a fact is missing, write NEEDS OWNER REVIEW. Do not invent customer history, consent, address, arrival time, price, diagnosis, warranty, payment status, parts availability, emergency priority, permit/HOA approval, or job completion.
Pair this with the Inbound Text Message Response Checklist, First-Reply Quality Checklist, Lead Owner Assignment Checklist, and Local Service Lead Response Resource Library.
Product signal: if technician-handoff resources earn clicks/replies/reuse, consider adding a Local Lead Rescue field-handoff appendix covering address/access proof, technician owner, promise already made, missing detail, customer-safe update, and no-invented-price/diagnosis/warranty/arrival/payment/completion guardrails. This run records one signal only; monitor before editing the buyer ZIP.