ServiceTitan arrival notifications and when a CSR steps in

The missed arrival is not a notification problem anymore

It is 12:18 p.m. The technician got to the maintenance call early. The homeowner is still at work. Meanwhile, two calls are waiting, and the dispatcher is trying to place an afternoon no-cool call.

The text saying “your technician is on the way” did its job. It reported a status. But the customer’s plan is now broken. That takes more than another automated HVAC text message.

This is where HVAC CSR workflow gets muddled. An arrival notice is not the same thing as a kept promise. When the facts change, someone has to decide what happens next, say it plainly, and make sure dispatch can deliver it.

Two bad ideas cause most of the trouble: that every text needs a reply path, and that an alert tool should handle rescheduling. A text cannot apologize or rebuild a schedule. It has enough trouble finding punctuation.

Automate routine facts. Put a CSR on anything that needs a decision, an apology, or a new promise.

Use the fact, choice, trust test

Before you send or answer an HVAC customer notification, run this quick test.

Fact: Is this a known schedule detail that needs no office decision? “Your appointment is scheduled for 1:00–3:00 p.m.” is a fact. So is a final technician-on-the-way text based on real field movement. Those are good candidates for customer notification automation.

Choice: Is the customer asking to change timing, routing, price, access, or job scope? “Can you come after 4?” is not a status update. It changes the day. A CSR needs to check with dispatch before agreeing to anything.

Trust: Is the customer upset, confused, worried, or reacting to a failed promise? “Your technician came while I was gone” needs a person, even if the original notice was accurate. The customer needs to hear what happened and what the office will do now.

If it is fact-only, automation can send it. If choice or trust enters the exchange, CSR ownership begins. That boundary keeps HVAC communication workflow clear when the phones are not.

What should run automatically

Automate routine facts in the order the customer needs them:

• Confirm the arrival window and send a shift update when dispatch facts materially change it.
• Send an ahead-or-behind notice before the customer has to ask.
• Send a final on-the-way text only when the technician is actually headed there.
• Include an office phone path without promising a text conversation you do not staff.

ServiceTitan supports automated on-the-way notifications and configurable templates. Native GPS, a tracking-URL token, and a verified service address affect the tracking details customers see. Set expectations accordingly.

Use stable wording. “Your technician is on the way” is better than “We’ll be there in 10 minutes” unless the office can stand behind that estimate.

Assign routine messages based on your office’s verified configuration and staffing, not on assumptions about a particular tool’s capabilities.

CTIA’s guidance calls for purpose-specific consent, consent records, and honored opt-outs for appointment alerts. Read it before treating a phone number as blanket permission.

What still belongs to a CSR

A CSR owns any moment involving a decision, apology, or new promise:

• Early arrival or missed appointment: Explain the miss and work with dispatch on the next workable visit.
• Rerouting, rescheduling, cancellation, access, or scope changes: Confirm what dispatch can actually do before agreeing.
• Conflicting stories or safety, vulnerable-customer, or payment concerns: Pause, verify the facts, and involve the right person.

ACCA recommends spotting delays from field updates, explaining them, then asking whether the customer wants the later appointment or a reschedule. That is complaint recovery, not a scheduling bot’s victory lap.

A warm handoff is simple: the CSR states the need to dispatch, dispatch confirms the option, and the CSR makes the customer-facing commitment.

Build the handoff inside ServiceTitan

Use a small, repeatable exception workflow; ownership rules remain office policy.

1. Check what was sent. Review message history, sent time, arrival window, and schedule changes. Chat history can be available when ServiceTitan Chat is configured, but automated notifications appear in a chat log only after a manual thread exists. Do not assume every alert created a staffed conversation.
2. Get the field fact. Ask dispatch whether the technician arrived, left, is delayed, or can return. Do not promise a new window yet.
3. Call with ownership. Explain what happened, apologize when needed, and offer only dispatch-confirmed options.
4. Record the agreed next step. In the customer record your office uses, document the contact, access limits, apology, and new commitment so the next CSR knows what the customer heard.
5. Flag the exception. Create an office flag or task with a named owner and due time.
6. Close the loop. Update the customer and job record, and make sure dispatch sees the plan. ServiceTitan offers dispatch and reschedule actions, though arrival-window behavior can vary by configuration. Confirm your setting.

Minimum job record fields

• Message sent and time
• Original and current arrival window
• Confirmed field fact and customer access or callback preference
• Apology or recovery offered
• Agreed next step, owner, and due time

A reply inbox is not active ownership. It is only a place where a message can wait.

A calmer office comes from a clear stopping point

The automatic layer should be judged on timely, accurate routine updates. The CSR layer should be judged on clear ownership and promises that hold.

That split gives time back to the CSR for booking calls, explaining real options, and recovering a customer relationship after a scheduling error. It does not remove the CSR from the work. It keeps them out of notification housekeeping and available for the moments that need judgment.

Before you turn on a new message, ask:

1. Is this only a fact we know is true right now?
2. Could the customer reasonably need to make a choice after receiving it?
3. If the promise fails, is a named CSR ready to own the next conversation?

If the first answer is yes and the other two are no, automate it. If choice or trust shows up, hand it to a person and make one promise the office can keep.