Broken-spring Saturday: a garage door office run from the driveway.

When the owner is also the only technician, every job on a busy weekend leaves a trail: spring sizes to restock, a safety-check record to complete, an install quote still waiting for an answer, and the platform paperwork that keeps the business able to advertise. None of it is urgent at nine on Saturday morning. All of it is overdue by Monday.

A few AI assistants can carry that preparation while the owner is up a ladder. They turn the technician's own measurements into a restock list, assemble the safety record for the technician to sign, keep the verification folder current, and lay out the weekend for a Sunday-evening review. They do not answer the phone, price a door, choose a spring, sign a safety test or submit anything to Google. The model is the one-man army: the owner-technician keeps every commitment and a few named assistants each prepare one kind of office work, as the pillar article on the one-man army explains in full.

On a busy weekend the office of a one-truck garage door company is the cab of the truck, and it is open for about ten minutes between jobs. Everything that can wait for those ten minutes, or for Sunday evening, is the work the assistants prepare.

The assistants here are Bots in Grok Bot: a parts desk, a records desk and a verification desk, each a named Bot with one job and its own chat, all running on the same cloud computer with a browser and files. They can message one another, pass a task across, and sit in a group of two to six Bots where a coordinator gives out the work. None of them goes near the phone, because Grok Bot describes no calls or text messages. None of them plugs straight into the door company's field-service, CRM or advertising software either: no field-service connector is named, and the CRM and advertising apps the documentation lists appear only in an enterprise network-settings table with no description of what they can do, so each link is a custom integration or supervised browser use where the vendor permits it, subject to testing.

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.

Consider a one-truck garage door company on a Saturday in this illustration; nothing here describes a real business. By nine the owner-technician's list holds four items:

• SPRING JOBS

  Three broken torsion springs booked across the weekend, each with the homeowner's photo of the door.

• A PENDING INSTALL QUOTE

  A new-door quote that went out on Wednesday and has had no reply.

• A VERIFICATION TASK

  A note to review the business's Advanced Verification details, because the business address changed last month.

• THE TRUCK

  Spring stock running low after a busy week.

The calls that produced those bookings, and the ones that will arrive over the weekend, belong to a separate system with a separate page. Nothing in this article changes how the phone is answered.

Three parts of this weekend already have their own pages on this site, and this article does not repeat them.

• CALLS

  What happens when a call goes unanswered, including triage, callback ownership and messaging conditions, is the subject of the garage door missed-call recovery page. Grok Bot cannot take or return a call.

• THE INSTALL QUOTE

  How a priced door proposal is followed up, and when follow-up stops, is the subject of the estimate follow-up page. Here the quote is simply an item on the owner's list.

• THE CRM

  How the system of record should be shaped for urgent repairs and planned installs is the subject of the CRM set-up page. The assistants below read from that record; they do not redesign it.

Spring work is neither a homeowner job nor an office decision. An article in DASMA's Door & Access Systems magazine urges that repairs of this kind be done by a trained door systems technician. The same logic applies inside the business: the technician measures and identifies the spring, and nobody else picks one.

The parts desk works from what the technician records on each job: the spring measurements and the parts used, typed or photographed on site. From an iPhone those photos go straight into the desk's chat through the share sheet; an Android phone's share sheet passes only text at present, so its photos wait for the desktop. The desk turns the records into a restock list against the owner's usual parts and suppliers, and flags anything it cannot read instead of filling it in.

Ordering stays with the owner. A supplier's website can sometimes be used through the Bot's browser where the supplier permits it, subject to testing, but checkout and payment are handed to a person: the Grok Bot documentation routes payment confirmations, logins and two-factor checks to a human takeover rather than letting the Bot complete them. Cursor's help pages add a Vault, where saved logins and cards let a Bot sign in and check out without seeing them, and no setting asks for approval each time a saved card is used, so this design saves no card there.

Each repair finishes with a safety check on the opener and the door, and the record of that check matters more than any other paper on the job. The safety-check records article in this series covers the record field by field. On a weekend like this one, the records desk does three things:

• PRE-FILLS

  Copies the job details, the door and opener as recorded on the work order, and the parts used into a blank record.

