HVAC dispatch software earns its keep on the hottest day of the year, when every no-cool call feels urgent and the board fills faster than anyone can sort it. The right system sorts calls by rules you wrote, matches each one to a tech with the right skills and parts, keeps customers posted, and lets your dispatcher make the final call. On a mild spring day almost any calendar works. On a heat-wave Tuesday, the gaps show.
This post is for HVAC owners and dispatchers who have lived through a peak week with a whiteboard, a phone and a headache. It walks through how a heat-wave board should be sorted, what the customer should hear, and when a custom build makes more sense than another subscription. For the broader view of job software, see our guide to field service management software.
What changes for HVAC dispatch on a heat-wave day?
On a heat-wave day, every call sounds urgent and the board fills faster than anyone can sort it. Priority drifts to whoever called loudest, the wrong tech or truck goes out, and customers call back asking for ETAs. Planned tune-ups clog the board next to no-cool calls.
A normal week has some breathing room. A heat wave does not. Here is what usually breaks:
- Priority gets set by whoever called loudest. Not by who is most at risk.
- The wrong tech goes out. An installer lands on a tricky service call, or a residential tech gets sent to a commercial rooftop unit.
- Trucks lack the part. A capacitor or a contactor that could have fixed it on the first trip is back at the shop.
- Customers call back to ask where the tech is. Each callback ties up the phone you need for new calls.
- Planned maintenance visits clog the board. Tune-ups booked weeks ago sit next to no-cool calls.
None of this means your dispatcher is slow. It means the tools were built for an average day.
How should an HVAC dispatcher sort a heat-wave board?
Sort by risk first, then by skill and parts, then by distance. The rules for each step should come from the owner and be written down before summer, so the software can apply them the same way every time. The software proposes the order, and the dispatcher reads it, moves what needs moving and sends it.
A simple order many owners like:
- Anyone at risk from the heat. Your intake asks, "Is anyone at risk from the heat?" Any caller who mentions a health risk goes to the on-call tech, never to a later slot. If anyone may be hurt or in danger, the only instruction given is to call 911, and your on-call person is alerted at once.
- No cooling at all, versus weak cooling. A dead system outranks a system that is running but struggling.
- Commercial accounts with service agreements. If your contracts promise a response window, those calls rise on the board.
- Maintenance plan customers. Many owners give plan holders a place near the front of the line.
- Everything else, grouped by area. So a tech can clear three calls in one neighborhood.
The software proposes an order. The dispatcher reads it, moves what needs moving, and sends it. Our post on HVAC after-hours calls covers how the night side feeds this board.
Matching the tech, the truck and the unit
A good board knows more than who is free. It knows who can do the job and what is on their truck. Tag each tech by skill, keep a parts list per truck, write your rule on pulling installers, and let distance break the ties.
Skills. Tag each tech: residential service, commercial rooftop units, installs, heat pumps, refrigerant work. The EPA's Section 608 rules (opens in a new tab) require technicians who service or dispose of equipment that could release refrigerant to hold Section 608 certification. A call tagged "commercial rooftop" only shows techs who do that work.
Parts. Keep a simple list of common parts on each truck. When a call mentions "outdoor fan not spinning," the board can favor the tech who carries the likely part.
Installers versus service techs. On a heat wave, some owners pull installers onto service calls. Others keep installs going. That is a business decision, and it belongs in your rules, not the software's guess.
Route. After risk and skill, distance matters. Our guide to route optimization software for service companies goes deeper on re-planning when a job runs long.
What should HVAC dispatch software send the customer?
It should send clear, honest updates so customers do not need to call. Dispatch software for small HVAC companies does not need to be fancy here; it needs to be on time. A booking note, ETA texts, delay notes and a polite reschedule offer for maintenance visits cover most of a peak day.
Useful messages on a peak day:
- A booking note. "We have your call. Your tech will be assigned shortly."
- An ETA text. Sent when the tech is assigned, and again when they are on the way.
- A delay note. If a job runs long, the next customer hears about it before they wonder.
- A polite reschedule for maintenance visits. Tune-ups booked for the hottest days can be offered a cooler day next week, with a one-tap way to accept or keep the slot.
Only text people who contacted you or gave you permission, and make opting out easy. FCC rules on automated texts (opens in a new tab) let people opt out at any time and in any reasonable way, even after they agreed.
Why does an off-the-shelf HVAC dispatching system fight you in July?
Because it was built for the average shop, not yours. A packaged HVAC dispatching system decides how priority works, which fields a tech fills out, and what the board looks like. You bend your process to fit it. A custom build works the other way, shaped around how you sort calls, tag techs and track truck stock.
We build dispatch software for HVAC companies shaped around how you sort calls, tag techs, track truck stock and send ETA texts, tied into the phone system, calendar and accounting software you already use. AI does the repeat work: proposing the board order, drafting customer texts, reading tech notes and photos back into the job, and starting warranty paperwork from the ticket. Your dispatcher decides. The SBA's guidance on AI (opens in a new tab) notes that AI can take on repeat tasks such as calendar reminders and sorting email.
For many shops, that starts as a scheduling and dispatch board with on-the-way texts, the kind of tool we describe at Tier 3 on our Solutions page. Larger shops often go further, to a full field service app with a tech phone view, photos, signatures and invoicing. Your data and logins stay yours either way.
What stays with the dispatcher?
The dispatcher keeps the final say on the board. A person approves every assignment, the dispatcher and owner judge who counts as at risk, and the tech on site makes diagnosis and repair choices. Prices, promises and warranty answers go to the office, and upset customers get a person.
- The final board. Every assignment is approved by a person.
- Who counts as at risk. The software flags; the dispatcher and owner judge.
- Diagnosis and repair choices. Those belong to the tech on site.
- Prices, promises and warranty answers. Those go to the office.
- Upset customers. A frustrated caller gets a person, with the job history in front of them.
Same team. Same jobs. More capacity. The dispatcher spends the day deciding, not copying addresses.
A heat-wave Tuesday
This is an illustration, not a customer story.
A mid-size HVAC shop opens on the third day of a heat wave. By early morning the board has a long list of calls.
The system has already sorted them. At the top: an older couple with no cooling. Next: a restaurant whose rooftop unit is down, under a service agreement. Then a run of no-cool homes on the east side, grouped together.
The dispatcher reads the list. She moves one call up because the customer mentioned a newborn. She swaps two techs because one has the condenser fan motor on his truck. She approves the board.
Customers get ETA texts. Three maintenance customers booked for that afternoon get a kind note offering a cooler day next week; two accept. That frees a tech for service calls.
At day's end, tech notes and photos are already on each job. A failed compressor under warranty has its paperwork started, waiting for the office to review.
Frequently asked questions
Can the software decide which call is an emergency?
It can flag calls based on your rules, like no cooling and someone at risk. It does not judge safety on its own. If anyone may be hurt or in danger, the only instruction it gives is to call 911, and it alerts your on-call person at once.
Will our techs need to learn a whole new app?
Not if the build fits how they already work. Many techs only need a simple phone view with the job, the address, notes and a place for photos.
What happens to maintenance visits during a heat wave?
Your rules decide. Many owners offer to move tune-ups to a cooler day and let the customer choose. Nobody is moved without being told. Customers who keep their slot stay on the board, and the dispatcher sees who moved and who stayed.
Is a custom build only for big HVAC companies?
No. A small shop with a few trucks feels a heat wave just as hard. The build starts small, often with just the board and the texts, and grows if it earns it.
Next step
If last summer's peak week still gives you a headache, book a free workflow consult. We are based in the Kansas City metro and meet owners in person or by video. We will look at how calls reach your board today, how you set priority, which techs and trucks handle what, and what a build shaped around your shop could look like. You can see the range of systems we build on our Solutions page.
About the ScaleAlphaAi team
We are a Kansas City company that designs and builds AI agents and custom software for small businesses, trades and growing firms. We write these guides from our work with owners and office teams: what AI handles well, what stays with your people, and how to start with one workflow.
Meet the team
