When storms scramble the schedule, what should send and who should call?

6:12 a.m.: one storm, two queues

At 6:12 a.m., the office has barely warmed up. Rain is still tapping the windows. A homeowner is reporting a split limb over a driveway, another says a tree is leaning toward a service line, and three pruning customers want to know whether today is still happening.

The aerial-lift crew cannot be everywhere. Holding it for qualified hazard work may mean moving planned pruning jobs, creating a second queue of homeowners who need a clear update.

Severe thunderstorms can bring tree-breaking winds, lightning, tornadoes, and flash flooding. The National Weather Service says so plainly.

Send a one-way update when the board has a confirmed answer; involve a CSR when the customer needs judgment, choice, or care.

Set the boundary before anyone sends a message

A good storm response schedule has clear owners because vague handoffs create bad promises.

Dispatch owns the board: crew fit, equipment, routing, and which planned jobs can move after capacity is checked. CSRs handle booking changes needing agreement, complaints, access or scope questions, and worried customers. The notification layer follows confirmed board changes; it can send timing updates, but cannot set priority, reroute crews, or turn an unverified note into a promise.

FEMA emergency-planning guidance similarly calls for named decision points, information, owners, and gaps before pressure arrives. Clear primary and support roles matter in a changing incident.

Board: dispatch confirms the schedule state.
Update: the system sends predictable timing information from that state.
Conversation: a CSR takes over when the answer depends on the customer or the facts are not settled.

Keep one source of truth for status, arrival window, trigger, and message history. If the board says one thing and the text says another, the text will win in the homeowner's mind every time.

Use four tests for every customer update

Before an automated customer update goes out, run four quick tests. They stop routine tree service communication from wandering into a conversation that needs a person.

A confirmed message can be plain: “Today’s pruning visit has moved to Thursday. Your arrival window is 10 a.m. to 1 p.m. We’ll send another update if that changes.”

Use a CSR when access, a neighboring-tree concern, or a repeat move requires judgment rather than a timing update.

First pass: dispatch protects hazard capacity and resets the board

Dispatch makes safety and capacity calls before anyone promises times:

1. Group incoming work. Separate reports into immediate hazards, urgent follow-up, and movable planned work. Capture facts, not drama: location, what is affected, access, visible line involvement, and whether the customer can safely stay clear.

2. Check the real limits. Review qualified crews, aerial-lift availability, equipment condition, travel, daylight, and current weather. Storm-damaged trees can hold stored energy, and wet trees and tools add electrical risk. OSHA-hosted training material advises treating downed lines as energized and stopping for help when the crew is uncertain.

3. Protect qualified hazard capacity. Hold the aerial-lift crew for work it is equipped and qualified to handle. Do not fill its route with ordinary pruning just because those appointments were first on the calendar.

4. Reseat planned work around confirmed capacity. Move pruning and non-urgent work only after dispatch knows what capacity remains. A wider window is better than a narrow fiction.

5. Leave uncertain jobs unmessaged. If dispatch has not decided, do not attach a made-up arrival time; use an early review notice only if your process supports it.

6. Use shared internal labels. For example: hazard review, held for dispatch, reseated, confirmed window, and CSR callback.

Priority follows verified hazard facts, access, crew capability, and resources—not first-come, first-served.

Second pass: routine changes send without feeding the phone queue

Once dispatch confirms a schedule state, proactive customer notifications can carry the routine information. This is where automated customer updates earn their place: they give a homeowner the current answer while CSRs handle the calls that cannot be answered with a timestamp.

Use this checklist for each approved trigger:

• Send only from a confirmed board state, not from a dispatcher’s tentative note.
• State what changed: delayed today, a wider arrival window, a new date, or crew en route.
• Give the current timing window, not false precision.
• Say when the customer should expect the next update if the schedule remains unsettled.
• Provide a clear reply path for questions or changes.
• Suppress duplicates and replace stale windows when the board changes again.
• Check failed deliveries and unanswered messages during the morning, then move uncertain cases into the CSR queue.
• Send routine updates only during your approved contact hours; reserve truly urgent safety communications for circumstances your policy, counsel, and messaging vendor permit.
• Honor consent, opt-outs, and approved contact rules. The FCC says autodialed texts to wireless numbers generally require prior consent, recipients can opt out in a reasonable manner, and the rules differ by message type. Review the FCC guidance with counsel and your messaging vendor before treating storm updates as an automatic exception.

Where Queue Up fits: Queue Up can follow confirmed schedule changes and send the approved update. It is not a routing tool, a priority engine, or a substitute for dispatch judgment. Its job is to keep routine tree service schedule updates current, so the CSR has time for the customer who needs a real conversation.

The goal is not to remove the CSR from storm response; it is to reserve CSR time for access, safety, and distressed-customer questions.

Pull these situations out for a CSR conversation

Some schedule change notifications should never be the last word. Move these cases to a CSR, with a clear callback owner and deadline:

• The customer must choose a new date, approve added work, change the service scope, or cancel.
• Gate codes, parking instructions, pets, tenant access, or contact details are missing or changed.
• A safety concern needs questions and facts, not a stock warning. Do not ask a customer to assess energized lines or make a call the crew has not made.
• The customer reports damaged property, disputes priority, or is already unhappy from a prior delay.
• The job has moved more than once.
• Payment, estimate, insurance, contract, or authorization questions are attached to the work.
• The customer signals distress, a disability, a language need, or another situation that calls for more time and a usable channel.
• An update failed, or the customer did not respond when a response is needed to keep the appointment.

A failed delivery is not an update; it is an open loop.

For added-care situations, ask what the person needs, record it, and return known facts to operations. FCA guidance similarly recommends workable channels, time for complex cases, and warm handoffs.

A warm handoff note should include:

• Current board status and the latest honest timing.
• Known facts: access, reported hazard, line status, prior contacts, and message delivery.
• The options the CSR may offer without returning to dispatch.
• The person who owns the next decision.
• A callback deadline, even if the answer is simply, “We are still assessing capacity and will call by 11 a.m.”

That note prevents the CSR from reopening the case and dispatch from receiving the same question through multiple channels.

Make the rule usable on the next bad-weather morning

Put this on one page near dispatch and the CSR work area. It should show approved board states, the matching message types, the red flags that require a call, and the owner for each exception queue.

Before the next storm, name the person responsible for board accuracy and the person responsible for aging CSR exceptions. During the morning, check delivery failures, stale arrival windows, and callbacks that have slipped past their deadline. Afterward, review wrong sends, missed calls, and jobs that moved repeatedly. Fix the trigger or handoff that caused the problem.

The operating boundary is short enough to remember under pressure: automate known timing; call when judgment or customer choice enters. Dispatch changes the board. Routine updates follow the board. CSRs handle the moments where a homeowner needs more than a message.