Best fit: HVAC, plumbing, roofing, restoration, pest control, locksmiths, appliance repair, property maintenance, cleaning crews, and other local-service teams that receive urgent calls, texts, forms, or after-hours requests.
First rule: route risk before selling
- If there may be danger to people, pets, utilities, structure, water, fire, gas, or security, route to the approved emergency protocol first.
- Do not let an AI draft diagnose the cause, quote a repair, or promise arrival windows without human confirmation.
- Ask only enough questions to route the lead; urgent intake should be short.
- Record the source, timestamp, location, callback number, and the person who accepted ownership.
1. Safety and shutoff questions
Before we go further, is anyone in immediate danger, is there active water/fire/smoke/gas/electrical risk, or is the property unsecured? If yes, please follow your emergency/safety process first and tell us the safest callback number.2. Location and access questions
What is the service address or ZIP code, and is someone currently on-site who can answer the phone and provide access if we can help today?3. Problem snapshot questions
In one or two sentences, what happened, when did it start, and what has changed since then? Please include any visible damage, error codes, leaks, noises, odors, or access issues.4. Photo or video request
If it is safe to do so, please send 2–4 clear photos or a short video of the issue, the surrounding area, and any label/model number. Do not move equipment, climb, touch wiring, or enter an unsafe area for photos.5. Same-day vs next-day routing question
Are you looking for same-day help if available, or is next-business-day follow-up acceptable? We will confirm fit and availability before promising a time.6. Callback and ownership handoff
Thanks, [First Name]. I have: [service], [location], [urgency], [known facts], [photos yes/no]. I am routing this to [owner/dispatcher] now. The best callback number I have is [number]. Is that correct?CRM labels to keep urgent leads from slipping
- urgent-new — urgent lead received, not yet owner-assigned.
- safety-review-needed — potential safety/property risk; human must review before reply.
- same-day-request — prospect asked for same-day help; availability not promised yet.
- photos-requested — waiting for safe photos/video before routing.
- dispatcher-owned — named person has accepted next action.
- next-day-follow-up — not emergency-fit, but needs timely close-the-loop reply.
AI prompt to summarize an urgent request safely
You are helping a local service business summarize an urgent service request for a human dispatcher.
Business type: [service business]
Lead source: [call/text/form/after-hours/referral]
Confirmed facts only: [facts]
Customer words: [paste notes/transcript]
Location/service area: [confirmed location]
Photos/video: [yes/no/needed]
Known safety risk: [none confirmed / possible / urgent]
Desired timing: [same-day / next-day / unknown]
Human owner: [dispatcher/manager]
Create:
1. A five-line dispatcher summary.
2. Missing triage questions, maximum three.
3. A draft customer reply under 450 characters.
4. A stop-rule note if safety, diagnosis, price, availability, warranty, or legal/insurance claims require human review.
Rules:
- Do not invent facts, diagnoses, prices, availability, or guarantees.
- Do not tell the customer a technician is coming unless confirmed.
- If safety risk is possible, say "human emergency/safety review required" before any customer-facing draft.Quick owner review checklist
- Is the emergency/safety protocol triggered?
- Is the service address inside the service area?
- Is someone accountable for callback and next action?
- Did the reply avoid price, timing, diagnosis, and guarantee claims?
- Is the lead tagged for follow-up if it cannot be handled today?
For a fuller intake and follow-up workflow, start with the free AI lead response quickstart, the Lead Response ROI Mini-Calculator, and the Local Service Lead Response Resource Library. The paid Local Lead Rescue System expands this into scripts, intake templates, stale follow-up, and response workflows.