Sixty inspection requests in three days: a siding week after hail.

Take an illustrative company: a siding business run by its owner, who inspects, estimates and sells, with one install crew under a crew lead and a part-time office helper. A hailstorm crosses the service area on a Tuesday evening, and by Friday sixty inspection requests are waiting. Most of those homeowners will wait regardless. What the owner controls is whether each house has one record, whether the waiting is in a sensible order, and whether every inspection produces a photo set that can be compared with the next.

That is the one-man army model applied to a siding surge: one owner making every decision, with a few named assistants each preparing one kind of work. The pillar article explains the model; this one follows a single week. The company, the storm and every number in it are invented by Aevrion; none of it describes a client or an outcome.

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.

The requests come in through every door the company has: the website form, emails from past customers, forwarded referrals and the owner's own notes from calls taken between jobs. The documentation for Grok Bot, the product used in this illustration, describes no calling, so the phone stays with the owner. What reaches the assistants is what has already been written down; the owner attaches emails as files, which the Bots can read. Moving form submissions into a folder the Bots can read is a custom integration, built and tested for the form tool the company uses.

Many of the sixty are the same house twice: a homeowner who filled in the form and also emailed. Replying to each separately would book the same wall twice and send a family two different dates. So the first job of the week is not a reply. It is a list of houses.

The owner created three Bots, each with one job and standing rules given to it in chat to remember: never contact a homeowner, an insurer or a supplier, never state a cause of damage, and report a gap rather than fill it. Remembered rules are guidance, not a lock, so every outgoing message waits as a draft for the owner.

• INTAKE BOT

  Keeps the request board: merges duplicates into one record per address, flags anything it cannot match and drafts inspection routes for the owner.

• ELEVATION BOT

  Files each inspection's photos into elevation folders, checks the set against the owner's photo protocol and drafts a neutral observation summary.

• CALENDAR BOT

  Holds the install calendar for jobs already sold, runs the morning weather check and coordinates the group.

So that the week's handoffs show in one place, the owner adds all three Bots to a single group chat. The Calendar Bot coordinates there, because inspection days and install days compete for the same owner; the documentation's coordinator can assign work, but a Bot that supervises others is Aevrion's arrangement, not a feature. Every homeowner and crew draft is written in the owning Bot's own conversation, where only the owner sends; a crew lead or the office helper may be asked, never sends.

Every request moves through the same states. Writing them down shows where a house can stall, and the stall that matters most has nobody's name on it.

1. 01

   Received

   Owner

   Intake Bot

   Advances when

   The address is matched to an existing record or opens a new one.

2. 02

   Unmatched

   Owner

   Nobody until the owner reads the flag

   Advances when

   The owner confirms which house the request belongs to.

   Ends when

   Closed as a duplicate, with the earliest request date kept.

3. 03

   Queued

   Owner

   Intake Bot

   Advances when

   The owner accepts a route day that includes the house.

4. 04

   Routed

   Owner

   Owner

   Advances when

   The homeowner confirms access in reply to a confirmation the owner sent.

5. 05

   Photographed

   Owner

   Elevation Bot

   Advances when

   Every elevation in the protocol has a wide shot and its close-ups, or the gaps are listed.

6. 06

   Summarized

   Owner

   Elevation Bot

   Advances when

   The owner reads the neutral summary and corrects it.

7. 07

   With the homeowner

   Owner

   Owner

   Advances when

   The owner sends findings and, if asked, an estimate.

   Ends when

   The homeowner decides what to do next, including whether to contact their insurer.

By Thursday night the Intake Bot has turned sixty requests into a shorter list of houses and drafted route days grouped by area. The order inside each route follows a rule the owner wrote before the storm: a wall open to the weather goes first, then houses where the homeowner reports broken or missing pieces, then everything else by request date. The Bot applies the rule and shows which clause put each house where it is. The owner reorders freely.

For each house on an accepted route, the Bot drafts a confirmation in its own conversation: the day, a window the owner chose, and three questions that save time at the curb. Will someone be home? Is there a gate, a dog or a locked side yard? Can every side of the house be reached? The owner sends each one, and passes the answers back for the board.

The owner's photo protocol is the heart of the week: short enough to follow on a wet driveway, strict enough that two houses photographed on different days read the same way. The Elevation Bot checks each set against it and lists what is missing.

• NAMING

  Front, right, back and left, as seen from the street and walking clockwise, so a note about the left elevation means the same wall every time.

• WIDE FIRST

  One wide shot of each elevation before any close-up, so each close-up can be placed on the wall.

