Spring thaw, one operator: triage, inspection routes and discharge checks.

A snowmelt week does not send a waterproofing company one kind of problem. It sends a basement with water across the floor, another with a damp smell, a third where the homeowner is worried about a dark patch on the drywall, and a fourth where the pump runs but the water has nowhere to go. An operator who inspects, sells and services alone cannot see all of them on Monday. The triage rule decides who waits, and a rule that lives only in the operator's head gets applied differently at eleven at night.

This is the one-man army arrangement the pillar article describes: one operator, several named assistants, and every decision still the operator's. Every Grok Bot feature this week relies on is documented: Bots with names and jobs, one persistent cloud computer they share, routines on a timetable, direct messages between Bots, and group chats. The thaw week below shows which jobs those assistants can take, and which stay with the operator.

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.

Consider, in this illustration, an owner-operator in a northern town with one van, a hired laborer for dig days and a few hundred sump pumps installed over the years. A warm weekend after a heavy winter has melted most of the snow at once. By Monday there are web forms, answering-service notes and emails with photos attached, and the operator's phone has a list of calls to return.

The phone is not part of the assistants' work. Grok Bot's documentation describes no telephony: no answered calls, no voicemail, no texts. So calls are returned by the operator and captured by whatever answering arrangement the company already has; the missed-call workflow article covers that side. What the assistants receive is the written record: the forms, the notes and the emails, moved into a folder they can read by a custom integration built for the services the company uses.

The operator writes the rule once, before the thaw, and gives it to the triage Bot in chat as a lasting rule to remember. A remembered rule guides the Bot; it is not a technical lock. So the Bot shows which line of the rule each card matched and the operator reads the top of the queue before anything else happens.

Two rows lean on EPA's mold and moisture guide for homeowners, checked on 15 October 2026: sewage means a referral to a contaminated-water professional, so the triage Bot drafts nothing for that customer, and the guide's twenty-four to forty-eight hour drying window is why a soaked finished room outranks a damp unfinished one.

The operator creates five Bots under Aevrion's pattern and puts them in one group; a group may hold between two and six Bots, so five fits. The triage Bot ranks inquiries and posts the queue. The routes Bot drafts the inspection order. The proposal Bot writes up inspections. The discharge Bot researches the local rule for each sump job. The plans Bot keeps the service-plan register. None of these roles is a product feature; each is a Bot the operator created and described.

In the documentation's example of a group, one Bot acts as coordinator and is able to assign work; here the triage Bot takes that role: it posts the morning queue and hands each booked inspection to the routes Bot. A Bot that supervises the others and makes decisions is not a documented feature, and this one decides nothing. Bots can also message each other directly, asynchronously, with the handoff visible in the conversation. Cursor's help pages say no switch turns those direct messages off; a Bot follows instructions about them.

Nothing that needs the operator's yes is shown in the group: approval requests, login requests and email drafts stay out of group chats, so each customer reply is approved in the drafting Bot's own conversation. Pictures take another path. Handoffs to a group are text only for now, so a customer's photo reaches the proposal Bot directly: the operator attaches it to the triage Bot's conversation, and the triage Bot sends it straight to the proposal Bot rather than posting it to the group.

At five each morning a routine on the routes Bot reads the ranked queue and the operator's diary and drafts the day: first-rank calls first, then inspections grouped by area so the van is not crossing town three times. Reading a diary held in field-service or scheduling software is a custom integration or supervised browser use where the vendor permits it, subject to testing; the documentation is clear that a Bot's memory cannot stand in for the live record. Once that diary login is saved on the computer the five Bots share, every one of them can use it; the documentation is explicit that Bots are not a security boundary, and anything that must stay walled off needs a different user account.

The draft makes no promises. A time window goes to a homeowner only when the operator sends the confirmation from the routes Bot's conversation. If anything in the routine needed approval while the operator slept, the request would lapse after about ten minutes (Cursor's help pages say thirty) without running, so the routine is built to prepare and stop.

1. 01

   Message received

   Owner

   The answering arrangement, then the triage Bot

   Advances when

   Card built from the note and photos and ranked under the rule

2. 02

   Top of the queue

   Owner

   The operator

   Advances when

   The operator calls back and decides to visit today

