A line of storms comes up off the Gulf on a Tuesday afternoon, and by three o'clock your board is a mess. Two crews are stuck behind high water on a feeder road. A customer out in Katy is texting to ask if you're still coming. Another one already left work early to meet you and is now sitting in an empty house, getting annoyed.
So you try to run the whole day from the cab of your truck, thumb-typing the same "we're running behind, weather's bad" message to one person at a time. Meanwhile the office phone keeps ringing, and every call is the same question you just answered by text for somebody else.
Storm season does this every year. It doesn't just cancel jobs, it scrambles the entire board and turns you (or your dispatcher) into a switchboard for an afternoon. The saving grace is that almost all of that communication is repetitive, and repetitive work is exactly the kind you can set up ahead of time. You can build a solid storm-comms plan in an afternoon, well before the next system shows up on radar.
Write the texts before the storm, not during it
The reason storm updates come out garbled is that you're writing them while soaked and behind schedule. Fix that by writing them now, when you've got a clear head, and saving them as canned messages your team can fire off in two taps.
You don't need many. Four or five templates cover most of what a weather day throws at you:
- Heads-up: "Storms are moving through Houston today. We're watching it and will text you the minute your appointment window changes."
- Running behind: "Weather's got us behind. We still plan to reach you today, just later than your window. We'll text a tighter time once the roads clear."
- Reschedule: "We can't get to you safely today. Reply with a day that works and we'll lock in the first open slot."
- All clear: "Weather's passed and we're back on schedule. Your appointment is still set for [time]. See you then."
- Emergency-only mode: "We're limiting today to no-heat and no-cool emergencies until conditions improve. If that's you, reply URGENT and we'll prioritize."
Keep each one short enough to read on a phone at a glance, and keep the tone plain. A customer riding out a storm doesn't want cheerful. They want to know whether to keep waiting.
Decide your triggers before the sky does
A template is only useful if everyone knows when to send it. So agree on the triggers in advance, and write them down where the crew can see them. Vague rules turn into arguments at the worst possible time.
- Flood watch or warning for a service-area county: send the heads-up text to everyone booked that day.
- A crew held up more than 45 minutes by water or road closures: send running-behind to that crew's remaining stops.
- Any stop you know you can't safely reach: send the reschedule text and pull it off the board.
- Storm's cleared and crews are rolling again: send all-clear to anyone who got a heads-up.
Notice these are tied to real conditions, not a feeling. When the trigger is concrete, a dispatcher or an automated flow can act on it without waiting to check with you mid-storm.
Build the reschedule flow so it mostly runs itself
Rescheduling is where the phone tag really piles up, and it's the piece most worth automating. A simple two-way texting setup (software that sends your template and reads the reply back) can carry most of the load. When a customer texts a day back, the system offers your open slots, the customer picks one, and it lands on the calendar without you touching it.
Here's the shape of a flow you can build with off-the-shelf scheduling and texting tools:
- You (or the trigger) mark a job as storm-affected.
- The customer gets the reschedule text automatically.
- They reply with a preferred day, and the system texts back two or three real openings.
- They pick one, it books, and both of you get a confirmation.
- Anything the system can't handle (an odd request, an upset customer, a safety question) gets flagged to a human right away.
That last step matters. The goal isn't to remove people from the conversation, it's to keep them out of the fifty routine reschedules so they've got time for the five that actually need judgment.
Keep the crew and the customer looking at the same board
The other storm-day breakdown is internal. A customer gets told one thing by text and something different by the tech who shows up, because the truck and the office weren't looking at the same information. Weather makes that gap worse, since plans change by the hour.
Pick one source of truth for the day's status, usually your scheduling software, and make every update flow from there:
- When a job moves, it moves on the shared board, not just in someone's head.
- The customer text and the crew's route pull from that same board, so they never disagree.
- Crews report delays into the system (a quick tap, not a phone call) so the next customer's text goes out on time.
When it's working, a customer who calls in gets the same answer whether they reach the office, read a text, or ask the tech at the door. That consistency is most of what people mean when they say a company handled a storm well.
Where automation earns its keep, and where it doesn't
Be honest with yourself about the line. Automated texting is great at the repetitive, predictable parts: sending status updates, offering open slots, confirming a new time. It's reliable precisely because those tasks don't require judgment.
It is not good at deciding whether a road is passable, whether a job site is safe, or whether a worried customer needs a real voice on the line. Don't wire up a system that auto-cancels a no-heat call for an elderly customer during a cold snap because a rule fired. Keep a person in the loop for anything with a safety or health angle, and make the handoff to that person fast and obvious. A tool that quietly makes the wrong call in a storm is worse than no tool at all.
Worth doing this week
You don't need the whole system before the next storm. Start with the pieces that pay off first:
- Write your five storm templates and save them somewhere the whole team can grab them in two taps.
- Write down your send triggers, tie each to a real condition, and share them with dispatch and crews.
- Turn on two-way texting in whatever scheduling tool you already use, and test the reschedule flow on yourself.
- Pick your one source of truth for daily status, and make sure customer texts and crew routes both read from it.
- Mark the one place a human always steps in, and make that handoff quick.
Set up right, most of a weather day runs on templates and a shared board, and you get to spend your attention on the calls that actually need it. If you'd rather have someone build the flow with you, that's the kind of thing we set up at AI Agency Houston, but the plan above stands on its own. Get the templates written this week, and you'll be ready when the Gulf sends the next one your way.