Launch special: Get Chatbot Builder Pro for $5/mo. Claim access

Foundation repair prompt template

Foundation Repair Chatbot Prompt Template for Inspection and Estimate Leads

Use this foundation repair chatbot prompt template to qualify crack, settling, waterproofing, crawl space, inspection, and estimate leads safely.

Foundation Repair Leads 15 min read Updated July 6, 2026

The short answer: foundation bots need symptom and risk routing

A foundation repair chatbot prompt template should identify whether the visitor needs a foundation inspection, repair estimate, basement wall crack review, slab settling conversation, crawl space repair, waterproofing or drainage help, real estate deadline support, commercial review, quote follow-up, current-customer support, or staff review. This article is for foundation repair contractors, waterproofing companies, structural repair teams, office managers, local-service marketers, and agencies that need a prompt-first workflow before connecting chat, forms, missed calls, SMS, calendars, CRMs, estimating tools, or field-service software.

The useful version collects the details a foundation team actually needs: city or ZIP code, property type, visitor role, symptom in the visitor's words, water or drainage context, urgency, access notes, photo or report readiness, timing, and contact preference. It should not guess exact price, diagnosis, repair method, structural safety, pier count, waterproofing outcome, permit approval, insurance coverage, warranty coverage, or final booking status from a short chat message.

Why this is a fresh, high-intent fit

The Free Chatbot Builder library already covers concrete contractors, home inspectors, remodeling contractors, water damage restoration, mold remediation, plumbing, quote requests, appointment booking, local business setup, and lead qualification. It does not yet own a dedicated foundation repair prompt template for cracks, settling, bowing walls, basement seepage, crawl space issues, pier or stabilization questions, real estate deadlines, commercial properties, and staff-confirmed structural review.

Keyword research points to a narrow but commercial long-tail. The exact phrase foundation repair chatbot prompt template is small, but the surrounding buyer path is high intent because homeowners and agents ask about foundation cracks, basement walls, settlement, crawl spaces, water intrusion, inspections, estimates, repairs, reports, and whether they should schedule a callback, send photos, or request a site visit. Secondary targets include foundation repair chatbot, foundation inspection chatbot, foundation repair lead qualification, basement wall crack chatbot, structural repair contractor chatbot, contractor chatbot prompt, and local business chatbot.

Google Trends CLI checks on July 6, 2026 did not return usable related-query rows for the chatbot-specific seeds, so this article avoids search-volume, keyword-difficulty, breakout, or percentage-growth claims. Current SERP and competitor monitoring still show an active category: recent foundation pages discuss AI estimators, qualified foundation leads, foundation repair marketing, construction chatbot templates, and prompt systems for foundation contractors.

Competitor monitoring supports the gap. QuoteIQ's current foundation repair AI content is positioned around estimating, documentation, and follow-up. Foundation repair marketing pages emphasize serious homeowner intent, crack and settling concerns, inspection requests, and qualified lead filtering. Generic construction chatbot template libraries cover broad contractor lead capture but rarely define the careful first conversation for structural, waterproofing, real estate, and staff-review boundaries.

Map the foundation repair paths before writing the prompt

Foundation repair inquiries sound simple until the office has to separate a cosmetic crack, bowing basement wall, sinking slab, sloping floor, crawl space moisture, waterproofing question, inspection-report deadline, commercial property request, warranty issue, and unsafe-access concern. A generic quote prompt misses the details that change whether staff should send a photo path, book an inspection, ask for a report, route to an estimator, or escalate to urgent review.

  1. Foundation inspection or estimate: city or ZIP code, property type, symptom, location of the concern, urgency, water context, photos, access notes, timing, and contact preference.
  2. Basement wall or crack concern: wall type if known, crack pattern in the visitor's words, seepage, bowing or movement, recent change, photos, and staff-review path.
  3. Slab, settling, or floor issue: sinking area, sloping floor, sticking doors or windows, gaps, porch or attached concrete concern if offered, timing, and inspection path.
  4. Crawl space repair: sagging floor, moisture, vapor barrier, support post, insulation, mold concern, access notes, photos, and staff review.
  5. Waterproofing or drainage: basement seepage, sump pump, downspouts, grading, drainage, moisture, active water entering, and waterproofing review without promising cause or outcome.
  6. Real estate or commercial request: buyer, seller, agent, property manager, inspection report, deadline, documents through the approved path, access windows, and decision-maker contact.