• CLOSE-UPS

  Each close-up labeled with its elevation and position, such as left, third course from the bottom, near the rear corner.

• OPENINGS AND TRIM

  Window and door surrounds, corners, J-channel and soffit on each side, because damage there changes the material list.

• OTHER ITEMS

  Whatever else the owner's checklist records at every house, such as gutters, downspouts and window screens, photographed in the same order.

• EXPOSED WRAP

  Any place the house wrap shows, noted for the owner's attention.

• GAPS

  Any elevation or item the protocol expects and the set lacks, with the reason if the owner gave one.

The owner photographs on a phone and attaches each set, in batches of six on the desktop, to the Elevation Bot's conversation with a line of notes. When the crew lead photographs a house the owner cannot reach that day, those photos come in the same way: the crew lead hands them to the owner, or saves them to a cloud folder the owner set up, which the Bot reads through a tested custom integration. The Bots sit on the owner's account, not the crew lead's.

The Bot files each set into folders by address and elevation in the computer's shared workspace, where the other Bots can read them. It never deletes or renames a photo the owner filed, and a missing elevation is a listed gap, not a silent hole. When the Elevation Bot needs a photo the Intake Bot received with a request, it asks the Intake Bot directly, Bot-to-Bot, because group handoffs are currently text-only; Cursor's help pages say no switch turns off direct messages between Bots.

For each house the Elevation Bot drafts a short summary the owner corrects before anyone else sees it. Its value is that it is neutral. It records what is on the wall and in the photos. It never says what caused a mark, never says whether anything is covered by insurance and never estimates what a repair will cost.

Some homeowners will contact their insurer and some will not; that is their decision, and the claim is theirs. In this company the owner attends an adjuster's inspection only when the homeowner asks, and the Bot's part is clerical: it records the date the homeowner gives and prepares the elevation set and summary for the owner to bring. It does not contact an insurer or an adjuster. No draft offers to negotiate, and none claims the company acts for the homeowner.

Only one state's rule is set out here. As checked on 15 October 2026, Texas Insurance Code section 4102.163 bars a contractor from acting as a public adjuster, or advertising that it will adjust claims, for any property on which it is doing or may do contracting work, and that holds even if the contractor holds a public adjuster license under that chapter or acts under a power of attorney or other agreement. That is Texas's rule. Other states' rules are not described here, and a company in any state checks its own position with its lawyer.

The FTC's guidance for homeowners after storms and disasters, checked the same day, says to verify insurance coverage rather than rely on a contractor to say what is covered, and never to sign an insurance check over to a contractor. The owner's drafts are written to sit beside that advice. The claim file itself, from scope versions to supplements, is the subject of the roofing claim-records guide in this series, which owns that workflow for roofing, siding and gutters.

The storm did not cancel the jobs sold before it. On Friday the Calendar Bot's morning check reads rain for Saturday at the house where the crew is halfway through a re-side, with the back wall wrapped and the front still open for tear-off. Under the owner's written rule, open-wall tear-off holds and trim work under the porch may go ahead. The Bot posts the recommendation to the group as text and drafts, in its own conversation, a notice to that homeowner and a two-day crew plan rebuilt around the hold. The owner asks the crew lead's view, makes the call and sends the notice. The Bot cancels nothing, and because the check runs before anyone is watching, it stops at drafts.

By the following week the board holds far fewer open houses, and the ones that become jobs turn into ordinary siding work: an estimate in squares, a selections sheet the homeowner signs, an order and an install date the weather will try to move. The elevation folders built in the surge are the base for all of it, which is why the protocol mattered more than the speed.

If a surge like this would swamp a company today, the readiness assessment is the place to start. It is free, scores one workflow against twelve fixed dimensions and returns its result and blockers at once; storm intake is the workflow to score, and ownership clarity will be its weak dimension if only the owner can say which request belongs to which house. The request board, the photo protocol and the group can then be scoped with Aevrion Ops, with any custom integrations tested before storm season rather than during it.

1. After hail, merge requests into one record per house before replying; a duplicate booked twice costs more than a slow reply.
2. A fixed elevation protocol (named walls, wide shot first, labeled close-ups, listed gaps) makes every inspection comparable.
3. Observation summaries stay neutral: what was photographed and noted, never cause, coverage or cost.
4. The homeowner files any claim; in this illustration the owner attends an adjuster's visit only when asked, and Texas bars contractors from public adjusting on properties they work on.
5. Drafts live in each Bot's own conversation with the owner, photos move Bot-to-Bot, and only the owner sends.