HVAC dispatching in 2026 — what good dispatch actually looks like

Dispatch is the part of HVAC operations that's most often broken. It's also the most misunderstood.

Vendors sell "dispatch software" as if it's a product. It's really a set of features — some of which you need, some you don't. Here's what good dispatch actually looks like, what the features mean, and what separates adequate tools from great ones.

The dispatch problem, in plain English

You have 5 techs. You have 18 calls scheduled for the day. Two calls got emergency-bumped at 7am. Tech #3's truck won't start. Mrs. Henderson has a 2-hour arrival window and it's 1:45pm and Tech #2 is still on a capacitor change across town.

Your dispatcher (or you, if you're a smaller shop) has to:

See every tech's current job and ETA
Know each tech's skills (can #4 handle a commercial RTU?)
Know which calls are prepaid / membership / commercial / emergency
Minimize drive time
Notify customers when ETAs shift
Keep techs informed of changes

Good dispatch software does all of this in one interface. Bad software makes you juggle a whiteboard, a phone, and three browser tabs.

The five features that actually matter

1. A drag-and-drop scheduling board

You should be able to see every tech as a row (or column) and every hour as a column (or row). Unassigned calls stack on the side. Dragging a call onto a tech = assignment. This sounds basic; a surprising number of tools do it poorly.

What to test: drag a 2-hour call onto a tech's 10am–12pm slot. Does it show real time? Does it conflict-warn if the tech is already booked? Can you drag it to a different tech without a dialog?

2. A live map

On a good dispatch tool, the map shows:

Each tech's current location (via the mobile app GPS)
Each job as a pin
The planned route for the day

This matters most for route optimization — if tech #2 just finished a call 10 minutes from a new emergency, assign it to them, not #5 who's 45 minutes away.

Bad implementations: static maps that show addresses but not live positions. Or maps without route visualization. Functional, but not game-changing.

3. Skill- and tier-based routing

Not every tech handles every job. A 1-year apprentice shouldn't get a commercial chiller call. A senior tech shouldn't get routine filter changes.

Good tools let you tag techs with skills (residential install, commercial maintenance, heat pumps, etc.) and tag jobs with the same. The dispatch view filters accordingly. This prevents misroutes.

Enterprise tools (ServiceTitan, FieldEdge) handle this cleanly. SMB tools often don't; you handle it in your head.

4. Customer ETA communication

When a call is assigned or re-assigned, the customer should get an SMS. Something like: "Your HVAC tech, Mike, is on the way. ETA: 2:30–3:00pm. Reply STOP to opt out."

This one feature probably reduces "where's my tech?" calls by 80%. Almost every modern FSM tool has it. Check that it's enabled in the tier you're buying and that the SMS doesn't come from a weird 10-digit number (which gets ignored or flagged as spam).

5. Tech mobile app with real-time updates

When the dispatcher reassigns a job, the tech's phone should update. When the tech marks a call "en route" or "arrived," the dispatch board updates. This two-way sync is what separates modern FSM from email-based dispatch.

Test the mobile app during a trial with an actual tech's phone — not the iPad at a trade show demo.

What most tools get wrong

Dispatch that requires manual refresh. Browser-based dispatch boards that don't update in real time force your dispatcher to hit refresh every 2 minutes. That's time not spent dispatching.

SMS that goes through a random 10-digit number. Customers ignore these. Good tools use a branded short code or a consistent business number. Ask specifically.

Hidden call counts. You think you're paying for "unlimited two-way SMS" and then you discover there's a 5,000/mo cap that kicks in during busy season.

Per-tech pricing that kills growth. If you grow from 5 to 8 techs and your tool jumps $200/mo because you crossed a tier, factor that in.

The dispatch workflow, end-to-end

A good dispatch flow looks like this:

Customer calls or books online. Call is created in the FSM tool with contact, address, and scope.
Dispatcher (or auto-assign logic) picks a tech and a time slot. Customer gets confirmation text.
On the day-of, the tech opens their mobile app, sees the schedule, taps "en route" for the first call.
Customer gets an "on the way" SMS with ETA.
Tech arrives, works, invoices on-site.
Dispatcher sees the status change and can plan tech #2's next call around the real-time update.
End of day, dispatcher reviews: how did drive time stack? Where did we lose an hour? What changes for tomorrow?

Tools that support this full loop are "modern." Tools that require manual status updates from the office are stuck in 2012.

What to test in a trial

Create a sample day with 6 calls and 2 techs. Assign them. Drag one call to the other tech. Cancel one. How many clicks?
Use the mobile app to mark a call "en route" and "arrived." Does it reflect on the desktop dispatch board within 30 seconds?
Send a test customer SMS. Does it come from a recognizable number?
Import a real week of past calls (most tools allow CSV import). Does the drive time visualization look accurate?
Simulate a mid-day re-route. Cancel a call, add an emergency, reassign. Does the impacted tech's phone update in real time?

If any of these break or feel clunky, the tool's dispatch is not production-grade for your size.

The right tool per size

Team size	What you need	Tools that fit
1–3 techs	Scheduling + reminders. Real-time dispatch is overkill.	Jobber, Housecall Pro, Workiz Lite
4–10 techs	Real dispatch board with live map	Workiz Standard, Housecall Pro Essentials, JobNimbus
10–20 techs	Skill-based routing, advanced reporting	ServiceTitan, FieldEdge, Workiz Ultimate
20+	Multi-location dispatch, enterprise reporting	ServiceTitan, BuildOps

Dispatch is an operational function, not a product feature. Software makes it faster, but the underlying logic — which tech, what job, when — is yours. The best FSM tools amplify a good dispatcher. The wrong tool creates work where it saves you none.

Before you buy, test the dispatch flow end-to-end with a real tech. If the mobile experience is clunky or updates are slow, the sticker price doesn't matter.

Keep reading: HVAC software buyer's guide, commercial vs residential HVAC software.