Use this before sending any AI-assisted customer update
STOP AUTOMATION: do not promise emergency dispatch, extraction, sanitizing, habitability, price, insurance coverage, claim reimbursement, drain repair, mold prevention, or safety clearance until an owner/manager has checked the job record, call notes, photos, access constraints, contamination risk, crew availability, approved communication channel, and escalation policy.
- Do not tell the customer a space is safe, sanitized, dry, mold-free, or ready for use unless the approved field/source record says so.
- Do not guess whether the source is sewer, greywater, stormwater, toilet overflow, main-line backup, appliance leak, or another cause.
- Do not promise insurance coverage, waived fees, reimbursement, or exact arrival windows from an AI draft or partial call transcript.
Copy/paste sewer-backup source card
- Caller / property / trigger: customer name, service address, caller role, after-hours status, affected rooms, active overflow status, number of occupants/tenants, and customer-authorized communication channel.
- Hazard and stop-rule notes: sewage/unknown water, electrical exposure, standing water, children/pets/tenants, odor, visible contamination, shutoff status, and whether the update must be acknowledgement-only.
- Evidence and access: photos requested/received, drain/toilet/floor-drain source if known, access limitations, lockbox/gate/tenant notes, parking, equipment access, and missing evidence.
- Dispatch and scope boundary: plumber vs restoration vs mitigation handoff, extraction/sanitizing estimate status, emergency/rush review, crew availability, disposal requirements, and owner/manager approval needed before promises.
- Customer-safe update owner: dispatcher, on-call manager, mitigation lead, plumber, claims coordinator if applicable, approved message template, and what cannot be promised before field review.
- CRM label:
sewer_backup_emergency,water_cleanup_source_needed,contaminated_water_review,dispatch_manager_review, orstop_automation_safety_claim.
Customer-safe snippets
Acknowledgement without overpromising
We have your sewer backup / water cleanup request in the job record. Before we confirm arrival timing, cleanup scope, safety status, pricing, insurance details, or repair recommendations, our team will review the source notes, photos, access details, hazard flags, crew availability, and approved communication path.
Photos or access details still needed
To keep the emergency record accurate, please send only the requested photos or access details through the approved channel. Avoid entering affected areas if there is standing contaminated water, electrical risk, or any safety concern. We will review the source record before sending a source-backed next-step update.
Customer asks if it is covered or safe
We do not want to guess about coverage, reimbursement, habitability, sanitation, mold, or safety clearance. We can document the issue and response notes, but claim or safety conclusions need to come from the approved field/source record and manager review.
AI audit prompt
Review this draft customer update about a sewer backup, drain overflow, contaminated water, water extraction, cleanup, sanitizing, emergency dispatch, insurance claim, arrival window, or repair recommendation. Flag invented claims about source/cause, safety, habitability, mold, sanitation, coverage, reimbursement, price, arrival timing, scope, or authorization. Rewrite it as a source-backed acknowledgement with clear unknowns, manager/field review, customer-safe wording, and STOP AUTOMATION guardrails.
Why it connects to Local Lead Rescue
Local Lead Rescue System packages practical intake, follow-up, CRM-label, and human-review patterns for local-service teams. This free worksheet is a narrow emergency-response example of the same source-card approach for high-pressure calls where staff and AI should acknowledge quickly without inventing risky claims.
See Local Lead Rescue System Start with the free missed-lead checklist