Local service lead response • missed calls • callback tracking
Missed leads are not just a speed problem; they become a memory problem when nobody can prove who called, what was said, whether texting is allowed, and when the next attempt is due. Use this copy/paste log to keep callback attempts honest and owner-reviewed before a lead is marked lost.
Use the free AI Lead Response Quickstart See Local Lead Rescue System
Lead/customer: [name or lead ID]
Source: [phone / form / marketplace / referral / email / social]
Original request: [customer words only]
Consent/contact rule: [call OK / text OK / email OK / unknown / do-not-contact]
Attempt 1: [date/time, channel, owner, result, message left?]
Attempt 2: [date/time, channel, owner, result, message left?]
Attempt 3: [date/time, channel, owner, result, message left?]
Next due: [date/time + owner]
Stop reason: [booked / not a fit / no answer after policy cadence / wrong number / opted out / owner review]
STOP AUTOMATION: Do not invent contact attempts, consent, customer intent, urgency, availability, pricing, diagnosis, warranty, or opt-out status.
Hi [Name] — this is [Business]. We saw your call about [service/request]. If texting is OK, reply with [one useful detail] and the best callback window. If not, we can call back at [real window].Review: only text when consent and local rules/policy allow it.
Hi [Name], we tried to reach you about [service/request]. To route this correctly, could you send [one detail/photo/address area/access window]? If the issue is already handled, reply "all set" and we will close the request.Review: ask for the minimum useful detail; do not request sensitive information unnecessarily.
Hi [Name], we have not been able to connect about [service/request]. We will pause follow-up for now. If you still need help, reply here or call [number] and mention [lead/reference].Review: confirm cadence, opt-out, and policy before sending any final message.
| Label | Use when | Required proof |
|---|---|---|
| CALLBACK-ATTEMPTED | An owner tried to reach the lead. | Timestamp, channel, owner, result |
| CALLBACK-DUE | A next attempt is scheduled. | Due date/time + assigned owner |
| NEEDS-ONE-DETAIL | The lead cannot be routed without one missing fact. | The exact requested detail |
| OWNER-REVIEW | The lead touches consent, opt-out, emergency, warranty, price, diagnosis, or policy risk. | Question for owner/manager |
| LOST-NO-CONTACT | The lead is closed after approved cadence. | Completed attempts + stop reason |
You are helping a local service business summarize callback attempts. Use only the notes provided. Return: (1) lead source, (2) request summary, (3) attempt history, (4) consent/contact rule, (5) next due owner and time, (6) safest next message, and (7) OWNER-REVIEW items. Do not invent contact attempts, consent, urgency, availability, pricing, diagnosis, warranty, opt-out status, or customer intent. If evidence is missing, write NEEDS OWNER REVIEW.
Pair this with the Missed-Call Text-Back Templates, No-Answer Follow-Up Sequence, Call Disposition Code Checklist, and Local Service Lead Response Resource Library.
Product signal: if callback attempt resources earn reuse, consider adding a Local Lead Rescue worksheet for attempt history, owner due time, consent status, lost/no-contact reason, and no-invented-contact-history guardrails. This run records one signal only; monitor before editing the buyer ZIP.