AI for foundation repair companies: what the assistant must never say.

Foundation inquiries arrive worried. A homeowner sends a photo of a stair-step crack in a block wall, or mentions a door that has started to stick, and asks whether the house is safe. The tempting reply, from a salesperson or from software, is reassurance or a diagnosis. North Carolina's engineering board has said in writing that a statement of foundation failure belongs to a professional engineer who has evaluated the conditions, and a careful company builds its intake around that line wherever it works.

Supervised AI assistants can still carry the paperwork around that judgment: a neutral intake record, the inspection booking, the engineer's pack, the report chase and a warranty register that outlasts the job. They never state a cause, a severity or a repair, and they never promise a result. The home-service industries overview lists the other trades in this series; this page deals with the foundation company's office.

The North Carolina Board of Examiners for Engineers and Surveyors publishes Foundation Repair Guidelines, first dated July 2011 and most recently revised on 22 October 2024, as an interpretative guide to the state's engineering and surveying licensing act. It is one board reading one state's statute. Rules vary by state, and nothing on this page describes any other state's position.

Three points in the guideline, as checked on 15 October 2026, matter most to a sales office. A statement that a foundation has failed, or that it needs structural repair, should come only from a professional engineer (PE) who has evaluated the conditions. A contractor may inspect, form a preliminary assessment and refer the client to a PE, and a home inspector notes a possible issue and refers in the same way. And the count and placement of piers sit inside the engineer's analysis from the first assessment onward. The intake article in this series walks through the guideline point by point, message by message.

Because the boundary sits inside the first conversation, the most important part of an intake assistant's design is a list of omissions. The owner writes it once, in plain words, shows it to the company's engineer, and it governs every draft the assistant prepares.

The Intake Bot's lasting rules list what a draft never contains: a cause, a severity, a repair, a result, a reading of the homeowner's photo or a repair price. What a draft can offer instead is an inspection, at a time a person has opened. The intake article shows how a reply handles each question a homeowner may send with their photos.

The owner creates these assistants as Bots in Grok Bot, following Aevrion's pattern. In Grok Bot, an agent product, each Bot is a durable, named teammate with one job on a persistent cloud computer, and lasting rules such as boundaries are given to it in chat for it to remember. So the six omissions are written there. A remembered rule guides; it does not enforce, which is why the owner reads every homeowner draft in the Intake Bot's conversation before choosing Send. An office person who handles intake can be asked about a draft, but the drafts sit in the owner's account, so the owner sends them.

The documentation contains no telephony at all: the Bots neither take calls nor leave voicemail nor text homeowners, so the assistant starts from what the person on the phone captured. Nor can a routine be scheduled to run more often than once every five minutes, so this back office prepares the next step; it does not reply the moment a message lands.

Customer-facing words leave as drafts: a Bot's email appears as an editable draft, and the owner chooses Send or Discard. Approval is configured rather than universal, tied in the documentation to the kind of tool, the riskiness of the action and the owner's own rules, so the owner adds a stop before anything is sent outside the company, a boundary the documentation itself lists.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

Inquiries arrive as an email or web form with photos, or as a note from whoever took the call. Bringing those within the assistant's reach needs a custom integration, made for the company's own inbox or form and tested on it; the simplest version is the owner attaching the office's note and the homeowner's photos to the Intake Bot's conversation, up to six attachments at a time on desktop.

The Intake Bot then builds an intake record and a draft reply. The record holds the homeowner's own words; the symptoms they list, such as cracks, sticking doors, sloping floors, gaps at frames or a bowing wall; where and since when; and any earlier foundation work or warranty. The draft thanks them, asks the questions the record lacks and offers the windows a person has opened. It does not answer the question they asked, and says so kindly: that can only be looked at in person, and, where needed, by an engineer.

Windows come from the company's real calendar, read each time; the documentation treats a Bot's memory as a convenience, never as the record itself. Reading a scheduling system is a custom integration or supervised browser use where the vendor permits it, subject to testing, and a person confirms the slot.

On site, an inspection may include a floor elevation survey, recording relative heights across the floor with a manometer or laser level, map the visible cracks, and note grading, drainage and trees. The assistant's part ends at the front door: it prepares the job sheet and files what the inspector records, exactly as recorded.

When the inspector suspects a structural issue, or the company sends every repair to its engineer, the job passes into an engineer's evaluation. The back office cannot speed up engineering. It can make sure the engineer never waits for paper.

In a company running more than one Bot, the Intake Bot can pass the job to an Engineer Desk Bot by an asynchronous Bot-to-Bot message, which the documentation describes, with the handoff visible in the conversation. Cursor's help pages say no switch turns that messaging off; a Bot follows instructions about it. Files sit in the shared workspace that every Bot can read. The Engineer Desk Bot assembles the pack below, an Aevrion pattern the engineer should edit, and drafts the covering email; the owner sends it. Reaching an engineering firm's own portal is a custom integration, if that firm allows one.

