HVAC Heat Wave Call Surge: Triage and Dispatch (2026)

TL;DR

A heat wave does not raise HVAC demand gradually. It triples the no-cool calls in a day, and every caller describes the same symptom with the same urgency. As of September 2026, the shops that come through those weeks well are not the ones with the most trucks. They are the ones that decided in advance who gets served first, held back capacity for the calls that truly cannot wait, told everyone else the truth about timing, and paused the work that could move.

This is the operating plan: the priority tiers and the intake questions that sort callers into them, how many slots to hold, what to do with maintenance visits, how to write honest ETAs, how to run the on-call rotation without burning out the team, and the review you run once the forecast breaks. For the broader software picture, our HVAC scheduling software guide covers the everyday setup this plan sits on top of.

Why first-come, first-served fails in a surge

On a normal Tuesday, booking calls in the order they arrive is fair and mostly harmless. In a heat wave it produces the worst possible outcome. The retiree whose only system died at 11 a.m. waits behind the family with a working upstairs unit who wanted the downstairs one looked at. The earliest callers are often the most organized customers, not the most at-risk ones.

A surge is a rationing problem. You have a fixed number of tech-hours per day and more demand than hours. When supply is fixed, the order in which you serve people is the whole decision, and it should be made on purpose, in writing, before the phones start.

The priority tiers

Keep it to four tiers. More than that and call-takers stop applying them consistently under pressure.

Tier 1: health risk, or no cooling at all. An elderly occupant, anyone with a medical condition affected by heat, an infant, or a home with zero working cooling during dangerous temperatures. These calls get the next available truck and a held slot if one exists. If you genuinely cannot reach them the same day, say so plainly and suggest they get to a cooler location, and log that you said it.

Tier 2: no cooling, no identified health risk. A system fully down in an occupied home. Same-day or next-morning target.

Tier 3: partial cooling. One zone out, a unit short-cycling, a system running but not keeping up. Uncomfortable, not dangerous. Next available standard slot.

Tier 4: routine and planned work. Tune-ups, quotes for replacements that are not urgent, filter changes, second-opinion estimates. These are the candidates to pause.

Tiers only work when the intake questions reveal them. Add three questions to every no-cool call during a surge: Is anyone in the home elderly, medically vulnerable, or very young? Is there any working cooling in the house right now? When did it stop working? Those three answers sort almost every call in under a minute, and they go straight into the job notes so the dispatcher sees them without calling back.

The tiering discipline is the same one we describe for any business in emergency versus scheduled jobs dispatch triage. A heat wave is that problem at three times the volume.

How the tiers translate into dispatch

The table is for your office, not your customers. Nobody on the phone should hear the words "tier 3." They should hear a date, a window, and a reason that makes sense.

Hold slots on purpose

The single most useful structural move in a surge is to leave capacity unbooked. It feels wrong when the phone is ringing and there is a customer on the line who wants that 1 p.m. But a fully booked board at 8 a.m. means that every Tier 1 call after 8 a.m. bumps someone who was already promised a time.

A worked example with stated assumptions: say you run six techs, and in a surge each can realistically complete five no-cool calls a day once drive time and diagnosis are counted. That is thirty calls. Holding one slot per tech keeps six calls open for the day. If Tier 1 calls claim four of them, you release the other two around early afternoon to the Tier 2 list, which is already waiting. You have not lost capacity. You have reserved it for the people who need it most, and turned it over when they did not appear.

Build the held slots as visible blocks on the calendar, labelled plainly, so nobody books over them without deciding to. Our post on seasonal demand scheduling covers how to plan these peaks before the season starts rather than during the first hot week.

Pause maintenance visits, but do it properly

Tune-ups and maintenance-plan visits are the obvious capacity reserve, and most shops should pause them for the length of a surge. The failure mode is pausing them silently. A maintenance customer who waits at home for a tech who was quietly reassigned becomes an angry customer in the middle of your busiest week.

Do it in three steps. First, contact every affected customer before their visit, not the morning of. A short text works: the heat wave has us prioritizing homes without cooling, your tune-up is moved to a specific date, reply if that does not work. Second, give a real new date, not "we'll be in touch." Third, put those visits back on the calendar the week the forecast breaks, because members who pay for a plan expect the plan to be honored. The mechanics of running those plans without letting them collide with peak season are in maintenance agreement and membership scheduling.

One exception worth making: if a maintenance customer is also a Tier 1 profile, an elderly occupant in an older system, a proactive check during the surge can prevent a far worse emergency call two days later.

Honest ETAs are a capacity tool

When you are overbooked, the temptation is to promise the customer a time that keeps them from calling a competitor. It backfires. A customer told "this afternoon" who is still waiting at 7 p.m. calls back, and every callback eats a call-taker's time during the hours you can least spare it. Many of them cancel and book the competitor anyway, after you already spent a slot planning around them.

The honest version is harder to say and cheaper to live with. "We are running about a day behind because of the heat. I can get you tomorrow between 10 and 2. If anything opens earlier today I will text you." That customer can plan: fans, a cool room, a night at a relative's. Some of them will book elsewhere, and that is fine, because you did not have the capacity to serve them today anyway.

