First heat wave triage: 40 no-cools, 4 techs

The first real heat wave does not build up. It arrives on a Tuesday. It was 78 last week and nobody thought about their air conditioning, and now it is 95 by ten in the morning and every phone in the office is lit. By noon you have forty no-cools written down and four trucks to run them with. You are not going to reach everyone today. You know that already. The question is which twenty you reach, in what order, and what you tell the other twenty so they do not call three more companies while they wait.

That decision is triage, and on the first hot day most small HVAC shops do it badly. Not because the owner is careless, but because the calls come in faster than anyone can think, they get scribbled on a legal pad or dropped into a group text, and the truck that should have gone to the eighty-year-old on oxygen goes to whoever yelled loudest at 8am. The heat did not cause that. The lack of a system did. Like most of what the rest of this proof and getting paid hub covers, the fix is a place to keep the work straight, not more hustle.

The morning the board melts

Here is how it goes without one. Calls start at 7:30. The office manager writes them on a pad, one line each, in the order they ring. By 9 the pad has thirty names and no order to them. The techs are texting the group thread asking what is next, and you are answering each one by hand from the truck.

At 9:40 a customer who called first thing, a maintenance-agreement account you have had for six years, calls back angry because nobody has come. She was line four. But line four got buried under twenty-six newer lines, and the last tech who freed up grabbed the call closest to him, a first-time caller across town. Now your best account is shopping your competitor while she waits, and your tech just drove past two of her neighbors to get to a stranger.

By 2pm the board is a mess nobody trusts. Two techs have quietly worked the same side of town while the other half of the map went untouched. Customers told “sometime today” are calling back for a real time you cannot give them. And the callbacks you promised to make yourself never happened, because you spent the day being the dispatch computer instead of running one.

None of that is a labor problem. Four trucks can move a lot of no-cools in a day. It is a sequencing problem, and sequencing is the one thing a legal pad and a group text cannot do.

The three-tier list

You need the triage decided before the calls come, so that on the hot day the office manager is sorting into buckets instead of inventing an order under pressure. Three tiers is enough for a four-truck shop. Any more and it slows the sort down.

Tier one, go today, no question. Vulnerable people and contract obligations. The elderly, infants, anyone medically fragile, and anyone on a maintenance agreement that promises priority. These are the calls where waiting is a real risk or a real breach, and they get worked first regardless of when they rang. Ask two questions when the call comes in: is anyone in the home elderly, very young, or in poor health, and are you on a plan with us. The answers set the tier.

Tier two, today if the trucks reach it. Everyone else with no cooling in a hot house, worked after tier one, batched by where they sit on the map. Most of your forty calls land here. Some of them are going to roll to tomorrow, and the sooner you tell them that the better it lands.

Tier three, schedule for tomorrow now. New construction, second-system-out homes where one system still cools, warranty items that are not emergencies, and anyone who says “no rush.” Do not leave these floating on the today list where they clog the sort. Book them a real slot tomorrow and take them off the board.

Sorting into those three buckets takes about thirty seconds a call, and it means at any hour you can look at the list and know exactly what has to move next. The pad cannot do that. The group text buries it.

Batch by map, not by clock

Once the tiers are set, the second lever is geography. Forty no-cools are not forty separate trips. They are four or five clusters, and a tech who works one cluster clean before crossing town runs twice the calls of a tech who chases the list in the order it rang.

So after tier one is spoken for, group tier two by area and hand each tech a side of the map, not a top-of-the-list call. The tech on the north side works north. When he clears it, he pulls the next north call, not the oldest. This is the single biggest difference between a good hot day and a bad one, and it is invisible on a legal pad because a pad has no map in it. A record showing each open call with its address in one place lets you see the clusters and split them without three phone calls.

If you have wrestled with running several trucks off scattered notes, the same fix that ends the one-man-band scramble as you grow to three techs is the one that holds a heat wave together: every call in its own place, visible to whoever picks it up.

The early callback

The hardest part of a heat wave is not the twenty you reach. It is the twenty you do not. And the shops that come out of a hot week with their reputation intact are the ones that told the truth early instead of letting people sit.

Here is the script. When a tier-two call is going to roll, someone calls them by early afternoon, not at 6pm: “We are slammed today with the heat and I want to be straight with you. We can get a truck to you tomorrow morning between eight and eleven. If anything opens up today I will call you, but I do not want to promise you a today I cannot deliver.” That call takes ninety seconds and it does two things. It keeps the customer from calling three competitors out of silence, and it stops the angry 6pm callback that eats your evening.

The reason this rarely happens on the bad day is simple: the person who should make the call is buried being the dispatch board. When the sorting and the sequencing run themselves, the office manager has the ten minutes it takes to make those calls, and every one is a customer kept instead of lost.

Do the plain math on it. If early callbacks save five accounts over a hot week that would otherwise have hired someone else, each worth a service call now plus a changeout down the road, you are protecting real money with a script and ninety seconds a call.

What holds it together

A heat wave does not break a shop because there are too many calls. It breaks a shop because forty calls collapse into one unreadable thread, and the sequencing falls to whoever is loudest instead of whoever waits worst.

The fix is that each call gets its own thread. The vulnerability answer and the maintenance-agreement flag ride at the top so the tier is obvious at a glance. The address sits where the tech pulling the call can see it and batch by map. The tech marks the call done when he leaves, so the board is current without a single “where are you now” text, the same way you would check a tech showed for a tune-up without calling him off a roof. And when a half-diagnosed call has to pass to the next truck, the handoff is reading the thread, not re-explaining it. The group text collapses forty jobs into one wall of panic and buries the account that waits worst under the caller who yelled loudest; a thread per call keeps them forty readable places, and leaves you the ten minutes to tell the waiting customers the truth. We are new, so put the next hot day on it and see whether the board still melts.