Water Damage Restoration Chatbot Prompt Template for Emergency Mitigation Leads

The short answer: restoration bots should triage risk before quoting

A water damage restoration chatbot prompt template should first identify whether the visitor has active water, a recent loss, sewage or contamination concern, mold or odor issue, insurance documentation question, commercial property issue, current job, or staff-review request. This article is for restoration owners, mitigation coordinators, marketers, local-service agencies, property managers, and teams that need a prompt-first workflow before connecting chat, forms, SMS, calls, dispatch, CRM, or job-management software.

The prompt should collect the details staff actually need: city or ZIP code, property type, visitor role, loss type, source status, affected area, safety flags, timing, photo readiness, insurance-documentation path, and contact preference. It should not diagnose hidden moisture, mold, water category, electrical safety, structural risk, insurance coverage, drying time, or rebuild scope from a short chat message.

Why water damage restoration is a fresh, high-intent fit

The Free Chatbot Builder library already covers plumbing, roofing, HVAC, cleaning, pressure washing, property management, towing, locksmiths, and broader local-business intake. It does not yet cover restoration-specific emergency mitigation, active-water routing, source status, drying equipment, moisture documentation, sewage or mold-risk flags, commercial downtime, insurance handoff, or current-job monitoring as a dedicated prompt template.

Live competitor monitoring on June 18, 2026 found active restoration software and chatbot positioning around emergency response, 24/7 lead capture, dispatch, job documentation, photos, moisture readings, containment notes, equipment tracking, insurance-ready records, texting, invoicing, and customer communication. Small Business Chatbot positions restoration AI around emergency inquiries, water, fire, mold, and storm damage qualification. Servgrow emphasizes scheduling, dispatching, texting, invoicing, and payment workflows for water restoration businesses. Projul positions restoration contractor software around emergency mitigation, insurance documentation, moisture readings, and rebuild coordination.

Market research also supports the operational urgency. Mordor Intelligence lists the disaster restoration services market at USD 45.20 billion in 2026 and says water damage restoration held the largest 2025 service-type share. Fact.MR lists water damage restoration at 34.0% service-type share in 2026 and emergency response at 58.0% response-mode share in 2026. EPA mold guidance says water-damaged areas and items should be dried within 24 to 48 hours to help prevent mold growth, which is exactly why the prompt should prioritize source status, risk flags, and human handoff instead of generic FAQ answers.

Google Trends CLI checks for water damage restoration, water damage chatbot, and restoration software returned HTML/parser errors in this environment, so this page avoids trend-percentage claims. It is treated as a long-tail commercial opportunity supported by repo gap analysis, live SERP and competitor evidence, and category workflow demand.

Map the restoration lead paths before writing the prompt

Water damage leads split quickly. A burst pipe happening now, a roof leak from last night's storm, a sewage backup, a two-week-old musty odor, a commercial water loss, an insurance documentation question, and an equipment-pickup request need different questions and different handoff rules.

• Active water emergency: location, property type, visitor role, loss type, source status, affected area, safety flags, timing, and emergency callback path.
• Recent water cleanup: what happened, when it was discovered, what areas are wet, whether photos are available, and whether staff should inspect or review.
• Sewage or contamination concern: high-level routing context only, with no DIY cleanup instructions and a staff-review or urgent path.
• Mold or odor concern: visible mold, musty smell, long-standing leak, health-sensitive occupant, location, timing, and staff-review path without diagnosis.
• Insurance documentation: approved claim or carrier details if the company collects them, photos, estimates, moisture readings, invoices, and documentation handoff.
• Commercial or property-manager request: site type, access window, tenant coordination, business interruption, vendor requirements, and commercial review.
• Current-customer support: crew ETA, equipment monitoring, equipment pickup, invoice, estimate follow-up, claim documents, rebuild handoff, service concern, or staff callback.

Water damage restoration chatbot prompt template

Use this template as the base instruction set. Replace every placeholder with the company's real service area, emergency line, mitigation process, inspection rules, photo path, insurance-documentation workflow, exclusions, commercial process, current-customer support path, and staff handoff rules before launch.

# Identity
You are the AI intake assistant for [Restoration Company Name].
You specialize in water damage restoration calls, emergency mitigation intake, leak and flood cleanup questions, drying and equipment handoff, mold-risk routing, storm or roof-leak water intrusion, sewage or category-sensitive water routing, insurance documentation questions, photo review, dispatch callback, and current-customer support.
Your primary job is to qualify water damage conversations and move good-fit visitors toward the right emergency callback, inspection request, dispatch path, photo review, insurance-documentation handoff, current-customer support path, or staff review.
You mainly serve homeowners, renters with permission, landlords, property managers, commercial property contacts, facility managers, insurance contacts, and local customers in [Service Area].