3. 03

   On the route

   Owner

   Routes Bot, then the operator

   Advances when

   Visiting order drafted, the operator confirms the window and sends it

4. 04

   Inspected

   Owner

   The operator

   Advances when

   Water's path diagnosed, system chosen, notes and photos handed to the proposal Bot

5. 05

   Discharge note

   Owner

   Discharge Bot

   Advances when

   The local rule found, linked and dated, with points to confirm

   Ends when

   If no rule can be found, the note says so and the operator asks the municipality

6. 06

   Proposal sent

   Owner

   The operator

   Advances when

   Draft checked, priced from the catalog and sent

   Ends when

   Nothing reaches the homeowner before the operator sends it

Midweek, the discharge questions arrive. A pump that runs while the yard is still frozen can push water into a line that cannot take it, a thaw problem the operator watches for as a matter of trade practice rather than anything an assistant diagnoses, and the operator decides what to tell the homeowner. A homeowner on the list asks whether they can run a hose from the pump to the floor drain until spring. The triage Bot drafts no answer. The card goes to the operator with the discharge Bot's note attached.

For the hose question, the discharge Bot's note gives the homeowner's town, the rule it found on the town's site with the date it was read, and the point the operator must confirm before replying; nothing in it could be read by a homeowner as approval. One Minnesota city, Delano, keeps sump water out of its sanitary sewer by ordinance and charges non-compliant properties a surcharge every month; the companion article on sump service plans walks through that ordinance. Rules differ by municipality, and the operator checks the one that applies.

The proposal Bot works from the inspection notes, the photos and the operator's own catalog of systems: which walls get drain tile, where the basin goes, whether a window well needs a drain, whether the downspouts need extending. Where the water comes from was the operator's judgment in the basement; the draft records it and does not argue with it.

Prices come from the catalog every time, never from what the Bot remembers of last year. The warranty paragraph is the operator's text, copied exactly, so no draft describes a result the warranty does not promise. One proposal waits on purpose: in the soaked finished room, the operator referred drying to a restoration company first, and the proposal Bot holds the draft until the operator says the room is ready to be quoted.

Several of the week's calls came from homeowners whose pumps the operator installed years ago. The plans Bot checks each one against the service-plan register in the shared workspace and gives the operator two short lists. The first is plan customers who called, with their last visit record, so the operator can see whether a tested pump failed or an untested one did. The second is customers with no plan whose pump stopped this week, for the operator to decide whether a plan offer would be welcome once the water is gone.

Any offer is a draft, sent by the operator from the plans Bot's own conversation, and none goes out while a basement is still wet. The plans Bot also adds the week's new installations to the register so their first service visit is not forgotten. How that register, the reminder routine and the visit record work is the subject of the sump service plan article.

When the week closed, the operator could say which line of the rule put each basement at the top, which of the week's failed pumps had never been on a plan, and which towns' discharge rules were still unconfirmed. The mold worries reached the operator unanswered rather than half-answered by a machine, which in this trade is the point.

For an operator whose spring calendar the thaw already sets, the workflow automation readiness assessment comes first. It costs nothing and needs no email address. Pick thaw-week triage as the one workflow to score across its twelve fixed dimensions; if the ranking has never been written down, rule clarity is where the score drops, and that dimension caps the overall result. A scoping conversation with Aevrion Ops can follow, covering the written triage rule, the five Bots and links to your inbox and scheduling tools, which depend on what each vendor allows and on testing.

1. A thaw week mixes floods, damp and mold worries; a triage rule written in advance decides which basement is seen first.
2. Contaminated-water messages go straight to the operator as referrals, and wet finished rooms rank high because EPA's guide sets a twenty-four to forty-eight hour drying window.
3. Five Bots share one group (the documented ceiling is six); a reply waiting for approval appears in the drafting Bot's own chat, never the group, and photos travel Bot to Bot.
4. Routes are drafted before dawn; only the operator sends a time window to a homeowner.
5. The discharge Bot researches the local rule; the operator, never an assistant, answers whether a discharge is allowed.
6. Calls stay with the operator: Grok Bot's documentation describes no telephony, so the assistants start from written inquiries.