What an ‘on-the-way’ text can—and can’t—fix for tree service crews
See where ServiceTitan’s on-the-way alerts work well, where arrival communication still breaks down, and when your tree service needs another process.
The message worked. The timing did not.
It’s September. The crew pulls up to a pruning job, chip truck rumbling at the curb, and the customer is already gone. They expected you later, so the gate is locked and the dog is loose in the yard. Nobody did anything reckless. The notice simply came after the customer had made their plan.
That is the hard part of tree service arrival communication: a message can be correct and still arrive too late to help.
Before adding another automated text, run one test. Did the customer need to know the crew had left, or did they need useful lead time before then? Most misses fall into one of three buckets: setup, timing, or a conversation that needs a person.
What ServiceTitan’s on-the-way alert does well
ServiceTitan’s dispatch alert does exactly what its name promises. It can send an automatic notice when a technician is dispatched, as long as you have configured a default outbound SMS number. That makes it a strong ServiceTitan on-the-way text for the customer who only needs a heads-up that the crew is now moving.
Arrival tracking can add useful detail, but it is not magic sprinkled on a template. ServiceTitan requires native GPS on each technician device and a Tech Tracking URL token in the notification template. For the customer to see the map, distance, and ETA, the service address must also be verified. Without that verification, the tracking page shows the technician name and destination address instead. ServiceTitan’s dispatch notification guide lays out those dependencies.
Before you blame the alert, check:
- Is the default outbound SMS number configured, and is the customer’s mobile number accurate?
- Does each field technician use native GPS, rather than a separate GPS provider that cannot supply Track Now links?
- Is the service address verified, and does the message template include the tracking URL token?
Native GPS matters here. ServiceTitan says GPS location can be accurate within 3–10 meters, while cellular triangulation may be about 500 meters when GPS is unavailable. Non-native devices can still receive dispatch notifications, but they do not support real-time tracking links. That distinction is documented here.
Myth: one more text fixes the missed arrival
Myth: The customer missed the crew, so we need another tree service arrival alert.
Reality: The dispatch notice may have fired exactly as designed. But by dispatch, the customer may already be at school pickup, across town, or in a meeting. Tree routes move because a removal ran long, rain paused climbing, the crew made a dump run, or the loader needed attention. More alert volume does not create earlier information.
Myth: An automated message covers the communication problem.
Reality: A message only helps when its trigger matches the decision the customer needs to make. A dispatch alert is tied to dispatch. An arrival notice is tied to the technician tapping Arrive. ServiceTitan treats those as separate events. Its customer communication guide also notes that a rescheduled appointment does not automatically send a new booking confirmation.
Treating every miss with another text is like using duct tape on the dispatcher’s entire day. It has its place, but not on everything.
Sort the problem before choosing the fix
Tree service notification workflow gets messy when every issue lands in the same bucket. Name the symptom first. Then assign the first fix and the person who owns it.
| Symptom | Likely cause | Best first fix | Owner |
|---|---|---|---|
| No alert, or wrong details | Bad number, template, address, or trigger setup | Audit customer data and notification setup | CSR or dispatcher |
| Customer needed earlier notice | Dispatch happened after their plans changed | Send an earlier queue position or arrival window update | Dispatcher |
| Crew is running late | No trigger for a changed ETA | Send a revised window or delay update | Dispatcher |
| Today’s job order changed | Route sequence changed without notice | Tell affected customers about the new order | Dispatcher or service manager |
| Gate, pets, permit, or access issue | Customer needs to answer a question | Call or text from an owned inbox, then record the answer | CSR or dispatcher |
| Customer wants another date | This is a booking-change conversation | Confirm options and reschedule with a person | CSR |
The owner column is not busywork. If a customer sends back, “Gate code changed,” someone has to see it and act before a crew burns 30 minutes at the curb. ServiceTitan documents two-way texting through its separately enabled Chat feature, with replies appearing in the Chat inbox when that feature is enabled and tested. Do not assume every automated ServiceTitan dispatch notification is a monitored conversation channel.
Your text practice needs a consent and opt-out process, too. The FCC says autodialed mobile texts require prior consent, and recipients can opt out by reasonable means. The FCC guidance is plain about both. Appointment alerts are informational messages under CTIA’s messaging practices, but that does not excuse a dead-end reply path or ignored opt-out request.
When the native alert is enough
Keep the ServiceTitan dispatch setup simple when you can answer yes to these questions:
- Do crews reliably update dispatch status and tap Arrive when they get there?
- Are mobile numbers and service addresses accurate before the job is dispatched?
- Are native GPS and tracking settings in place where you promise tracking?
- Does the customer only need immediate pre-arrival notice?
- Does the office already have a clear process for delays, access questions, and inbound texts?
If yes, the native alert is enough. Do a configuration audit before buying or adding anything. A well-run dispatch alert is useful, and it does not need to become a larger project just because one job went sideways.
When earlier queue updates earn their place
Earlier updates earn their place when the customer’s position changes before dispatch. That is common in tree work. A customer who was third in line at 8:00 a.m. may be first after a rain delay, or fifth after a hazardous removal takes over the morning.
Queue Up is a focused one-way communication option for proactive tree service notifications: queue position, updated windows, delay notices, and pre-arrival messages. It supports the dispatcher and service manager by giving them a repeatable way to keep customers informed. It does not replace their judgment, and it should not pretend to.
Still needs a person.
A queue update cannot settle a gate-code question, decide whether pets are secured, confirm a permit issue, or book a new date. Those are exceptions and replies. Give them a named owner, a monitored inbox or phone path, and a clean handoff when the dispatcher is tied up.
Use the smallest fix that matches the failure
Fix configuration when the trigger or customer data is wrong. Add earlier updates when lead time is the gap. Use owned human follow-up when the customer must answer before work can start.
Was this late notice, a changed sequence, or an unresolved conversation? The answer tells you whether the ServiceTitan on-the-way alert needs tuning, support, or no blame at all.