Casson Technologies
All posts

Storm Tuesdays in Louisville (and the $5,000 jobs that go to whoever picks up)

The first big front of spring, the first ice storm of winter — that's when Louisville tree crews bleed jobs to voicemail. Here's what AI answering actually does on storm night.

Adam

There's a sound a chainsaw makes that drowns out everything else. Phones included.

Last Tuesday, a front rolled through Louisville. Big one. Hail, wind, the works. By 9 PM, half the trees in the Highlands were leaning toward somebody's roof, and the other half were already on it. If you run a tree crew, you already know what happened next: the phone started ringing. And ringing. And ringing some more.

Except your phone was sitting on the truck seat. And you were 40 feet up in a bucket on a job that started at noon and was going to run another two hours.

Every one of those callers got voicemail. And then they called the next tree service in their search results.

Louisville is a two-storm-season town

Here's the part nobody outside the trade really thinks about: we get two storm seasons. There's the spring front pattern — those big nasty cells that roll in from Indiana between March and June and snap limbs off everything in their path. Then there's the winter version: ice storms. Less dramatic in the moment, way more carnage when the sun comes up.

Both produce the same call pattern. Quiet for weeks. Then the front lands, and from about 7 PM that night until midnight, you get hit with thirty, forty, fifty inbound calls. Every one of them is somebody pretty sure there's a tree on their car, or leaning toward a power line, or blocking their driveway in Anchorage or out in Oldham County.

Every one of those calls, depending on your job mix, is worth somewhere between $500 and $15,000+.

I'll let you do that math.

The phone problem isn't a phone problem. It's a hands problem.

Most tree service owners I've talked to in Louisville (and across the river in Jeffersonville and New Albany) are not bad at picking up the phone. They're just running a saw thirty feet up. Or rigging a takedown over a customer's pool. Or elbow-deep in a chipper getting the morning's branches loaded.

You can't pick up a phone with both hands on a chainsaw. You shouldn't pick up a phone with both hands on a chainsaw. And even if you could hear it ring (you can't, the saw is right there), you'd be dropping into voicemail somewhere between cut three and cut four. By then your customer is already on the next listing.

That's the actual problem. Not lazy answering. Not bad voicemail messages. Just the physics of a job that requires both of your hands and most of your attention to keep you out of the ER.

7 PM to midnight is the whole game

Want to know when 80% of your storm-season inbound actually happens? Not while you're working. After.

After people have driven home. After they've gotten the kids to bed. After they've stepped outside with a flashlight and looked at what just happened to their oak.

7 PM to midnight, the Tuesday after a big front. That's when the phone goes nuclear.

If you're like every tree crew I know, you're showering off sap and pine pitch from like 6:30 to 7:30. Then eating something. Then maybe sitting down for the first time all day. Are you answering call 22 of 47 that have come in since you put your phone down at 6? Nope. You're staring at the ceiling trying to remember if you ever called your mom back this week.

Here's the thing, though. Whoever picked up at 9:14 PM Tuesday won the $5,000 storm job. Not the best crew. Not the closest crew. The crew that picked up.

A human receptionist gets hung up on by call number 3

Some operators get smart and hire somebody to handle storm-season overflow. This works for about a week, and then it doesn't.

Here's why: a human can answer one phone at a time. Call 12 lands while she's still on call 11? Call 12 hits voicemail. Call 13 hits voicemail. Call 14 hits voicemail. By the time she's done with call 11 and ready to call 12 back, call 12 has already booked with somebody else.

Which is the same outcome as not having the receptionist at all, except now you're paying for it.

I'm not anti-receptionist. I'm just saying the math doesn't work for a tree service in Louisville during the eight or nine weeks a year that actually pay for the year.

The AI handles call 14 and call 15 and call 16 simultaneously

This is the part nobody quite gets until they've watched it happen.

The voice agent we set up at Casson Technologies isn't a phone tree. There's no "press 1 for emergencies, press 2 for estimates." It's a conversation. The caller talks, it talks back, and the whole thing sounds like a polite, awake person who works in your office and knows the difference between deadwooding and a topping cut.

And it does this on every call. At the same time. As many concurrent callers as your forwarding setup can route, the AI handles. Storm Tuesday at 9:14 PM, four people calling at once about four different fallen oaks? Four conversations happening in parallel. Four bookings or four escalations to your cell. No queue. No voicemail.

The triage is the actual product

Here's what we configure for tree crews specifically. The AI listens for emergency signals and routes those differently than estimate calls.

  • Tree on a house.
  • Tree on a car.
  • Tree leaning toward a power line.
  • Tree blocking a driveway.

Anything with that energy gets routed straight to your cell, with location and situation already collected, so you call back with the info in hand instead of starting from zero.

The pruning-and-estimate calls go on the calendar. Customer wants a quote on next month's deadwooding pass on the three white oaks at her place in St. Matthews? Booked, calendar slot, confirmation SMS sent. You find out about it in the morning.

If a caller asks about credentials — and they do, especially for the bigger jobs — the AI confirms what you actually have. ISA-certified arborist, insurance limits, whatever you tell us to mention. It's not going to invent credentials you don't have. That would be bad. It just answers the question honestly if it comes up.

The math, if you're a tree crew in Louisville on Growth

Our Growth plan runs $597/mo. That includes 24/7 coverage, the full CRM and pipeline, missed-call text-back, and the AI handling the storm-Tuesday-at-9-PM scenario.

One booked storm-emergency takedown — $5,000-ish for a tree on a roof with crane access — is more than eight months of Growth.

Now, depending on your job mix, you might not book a storm-emergency takedown every single month. Some crews run mostly estimates and routine pruning at $400-$800 a pop. The math still works at that level — three or four recovered missed calls a month covers the plan and then some. The storm-job math is just the easy version.

One Tuesday is the whole pitch

Honestly, this whole thing comes down to one or two Tuesdays a year. The first really nasty front of spring. The first ice event of winter. You're going to get 40 calls between 7 PM and midnight that you literally cannot answer — and right now, those 40 calls are going to whoever's number sits second on the Google results.

We just want them to come to you instead.

Setup is under 48 hours. We handle the script, the routing, the calendar wiring, the emergency keywords. You go back to running the saw and stocking the truck for tomorrow. The phone takes care of itself.

Want to hear what it sounds like? There's a button on our homepage that opens the demo agent right in your browser. Try something like "hi, my name is Adam, I think there's a tree on my car" and see how it handles it. (Spoiler: it handles it.)

If you'd rather just talk to a person about whether this fits your operation, the book a demo page does exactly that. Either way, the next storm season is going to come whether you set this up or not. The only question is which crew picks up first.