# AI Dispatcher for HVAC. You still apply | HVACSoftware.com

> The AI proposes who, when, and which job by skill, zone, and truck capacity. A person still applies the card. Same job as front office. Book a demo.

*Markdown mirror of https://hvacsoftware.com/ai-dispatcher/ — AI Dispatcher.*

**AI Dispatcher for HVAC. You still apply.**

Propose by skill, zone, and capacity — a person still applies the card so the truck runs the same job front office wrote.

AI Dispatcher is listed on Microsoft Marketplace.

## Skill, zone, and capacity — what the AI weighs.

Before a card moves, the engine scores the cert, the territory, and the remaining dollars and jobs on the truck together.

Buyers already expect dispatch software to match a tech by skill and service area, respect capacity, and keep a live board instead of a whiteboard. Drive time and a same-day no-cool sit in that same pass. An unqualified name is not proposed just because the pin is near. A truck that is already full does not get the next install.

## The AI proposes. A person still applies.

Suggestions land in a review queue. Apply or discard — nothing goes live until a person does.

That applied assignment is what back office and the truck run. Drag a card you disagree with and the board re-checks the day. The shop keeps the keys. Assist is the public path on this page; assign-on-create is a later shop setting, not how this page sells the dispatcher.

## The board shows who, when, and why.

Rows are trucks. Cards are jobs. Open a proposal and read the matched skill, the zone, and the capacity headroom.

Then drag and the board re-checks surrounding stops. The dispatcher is not a black box that drops a name and hides the work. Who, when, and which job stay readable on the card a person still applies.

## Slot a no-cool without wrecking the day.

An emergency still has to fit skill, zone, and the overtime cap. The AI proposes a resequence. A person applies it.

SLA windows stay on the card. Surrounding stops move only after the new proposal is checked. The day does not blow a shift-end rule because a pin looked close. Guardrails are data on the board, not a note in someone's head.

## Front office feeds the brain.

Unified inbox, voice agents, and zone booking write the same job the dispatcher proposes on.

That is the information gain against a dispatch overlay the office reconciles later. A lead in one tool and a visit in another is the failure mode. Intake writes the record a person still applies. Back office opens that assignment.

## Routes run after a person applies.

Routing sequences stops that already have a name. Dispatch decided who owns the day before the line was drawn.

Capacity, skill, and zone belong in that first decision. Once a person applies the board, route optimization orders the stops — it does not replace the proposal. Drive time was already weighed. The route respects the day that was applied.

The gain is one native job from inbox and booking onto the board — not a pin-to-pin router, not a whiteboard, not a ProBook-class overlay the office reconciles later.

### Apply or discard.

Every job lands as a proposal a dispatcher reviews, edits, applies, or discards. Assist is that queue. Some shops later turn on assign-on-create for boards they have stopped second-guessing. That setting is not how this page sells the dispatcher.

### Every proposal shows its reasoning.

Matched skill, zone, and capacity headroom sit on the card. Disagree, and the whole board re-checks.

- **Skills** — EPA 608, install, commercial refrigeration — tagged on the tech and required on the job.
- **Zones** — North, west, a radius, a polygon, or a zip list. The address already knows the territory.
- **Capacity** — Dollars and jobs per truck, and hours rather than pin count. A $2,100 install does not land on a full row.
- **Drive time** — Minutes between stops, weighed with the rest. Not a line drawn after the names are already inked.

- **Skill** — EPA 608 matches the furnace. An uncertified name is not proposed. (Match)
- **Zone** — North is his territory. The address tagged the job before the board opened. (Match)
- **Capacity** — Open after the 8a tune-up. The $ install stays on Diego. (Match)
- **Window** — 9:40–11:10 still hits the promise time. (Open)
- **Drive** — Sixteen minutes from the last stop. Not the closest pin if that pin is full. (16m)

### Inbox, voice, and booking write the same card.

Unified inbox, a voice turn, and a zone booking create one job. The AI dispatcher proposes who and when, and a person applies it. Back office and the truck run that assignment. The record never forks.

