How a tree service uses AI for storm day customer updates

A storm rolls through Waukesha County overnight. By 7am your phone has 40 messages. Homeowners have trees down on their cars, their fences, their roofs. Everyone wants to know the same thing: when are you coming. You've got two crews and one of you. Answering each text one at a time eats the whole morning you should spend on chainsaws.

The problem isn't the work, it's the waiting

Storm damage jobs don't take longer to answer for than any other call. The problem is volume. Everyone calls at once, and everyone wants the same answer: where am I in line. Customers get anxious fast when a tree is on their driveway. Six hours of silence makes it worse. Most of that anxiety isn't about the wait itself. It's about not knowing.

A short, personal update text does more to calm someone down than a fast arrival time does. People can handle "you're 4th on our list, we expect to reach you by 3pm" a lot better than silence.

Build one list, then let AI write the messages

Start with a simple list. Write down customer name, address, what's damaged, and their spot in your queue for the day. You probably already have this scribbled somewhere or in your scheduling tool. Paste that list into an AI chat. Ask it to write a short, friendly text for each person, using their name and situation. Something like this:

"Hi Denise, this is [your name] from [your company]. We've got your fallen tree on the list, you're 6th today. Based on how the morning's going, we expect to reach you by early afternoon. We'll text again when we're on our way."

Do this for all 40 names in one prompt. You'll have a full batch of personalized messages in under 3 minutes. Typing each one by hand could easily eat an hour of a morning you don't have.

Why personalized beats a mass text

A generic blast that says "we're experiencing high call volume, we'll get to you soon" reads like every other business's storm auto-reply. It doesn't tell anyone anything useful. It doesn't feel like a real person wrote it. A message with their name, their specific damage, and a queue position feels different. It feels like someone's actually looking at their job. That difference is what keeps customers from calling back every hour asking for an update.

Send from your own number, one at a time

The AI writes the messages, but you're still the one sending them. Send them from the same number you'd normally text customers from. Most contractors copy each message and send it manually. That still takes some time, but a lot less than writing each one from scratch. If you use a texting tool that supports bulk personalized sends, you can plug the list in directly.

• Keep messages short, under 3 sentences
• Always include a rough timeframe, even a wide one like "by end of day"
• Say you'll text again when you're on the way, and actually do it

What this buys you on a chaotic day

Say a bad storm brings in 40 calls in one morning. Writing 40 individual, thoughtful updates by hand might take you 60 to 90 minutes you don't have. Doing it through AI in a batch cuts that to maybe 15 minutes of writing. Add a little time to send them. That's an extra hour back on a day when every hour matters. Customers also get a better experience than a form-letter auto-reply.

There's a set of ready-to-use prompts for jobs exactly like this at /skills. They're built for contractors who need to move fast without sounding like a robot.

Updating the list as the day changes

Storm day schedules never hold exactly as planned. A tree that looked like a 2-hour job turns into 4 hours once you're on site. Maybe it's tangled in a power line. That pushes everyone behind. When that happens, update your list. Run a quick second batch of messages for anyone whose timeframe changed a lot. You don't need to text everyone again. Just text the ones now waiting noticeably longer than what you first told them.

This second round takes even less time than the first. You're only updating a handful of names instead of the full list. A short "quick update, we're running about an hour behind due to a bigger job than expected, still coming today" keeps the trust you built with the first message. It stops people from wondering why the estimated time came and went.

Keep it human where it counts

If a customer texts back with a specific worry, like a tree resting on a power line, don't let AI touch that reply. Handle safety concerns and anything urgent yourself, right away. The batch messages are for routine updates. Anything that sounds like an emergency gets a real, immediate response from you.