1) Weather-delay source card
Copy this block into the job note, CRM, dispatch board, or AI prompt before sending a reschedule message.
Customer / job:
Original appointment window:
Weather trigger: rain / snow / storm / heat / wind / road closure / unsafe access / other
Current job status: not dispatched / en route / on site / paused / needs manager review
Safety constraint confirmed by: dispatcher / technician / owner / vendor / official alert / customer photo
New window approved by scheduler: yes / no / pending
Customer preference captured: earliest available / specific day / call first / text only / cancel / owner review
Fee, discount, deposit, or warranty impact approved by owner/accounting: yes / no / not applicable
CRM label to add: WEATHER_DELAY_RESCHEDULE
Next internal owner and due time:
Evidence link/photo/alert/source:
2) Customer-safe acknowledgement snippets
- Delay known, new window not approved: “Weather is affecting today’s schedule. I’m checking the next safe opening now and will send the confirmed option before we move the job.”
- Unsafe access: “We do not want to send anyone into an unsafe access condition. Please send any gate/road/site update you have, and we’ll confirm the next safe arrival window.”
- Customer asks for a discount: “I can document that request for the owner/manager. I don’t want to promise a credit before it is reviewed.”
- Technician already en route: “The technician is reviewing whether the route/site is still safe. We’ll update you with the confirmed status instead of guessing.”
3) AI audit prompt
Review this draft weather-delay response before sending. Flag any unsupported promise about arrival time, safety, fees, discounts, warranty, diagnosis, parts, completion date, or liability. Rewrite it so it only uses approved facts from the source card, includes the next owner/due time, and uses the CRM label WEATHER_DELAY_RESCHEDULE. If a new schedule window is not approved, say STOP AUTOMATION.STOP AUTOMATION rules
- STOP AUTOMATION if the new arrival window has not been approved by dispatch/scheduling.
- STOP AUTOMATION before waiving fees, changing deposits, promising discounts, or deciding warranty coverage.
- STOP AUTOMATION if safety conditions, road access, customer access, or technician availability are unclear.
- STOP AUTOMATION before blaming the customer, vendor, technician, municipality, or weather event for damages or delays.
Product bridge
This resource is a small slice of the Local Lead Rescue System: missed-lead recovery, dispatch-safe text templates, owner-review prompts, CRM labels, and follow-up routines for local-service teams that need faster replies without risky promises.