How to evaluate customer text workflows after a storm reroute

A storm reroute is the real test

A September storm can send the aerial-lift crew to a tree on a roof and push routine pruning work later or into tomorrow. Dispatch must cover safe work with the crew and equipment available while the CSR handles arrival-time questions.

Storm work may involve unsafe conditions, disrupted cell or GPS service, and equipment limits while crews still serve home clients in a Tree Care Industry Association storm-response review.

Evaluate whether a notification workflow detects the first operational change, identifies every affected job, and gives customers an accurate update without creating unnecessary ETA calls.

First, separate board changes from customer updates

The crew board is the operational truth. It says who is going where, with which equipment, and in what order. A customer text is the consequence of a change on that board. Those are related, but they are not the same workflow.

A standard appointment reminder is useful. It usually points back to the original appointment. ServiceTitan documents automated booking confirmations, reminders, dispatch alerts, arrival notices, and completion surveys; its dispatch and arrival alerts are tied to a technician being assigned or en route in its customer notification documentation. That is the normal ServiceTitan customer texting baseline.

Schedule-driven customer notifications need a different test: can the message reflect the current queue after a reroute, not the appointment that existed yesterday?

Dispatch owns crew coverage. The CSR owns customer conversations that need a person. Operations sets the rules. Texting should make the handoff clearer.

Test 1: How much of the schedule can trigger a text?

Ask the vendor to map every trigger to the exact schedule field or event it watches. “Automated schedule update texts” is a label, not an answer.

Use this scorecard during the demo. Mark yes only when you see it work against a real job and customer record.

Reminder rules are not live schedule-change triggers. ServiceTitan says reminders can be set for 24 hours before the appointment or a specified time the prior day, and same-day bookings made after that window do not receive one in its reminder settings guide.

Ask: What exact ServiceTitan field or event causes this text to send? Mark partial until the vendor shows it.

Test 2: What happens to every displaced job?

Run a storm reroute in a sandbox. Test jobs that were not directly changed but were displaced by the reroute.

Setup

Create one day with a lift crew assigned to hazard-capable work and several lower-risk pruning jobs behind it. Include one job with a missing mobile number, one late addition, and one job that could move into tomorrow.

Action

Reassign the lift crew to an urgent hazard job. Move the pruning jobs later, change the order of at least two jobs, then make a second reroute after the first update is queued.

Expected result

A workable customer notification workflow should:

• Produce a full list of affected jobs, including the pruning work left behind.
• Base each update on the revised queue, not stale appointment data.
• Send messages in a sensible order when several customers shift at once.
• Recheck late additions and jobs moved across days.
• Flag missing or failed contact data for the CSR instead of quietly treating it as complete.
• Avoid sending an old update after the second reroute changes the plan again.

Verify that the workflow identifies both the directly changed job and every job displaced by that change.

Test 3: Does one-way messaging protect the dispatch handoff?

A one-way operational text can be appropriate during storm schedule changes. Dispatch needs to manage coverage rather than open-ended customer threads. One-way messages must still identify the sender, explain the change, and provide a contact path.

The message should say who it is from, why the plan changed, and what happens next. If a customer needs help, give them the published call path. ServiceTitan’s documentation notes that business-unit phone numbers can appear in reminder and dispatch messages so customers can reach the business when needed.

Treat consent, opt-out handling, quiet hours, and failed delivery as operating controls, not footnotes. CTIA’s messaging guidance classifies appointment reminders and alerts as informational messaging and says opt-in disclosures should identify the organization, originating number, opt-out and customer-care information, and privacy policy in its 2023 best-practices guide. For covered robotext programs, FCC rules also require a non-reply-capable text to disclose that limitation and provide a clear alternative way to revoke consent under the FCC’s 2024 TCPA order. Have qualified counsel review your program design.

Pass signs

• The sender and reason are plain.
• The text gives a useful next step and a phone path for help.
• A delivery failure lands with the CSR or assigned exception owner.
• Consent and opt-out status are checked before sending.

Fail signs

• “Reply STOP” appears on a number that cannot process it, with no alternative.
• Customers reply into an unmanaged inbox.
• Dispatch must chase failed texts while crews are being reassigned.

The point is time returned to dispatch for coverage work, with the CSR holding the exceptions that need judgment.

Test 4: Can the team prove what was sent?

“Sent” is not enough when a customer asks why nobody arrived. The CSR needs the exact record without searching through multiple systems.

Use this field-level checklist for every customer message log.

Identity

• Customer and contact ID
• Job ID and business unit
• Sending number or brand
• Consent and opt-out status at send time

Event

• Schedule event or trigger that caused the send
• Original and revised date, arrival window, or queue position when relevant
• Exact rendered message body, template, and version
• Automation or person that initiated it

Delivery

• Send timestamp and time zone
• Provider submission state
• Delivered, failed, retried, or duplicate-attempt state
• Failure reason where available

Do not call a message “read” unless the delivery provider actually supplies a supported read signal. Sent, delivered, and read are different facts.

Review

• Search and filters a CSR can use during a live call
• Shared visibility for dispatch, CSR, and operations
• Retention and export options
• An audit trail when workflow rules or templates change

CTIA recommends keeping detailed consent metadata and opt-in and opt-out requests in its messaging guidance. For storm work, retain the schedule event and revised commitment with that record.

Run one live reroute before you buy

Bring one lift-crew hazard reassignment into the demo and score what you observe. Feature names do not count.

Queue Up fits this test when you need daily queue texts, refreshed updates after board changes, and CSR review of the message log. It supports dispatch and CSR work.

Choose the workflow that reduces manual updates and gives dispatch more time to cover changed work.