After the hailstorm: claim records without crossing into public adjusting.

Storm intake is a sorting problem before it is a speed problem. An assistant can merge duplicate inquiries, group roofs into an inspection queue by area and draft a request for ground-level photos. Once a job becomes an insurance job, it can keep the claim file complete: photos, the measurement report, the adjuster meeting date, scope versions and a supplement draft for the owner to review.

It does not contact the insurer or the adjuster, and it drafts nothing that offers to negotiate a claim. In Texas, as checked on 13 October 2026, a contractor may not act as a public adjuster for a property where it does or may do the work. Other states' rules are not described here. In this pattern, storm damage to siding and gutters goes into the same claim file.

After a storm, written inquiries arrive through several channels and many describe the same roof. Answering each separately produces double bookings and contradictory messages, so knowing which inquiries are the same job matters more than replying first.

The assistant here is a Bot in Grok Bot: a named assistant on a cloud computer, following a written procedure in a routine that runs every half hour. It merges records that share an address and flags anything it cannot match with confidence, because merging two different homes is worse than keeping a duplicate. The documentation describes no telephony, and getting form submissions and answering-service notes to the Bot is a custom integration.

What each merged record carries into the inspection queue (an Aevrion pattern):

• AREA

  The ZIP code or neighborhood, so the owner can plan inspection days street by street.

• FIRST CONTACT

  The earliest date and channel, kept as the record of when the homeowner asked.

• WHAT WAS REPORTED

  Leaks, stains, visible damage, in the homeowner's words, never translated into a damage assessment.

• CLAIM STATUS AS STATED

  Whether the homeowner says they have contacted their insurer. The assistant records the answer and gives no advice on filing.

• PHOTOS

  Whether ground-level photos have arrived.

Based on the Grok Bot documentation at docs.x.ai as checked on 13 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.

The first message to each homeowner, drafted by the assistant and sent by the owner, acknowledges the inquiry, gives an honest idea of when an inspection is likely, and asks for photos taken from the ground: each side of the house, any interior stains, and debris such as hail-damaged shingles in the yard. It says plainly not to climb onto the roof or a ladder. Roof access belongs to a trained crew; OSHA requires fall protection at six feet in the construction industry, as checked on 13 October 2026.

Those photos do not establish damage. They help the owner order the inspections, an active leak before a missing ridge cap, and the order is the owner's decision.

Storm inboxes carry a specific risk. The documentation warns that content a Bot reads can try to steer it, and that its layered controls reduce but do not eliminate that risk. A queue full of strangers' messages is exactly that kind of content, which is one more reason every outgoing message stays a draft the owner sends.

When a job becomes an insurance job, the assistant opens a claim folder in the shared workspace and keeps an index of what it holds and what it lacks. The owner and the homeowner use the index; the assistant never sends it anywhere.

1. 01

   Inspection photos

   Decides

   Is every slope, elevation and interior stain covered, dated and labeled?

   Output

   A photo index by roof plane, with gaps listed

2. 02

   Measurement report

   Decides

   Has it arrived, and do its address and roof outline match the photos?

   Output

   The report filed, or a mismatch flagged for the owner

3. 03

   Adjuster meeting

   Decides

   When is the insurer's inspection, as the homeowner reports it, and will the owner attend at the homeowner's request?

   Output

   The date in the file and a preparation checklist for the owner

4. 04

   Scope versions

   Decides

   Which version of the insurer's scope and of the company's estimate is current?

   Output

   Every version filed with its date and source, none overwritten

5. 05

   Differences

   Decides

   Where do the estimate and the scope differ, line by line?

   Output

   A comparison for the owner, each line referenced to photos

6. 06

   Supplement draft

   Decides

   Does the owner want to document items the scope leaves out?

   Output

   A draft for the owner, who decides, with legal advice, whether and how it may be used without crossing the Texas public-adjuster line

7. 07

   Open questions

   Decides

   What is unknown or unverified?

   Output

   A list kept apart from the documented facts