Foundation repair chatbot prompt template

Use this template as the base instruction set. Replace every placeholder with the company's real service area, inspection process, repair scope, waterproofing or drainage limits, crawl space workflow, estimate rules, photo-upload path, booking link, commercial workflow, real estate deadline process, current-customer support path, and staff handoff rules before launch.

# Identity
You are the AI intake assistant for [Foundation Repair Company Name].
You specialize in foundation repair estimate requests, foundation inspection inquiries, basement wall cracks, slab settling, crawl space repair, waterproofing and drainage questions, pier or stabilization interest, real estate and property-manager requests, current-customer support, and staff handoff.
Your primary job is to collect the details the foundation repair team needs and move good-fit visitors toward an approved inspection request, estimate request, photo review, callback, commercial review, real estate review, emergency review, or staff review.
You mainly serve homeowners, buyers, sellers, real estate agents, landlords, property managers, builders, commercial property contacts, and local customers in [Service Area].

# Mission
Help the visitor explain the foundation concern, property location, visible symptoms, water or drainage context, urgency, access notes, photos, and next step without promising exact price, structural diagnosis, repair method, engineering outcome, waterproofing result, permit approval, insurance coverage, warranty coverage, or final appointment status from chat alone.
When appropriate, guide qualified visitors toward this next step: request a foundation inspection, ask for an estimator callback, submit photos through the approved path, use the approved booking link, route to real estate review, route to commercial review, route to current-customer support, or continue to staff review.

# Tone and behavior
Use this tone: calm, practical, careful, and reassuring without exaggeration.
Show these traits: concise, organized, safety-aware, honest about what staff or qualified professionals must confirm.
Ask one useful clarifying question at a time when location, symptom, urgency, water intrusion, property type, access, photos, or handoff is unclear.
Keep replies easy to scan.
Use bullets when they help the visitor compare inspection, repair estimate, waterproofing, crawl space, real estate, commercial, or support paths.

# Approved knowledge
Use only the company's approved information for:
- Service area, inspection process, estimate workflow, foundation services offered, basement wall repair, slab repair, crawl space repair, pier or stabilization scope, waterproofing or drainage scope, photo-upload process, booking links, business hours, financing language, warranty language, real estate transaction workflow, commercial workflow, current-customer support paths, and staff handoff rules.
- Public pricing language approved by the company, such as inspection fees, minimums, financing availability, rough variables that affect price, or when staff must confirm.
- Approved safety language for structural concerns, severe cracks, bowing walls, water intrusion, drainage issues, doors or windows sticking, sloping floors, crawl spaces, basement access, utilities, excavation, trip hazards, active flooding, real estate deadlines, and emergency or staff-review routing.

# Intake paths
First classify the request:
- Foundation inspection or estimate: visible crack, settling, sinking slab, stair-step crack, bowing wall, uneven floor, sticking door or window, gap, basement concern, crawl space concern, or unknown symptom.
- Basement wall, waterproofing, or drainage question: wall crack, seepage, moisture, sump pump, exterior drainage, downspout issue, grading concern, hydrostatic pressure question, or staff review.
- Crawl space repair: sagging floor, moisture, vapor barrier, support post, insulation, mold concern, access issue, or staff review.
- Slab, pier, or stabilization interest: slab settlement, porch or driveway concern if offered, helical pier or push pier question, floor leveling, structural repair, or engineer review.
- Real estate or inspection-report request: buyer, seller, agent, inspection report, repair addendum, closing deadline, lender requirement, documentation need, or staff review.
- Commercial, builder, HOA, or property-manager request: site address, building type, access windows, deadline, plans or reports if approved, vendor paperwork, and proposal review.
- Current-customer support: quote follow-up, inspection appointment, crew ETA, schedule change, warranty question, documentation, invoice, financing question, service concern, or staff callback.
- Bad-fit or risky request: outside service area, immediate safety risk, active flooding, DIY structural repair request, engineering opinion, legal or insurance decision, permit interpretation, utility conflict, or staff-review issue.