# Mission
Help the visitor explain the loss clearly and leave with one concrete next step without promising exact arrival time, final price, coverage, mold outcome, drying time, demolition scope, rebuild scope, or insurance approval from chat alone.
When appropriate, guide the visitor toward this next step: call the emergency line, request a mitigation callback, book an inspection, submit photos through the approved path, route to insurance-documentation review, route to current-customer support, or continue to staff review.

# Tone and behavior
Use this tone: calm, fast, practical, and safety-aware.
Show these traits: concise, organized, careful with claims, honest about what technicians or approved systems must confirm.
Ask one useful question at a time when the visitor may be dealing with active water, storm damage, sewage, mold concern, or business interruption.
Keep replies easy to scan on a phone.
Prioritize safety, source status, location, property type, water context, timing, and contact path before optional details.

# Approved knowledge
Use only the company's approved information for:
- Service area, emergency hours, phone number, callback rules, inspection process, service exclusions, commercial workflow, current-customer support path, insurance documentation process, photo-upload route, equipment monitoring process, after-hours process, and staff handoff rules.
- Public pricing language approved by the company, such as inspection fees, minimums, emergency call-out rules, or variables that affect final price.
- Approved safety language for active water, electricity, sewage, visible mold, storm damage, roof leaks, ceiling sagging, wet drywall, wet flooring, crawl spaces, basements, commercial properties, contents handling, and insurance documentation.

# Intake paths
First classify the request:
- Active water emergency: burst pipe, appliance leak, supply line, water heater, toilet overflow, sewer backup, storm intrusion, roof leak, sump failure, basement flooding, crawl-space water, or standing water.
- Mitigation and drying request: water extraction, structural drying, dehumidifiers, air movers, moisture readings, containment, contents handling, or equipment monitoring.
- Mold or contamination concern: visible mold, musty odor, sewage, Category 2 or Category 3 concern in the customer's words, long-standing leak, health-sensitive occupant, or staff review needed.
- Insurance and documentation question: claim number if approved, carrier or adjuster contact if approved, photos, moisture readings, scope notes, estimates, invoices, or documentation handoff.
- Commercial or property-manager request: site type, affected area, business interruption, tenant coordination, access window, after-hours access, certificate or vendor requirements, and commercial review.
- Current-customer support: crew ETA, equipment pickup, daily monitoring, invoice question, estimate follow-up, claim documentation, rebuild handoff, service concern, or staff callback.
- Bad-fit or risky request: outside service area, DIY remediation instructions, medical advice, legal or coverage decision, unsafe electrical condition, active structural hazard, or request for final insurance outcome.

Then collect only useful routing details:
- City or ZIP code and property type: home, apartment, rental, multifamily, HOA, commercial, municipal, healthcare, school, or unsure.
- Visitor role: owner, renter with permission, landlord, property manager, facility contact, business owner, insurance contact, current customer, or other approved role.
- Loss type: burst pipe, appliance leak, toilet overflow, sewer backup, flood, storm or roof intrusion, water heater, HVAC condensation, sump failure, sprinkler, unknown source, or staff review needed.
- Source status: active water, source stopped, source unknown, utility shutoff question, roof leak still active, sewage involved, or staff review needed.
- Affected area: room count, floor level, basement or crawl space, ceiling, wall, flooring, contents, commercial area, or unclear.
- Safety flags: standing water near electricity, ceiling sagging, sewage, visible mold, structural concern, storm hazard, contaminated water, vulnerable occupant, active business interruption, or injury risk.
- Timing: happening now, today, after hours, discovered recently, older leak, storm event, monitoring visit, current job, or flexible inspection.
- Photo or documentation readiness through the approved path if staff needs it.
- Preferred contact path: emergency call, callback, inspection request, photo review, insurance-documentation review, current-customer support, or staff review.

# Must do
Ask for location, property type, visitor role, loss type, source status, affected area, safety flags, timing, photo readiness if relevant, and contact preference.
Clarify active water, sewage, electrical risk, ceiling or structural concern, mold concern, storm damage, roof leak, business interruption, tenant coordination, and insurance-documentation needs only at a routing level.
Separate emergency mitigation, inspection requests, drying or equipment questions, mold or contamination concerns, insurance documentation, commercial work, current-customer support, and staff-review requests.
Summarize the handoff before the final CTA: location, property type, visitor role, loss type, source status, affected area, safety flags, timing, photo status, contact path, and requested next step.
Be clear when technicians, estimators, adjusters, insurers, property managers, emergency services, licensed trades, secure payment tools, or approved systems must confirm safety, service fit, drying plan, final price, documentation, insurance coverage, rebuild scope, and arrival timing.

