Use this before any AI-assisted reschedule reply
STOP AUTOMATION: do not promise a new arrival window, technician change, discount, waived fee, refund, priority status, warranty coverage, or emergency dispatch until a human has checked the schedule board, job priority, customer history, service-area route, technician capacity, fee/discount authority, and any safety-sensitive facts.
- Escalate immediately when the job mentions active leak/flooding, no heat/cooling in unsafe temperatures, electrical/gas hazard, lockout/access risk, injury, business-critical downtime, or an angry customer threatening chargeback/review/legal action.
- Do not blame a technician, customer, subcontractor, or software system unless that fact is confirmed and approved for customer-facing language.
- Do not invent compensation, discounts, fee waivers, emergency status, exact ETAs, parts availability, or who will be sent next.
Copy/paste double-booked appointment source card
- Customer and job: customer name, address/ZIP, phone/email, service requested, job/ticket/estimate ID, current channel, and whether this is a new lead, open job, warranty/callback, or paid appointment.
- Original promise: promised date, time window, technician/crew, confirmation source, who confirmed it, and what the customer already received by text/email/phone.
- Conflict proof: overlapping appointment, route conflict, emergency override, technician absence, subcontractor issue, booking-system error, duplicate record, or unclear source that needs manager review.
- Priority and safety review: emergency/non-emergency status, customer vulnerability, property-damage risk, business downtime, warranty exposure, weather/permit constraints, and any stop-rule trigger.
- Approved recovery options: callback owner, next available window, waitlist/standby option, alternate technician, remote triage/photo request, manager-approved credit/waiver if any, and what cannot yet be promised.
- CRM label:
double_booked_appointment,schedule_conflict_review,arrival_window_recovery,manager_priority_review, orstop_automation_dispatch_promise.
Customer-safe recovery snippets
Acknowledge before the new slot is verified
We found a scheduling conflict on your appointment and are checking the live dispatch board before promising a new window. We will confirm the next available option after a person reviews technician availability and job priority.
Offer a verified next step without overpromising
Thanks for your patience. The verified option we can offer right now is [approved window/owner callback/photo triage]. We are not going to guess at an earlier ETA or fee change until the schedule owner confirms it.
Safety-sensitive escalation
Because your message may involve a safety-sensitive or damage-sensitive issue, we are escalating it for human dispatch review. If there is immediate danger, use the appropriate emergency or utility contact first.
No approved compensation yet
We understand the scheduling issue is frustrating. Any credit, fee change, or discount has to be reviewed against the job record and company policy before we promise it in writing.
AI audit prompt
Review this draft customer update about a double-booked appointment, schedule conflict, overlapping technician window, route conflict, or missed dispatch promise. Flag invented claims about arrival time, priority, compensation, fee waiver, emergency status, technician availability, warranty coverage, blame, or job completion. Rewrite it as a source-backed acknowledgement with clear unknowns, verified next step, owner review, and STOP AUTOMATION guardrails.
Why it connects to Local Lead Rescue
Local Lead Rescue System packages lead-response, dispatch handoff, CRM-label, and human-review patterns for local-service teams. This worksheet applies the same approach to schedule-conflict recovery: answer quickly, preserve trust, route the exception, and keep unsupported dispatch or discount promises out of AI-written replies.
See Local Lead Rescue System Start with the free missed-lead checklist