HVAC dispatch software: what a 14-call Tuesday actually looks like.

Most HVAC dispatch software was built to bill, not to plan. It runs the office. It does not run the day. The dispatcher does that, and the gap between what the software can do and what the day actually demands is where service margins quietly bleed. This is a look at a regular Tuesday inside an HVAC service operation — how the day gets built, where it breaks, and what dispatch software would need to do differently to actually keep up.

The math of a 14-call Tuesday

Three trucks. A 9-hour billable window per truck. Maintenance visits run 45 to 60 minutes. Service calls run 60 to 120. Estimate ride-alongs are 30 plus travel. Drive time between residential calls in a typical suburban service area runs 15 to 25 minutes — sometimes more in a sprawl like Charlotte, Houston, or anywhere with a thirty-mile-wide service radius.

If you sit down with paper and a calculator, a "perfect" 14-call day pencils out to about 28 hours of fieldwork across the three trucks. That's only an hour over capacity. The problem is that those numbers describe a fantasy day with no emergencies, no parts delays, no comp time, and no comfort consult that runs 45 minutes long because the homeowner has three quotes and wants to talk through every one of them.

Real days don't pencil out. Most HVAC service companies leak somewhere between 15% and 30% of their planned billable hours to schedule churn — calls reshuffled, techs sent back across town, parts trucks running late, install crews held up. The dispatcher's job is to minimize that leak. Good dispatch software gives her tools. Bad dispatch software becomes a tool, in the wrong sense.

Where the schedule breaks

Five things, in roughly the order they break a typical HVAC service day:

The 8:12 AM emergency

Residential HVAC emergencies cluster around the first heat wave and the first cold snap. They are unpredictable inside the day but extremely predictable across the season. The third-floor walkup at 8:12 is not a surprise; it just has a name and an address attached now. The dispatcher's question is: which truck pushes which job to take this one, and what does that do to the rest of the team's day?

Most dispatch software answers "drag the call onto the truck you want." That's not an answer. That's a UI. What the dispatcher actually needs is: what gets displaced if I put this on Tom's truck, what's the new ETA for the displaced job, and is the customer at that job the kind of customer who tolerates a same-day reschedule? The software almost never knows the third part.

Parts that didn't ship Monday

The Carrier check-back this morning is the third visit on a furnace that needs a board replaced under warranty. The replacement board was supposed to ship overnight from Atlanta. It did not. The dispatcher learns this at 7:55 AM when the tech texts to ask whether to bring the loaner or go without. There's a parts truck running between the supply house and the field, but the loaner is on a different truck, in a different zip, with a different tech. Now the morning has a parts shuffle that nobody planned.

This is not a software failure. Parts logistics live in a different system from dispatch in almost every HVAC shop. But it becomes a software failure when the dispatcher has to manually retype the new plan into three places: the service ticket, the tech's mobile app, and the customer-facing reminder email.

Multi-day installs blocking same-day responsiveness

The install crew is tied up. The crew lead's phone is on silent. They are not coming off the heat-pump retrofit to take a service call. Good dispatch software treats multi-day installs as protected windows, not soft suggestions. Many older systems treat them as "scheduled blocks" the dispatcher can override — which is technically correct and practically catastrophic, because at 4 PM the install crew is going to get pulled to a service call by someone who didn't know better, and the homeowner whose retrofit is now half-finished is going to leave a one-star review.

Comp time, skill, and the wrong tech for the call

Tom is good at diagnostic service. Marisol is better at comfort consults — she's an actual comfort advisor with the IAQ certs, and homeowners trust her on humidifier and ductless conversations. A dispatch system that routes purely on drive time will put Tom on the comfort consult because his truck is two miles closer. That's a 12-minute drive saved and probably a $4,000 contract lost. Skill-tagging, customer-rep history, and rep preferences are not flashy features. They are the difference between a dispatched call and a closed sale.

Manufacturer call-backs

The Carrier furnace is the third call-back on that install. Every shop has a handful of accounts that drift into "this is the fifth time we've been out for this" territory. The dispatcher knows it. The owner knows it. The CRM has the data buried somewhere. But the dispatch software almost never surfaces it as a flag — the kind of flag that would let a service manager say "stop dispatching to this address; route it through the install supervisor first." Most systems just keep booking the truck.