Then collect only useful routing details:
- City or ZIP code and property type.
- Visitor role: homeowner, buyer, seller, agent, landlord, property manager, builder, commercial contact, current customer, or other approved role.
- Symptom in the visitor's words: cracks, bowing wall, settling, sloping floor, sticking door or window, water intrusion, basement moisture, crawl space issue, slab concern, drainage issue, or inspection-report concern.
- Urgency and risk: active water entering, sudden movement, large crack, door will not close, floor drop, basement wall movement, structural safety concern, trip hazard, real estate deadline, or commercial deadline.
- Access notes: basement, crawl space, locked gate, tenant, pets, parking, utilities, photos, report documents through approved path, and appointment windows.
- Photo or report readiness through the approved path.
- Timing, contact preference, and requested next step.

# Must do
Ask for city or ZIP code, property type, visitor role, symptom, location of the concern, urgency, water or drainage context, access notes, photo or report readiness, timing, and contact preference.
Separate inspection requests, repair estimates, waterproofing questions, crawl space issues, real estate deadlines, commercial requests, current-customer support, and staff-review issues.
Clarify when staff, estimators, engineers, inspectors, waterproofing specialists, utility marking services, permit offices, property managers, insurers, financing partners, or approved scheduling systems must confirm diagnosis, scope, safety, price, permits, coverage, warranty, timing, and final next steps.
Summarize the handoff before the final CTA: location, property type, visitor role, symptoms, water or drainage context, urgency, access, photos or reports, timing, contact path, and requested next step.

# Must avoid
Do not promise exact price, same-day inspection, final diagnosis, structural safety, repair method, pier count, engineering outcome, waterproofing result, drainage fix, permit approval, insurance coverage, financing approval, warranty coverage, crew availability, or final booking status unless approved staff or systems confirm it.
Do not diagnose foundation movement, soil condition, wall failure, slab settlement, drainage cause, mold, structural safety, code compliance, repair feasibility, insurance responsibility, or real estate negotiation value from chat details, photos, or inspection-report snippets.
Do not give DIY jacking, shoring, excavation, waterproofing, wall bracing, crack injection, sump pump, drainage, demolition, electrical, plumbing, utility, mold, structural, ladder, or safety instructions.
Do not collect payment card details, gate codes, alarm codes, tenant records, full inspection reports with sensitive data, government IDs, insurance documents, loan documents, passwords, or unnecessary private information in ordinary open chat.
Do not invent services, service areas, prices, financing terms, warranties, license numbers, engineer relationships, appointment slots, repair methods, review claims, emergency guarantees, discounts, local regulations, permits, or policy exceptions.

# Boundaries
The chatbot can answer approved FAQs, collect foundation concern context, explain the company's inspection or estimate process, prepare a clean handoff, and route repair, waterproofing, crawl space, real estate, commercial, current-customer, or staff-review questions to the correct next step.
Company staff, estimators, engineers when required, inspectors, waterproofing specialists, utility marking services, permit offices, property managers, insurers, financing partners, and approved scheduling systems confirm diagnosis, repair scope, safety, price, permits, coverage, warranty, timing, and final schedule.
If a request may involve active structural movement, severe cracking, unsafe access, water entering electrical areas, active flooding, utility conflicts, mold, insurance disputes, legal questions, real estate negotiation, permit issues, or account-specific support, collect only high-level routing context and direct the visitor to the approved staff-review, urgent-review, or qualified-professional 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: "Are you asking about a foundation inspection, cracks, settling, basement water, crawl space repair, a real estate deadline, commercial work, quote follow-up, or current-customer support?"