Two mechanics make honest ETAs possible. The first is a real window, as covered in arrival time windows. The second is an en-route text built on where the truck actually is. Live GPS with traffic-based ETAs is on the Pro plan and up, and during a surge it is what stops the office guessing when a tech will actually arrive at the fourth call of the day.

The on-call rotation during a surge

Heat waves do not respect business hours. Systems fail at night, when the house has been cooking all day, and some of those are Tier 1. Your normal after-hours rotation was not designed for five nights in a row of heavy calls.

Adjust it in advance. Shorten on-call stints so no tech carries three consecutive surge nights. Decide which after-hours calls get a truck tonight (Tier 1 only, typically) and which get a firm first-thing-tomorrow slot. Give the on-call tech a written threshold so they are not deciding at 11 p.m. with a tired brain. The full rotation design is in after-hours on-call scheduling.

Phone coverage matters as much as truck coverage. A surge produces more calls than a small office can answer, and every missed call during a heat wave is a household with no cooling that dials the next number on the list. An AI receptionist that answers calls, collects the caller's details, and routes urgent ones to the on-call technician is one way to keep the intake questions asked when every line is busy. GetTimePad's KeyBot does that on the Pro and Agency plans.

Protect the technicians

The customers are hot. So are your techs, and they are working in attics and on rooftops. A surge plan that does not account for technician heat exposure is incomplete.

Put it in the schedule, not just in a safety memo. Push attic-heavy jobs toward morning where you can. Plan breaks between calls rather than hoping techs take them. Require a check-in when a tech goes into an attic alone. Keep water and cooling gear in every truck. OSHA publishes heat illness prevention guidance for employers, and the time to read it is before the first 100-degree day, not during it.

Overtime needs a ceiling too. Five fourteen-hour days produce mistakes, missed diagnostics, and a tech who quits in August. Your capacity is not unlimited just because the demand is.

Use the dispatch board, not the whiteboard

A surge moves too fast for a paper board and a group text. What the dispatcher needs is one view showing every tech's location, what they are on, which calls are waiting, and which are Tier 1. Dispatch software with a live technician map and drag-to-assign lets the dispatcher move the nearest free tech onto a new Tier 1 call in seconds instead of phoning around to find out who is closest.

Color-code by tier so the board tells the story at a glance. Flag urgent jobs with a priority marker. Keep the intake answers in the job notes so the tech walking into a Tier 1 home already knows there is an elderly occupant and can greet them accordingly.

Run a review after the surge

When the forecast breaks, the team will want to forget the week. Spend one hour on it first, because the next heat wave is coming and this one taught you things.

Review five questions. How many calls did we take, and how many did we serve same day by tier? How many held slots got used by Tier 1, and how many were released? How many callbacks did we get from customers asking where the tech was, which tells you whether the ETAs were honest? How many maintenance visits were paused, and have they all been rebooked? Did anyone on the team hit a safety or fatigue limit? Write the answers down and update the plan while it is fresh.

The goal is a better written plan next time: tighter intake questions, a more accurate held-slot count, a rotation that did not grind anyone down. For how the same setup runs the rest of the year, see the HVAC scheduling software page.

Frequently asked questions

How should an HVAC company prioritize calls during a heat wave?

Prioritize by risk to the person, not by who called first. Put elderly customers, medical conditions, infants, and homes with no working cooling at all at the top, then partial-cooling and comfort calls, then routine and maintenance work, and write the tiers down so every call-taker applies them the same way.

Should we pause maintenance visits during a heat wave?

Yes, for most shops the right move is to pause non-urgent tune-ups for the length of the surge and move those techs to no-cool calls. Contact every maintenance customer in advance, offer a firm new date, and put them back on the calendar as soon as the forecast breaks so the work is delayed rather than lost.

How much does GetTimePad cost?

GetTimePad is $79/mo Starter for one staff member, $199/mo Pro for up to five staff, and $499/mo Agency for unlimited staff. Scheduling, online booking, and automated reminders start at Starter, while live GPS with traffic-based ETAs and the dispatch tools most useful in a surge land at Pro. Annual billing gives you two months free. See /pricing.

What ETA should we give customers when we are overbooked?

Give the honest one, even when it is tomorrow afternoon. A realistic window the customer can plan around beats an optimistic promise you miss, because a missed promise generates a second angry call and often a cancelled job, while an honest wait lets the customer arrange fans, a cooler room, or a relative's house.

How do we keep technicians safe during a heat wave?

Build heat into the schedule itself: fewer attic jobs in the hottest hours, water and breaks planned between calls, and a check-in rule so nobody works alone in an attic without someone knowing. OSHA publishes heat illness prevention guidance for employers, and it belongs in your surge plan before the first hot day.

How many emergency slots should we hold open each day?

Hold a small number of unbooked slots per tech each day during a surge, typically one or two, and release them in the early afternoon if no top-tier call has claimed them. The held slot is what lets you say yes to an elderly customer with no cooling at noon without bumping someone you already promised.