[Front office](https://hvacsoftware.com/front-office/)

- [Unified inbox](https://hvacsoftware.com/front-office/unified-inbox/)
- [Voice agents](https://hvacsoftware.com/front-office/voice-agents/)
- [Contact center](https://hvacsoftware.com/front-office/contact-center/)
- [Online booking](https://hvacsoftware.com/front-office/online-booking/)

### Emergencies, SLA, overtime, resequence.

The AI names a fit that does not blow the cap. A person still applies the change. The rest of the board re-checks.

| Guardrail | What the AI proposes | What a person applies |

| --- | --- | --- |

| No-cool / emergency | A slot that still fits skill and zone | The interrupt, after they check the afternoon |

| SLA window | A card that still hits the promise time | The window the shop will keep |

| Overtime cap | A resequence that stays inside the shift | The overtime exception, if any |

| Dynamic resequence | Surrounding stops reordered around the new card | The new day |

### Routing draws the line. Dispatch picks the name.

Once a person applies the board, route optimization sequences the stops. Capacity already decided who owns the day.

| Question | Generic routing | This dispatcher |

| --- | --- | --- |

| Who gets the job? | Assumes the names are already inked | Proposes the tech from skill, zone, and capacity |

| What is full? | A map of pins | Dollars and jobs on the row, before the next card |

| What about drive? | The line between stops | Weighed with the assignment, not after it |

| What ships to the truck? | A route | A proposal a person still applies |

- **8:00** — Tune-up — Applied
- **9:40** — No-cool — Applied
- **14:00** — Callback — Applied

The line is drawn after a person applies the names.

## Front office wrote it. Back office runs the assignment.

This page owns the board. Intake writes the job. The books run what a person applied.

- [Front office](https://hvacsoftware.com/front-office/)
- [Unified inbox](https://hvacsoftware.com/front-office/unified-inbox/)
- [Voice agents](https://hvacsoftware.com/front-office/voice-agents/)
- [Contact center](https://hvacsoftware.com/front-office/contact-center/)
- [Online booking](https://hvacsoftware.com/front-office/online-booking/)
- [Back office](https://hvacsoftware.com/back-office/)

## HVAC AI dispatcher, answered.

What it weighs, what a person still applies, and how front office reaches the board.

### What is an HVAC AI dispatcher?

An HVAC AI dispatcher proposes who takes which job and when by skill, zone, and truck capacity, then a person applies that card so the truck runs the same assignment the office booked. It keeps a live board instead of a whiteboard. Drive time and a same-day no-cool sit in the same pass. Nothing goes to the field until the shop says yes.

### Does it auto-assign jobs?

No. The AI proposes a technician and a window. A person still applies or discards the card before it reaches the truck. Assist is that review queue. Assign-on-create is a later shop setting, not how this page sells the dispatcher. The applied assignment is what back office and the truck run.

### How do skill, zone, and capacity work together?

They are one pass, not filters the office runs after a map is drawn. Skill and certification have to match the job. The address already knows the territory. Remaining capacity is dollars and jobs on the truck, not pin count. An unqualified or full row is not proposed just because it is closest.

### How does front office booking reach the dispatch board?

Unified inbox, voice agents, and zone booking write the same job object the dispatcher proposes on. A customer window is already a job, with the property and the zone attached. The AI names who and when on that record. A person applies it. Back office opens the assignment the truck will run.

### What's the difference between dispatching and routing?

Dispatching decides who should get the job. Routing sequences stops that already have a name. This dispatcher proposes from skill, zone, and capacity first. Once a person applies the board, route optimization orders the day. Drive time was already weighed. The route does not replace the proposal.

### Can it run on top of an existing FSM?

Yes. It can propose on jobs and technicians from the system you already run, or sit inside the same OS as front office and back office. Standalone or in-platform is a wiring choice. It is not a second job object. A person still applies the card either way.

## See the AI propose. Watch a person apply it.

A walkthrough of skill, zone, and capacity on the board, a proposal, the apply step, and the job front office already wrote. One conversation, not a self-serve signup.

### Who this is for

- **Residential** — Keep no-cools and tune-ups on one board a person still applies.
- **Commercial** — Match the visit to the tech who is cleared for that equipment, then apply it.
- **Enterprise** — Govern who / when / which job across branches on the same kind of proposal.

### What a demo covers

- **Skill · zone · capacity** — What the AI weighs before a card moves.
- **The gate** — A proposal in the queue. Apply or discard.
- **The board** — Who, when, and why, readable on the card.
- **SLA · resequence** — A no-cool that does not blow overtime.
- **The same job** — Inbox and booking wrote it. Back office runs it.

### What we ask in the first conversation

1. Who owns the board today — a dispatcher, a manager, or a whiteboard?
2. Do you match by closest pin, or by skill, zone, and capacity?
3. Does the job the office booked stay the job the truck opens?

[Book a demo](https://calendly.com/jeel-fieldcamp/30min?utm_source=hvacsoftware.com&utm_medium=markdown&utm_content=ai-dispatcher)

---

Also here: [Home](https://hvacsoftware.com/) · [Front office](https://hvacsoftware.com/front-office/) · [Back office](https://hvacsoftware.com/back-office/) · [llms.txt](https://hvacsoftware.com/llms.txt)