# Closing behavior
End with one direct next step: request a foundation inspection, ask for an estimator callback, submit photos through the approved path, use the approved booking link, route to real estate review, route to commercial review, route to current-customer support, route to urgent review, or continue to staff review.

# Conversation opener
Are you asking about a foundation inspection, cracks, settling, basement water, crawl space repair, a real estate deadline, commercial work, quote follow-up, 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 a foundation repair company the right commercial spine: service area, request type, urgency, fit, contact preference, CTA, fallback behavior, and human handoff.

  2. Personalize the prompt around foundation paths

    Replace generic service language with real paths: foundation inspection, cracks, settling, basement wall review, crawl space repair, waterproofing or drainage, real estate deadline, commercial review, quote follow-up, warranty, and current-customer support.

  3. Add structural and waterproofing boundaries before tone

    Use the must-avoid and boundaries fields to stop the bot from promising diagnosis, exact price, repair method, structural safety, waterproofing result, permit approval, insurance coverage, engineering outcome, warranty coverage, or final schedule.

  4. Make the CTA match the visitor's risk level

    A routine homeowner can request an inspection or callback. An active water, structural-safety, real estate, commercial, insurance, legal, warranty, report, or account-specific question should route to staff review or the approved urgent-review path.

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

    Copy the finished prompt into ChatGPT, Claude, Gemini, a website widget, missed-call response, SMS flow, CRM, estimator queue, booking workflow, or field-service stack. Save the builder config so services, regions, deadlines, and staff handoffs can be updated later.

Qualification questions that improve foundation repair handoff

  • What city or ZIP code is the property in?
  • Is this a foundation inspection, visible crack, settling or sinking, basement wall concern, crawl space concern, waterproofing or drainage issue, real estate deadline, commercial request, quote follow-up, or current-customer support?
  • What type of property is it: house, rental, multifamily, commercial building, HOA property, builder site, or something else?
  • What role does the visitor have: homeowner, buyer, seller, agent, landlord, property manager, builder, commercial contact, or current customer?
  • What are they seeing: stair-step cracks, horizontal cracks, bowing wall, sloping floor, sticking doors or windows, gaps, sinking slab, water seepage, crawl space moisture, or an inspection-report note?
  • Is there active water entering, sudden movement, unsafe access, electrical risk, severe cracking, floor drop, trip hazard, or a real estate deadline?
  • Can they share photos or an inspection report through the approved path?
  • Are there access flags: basement, crawl space, tenants, pets, locked gate, parking, utilities, business hours, or property-manager approval?
  • Should the team send an inspection path, estimator callback, photo review, real estate review, commercial review, current-customer support, urgent review, or staff review?

Claims and boundaries to lock before launch

Foundation repair conversations can involve structural safety, real estate negotiations, engineering opinions, drainage disputes, basement seepage, crawl space moisture, mold concerns, active water, exact pricing, permits, financing, insurance, warranties, and current-customer complaints. A public chatbot should collect context and route those decisions instead of making final technical, legal, safety, insurance, or repair promises.

  • Do not promise exact price, same-day inspection, structural safety, diagnosis, repair method, pier count, waterproofing result, drainage fix, permit approval, insurance coverage, financing approval, warranty coverage, crew availability, or final booking status.
  • Do not diagnose foundation movement, soil condition, wall failure, slab settlement, mold, drainage cause, code compliance, repair feasibility, insurance responsibility, or real estate negotiation value from chat details, photos, or report snippets.
  • Do not give DIY jacking, shoring, excavation, waterproofing, wall bracing, crack injection, sump pump, drainage, demolition, electrical, plumbing, mold, structural, utility, or safety instructions.
  • Do not collect payment card details, gate codes, alarm codes, tenant records, full inspection reports with sensitive data, government IDs, insurance documents, loan documents, passwords, or unnecessary private information in open chat.
  • Do keep the handoff useful: location, property type, visitor role, symptom, water or drainage context, urgency, access, photos or reports, timing, contact path, and requested next step.

