Dispatch Confirmation, Arrival Protection & Technician Brief
From the moment a call is booked to the moment the technician knocks, the customer knows what is happening, and the technician arrives already knowing the equipment, the history, and whether this customer is a member.
- Tier
- Foundational
- Build order
- 2nd of 7 for HVAC
- Shape of it
- 8 steps, 1 decision point
- At launch
- Runs supervised, with you approving what goes out
The problem this solves
Two failures, one on each side of the same appointment.
The customer side: an arrival window is given, the route runs late because the second call of the day turned into a two-hour job, and the customer calls the office to ask. On a peak day those calls consume the CSR capacity that would otherwise be booking new work, so a delay in the field turns into lost bookings at the desk.
The technician side: the truck arrives without the equipment age, the model and serial, the warranty status, the membership status, or a note that the last two visits were for the same fault. So the diagnosis starts from zero, the common part is not on the van, and the job becomes a return visit that nobody can invoice.
How it works, step by step
Every wait, threshold and branch below is a value we set with you during the build, against your stages and your language. None of it is a default we impose.
- What starts it
- It decides something
Step 1Trigger
A job is booked. The customer immediately receives a confirmation naming the date, the arrival window, the diagnostic fee, and how to reschedule.
Step 2
The evening before, a reminder goes out with the same details and a single question that changes the job: has anything changed, and is the system running at all right now?
Step 3
Any answer indicating a change gets routed to dispatch rather than filed. A system that has stopped completely overnight moves up the triage ladder.
Step 4Branch
When the technician is dispatched, the customer receives the technician's name and a live arrival estimate. If the route slips past the window, the customer is told before they have to ask.
Step 5
In parallel, the technician receives the brief: equipment make, model, serial and age, install date if known, warranty and membership status, the last three visits on that system, the reported symptom in the customer's own words, and any open estimate.
Step 6
The brief flags likely parts based on the reported symptom and the equipment, so the van is loaded before the truck leaves rather than after the diagnosis.
Step 7
On completion, the job cannot close without the model and serial, a photo, the diagnosis, and an explicit customer decision recorded as approved, declined, or deferred with a date.
Step 8
Anything left open becomes a task with an owner and a date, not a note.
How it gets built
Built inside what you already run
- ServiceTitan
- Housecall Pro
- Jobber
- FieldEdge
- or whatever your office already runs on
Nothing to log into and nothing to license. If a system needs a record your platform does not hold, we add the field to your platform rather than starting a second one beside it.
This is the actual build order, in the phases its own steps fall into. It runs in supervised mode first, with you approving what goes out, until you are happy with the tone.
- 1
Agree
Agree the confirmation and reminder content with the owner, including exactly how the diagnostic fee is described. Get that line signed off; it is the one customers argue about.
The thresholds, the wording and the names are yours. We write them down with you and get the consequential ones signed off.
- 2
Build
Wire booking events out of the field service platform, and confirm that a test booking produces exactly one confirmation.
Built inside the software you already run, against your stages and your language.
- 3
Build
Build the reply handling so a customer response reaches dispatch as a task, not an unread message in a shared inbox.
- 4
Build
Connect arrival status to whatever the platform already exposes. If it exposes nothing usable, the dispatcher marks en route and the automation carries it, which is a smaller ask than it sounds.
- 5
Build
Assemble the technician brief from the customer record and push it to whatever the field already opens. Do not build a second app for them to check.
- 6
Build
Add the required completion fields and, critically, agree with the service manager what happens when a technician cannot fill one.
- 7
Prove
Run for two weeks with the dispatcher watching every message before it sends.
It runs with a person approving what goes out until you are happy with the tone. Nothing sends unreviewed on day one.
What changes after it goes live
How it runs today
Two failures, one on each side of the same appointment.
After this one is live
The "where is my tech" calls stop being the fourth most common reason the phone rings. The CSR gets that capacity back on the day it is worth the most. The technician stops diagnosing blind, so the second truck roll for a part that could have been on the van becomes the exception rather than a normal cost of doing business. And every job closes with the equipment data on it, which is what makes System 6 possible at all.
How to measure whether it worked
Your arithmeticRun with your numbers, not ours
Take the number of return visits last season that existed only because the part was not on the truck, and multiply by the loaded cost of a truck roll. Add the CSR hours spent on status calls during peak weeks. Both numbers are already in the business; neither usually appears on a report.
We agree the baseline before anything is built, and we do not take credit for things that were going to happen anyway. There is no figure on this page claiming what we have produced for somebody else, because there is no verified figure to publish.
What we will not do
This is from the same delivery document as everything above it. It is on the page because a supplier who has not thought about it will not tell you, and you would find out later.
Every system here sends automated messages to consumers in the United States, which puts all of them inside the TCPA and inside carrier A2P 10DLC registration. These are two different things and both apply. Registration is a carrier trust requirement; it does not create consent and does not make an unlawful message lawful. Unregistered application traffic gets filtered or blocked.
Classify every system before it sends. A service message is narrowly connected to an existing job: appointment confirmation, technician on the way, part arrived, invoice. A marketing message promotes something: a tune-up offer, a replacement promotion, a membership push, an estimate reactivation sequence. The standards of consent are different, and a promotional line inside a service template converts the whole message into marketing.
The minimum a compliant build has to do:
- Consent recorded per number with the date, the source, the exact wording shown, the sending brand, and whether it covers service, marketing, or both. Marketing needs prior express written consent with an unchecked opt-in, and consent cannot be a condition of purchase.
- A2P 10DLC registration of the brand, the numbers, and a campaign use case that matches the traffic actually sent. An appointment-reminder campaign does not quietly become a seasonal promotion campaign.
- Quiet hours of 8am to 9pm in the recipient's local time, not the office's, with queued sends held until the window opens. Apply the same gate to service messages by default and handle genuine emergencies as a named exception.
- Opt-out handling for STOP, UNSUBSCRIBE, CANCEL, END, QUIT, REVOKE and OPT OUT, and for free text like "stop texting me". Suppress immediately in practice rather than to the outer limit of the rule, cancel messages already queued rather than only future ones, and propagate the suppression to every sending number, system and platform the contractor controls.
- Replies routed to a monitored human queue, always. A reply that says the heat is off is not a marketing response.
- Human review before any sequence that would materially pressure a prospect, which in this playbook means System 4.
- Suppression reconciled across systems, so a customer cannot opt out in the field service platform and keep receiving messages from the marketing tool.
- Purchased or scraped lists are not messaged. Consent has to name the actual sender.
Nothing in this document is legal advice. State mini-TCPA statutes, carrier policy, and the exact dialling or sending technology can each add requirements, and the rules in this area have moved more than once recently. Every template that states a commercial term, a price, or a guarantee requires review by the contractor's own counsel before it goes live.
Nothing here is legal advice. Rules in this area have moved more than once recently, and every template that states a commercial term or a guarantee goes to your own counsel before it goes live.
Seven systems forHVAC.
We build one at a time and prove it moved before starting the next. The tiers are the dependency order, not a price list.
Tier 1Foundational
Nothing arrives late or unowned. These come first because everything above them assumes they are true.
- 1Multi-Channel Capture, Triage & Instant ResponseFastest visible result, and it is the one that survives the first heat wave, which is when the owner decides whether any of this was real.
- 2Dispatch Confirmation, Arrival Protection & Technician Briefyou are hereProtects the capacity and the truck rolls already paid for.
Tier 2Growth
The recoverable money. These work the pools the foundational systems have made visible for the first time.
Tier 3Flagship
One connected system end to end, plus what the owner reads on a Monday. Only once the pieces are proven individually.
- 5The Complete Service-to-Install SystemThe flagship, once the pieces are proven individually.
- 6Service Agreement Renewal, Fulfilment & ReactivationCompounds everything above, and depends on the equipment data System 2 started collecting.
- 7The Owner's Morning BriefOnly meaningful once there are systems to report on.
The tiers are the dependency order for HVAC, not a price list. Most firms do not start at the first one, because the order is a default and the call is where it gets changed.
A note on sequencing this trade
Do not build all seven at once.
Each stage is proven against its agreed measure before the next begins.
Season note. Build Tier 1 in the shoulder season and let it run through one peak before starting Tier 2. A contractor who sees System 1 hold on the first hot Saturday will build the rest without being sold again.
Back to the HVAC overview for the stage map and where these fit.
Is this the oneyou need first?
Often it is not. On the call we look at what is actually costing you most right now, which is frequently a different system from the one that brought you to this page. If there is nothing worth building yet, we will say so.