The first heat wave in a two-truck HVAC shop: surge operations.

When the first heat wave lands, a small HVAC office stops being an office and becomes a triage desk. Nearly every ticket says the same thing, no cooling, and the order in which they are answered is a judgment about people: who is in the house, how vulnerable they are, whether the household has a maintenance agreement, and where the trucks will be. Those judgments can be prepared for, but they cannot be made well at the moment the queue is longest.

This article covers the operating side of that week: the rules an owner writes before the forecast, the queue card that carries them, and how a small roster of AI assistants can prepare the triage desk without making its decisions. Aevrion's HVAC operations page covers lead flow, CRM design and the service itself, and calls are treated here as a separate system.

DOE's consumer guide to home heating and cooling advises that air conditioners be inspected in the spring and furnaces checked in the fall (as checked on 13 October 2026). For a shop with maintenance agreements that produces two booking waves a year, and the spring wave of cooling tune-ups can still be running when the first hot week arrives. The heat wave does not replace the spring queue; it lands on top of it.

Consider a two-truck shop in this illustration: the owner, who runs the second truck when needed, one technician, a summer apprentice, and nobody full-time in the office. Tune-ups are booked through May. Then the forecast turns, and the written inquiries, answering-service notes and messages start saying 'no cool' far more often than anything else. The volume is not the point; the shape is. Every ticket is now competing for the same two trucks, and every hour of indecision is an hour a household spends in the heat.

These are decisions, so they belong to the owner. Writing them down in April is what lets an assistant apply them consistently in July, and what lets the owner see at a glance when a rule produced the wrong answer.

• WHO COUNTS AS VULNERABLE

  The owner defines the flag: an infant in the home, an older occupant, someone whose medical condition or equipment depends on cooling, or anything else the owner decides belongs on the list. An assistant marks a card only when the customer's own words match that list. It never infers vulnerability, and the owner decides how a flagged card is prioritized.

• WHERE AGREEMENT MEMBERS SIT

  Agreement member yes or no goes on every card, read from the system of record. The rule says how membership ranks against vulnerability. In this illustration a vulnerable household without an agreement comes before a member whose upstairs is merely warm, and the owner can change that ranking.

• WHAT NO-COOL MEANS

  Not cooling at all, cooling weakly, a frozen coil, water from the air handler, a new noise. Each carries a different urgency under the owner's rule, and the card records which one the customer described.

• ROUTE AREAS

  The service area split into zones the dispatcher recognizes, so each day's cards can be grouped by area for the dispatcher to accept or reject.

• WHO MAY TOUCH REFRIGERANT

  Only technicians who hold the right type of Section 608 certification, or an apprentice under the close and continual supervision EPA's rules require. The roster says who that is before the week starts.

The card is the triage desk's working unit. An intake assistant fills it from what has already been captured in writing, and the owner or dispatcher reads it. The format is an Aevrion pattern and should be adapted to each shop.

In the One-Man Army model, one owner supervises a small roster of named AI assistants that prepare the work while the owner keeps every decision; the pillar article explains it in full. For a heat wave, Aevrion's pattern is a temporary surge group of four Bots: a Coordinator, an Intake Bot that builds the cards, a Scheduling Bot that groups them by route area, and a Customer Drafts Bot that prepares the status messages the owner may choose to send.

The pieces are documented. Grok Bot supports group chats of two to six Bots in which a coordinator can assign work, Bots that send each other asynchronous requests, and handoffs of ownership from one Bot to another. The Coordinator's job is narrow: post the queue in the owner's order, assign each card to the Bot that prepares its next step, and report what is waiting on a person. A chief-of-staff Bot that supervises the others is not a documented feature; it is Aevrion's pattern, built on those pieces.