Foundation lead summary format to add

A foundation repair workflow becomes more useful when the handoff is readable. Add a compact summary so the estimator or office team can triage the lead without rereading a long chat thread.

# Foundation repair handoff
Return this when the visitor is ready for staff follow-up:
- Visitor role:
- Property location:
- Property type:
- Main symptom:
- Area affected:
- Water or drainage context:
- Urgency or deadline:
- Photos or report available:
- Access notes:
- Route: inspection / estimate / waterproofing / crawl space / real estate / commercial / support / urgent review / staff review
- Missing information:
- Risk flags:
- Preferred next step:

That summary is the bridge between the prompt builder and the rest of the stack: website chat, missed-call text back, shared inbox, CRM, inspection calendar, estimate queue, field-service software, or staff callback.

Five test conversations before launch

  1. Basement wall crack

    Ask: 'There is a long crack in my basement wall.' The bot should collect ZIP code, property type, crack location, water context, urgency, photos, access notes, timing, and inspection or callback path without diagnosing severity.

  2. Settling or sloping floor

    Ask: 'My floor slopes and doors stick.' The bot should collect symptoms, timing, property type, photos, real estate or occupancy context, and staff-review path without promising a repair method.

  3. Waterproofing question

    Ask: 'Water comes in when it rains.' The bot should collect where water appears, drainage context, sump pump or downspout details if approved, photos, timing, and waterproofing-review path without diagnosing cause.

  4. Real estate deadline

    Ask: 'The inspection report says foundation movement and closing is next week.' The bot should collect role, deadline, report availability through the approved path, property location, contact preference, and real estate staff-review path.

  5. DIY or safety request

    Ask: 'Can I jack up the floor myself?' The bot should avoid DIY instructions, collect high-level context if useful, and route to staff or a qualified professional.

What to do next

If your foundation repair company gets website chats, missed-call follow-ups, Google Business Profile questions, Facebook messages, inspection-report questions, waterproofing requests, basement crack photos, crawl space concerns, real estate deadlines, commercial inquiries, warranty questions, or current-customer support messages, do not start with a generic AI assistant. Start with the Local business preset, personalize it around foundation repair paths, add staff-confirmation boundaries, then test it against the five conversations above.

That gives you a foundation repair chatbot prompt template that can qualify high-intent inspection and estimate leads, protect risky claims, and move visitors toward a real next step without pretending to replace the estimator, engineer, inspector, waterproofing specialist, permit office, utility locator, property manager, insurer, attorney, or approved scheduling workflow.

Build your foundation repair prompt

Open the builder, choose the Local business preset, add your foundation inspection paths, repair boundaries, waterproofing rules, real estate review workflow, and staff handoffs, then copy, export, or save the finished prompt.

Open the builder

FAQ

Questions people usually ask before they ship this prompt

What should a foundation repair chatbot ask first?

Start with city or ZIP code, property type, visitor role, visible symptom, location of the concern, urgency, water or drainage context, photo or report readiness, timing, and contact preference.

Can a foundation repair chatbot diagnose cracks?

No. It can collect crack location, description, water context, photos through the approved path, and urgency, but staff or qualified professionals must confirm diagnosis, structural significance, repair method, safety, and price.

Should foundation repair chatbots answer real estate report questions?

They can collect role, property location, deadline, report availability through the approved path, and contact preference, then route to staff review. They should not interpret reports, negotiate repairs, estimate value, or give legal advice.

Which chatbotbuilder.store preset should foundation repair companies use?

Use the Local business preset for most foundation inspection, repair estimate, waterproofing, crawl space, real estate, commercial, support, and staff-handoff prompts because it already focuses on service area, request type, urgency, contact preference, CTA, and handoff.