Storm-day customer updates: what to automate and when to call

The storm changed the board before the phones opened

At 6:45, the dispatcher has three overnight damage calls, two aerial-lift jobs booked for pruning, and a crew asking whether a road is passable. The planned work does not disappear because the storm arrived. It has to move around urgent hazard work without putting crews into a bad site.

Meanwhile, homeowners with an 8:00 window are waiting for a useful update. Not a vague “weather delay” text that creates three more questions.

That is the hard choice on a storm morning: protect hazard-response capacity without leaving moved customers in the dark. The operating boundary is simple: dispatch makes the work decision; automation reports a settled decision; a CSR handles the conversation when judgment is still needed.

First, let dispatch settle the work

A customer notification workflow starts with the dispatch board, not with the send button. The dispatcher owns routing, crew fit, travel, equipment, and where a job can be reseated. A message cannot know that the only available aerial lift is needed for a damaged tree near a structure. The dispatcher can.

Before crews head out, check the hazard level, required equipment, site conditions, and promised arrival windows. Weather monitoring and a pre-set action plan belong in outdoor-work planning, too. If thunder is heard, NOAA advises getting to safe shelter and waiting 30 minutes after the last thunder before work resumes. NOAA’s lightning guidance is a useful reminder that a schedule is never more important than a safe call.

Use one current board as the source for every outbound update. Do not trigger a customer message from last night’s route, a technician’s informal estimate, or a half-finished move.

Before any tree service scheduling update sends, the board needs:

• A status: unchanged, delayed, moved, pending review, or canceled.
• The old window and the current, customer-ready window.
• The reason category, such as weather hold, crew reassignment, or access issue.
• The dispatcher who owns the decision.
• A timestamp for pending review, so “we’ll figure it out” does not become a status.
• A note on whether the customer must choose or approve the next step.

Storm work can disrupt cell service, GPS, and weather updates, according to the Tree Care Industry Association’s storm-response guidance. A clearly owned board beats a clever workflow built on bad information.

Use a three-question test before anything sends

The fastest way to create a longer phone queue is to send a message that sounds final when it is not. Use this test before an automated customer update goes out.

1. Is the dispatch decision final enough to share?

   A confirmed new arrival range is final enough. “We may move this after we see what the lift is doing” is not.

2. Is the update informational, rather than negotiable?

   “Your crew is now expected between 1:00 and 3:00” is information. “Can you take Thursday or Friday?” needs a person who can listen, answer questions, and record a choice.

3. Is there no known customer, site, or safety exception?

   A standard pruning visit with a confirmed delay can sit in the automatic lane. A locked gate, a tenant who needs notice, a tree on a roof, or a worried caller cannot.

Only send automatically when all three answers are yes. If any answer is no or unclear, place it in the CSR escalation process. This is fast triage, not a substitute for judgment.

What belongs in the automatic lane

Automated updates work when they carry stable facts from the live board, rather than repeatable uncertainty.

Safe use cases include:

• A narrowed arrival window after dispatch confirms crew sequence.
• A routine delay with a credible revised range.
• A permitted same-day reseating, crew-en-route notice, or queue-position change tied to the board.
• A weather hold when the customer need not make a choice.

Each notification should include the reason category, current timing, the next update point, and a real contact path. Do not promise an arrival time dispatch has not confirmed.

A message anatomy can be this plain:

• Business and purpose: who is contacting the homeowner, and why.
• Current status: delayed, moved, or crew en route.
• Timing: the confirmed window or the next promised update point.
• Customer path: a monitored reply, callback number, or rescheduling route.
• Preference control: opt-out instructions where required for the program and channel.

Where Queue Up fits: Queue Up should follow the status dispatch has already set. It can send the one-way timing layer quickly, but it should not edit the route or decide which job loses the aerial lift. That is dispatcher work, full stop.

Build safeguards around the automatic lane: block duplicate sends, stop stale updates once the board changes, respect quiet hours, and keep consent and opt-out records current. The FCC says autodialed texts to mobile phones require prior consent outside emergency purposes, with different standards for informational and commercial texts. Its consumer guidance also says people may opt out in a reasonable manner. CTIA guidance treats appointment reminders and alerts as informational only when the person gave their number and agreed to that specific purpose; adding a coupon or sales prompt can change the treatment. Read the CTIA guidance and have counsel review the actual program, since channel, location, and message purpose matter.

What still needs a CSR conversation

Some updates are not updates at all. They are a decision, an apology, a safety concern, or a request for help. Do not hide those behind a text template.

Customer judgment

Send these to a CSR:

• The homeowner must accept a new date or choose among openings.
• There is a complaint, repeat delay, missed promise, or refund request.
• The caller has access needs, is anxious about a hazard, or has a special service agreement.

Site and business risk

These also need a human path:

• Access or coordination—such as a gate, tenant, access code, or parking rule—affects the visit.
• The caller reports property damage, an insurance concern, or disputed responsibility.
• There is a tree on a structure, an unstable limb, blocked access, or a possible energized line.
• The request exceeds the CSR’s authority.

OSHA says the tree and worksite should be assessed before work, including damaged trees, equipment, limbs, and energized lines. OSHA’s tree-care guidance supports a written escalation rule; give emergency or utility guidance instead of placing an immediate-danger caller into a booking queue.

For the handoff, dispatch provides the old plan, safe new plan, permitted options, and escalation contact.

Run the handoff without making customers repeat the story

A clean dispatch-CSR handoff keeps customers from repeating the story. Use this sequence:

1. Dispatch records the change: old plan, new plan, reason, and safe options.
2. The CSR sees context: contact preference and known access issues.
3. Name one owner: decide the next customer touch and when.
4. Write the outcome back: accepted date, declined option, callback, or escalation.
5. Resume automation only after recording the decision: it must not contradict a live conversation.

Give safety and property-damage reports an urgent path to operations leadership. For other calls, triage by risk, not arrival time. The queue may object, but it does not get a vote.

Close the loop before the next storm morning

At day’s end, review the customer notification workflow while the details are still visible. Check sent notices, CSR calls, and exceptions that should have been caught earlier.

• Find outdated windows, duplicate contacts, and promises still unresolved.
• Count avoidable inbound calls, corrected messages, escalations, and kept promises.
• Change a rule when a real pattern appears, not because one unusual complaint rattled the room.
• Name the person responsible for templates and exception rules.

The point of a storm response process is not to automate every customer touch. Automate stable facts that dispatch has settled. Assign changing choices, safety concerns, and human frustration to people who can do something with them.