When HVAC ETA texts help—and when customers need a person
A practical guide to automating routine HVAC ETA updates while keeping access issues, schedule changes, complaints, and urgent calls with a real person.
The board moved, but the customer did not get the memo
It is 2:18 on a summer afternoon. The install call ran long, the maintenance tech found a bad capacitor, and three visits on the HVAC dispatch board just slid to the right.
Meanwhile, new web requests are landing, the noon rush has not quite let up, and your phone lights up with the familiar question: “Are you still coming?” Again. That loop has earned its own chair in the office.
A customer whose service window changed needs an HVAC ETA update. But a customer with a locked gate, a sick child at home, or no cooling in a second-floor bedroom needs more than a status alert.
The useful question is simple: is this a stable fact to share, or a judgment call that needs a person?
Myth: every customer text counts as customer service
A text can be good customer service. It is not automatically a customer-service conversation.
Automated customer notifications work well when they deliver a predictable fact: the service window has moved, the technician is on the way, or the appointment is still within the window already given. The CSR should not have to type the same clean update to eight customers while the board changes underneath them.
But a changed plan needs an answer. A reschedule request needs a choice. A complaint needs someone to hear what went wrong and decide what happens next. Research on channel choice reaches the same practical conclusion: people choose more interactive channels when they need personal, situational support, especially for complaints and redress. Customers’ channel choice review
Ask two questions: Is the message only information? Does the customer need to reply, decide, or feel reassured?
If the first answer is yes and the second is no, send the update. Otherwise, put a person on it.
Good automation territory: routine updates with no decision attached
Automated HVAC ETA texts earn their place when the dispatch event is dependable and the message does not create a new commitment.
-
The afternoon queue shifts, and a later service window is now likely. Send a revised window to every affected customer, once the board supports it. Do not wait for each customer to call first.
-
The technician is actually dispatched and headed toward the stop. Send a technician on-the-way text. ServiceTitan’s dispatch notifications can automatically send at dispatch. Its customer notifications use a shared arrival-window setting for confirmations and reminders. Its arrival-window options are documented here.
-
Several customers need the same plain update. Use the same timing and wording across the affected visits. Consistency matters when the office is busy.
-
The board gives you a window, not a precise arrival minute. Say “We’re now expecting our technician between 3:00 and 5:00 PM,” not “They’ll be there at 3:27.” An arrival window leaves room for traffic, parts runs, and unexpected delays.
-
The text channel does not accept replies. Keep the message one-way. Do not invite a reply that nobody can see, then call that communication.
On-the-way timing still needs common sense. ACCA’s practical guidance suggests roughly 45 minutes to an hour of notice when that gives the customer time to prepare without rushing the technician. That is a useful check, not a magic number. Read the ACCA guidance.
Human handoff territory: the customer needs an answer, choice, or reassurance
The moment a customer’s response could change the appointment, stop the technician at the door, or raise the stakes, the CSR or dispatcher owns the next step.
| Situation | Why automation falls short | Who takes the next step |
|---|---|---|
| Access detail: gate code, locked property, pet, or tenant | A text cannot confirm the note was received and added for the technician. | CSR uses a reply-capable channel and logs it. |
| Customer cannot hold the revised window | They need choices based on openings and technician skills. | CSR offers times or a callback. |
| Complaint, repeat delay, or urgent no-cool call | The issue needs ownership or a priority decision. | Service manager and dispatcher respond. |
| The prior job runs long or older notes affect the response | Another ETA may be too uncertain, or prior promises may matter. | Dispatcher checks the job; CSR reviews the log and updates the customer. |
| Delivery fails or a customer replies to a one-way number | The update did not reach a usable conversation path. | Named office owner calls or routes the customer to the office line. |
For non-reply-capable texts, FCC rules require clear disclosure that two-way texting is unavailable and reasonable alternate ways to revoke consent. See the FCC’s robotext rule. Have compliance counsel review your message program.
Guardrails that keep an ETA text from becoming a promise
-
Use a trusted board event and an honest window. Send only when the committed window is likely to change or the technician is truly dispatched. State a range, not a minute.
-
Name an office owner and log the contact. Give customers a real office number or reply-capable route. Assign delivery failures, access questions, opt-outs, and escalations to the CSR, dispatcher, or service manager; record the window, send result, and resolution. During a major board reshuffle, pause automation until the plan is stable.
Where Queue Up fits — and where it stops
Queue Up belongs on the routine side of this workflow: use it to support proactive updates while the CSR handles work that requires judgment. Confirm the current product capabilities and handoff routes in product documentation before configuring messages.
The limit matters: a one-way delivery path cannot collect or record a confirmation, gate code, access reply, or exception response. Build an office-owned path beside it before turning messages on.
The quick decision rule for the next board shift
When the HVAC dispatch board moves, do not make the CSR choose between typing routine updates and handling the customer who actually needs help.
Stable fact, no reply needed: send the proactive update.
Customer choice, changed commitment, risk, or emotion: get a person involved.
That is not automation replacing the CSR. It is automation protecting the CSR’s attention for booking changes, upset customers, access problems, and urgent calls. Set the owner for those exceptions first. Then let the routine HVAC ETA texts do their quiet job.