A routine that checks overnight for a late report can only prepare: any approval it raises with nobody watching expires after about ten minutes (Cursor's help pages say thirty) and the step does not run, so the morning starts with a drafted reminder for the owner to send. And the Bots share one cloud computer, with its browser sign-ins, so an engineering firm's portal login saved there is open to every Bot on the account; separate Bots are not a security boundary. Sign out of that portal when the pack is uploaded, or give the work its own user account, the documentation's route to real separation.

Pier vocabulary belongs to the engineer. In the trade's vocabulary, helical piers are screwed down to load-bearing strata; push, or resistance, piers are driven hydraulically. Which kind, how many and where is the design question, and the sales script never gets ahead of it.

• THE INQUIRY

  The homeowner's own description and photos, dated and unedited.

• THE INSPECTION RECORD

  The inspector's notes, crack map and elevation readings as recorded, with the instrument and the reference point used.

• SITE OBSERVATIONS

  Grading, drainage and trees as noted, labeled as observations, not conclusions.

• HISTORY

  Any earlier repair at the address, with its warranty and paperwork if the homeowner has them.

• ACCESS

  Who will be home, crawl-space or basement access, pets and parking.

• STILL MISSING

  Every item on the engineer's checklist the pack does not yet contain.

The stages below are an Aevrion pattern for a company that uses an associated or outside engineering firm. Bots hold only preparation; every stage that produces a judgment about the house is held by a person.

Stage five is where back offices drift. The Bot files the engineer's report and never rewrites it for the homeowner; the proposal carries the document as written, and questions go to the owner and the engineer. The crack-photo-to-warranty article in this series follows that crossing, out to the engineer and back, in detail.

1. 01

   Inquiry logged

   Owner

   Intake Bot

   Advances when

   The intake record and a draft reply are ready, and the owner sends the reply

2. 02

   Inspection booked

   Owner

   The office person or the owner

   Advances when

   A slot is confirmed with the homeowner

3. 03

   Inspected

   Owner

   The inspector

   Advances when

   The inspector records findings and decides whether to refer to the engineer

   Ends when

   Where there is no referral, the inspector, not the assistant, tells the homeowner what the visit recorded; whether the foundation needs structural repair is not stated without a PE's evaluation

4. 04

   With the engineer

   Owner

   The PE

   Advances when

   The engineer evaluates; the Engineer Desk Bot tracks the report and drafts reminders for the owner

5. 05

   Design received

   Owner

   The owner

   Advances when

   The owner reads the report; the Bot files it and lists dates, drawings and any permit the owner names

6. 06

   Proposal

   Owner

   The owner

   Advances when

   The owner prices the engineered design and sends the proposal with the engineer's report attached unchanged

7. 07

   Installed

   Owner

   The crew lead

   Advances when

   Work follows the design; post-repair readings and any engineer's completion sign-off are filed

8. 08

   Warranty on file

   Owner

   The owner, then the Warranty Bot

   Advances when

   The owner issues the written warranty and the Warranty Bot adds it to the register

   Ends when

   The row stays open for the term the written warranty states

A foundation repair can be asked about years later, by the homeowner or, where the written warranty allows a transfer, by a later owner. The warranty register answers: one row per repaired property, held in the company's own system rather than a Bot's memory.

Transfers run as the written warranty allows. When a transfer is requested, the Warranty Bot reads the company's warranty for that property, lists what it requires, and drafts the paperwork for the owner to approve. It does not interpret the warranty, decide whether a transfer is valid or tell a buyer what is covered. Those answers come from the owner, and from the owner's lawyer where the wording is in doubt.

North Carolina's guideline adds a records point worth copying: as-built drawings carry the PE's certification only so far as the PE, or someone under the PE's responsible charge, verified the field conditions; otherwise they must state where the field data came from. The register stores each drawing with that statement attached.

• PROPERTY AND HOLDER

  The address, the original holder and any later holder under a transfer.

• THE DOCUMENT

  The written warranty itself, its date and its stated term, linked rather than summarized.

• WHAT WAS DONE

  The engineer's design reference, the work order, the as-built drawings and the completion paperwork.

• READINGS

  Elevation readings from before and after the repair, exactly as recorded, with who took them and when.

• TRANSFERS

  Each request, when it arrived, the paperwork the warranty asks for and its status.

• CONTACTS

  Every inquiry made under the warranty, and who answered it.

Every item below is either an engineering judgment or a commitment in the company's name. The Bots prepare the paper for each one and hold none of them.

• STRUCTURAL STATEMENTS

  Failure or structural need: a PE where the state's rule requires one, and in this design everywhere.

• REFERRAL

  Whether a job goes to the engineer: the inspector and the owner.

• DESIGN

  Repair method, pier type, number and location: the engineer.

• PRICE

  The owner, from the engineered design.

• LIFT AND RESULTS

  Level floors, lift or cracks closing: never promised by the back office.

• PERMITS

  Whether one is required, and every application: the owner.

• WARRANTY TERMS AND TRANSFERS

  The owner, from the written document.

The first step is a page, not software: what the company's intake must never say, written by the owner and read by its engineer. Then trace a month of inquiries from photo to warranty and find where jobs waited: for an inspection slot, for paper the engineer asked for, for a report nobody chased, or for a warranty file nobody could find.

For a foundation company, the scoping work with Aevrion Ops covers the intake boundary, the Bots and their approval rules, and custom integrations to the inbox, scheduling and job systems already in use, built only where a vendor's terms or API permit and tested first. Once the omissions page exists, the readiness assessment for workflow automation is the next step. Where the engineer relationship or the warranty book is the harder problem, start with a conversation through the contact page instead.

1. North Carolina's engineering board says a statement of foundation failure should come only from a PE who has evaluated the conditions; rules vary by state.
2. The intake assistant's most important rule is a list of omissions: no cause, no severity, no repair, no result, no reading of the photo and no repair price.
3. That rule lives in the Bot's memory as a lasting rule, which is guidance rather than a technical control, so the owner reads every homeowner draft before sending it.
4. The engineer's pack carries the inquiry, the inspection record, readings and history; pier type, number and location stay the engineer's.
5. The warranty register keeps documents, readings and transfer paperwork in the company's own system, and transfers run as the written warranty allows.