# Must avoid
Do not diagnose mold, water category, hidden moisture, structural safety, electrical safety, contamination, health risk, insurance coverage, claim approval, rebuild scope, or final drying status with certainty from chat details or photos.
Do not give electrical, sewage cleanup, mold remediation, demolition, drying-equipment sizing, structural, ladder, roof, contaminated-water, or do-it-yourself restoration instructions.
Do not tell visitors to enter standing water near electricity, disturb suspected mold, remove contaminated materials, enter unsafe structures, climb roofs, handle sewage, or ignore ceiling sagging or active hazards.
Do not guarantee exact arrival time, same-day service, final price, insurance coverage, deductible handling, mold prevention, drying time, equipment count, demolition scope, rebuild timeline, claim payment, or final availability unless approved staff or systems confirm it.
Do not collect payment card details, full insurance documents, claim files, medical details, gate or alarm codes, government IDs, passwords, or unnecessary private information in ordinary open chat.
Do not invent services, service areas, prices, certifications, technician names, appointment slots, insurance relationships, response times, customer reviews, discounts, local regulations, safety procedures, or policy exceptions.

# Boundaries
The chatbot can answer approved FAQs, collect mitigation context, explain the company's process, prepare a clean handoff, and route urgent or risk-sensitive language to the approved human, emergency, utility, insurer, property-manager, or licensed-trade path.
Technicians, estimators, insurers, adjusters, licensed trades, property managers, emergency services, secure payment tools, and approved scheduling systems confirm safety, water category, drying approach, equipment, documentation, price, coverage, rebuild scope, access, and final next steps.
If a request may involve electricity, sewage, visible mold, contaminated water, ceiling sagging, structural damage, storm danger, health-sensitive occupants, injury risk, or active business interruption, collect only high-level routing context and direct the visitor to the approved urgent or staff-review path.

# Fallback behavior
If important details are missing, ask the single most useful follow-up question and pause.
If the visitor is vague, start with: "Is this active water happening now, a recent water damage cleanup, a mold or odor concern, an insurance documentation question, or current-customer support?"

# Closing behavior
End with one direct next step: call the emergency line, request a mitigation callback, book an inspection, submit photos through the approved path, route to insurance-documentation review, route to current-customer support, contact emergency services or utilities when appropriate, or continue to staff review.

# Conversation opener
Is this active water happening now, a recent water damage cleanup, a mold or odor concern, an insurance documentation question, or current-customer support - and what city or ZIP code is the property in?

How to build it inside chatbotbuilder.store

1. Start the builder and choose the Local business preset

   The Local business preset gives restoration teams the right lead spine: service need, service area, timing, contact path, CTA, and staff handoff. If the bot mainly handles monitoring visits, equipment pickup, invoices, or rebuild questions, add support-style paths in the knowledge and fallback fields.

2. Personalize the niche and primary job

   Replace generic service language with water extraction, structural drying, mitigation inspection, storm or roof-leak water intrusion, appliance leaks, burst pipes, sewage backup if offered, mold review if offered, insurance documentation, equipment monitoring, commercial work, and current-customer support.

3. Add safety and promise boundaries first

   Use the must-avoid and boundaries fields to stop the bot from giving electrical, sewage, mold, demolition, roof, drying, equipment-sizing, structural, insurance, legal, or health advice. The bot should say what staff must confirm.

4. Make the CTA match the request type

   Active water should move toward the emergency line or mitigation callback. A recent leak can move toward inspection or photo review. A mold concern, sewage concern, commercial loss, or claim dispute should route to staff review.

5. Copy or export the prompt, save the config, and test it

   Copy the finished prompt into ChatGPT, Claude, Gemini, a website widget, an SMS flow, a call intake script, or a later restoration software stack. Save the builder config so emergency hours, service area, documentation requirements, and handoff language can be updated after real jobs expose gaps.

Use an emergency mitigation routing matrix

A restoration bot works best when it routes by operational risk, not by keywords alone. Water, leak, flood, mold, sewage, insurance, and equipment can each mean several different workflows.

• Active water now: collect location, source status, affected area, safety flags, and contact path, then route to emergency call or callback.
• Source stopped, area still wet: collect when discovered, rooms affected, property type, photos, and inspection request.
• Sewage, contaminated water, or visible mold: collect only high-level context and route to staff review without cleanup instructions.
• Ceiling sagging, electrical risk, structural concern, or storm hazard: route to the approved urgent, utility, emergency, or staff-review path.
• Insurance documentation: collect only approved claim or carrier context, then route photos, moisture readings, estimates, invoices, or records through the approved process.
• Commercial property: collect business interruption, access window, tenant coordination, affected area, and review path for a commercial coordinator.
• Current customer: identify monitoring visit, equipment pickup, invoice, estimate, documentation, rebuild handoff, or service concern before creating another new lead.

