Local service lead response • referral sources • handoff notes

Referral Source Lead Handoff Checklist for Local Service Businesses

Referral leads can be high-trust, but they often arrive with missing details, unclear ownership, and risky assumptions about what the partner promised. Use this copy/paste checklist to capture the source, customer context, next owner, and safe reply before the lead gets lost or overpromised.

Use the free AI Lead Response Quickstart See Local Lead Rescue System

When to use this handoff

Copy/paste referral lead handoff card

Referral source: [person/company/channel]

Source relationship: [past customer / realtor / property manager / contractor / vendor / community partner / unknown]

Customer/contact: [name + approved contact method]

Need described: [service request in the customer/source's words]

Source facts only: [what the source actually said, not assumptions]

Missing detail to request: [address, photos, timeline, urgency, access, budget, decision-maker]

Next owner: [dispatcher / estimator / owner / tech / office manager]

Response window: [real callback or review window]

Partner/source follow-up: [thank-you sent / update after booked / no update unless permission]

STOP AUTOMATION: Do not invent referral relationship, consent, urgency, availability, price, diagnosis, warranty, discount, or guaranteed priority.

Three short scripts

1) First reply to referred customer

Hi [Name] — [Referral Source] suggested we connect about [service/request]. I have [known fact] and still need [one missing detail] so the right person can review it. The next real response window is [window]. If that works, reply here with [detail] and the best callback number.

Review: confirm the customer gave permission to contact them before texting/emailing.

2) Thank-you note to referral source

Thanks for sending [Name] our way. We received the referral and are reviewing [general service category]. We will handle the customer details directly and only share updates that [customer/business policy] allows.

Review: do not share customer details back to the source unless permission and policy allow it.

3) Missing-detail follow-up

Hi [Name], quick follow-up on the referral from [Source]. To avoid guessing, could you send [one detail/photo/address/access window]? Once we have that, [owner/team] can confirm the appropriate next step.

Review: ask for the minimum useful detail; do not request sensitive/private information unless necessary and approved.

CRM labels that keep referral leads from disappearing

LabelUse whenRequired proof
REFERRAL-NEWA partner/source introduced a new lead.Source + customer contact permission
REFERRAL-MISSING-DETAILThe team needs address, photos, timeline, access, or decision-maker info.One requested detail + owner
REFERRAL-CALLBACK-DUEThe customer is ready for a callback or quote review.Callback window + assigned person
SOURCE-THANKEDThe referral source has been acknowledged.Thank-you date + privacy-safe note
OWNER-REVIEWThe referral touches price, diagnosis, warranty, emergency, discount, relationship, or privacy risk.Question for owner/manager

AI summary prompt for referral handoffs

You are helping a local service business summarize referral leads. Use only the referral notes provided. Return: (1) source, (2) customer request, (3) missing detail, (4) next owner, (5) safe first reply, (6) privacy-safe source thank-you, and (7) OWNER-REVIEW items. Do not invent referral relationship, customer consent, availability, price, diagnosis, warranty, discount, priority, emergency status, or source promises. If evidence is missing, write NEEDS OWNER REVIEW.

Where this fits in the lead-response system

Pair this with the Lead Source Tracking Spreadsheet, Lead Owner Assignment Checklist, Call Disposition Code Checklist, and Local Service Lead Response Resource Library.

Product signal: if referral-source resources earn reuse, consider adding a Local Lead Rescue appendix for referral handoff cards, partner thank-you messages, privacy-safe updates, and source-specific CRM labels. This run records one signal only; monitor before editing the buyer ZIP.