• CHASES

  Lists which of the weekend's jobs have no completed record and asks the technician for the missing fields.

• DRAFTS THE CARE NOTE

  Prepares the owner-approved care note for each customer, including the advice to leave spring work to a trained technician, for the owner to send.

The technician completes the test fields and signs. The desk never checks a box on the technician's behalf.

As checked on 13 October 2026, Google's Advanced Verification policy lists garage door services in the United States among the categories where Advanced Verification is required to advertise. The policy describes checks on business registration and license validity, a recorded video interview, and requests for documents such as a business-name registration certificate or proof of address. It asks advertisers to tell Google promptly about changes that could affect verification, such as a license expiring, and says re-verification may be needed after significant changes such as moving location or changing website.

That is exactly the paperwork that slips in a one-owner business. The verification desk keeps one folder: the current business registration, any licenses that apply, proof of address, the insurance documents the owner chooses to keep there, and a change log of anything that might matter, such as an address or website change. When the log gains an entry, the desk raises it in the owner's own conversation with the relevant documents attached.

Everything that touches Google stays with the owner. The owner signs in, completes the video interview and submits; logins and two-factor checks are handed to a person in any case. An advertising-account session left signed in on the Bots' shared computer is open to the parts and records desks too. If that matters, the fix the documentation gives is a separate user account; adding another Bot separates nothing.

At ten past eleven the owner is under a door with a snapped torsion spring. The measurements go into the job notes, and the photo of the spring and its tag goes directly into the parts desk's own chat: the documentation says Bot-to-group handoffs are text-only, so the photo is kept out of the group altogether. All the group sees is one line from the coordinator: 'photo sent to Parts, job 3, restock check pending'. When the restock line is drafted, the parts desk says so in the group, and the owner looks at it between jobs.

The coordinator that posts those lines is an Aevrion pattern assembled from two documented pieces, the group coordinator and messages between Bots. The Grok Bot documentation describes no Bot that supervises a roster, and its Chief of Staff example only briefs a person. With the three desks and the coordinator, the group sits inside the documented limit of two to six Bots.

Anything that needs the owner's say stays out of the group. The homeowner's care-note draft waits in the records desk's chat, and the request to sign in to the advertising account waits in the verification desk's chat, because approvals, sign-in requests and drafts never show in a group. Where an approval card does appear, it offers Allow once, Always allow and Deny, and the iPhone has the same three buttons.

A Sunday-evening routine can assemble the weekend: jobs done, records unsigned, parts to reorder, the install quote's status as read from the system of record, and anything new in the verification change log. Routines run on a schedule at least five minutes apart, which is no constraint at all for a weekly summary.

The routine prepares; it is designed not to send. An approval raised by unattended work, such as a routine, expires after about ten minutes (Cursor's help pages say thirty) and the action does not run, and an approval never undoes work already done. So the routine leaves drafts, and the owner sends what is right after reading them. Whether a given step pauses for approval is set by the tool, its risk and the rules the owner writes, so those rules are written before the first busy weekend.

The records desk is the best first assistant: its output is the record the technician signs anyway, and nothing it produces reaches a customer without the owner. Run it on read-and-prepare work first, which is the documentation's own recommended starting point, before adding the parts desk.

For the sales side of the same business, the garage door lead-flow checklist on this site walks every handoff from inquiry to outcome and is the right place to start on calls and quotes; the garage door overview page explains how those parts connect. For the office work described here, the workflow automation readiness assessment is the first step with Aevrion Ops.

1. A one-technician garage door company builds an office backlog around every job: parts, safety records, a pending quote and verification paperwork.
2. Calls, quote follow-up and CRM set-up have their own pages; this model covers the office work around them.
3. Spring sizes come from the technician's measurements; a parts desk lists and flags but never chooses.
4. Google requires Advanced Verification for US garage door services; a Bot can keep the folder, and the owner signs in, interviews and submits.
5. The group line only says what moved; the spring photo goes straight to the parts desk, and approvals and drafts wait in each desk's own chat.
6. Weekend routines are designed to leave drafts for a Sunday review, because unattended approvals expire.