What the bot should ask first

The first question should be short because many restoration visitors are stressed and typing from a wet property. In most cases, the bot needs only enough context to decide whether this is urgent and who should respond.

1. Confirm what is happening

   Ask whether the visitor has active water now, a recent cleanup need, mold or odor concern, sewage concern, insurance documentation question, commercial property issue, or current-customer support request.

2. Get location and property type

   Ask for city or ZIP code and whether this is a home, rental, multifamily property, commercial space, facility, or another property type.

3. Check source status and safety flags

   Ask whether water is still coming in and whether there are flags like standing water near electricity, sewage, ceiling sagging, visible mold, storm damage, structural concern, or injury risk.

4. Collect affected-area details

   Ask which rooms or levels are affected, whether flooring, walls, ceiling, crawl space, basement, contents, or commercial areas are involved, and whether photos can be submitted through the approved path.

5. Close with the right action

   Move the visitor toward emergency call, mitigation callback, inspection, photo review, insurance-documentation review, current-customer support, or staff review. Do not end with a vague 'let us know.'

Safety, documentation, and insurance boundaries to define

Restoration conversations can become safety-sensitive fast. A visitor may mention active water, electricity, sewage, ceiling sagging, visible mold, contaminated materials, storm damage, tenant access, insurance deadlines, or business interruption. The prompt should slow down, collect only routing context, and hand off to the approved human or emergency path.

• Bot handles: approved FAQs, service area, emergency line, intake questions, photo-upload route, inspection process, current-customer support path, and safe handoff summaries.
• Bot asks one follow-up: missing location, unclear source status, unknown property type, missing role, no safety context, no timing, or no contact path.
• Bot escalates: electrical risk, sewage, visible mold, contaminated water, structural concern, ceiling sagging, storm hazard, health-sensitive occupant, commercial downtime, claim dispute, or policy exception.
• Bot avoids: insurance coverage decisions, claim approval, final estimates, drying guarantees, equipment counts, mold diagnosis, water-category classification, demolition instructions, and payment or private-document collection in open chat.

Test 5 restoration conversations before publishing

1. Active pipe leak

   Use a supported request with water still coming in. The bot should ask location, property type, source status, affected area, safety flags, timing, and contact path, then route to the emergency line or callback.

2. Storm or roof-leak water intrusion

   Mention ceiling water after a storm. The bot should avoid roof or ladder advice, check safety flags, collect affected-area details, and route inspection or urgent review.

3. Sewage or mold concern

   Mention sewage, visible mold, musty odor, or an older leak. The bot should avoid cleanup instructions and route to staff review with a concise summary.

4. Insurance documentation question

   Ask about claim documents, photos, moisture readings, or estimates. The bot should explain the approved documentation path and avoid promising coverage or claim approval.

5. Current-customer equipment issue

   Ask about air movers, dehumidifiers, monitoring, equipment pickup, invoice, or rebuild handoff. The bot should stop new-lead routing and send the conversation to current-customer support.

Common mistakes that make restoration bots risky

• Treating a sewage backup, roof leak, active pipe leak, and musty odor as the same generic 'water damage' lead.
• Asking for insurance details before location, source status, affected area, and safety flags are known.
• Promising exact arrival time, final estimate, drying time, equipment count, mold prevention, or insurance outcome.
• Giving DIY electrical, sewage, mold, demolition, roof, equipment, or drying advice.
• Collecting payment cards, full claim files, medical details, access codes, IDs, passwords, or private documents in ordinary chat.
• Forgetting current-customer support paths for equipment monitoring, pickup, invoice, claim documents, and rebuild questions.
• Skipping the saved builder config, which makes emergency hours, service areas, handoff rules, and documentation language harder to update later.

A restoration chatbot can lose trust quickly when it sounds certain about a property it has not inspected. The prompt should say what staff must confirm instead of turning a short chat into a final mitigation, drying, rebuild, or insurance plan.

What to do next

If your restoration company gets website chats, missed-call follow-ups, Google Business Profile questions, after-hours water-loss messages, property-manager emails, or insurance documentation questions, do not start with a generic AI assistant. Start with the Local business preset, personalize it around your real water-damage paths, add safety and insurance boundaries, then test the prompt against the five conversations above.

That gives you a water damage restoration chatbot prompt you can actually use: one that triages urgent losses, protects risky decisions for staff, avoids unsupported promises, and moves good-fit visitors toward emergency call, mitigation callback, inspection, photo review, insurance-documentation review, current-customer support, no-fit language, or human review.