An HVAC or plumbing schedule breaks in the same places every week. A no-cool call is booked as a tune-up. A leaking water heater is given the next open slot two towns away. A technician who only runs maintenance is sent to a drain that needs a camera. The board still looks full. The day is spent on windshield time, second trips, and arrival windows the office can no longer keep.
AI dispatch is useful when it makes that board easier to run. It should turn a messy call, text, or field note into a job record a dispatcher can assign. It should not move appointments on its own, invent an arrival time, or pick a technician the office has not approved.
This guide is the workflow, the tool categories that support it, and a 7-day setup a small HVAC or plumbing office can finish without replacing the scheduling system it already uses. If the office is still losing calls before they become jobs, start with AI missed call handling for HVAC and plumbing and an AI answering service. Dispatch only works on calls the office actually captured.
What the workflow has to change
Measure the workflow against three outcomes:
- Fewer jobs on the board with a missing address, a vague symptom, or a promise nobody wrote down
- Faster, explained moves when a job runs long, a part is missing, or an on-call leak comes in
- A handoff the CSR, dispatcher, and technician can read without replaying the call
If a tool does not improve one of those, it is another screen. Counting generated summaries is not a dispatch result. Jobs completed per technician, drive time, on-time arrivals, same-day reschedules, and second visits caused by a bad assignment are.
Build a dispatch-ready record before anyone touches the board
Most bad routes start at intake. "AC not working" is not a job. The dispatcher needs a record that separates what the caller said from what nobody has confirmed.
For HVAC and plumbing, the minimum record is:
- Customer name, service address, and a callback number that works
- Trade: heating, cooling, plumbing, drain, water heater, or a replacement lead
- The symptom in the caller's words, and when it started
- Safety or damage signals: gas smell, electrical smell, active water, no heat with a vulnerable occupant, sewage backup
- Membership, warranty, or recent visit when the office already knows it
- Access notes, pets, gate codes, and any arrival window already promised
- Skill, tool, or part the job may need, marked as a guess until a person confirms it
- The fields that are still blank
Keep facts and guesses apart. "Customer reports water on the floor by the water heater" is a fact. "Tank failed" is a diagnosis. The second line does not belong on the record until someone qualified says so. The same rule applies to "needs a new system" on a no-cool call.
A call booking script should collect these fields in the conversation. AI can then turn the transcript or the CSR's notes into the same record shape every time. The person booking the call still owns the promise.
Separate HVAC and plumbing work the board keeps mixing together
A single "service" column hides the jobs that wreck a route. Split them before you optimize drive time.
HVAC calls that need different people and different time:
- No cooling or no heat with a safety or vulnerability flag
- System running but not keeping up, which is often a diagnostic, not a part swap
- Maintenance or membership visit with a known checklist
- Replacement or second-opinion lead that should go to a comfort advisor, not the nearest maintenance tech
- Callback on equipment the company installed or repaired recently. See callback analysis before you send a different technician to guess at the last visit
Plumbing calls that need the same split:
- Active leak, sewage backup, or no water
- Water heater that is leaking, sparking, or producing no hot water
- Slow drain or a camera inspection, which needs the right machine
- Fixture repair that a plumber can finish from the truck
- Repipe, sewer line, or remodel lead that is a sales visit, not a one-hour service call
Write one next action for each type: on-call page, same-day slot, next maintenance window, advisor callback, or a polite out-of-area reply. The dispatcher confirms the category. The model only recommends it, and it should show the reason in plain language: "active water at the water heater," not a red badge with no sentence under it.
Match the skill, then the drive
The nearest truck is the wrong truck when it cannot finish the job. Skill and equipment come before miles.
Keep a short matrix the office actually updates: who runs maintenance, who diagnoses no-cool and no-heat, who sells replacements, who clears drains, who does water heaters, who has the camera, and who is on call. A practical assistant can compare the job record with that matrix, the technician's area, shift end, and open capacity, then show two or three options.
One option may be the short drive. One may keep the original technician on a callback. One may hold a maintenance tech for membership visits and send a diagnostic tech to the no-cool. The dispatcher picks. The software does not drag the card.
Treat schedule changes as a written event
The board falls apart when a job runs long, a part is not on the truck, or an emergency jumps the queue and nobody records which windows were already promised.
A controlled change has five steps:
1. State what changed and which jobs move. 2. Mark appointments with a prior reschedule, a hard window, or a vulnerable occupant. 3. Suggest the smallest move that still matches skill and area. 4. Draft the customer message from the time the dispatcher confirmed, not from a guessed ETA. 5. Save who approved the move and what the customer was told.
Field updates should use a short code the technician will actually send: diagnosis done, approval needed, running long, part required, customer not home, return visit needed. Interrupt the dispatcher only when the update changes today. Everything else waits for the end-of-day list.
Customer texts come last. Do not let a draft invent an arrival time, name a technician who is not assigned, or explain an internal delay the customer does not need. If the window is not confirmed, the message says when the office will call back. Appointment reminders should use that same confirmed window so the reminder and the dispatch board do not disagree.
Tool categories, not a vendor ranking
A small office does not need a new system of record to try this. It needs four jobs filled, in this order. Pick tools you already pay for when they can do the job. Do not add a subscription because a demo reordered a sample board.
The board you already trust
Service software, a shared calendar, or a disciplined spreadsheet remains the place appointments live. AI may suggest a move. A person makes it on this board.
Intake capture
A call transcript, web form, or text thread that fills the dispatch-ready record. This is the first thing worth turning on. An answering tool belongs here only after the office has defined what it may promise. Pair it with the missed-call and answering guides above.
A skills and equipment list the office maintains
A page in the shop book is enough. If the list is wrong, every recommendation is wrong. No routing product fixes a matrix nobody updates.
Approved message drafts
On-the-way, delay, and reschedule texts that pull only confirmed fields. A person sends them until the office has reviewed a week of drafts without a bad promise.
Skip automatic assignment until those four are boringly reliable. A 30-day version of the same rule, for any first workflow, is in the 30-day AI rollout plan.
A 7-day setup for one office
Run this on one trade first. HVAC maintenance and no-cool, or plumbing leaks and water heaters. Do not turn on both trades and automatic routing in the same week.
Day 1. Name the record
Write the field list above on one page. Pull ten jobs from the last two weeks and mark every blank that made the dispatcher call the customer back. That list is the template. Assign one owner, usually the dispatcher or service manager.
Day 2. Write the urgency rules
Four categories are enough: emergency review, same-day priority, routine service, not a service job. Put one real HVAC or plumbing example under each. "No heat, elderly occupant" is a rule. "The customer sounded upset" is not.
Day 3. Write the skills matrix
One row per technician. Columns for the work you actually sell. Note shift end and the truck's notable tools, including the camera and the water-heater kit. Leave sales leads in their own column so they are not treated as one-hour repairs.
Day 4. Rebuild yesterday
Take the previous day's calls and fill the new record by hand, using AI only to draft the summary from notes the office already has. The dispatcher marks every wrong assumption. Fix the template, not the model, when the same field is missing twice.
Day 5. Add the field shorthand
Agree on the six status phrases and where they land in the job. Technicians use them on the next day's calls. The dispatcher flags which ones should have interrupted the board and which ones were noise.
Day 6. Draft messages, do not auto-send
Write on-the-way, running-late, and reschedule texts that refuse to include a time unless that time is already on the board. Review every draft against what was actually promised.
Day 7. Read the overrides
Count how often the dispatcher changed the category, the assignee, or the wording. A repeated override is a missing skill, a bad urgency rule, or history the record never received. Keep the template. Leave automatic assignment off. Expand to the second trade only after a normal week produces records the office does not have to rewrite.
What "done" looks like
The office can point to a job and say what the caller reported, what is still unknown, who could run it, and what the customer was told. Recommendations that the dispatcher rejects are written down. Customer messages match the board.
That is the standard. Fewer incomplete jobs, fewer miles to the wrong skill, and fewer arrival windows the company has to take back. The schedule stays a decision the office can explain.
Related field guides
- AI missed call handling for HVAC and plumbing
- AI answering service for contractors
- AI call booking scripts for contractors
- 30-day AI rollout plan for contractors
- Callback note minimum fields before AI dispatch
Questions from search
How do HVAC and plumbing offices use AI for dispatch?
Use it to turn calls and field notes into a complete job record, suggest an urgency category with a reason, and offer two or three technician options. A dispatcher still assigns the job and approves any customer promise.
What should an AI dispatch setup include in the first week?
A required job-record template, four urgency rules with real examples, a technician skills matrix, one day of rebuilt calls, a short field-update code, and message drafts that are reviewed before anyone sends them. Leave automatic assignment off.
Does AI dispatch replace the scheduling software?
No. The board the office already trusts stays the system of record. AI fills records, recommends a category, and drafts messages. A person moves the appointment.