What dispatchers do when the software isn't enough

Watch a working HVAC dispatcher for a morning and you'll see three open tabs that aren't part of the official stack: a side spreadsheet with the day's calls in a custom order, Google Maps in another window for honest drive estimates, and a weather radar for the afternoon. There will be sticky notes on the monitor for the customers who require the special treatment that doesn't fit in the CRM's notes field. There will be a phone, and the phone will get used a lot.

None of this is a failure of the dispatcher. It is a sign that the software bought to coordinate the day cannot, in fact, coordinate the day. The dispatcher's workarounds are the operational truth. If you're an HVAC service owner and you've never asked your dispatcher what their workaround stack looks like, do that this week. You will learn more about your operation in 20 minutes than any KPI dashboard will tell you in a quarter.

If your dispatcher is running a side spreadsheet, your dispatch software is a CRM with a calendar bolted on.

What most HVAC dispatch software gets wrong

The honest read on the major players:

ServiceTitan is the dominant choice for mid- to large HVAC shops, and it earns the spot. It is a serious CRM with serious billing, serious reporting, and a serious enterprise sales motion. The routing engine is not its strength. It will build a sequence; it will not rebuild the day at 8:12 AM when an emergency lands. Most ServiceTitan shops use it for the front office and accept that the dispatch board is a manual board.

Housecall Pro is built for solo techs and small shops. Up to three or four trucks it's fine. Past that, the routing UI starts to creak — emergency insertion, multi-tech coordination, and parts handoffs are not things it was designed around. Many growing shops outgrow Housecall Pro between truck five and truck eight without realizing the dispatch chaos is software-induced.

FieldEdge is dispatch-first, which gives it a structural advantage on routing. It is also rigid. Adding a custom workflow (a parts-truck handoff, a multi-stop install, a comp-time rule) usually requires either a workaround or a configuration call. The user base loves it; the implementation curve is real.

Jobber, Workiz, and ServiceTrade each have specific strengths and the same general pattern: built around the work order, not around the day. The route exists as a representation of "what work is assigned." It does not exist as a live plan that knows what to do when reality lands.

This is not a hit piece. These are serious products and they each serve real customers well. The point is that "HVAC dispatch software" describes a category that is mostly CRMs with a map view bolted on. The actual dispatch — the live, reality-responsive rebuild of the day — is not what most of them are doing.

What "good" looks like in 2026

The bar moved. A dispatch system in 2026 that doesn't do these three things isn't really dispatch software, it's a scheduler:

Live rebuild on every event. An emergency call lands. The system computes the impact in seconds — which truck takes it, what gets displaced, what the new ETA is, what the downstream domino looks like. The dispatcher sees the consequence before she commits. Not after.

Voice-to-record capture. The tech finishes a service call, holds the phone, talks for 30 seconds: what was the fault, what got replaced, what to recommend next, when to follow up. The system produces the structured service record, the customer-facing summary, the parts-order signal, and the next-visit flag. The tech writes nothing. The dispatcher chases nothing. The CRM is honest by the end of the day because nobody had to choose between billable hours and data entry.

An assistant that knows the operation. A natural-language question — "Who has capacity tomorrow afternoon in the north zone?" or "Which maintenance accounts haven't been touched in 90 days?" — gets a useful answer in plain English, with the route to act on it. Not a dashboard. Not a report. An answer.

None of these are exotic. The pieces exist. The integration of them, on top of the dispatcher's existing CRM, is the work.

A 14-call Tuesday, replayed

Here is what the same Tuesday looks like with a live-rebuild dispatch layer sitting on top of the shop's existing field-service software.

Same dispatcher, same techs, same trucks. The day finishes at 5 PM instead of 6:30. The CRM is up to date because the techs didn't have to type, and the dispatcher didn't have to chase.

This is what we built Lead Mapper for HVAC to do — a routing-and-capture layer that sits on top of ServiceTitan, Housecall Pro, FieldEdge, or your CRM of choice. We don't replace your existing stack. We pick up where the dispatch features stop and the day actually starts.

What to look for if you're shopping

HVAC dispatch FAQ