HVAC dispatch and scheduling automation for the days that never go to plan
A technician overruns, a part is missing or an emergency must be fitted in, and the dispatcher spends the next hour on the phone. We build a workflow on top of your field service software that spots the change, proposes a revised schedule matched to skills, licences and location for the dispatcher to approve, then tells every affected customer their new time and sends on-the-way texts with the technician's name. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why trades schedules break by mid-morning
Every HVAC, plumbing and electrical schedule breaks by mid-morning. Jobs overrun, customers cancel, parts are not on the van and emergencies arrive. The dispatcher re-plans in their head and then phones every customer who is now going to be late.
Customers are not upset by delays as much as by silence. A homeowner who took the day off and hears nothing by 3pm calls the office, then leaves a bad review. Matching jobs to the right technician also matters: gas, refrigerant and electrical work need the right qualifications.
What we build
What our HVAC dispatch and scheduling automation includes
Change detection
Overruns, cancellations, emergency jobs and missing parts picked up from job status in your field service software.
Revised schedule proposal
A suggested re-plan that respects skills, licences, location and promised windows, for the dispatcher to approve.
Qualification matching
Only technicians recorded with the right registration or certification offered for regulated work.
Customer updates
Approved texts with new arrival windows, and on-the-way messages with technician name and photo.
Vulnerable customer flags
Customers flagged as elderly, unwell or without heating or cooling routed to a person for a call.
Day-end summary
Jobs completed, moved and carried over, with reasons, for the owner.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Day changes
A job overruns, cancels or an emergency arrives in the field service software.
-
02
Automated
Re-plan proposed
A revised schedule is proposed using skills, licences, location and windows.
-
03
Office or dispatcher review
Dispatcher approves
The dispatcher accepts, edits or rejects the proposal.
-
04
Automated
Customers updated
Affected customers get new times and on-the-way texts automatically.
-
05
Technician or owner decides
Priority calls
Who goes first in an emergency, and calls to vulnerable customers, are decided by the dispatcher and owner.
How it behaves
How dispatch automation behaves
What the customer sees
- A text when their window changes
- An on-the-way message with the technician's name
- A call from the office if they are flagged as vulnerable
What the dispatcher sees
- Proposed re-plans to approve or edit
- Only qualified technicians suggested for regulated work
- A day-end summary of moves and carry-overs
What the automation does
- Detects schedule changes from job status
- Proposes re-plans with travel and skills
- Updates customers only after approval
Edge cases and fallbacks
- No qualified technician free
- The proposal says so and the dispatcher decides whether to move other work.
- Customer replies that the new time does not work
- The reply goes to the office to rebook.
- Technician's registration has expired in the records
- Excluded from regulated jobs and the owner is alerted.
- FSM API outage
- No automatic changes; the dispatcher works the board as usual and gets an alert.
Architecture
Dispatch changes and customer updates at a glance.
- Input
- Logic and services
- AI step
- People
- Output
- Data
How it flows
- 1 Job status changes in the field service software, such as overruns, cancellations or new emergencies, reach the workflow.
- 2 A revised schedule is proposed that respects skills, licences, travel and promised windows.
- 3 The dispatcher approves or edits the proposal; nothing changes without approval.
- 4 The schedule board updates and every affected customer gets a new time and on-the-way text.
Project planner
How the project runs, phase by phase.
Dispatch, scheduling & customer ETA updates project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Dispatch process, technician skills and registrations, windows promised and FSM data.
-
02
Design
2 to 3 days
Re-plan rules, approval screen, customer message wording and vulnerable customer rules.
-
03
Build
1 to 2 weeks
Change detection, proposal logic, approval flow, customer texts and summary.
-
04
Shadow run
About 1 week
Proposals shown to the dispatcher while customers are still called by hand.
-
05
Launch
1 to 2 days
Switch on customer texts and train dispatchers.
-
06
Support
Ongoing
Rule tuning, new technicians and monitoring.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Dispatch rules, skills data and message wording.
$200 – $400
-
Build
Change detection, proposals, approvals and texts.
$500 – $1,300
-
Integrations
Field service platform, maps and messaging.
$150 – $400
-
Testing and shadow run
QA and a shadow run with the dispatcher.
$100 – $250
-
Launch and training
Switch-on and dispatcher training.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Works with the dispatch board in your field service software; we do not replace it. Messaging and n8n are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
- Maps and AI usage: Google Maps Platform and model fees at each provider's published rates.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: refrigerant work needs Section 608 certification
Anyone servicing, installing or disposing of stationary refrigeration and AC appliances must be a Section 608 certified technician, so matching uses recorded certifications.
Source: www.epa.govUK: gas work by Gas Safe registered engineers
Only Gas Safe registered engineers qualified for the work may work on gas fittings in homes and workplaces, so gas jobs are offered only to them.
Source: www.hse.gov.ukUS: texts are service messages only
ETA and schedule texts stay informational; marketing texts need prior express written consent under the TCPA rules.
Source: www.law.cornell.eduFree tools
Try these first, free.
Guides to read first
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
HVAC dispatch and scheduling questions questions, answered.
It is an automation layer on top of the dispatch board in your field service software. It proposes changes and updates customers; the dispatcher still approves every move.
Yes. Small teams often benefit most, because the owner or one office person is dispatching between other jobs. Customer updates alone save many calls.
It proposes assignments using skills, registrations, location and windows. The dispatcher approves them, especially for emergencies and regulated work.
A text when their arrival window changes and an on-the-way message with the technician's name, and photo if you want. Wording is yours.
ServiceTitan, Housecall Pro, Jobber, ServiceM8 and simPRO through their APIs, subject to your plan's API access. We confirm before quoting.
Jobs moved per day, customers notified before their window, calls asking where the tech is and jobs carried over.
Free 20-minute call
Want this for your heating, plumbing & electrical?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for heating, plumbing & electrical
All servicesHVAC & plumbing CRM automation
Every call, web form, Google lead and repeat customer lands in your field service CRM as a job or lead, with fast replies, follow-ups and a weekly report on which sources bring paying work.
From $1,000 · About 4 weeks Details
Missed-call text-back for contractors
Text every missed caller back within seconds from your business number, collect the address and problem, put no-heat and leak calls at the top of the list and send danger straight to a person.
From $1,000 · About 3 to 4 weeks Details
AI receptionist & answering service
An AI receptionist that answers calls and chats out of hours or when lines are busy, books service requests from your rules and sends any danger or emergency straight to a person.
From $2,500 · About 5 to 8 weeks Details