Two documented limits shape the group. Approval requests, login requests and email or Slack drafts do not appear in a group chat, so every customer message the owner might send sits in the Customer Drafts Bot's own conversation, and that is where the owner approves it. And handoffs to a group are text-only, so a photo of a frozen coil or a dripping air handler goes directly from one Bot to another. The owner can switch on per-Bot notifications, so a card waiting for a decision is visible without watching the group all day.

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.

In a surge, the cheapest capacity a small shop has is the drive it does not make. The Scheduling Bot groups the day's cards by route area and proposes an order within each area, with flagged cards pinned at the top wherever they sit. It reads availability from the calendar or field-service platform every time, through a custom integration or supervised browser use where the vendor permits it, subject to testing, because yesterday's availability is wrong by mid-morning.

The dispatcher, who in a two-truck shop is usually the owner, accepts the grouping, rejects it, or breaks it for a reason the rule cannot know: a technician with the right capacitor already on the truck, a customer who can only be home after four, a household the owner knows has an older relative staying. The Scheduling Bot never moves a booking on its own and never tells a customer a time. A grouping that keeps being rejected means the zones or the rule need rewriting.

Heat waves do not stop at six o'clock, and neither do the written inquiries. Routines can keep running through the evening on a schedule at least five minutes apart, so the Intake Bot can go on building cards from new notes on each scheduled run. What cannot happen overnight is anything that needs the owner's yes: an approval request raised by unattended work expires after about ten minutes (Cursor's help pages say thirty) and the action does not run. The design follows from that. Evening and overnight work ends in cards and drafts, and the owner reads the queue first thing.

Calls are a separate system. Grok Bot's documentation describes no telephony, so nothing in this setup answers or returns a call during the surge. How a shop handles calls it cannot pick up is the subject of the missed-call workflow article; this article starts from what has already been written down.

A heat wave pushes a shop to send whoever is available. Refrigerant work is where that pressure must not win. EPA's Section 608 rules require technicians who maintain, service, repair or dispose of equipment that could release refrigerants to hold Section 608 certification. There are separate types for small appliances, for high- and very-high-pressure appliances and for low-pressure appliances, plus a universal type, and apprentices are exempt only while closely and continually supervised by a technician who holds it (as checked on 13 October 2026).

EPA's page also says Section 608 credentials do not expire. So the useful list is not a renewal calendar; it is which certification type each person holds, entered by the owner from each technician's own credential. When a technician's notes point to refrigerant work, the Scheduling Bot checks that the assigned technician's type is on the list and flags the card if it is not. It does not decide whether refrigerant work is needed, how much, or whether a leak must be repaired first. Those are the technician's and the owner's calls.

The week after a heat wave is when the rules can be corrected while the cases are fresh. Which flagged cards were right, and which households should have been flagged but were not, because the customer never mentioned an infant or an elderly parent? Which route groupings did the dispatcher reject, and why? Which drafts did the owner never send? Each answer is a change to a written rule, made by the owner.

Replacement estimates written during the surge belong in the shop's normal follow-up process, which has its own article, and the surge group should be stood down before the fall wave rather than left running. Aevrion Ops can help HVAC owners write the surge rules, design the roster and build the integrations to their field-service platform, where the platform's API or terms allow it and after testing; the HVAC operations page describes the wider lead-flow work, and the workflow automation readiness assessment is the place to start.

1. A heat wave turns a small HVAC office into a triage desk, so the triage rules have to be written before the forecast.
2. Vulnerable-occupant flags, agreement ranking, no-cool categories and route areas are the owner's decisions; assistants only apply and mark them.
3. Each queue card carries the symptom, a vulnerable-occupant flag, agreement member yes or no, route area, equipment notes and what is missing.
4. A coordinator-led surge group of Bots prepares the queue; approvals and customer drafts stay in each Bot's own conversation, outside the group.
5. Overnight, cards and drafts are prepared and nothing is sent, because approvals from unattended work expire after about ten minutes (Cursor's help pages say thirty).
6. Refrigerant work goes only to technicians holding the right Section 608 certification type, or apprentices under close and continual supervision.