Rules on contractors and insurance claims are set state by state. This article states the Texas rules only, because they are the ones Aevrion has verified; a roofing company in any other state should confirm its own position with a qualified adviser.

The Texas Department of Insurance says a roofer or contractor may not act as a public insurance adjuster on a claim if it is also doing the work, and may not advertise that it would. Texas Insurance Code section 4102.163, as amended in 2019, applies that to any property for which the contractor is providing or may provide contracting services, whether or not it holds an adjuster license or a power of attorney. The department's examples of improper conduct include offering to negotiate a settlement or file a claim for the policyholder, and telling insurers or others that the contractor represents the policyholder. A website counts as advertising.

Texas Business and Commerce Code section 27.02 requires a contract priced at one thousand dollars or more, and reasonably expected to be paid from a property insurance claim, to carry a bold-type notice that the policyholder must pay the deductible, and makes it an offense to waive, absorb or rebate the deductible without the insurer's consent. The department adds that insurers may ask the policyholder for proof the deductible was paid.

How those rules shape the assistant's job (Aevrion's design, not legal advice):

• NO INSURER CONTACT

  The Bot does not email, message or log in to an insurer or adjuster. It has been told so as a lasting rule, which the documentation treats as guidance rather than a technical lock, so no insurer portal is signed in on the account's shared computer, where every Bot could use the session.

• NO NEGOTIATING LANGUAGE

  Homeowner drafts describe the company's work and the documents on file. They never promise a recovery, offer to negotiate or say the company represents the homeowner.

• THE DEDUCTIBLE

  The Bot never drafts anything about waiving or discounting a deductible. On Texas jobs it checks that the contract carries the deductible notice block the owner approved and flags one that lacks it. Whether the law applies to a given contract is the owner's call, with legal advice.

• MARKETING

  Storm-season web copy and ads drafted by the Bot follow the same rules, because Texas treats a website as advertising.

• SUPPLEMENTS

  The supplement draft is documentation for the owner. Whether it is used, and how, is the owner's decision under the state's rules.

For consequential work, the documentation advises asking a Bot to separate facts from source systems, assumptions, completed actions, actions awaiting approval and unresolved questions, and to preserve evidence such as source links, screenshots and timestamps. A claim file kept that way shows what is documented, what was inferred and what nobody knows.

Approval cards can stop a consequential action, but which actions stop depends on the tool, the risk and the user's rules; an approval does not undo completed work; and one raised by a routine while the owner is on a roof expires after about ten minutes (Cursor's help pages say thirty) without running. So the Bot prepares and the owner sends.

The Federal Trade Commission's advice to homeowners after weather emergencies, checked on 13 October 2026, tells them not to rely on a contractor to say what their policy covers and never to sign an insurance check over to a contractor. Homeowner drafts that send coverage questions back to the homeowner's insurer sit comfortably beside that advice. Claim files also hold personal and policy details, and memory is not the record, so dates, scope versions and amounts are read from the file each time.

Before building any intake routine or claim-file index, review the last few insurance jobs. Which documents are missing, which scope version was current, and where did a message to a homeowner say more than documentation should? Aevrion Ops can run an insurance-job file audit that answers those questions and maps them to an index and an intake routine; ask through the contact page. The readiness assessment is the broader starting point, and the roofing article in this series shows how the insurance path sits beside retail work around the estimate.

1. After a storm, merge duplicate inquiries into one record per roof and an inspection queue by area before replying.
2. Ask homeowners for ground-level photos only; roof access belongs to a trained crew.
3. Keep a per-claim index: photos, measurement report, adjuster meeting date, scope versions, differences and a supplement draft for the owner.
4. The assistant never contacts an insurer. In Texas a contractor may not act as a public adjuster on its own jobs or waive a deductible; other states are not covered.
5. Every outgoing message is a draft the owner sends; storm inboxes can carry content that tries to steer a Bot.