Gutters after the storm: handling the call surge without losing the urgent ones
A gutter company does not get a steady flow of calls. It gets quiet weeks and then a Monday with thirty messages because it rained over the weekend. An AI voice agent answers every call in that surge, sorts the queue by urgency and gets visits booked while your crew stays on the ladder. InfiVoice starts free with 100 credits and works in 30+ languages.
The real problem is the queue, not the call
If the phone rings ten times in an hour and you are ten feet up a ladder, you answer two and call back the rest at night. By then half of them have booked someone else. The agent does not do your work on the roof. It makes sure no call from the surge goes unlogged and that the urgent ones reach your phone before the routine ones.
Who calls and what they need
- The homeowner watching water pour over the edge. They want someone soon. This is the call that should skip the calendar.
- The one who found leaves, twigs or weeds growing in the gutter. They want it cleared before the next rain, but it is not an emergency.
- The one with a stain on the wall or damp in the basement who suspects the gutter. They need a person to look, not an agent guessing the cause.
- The property manager or landlord with several buildings. They ask about more than one address in a single call.
- The returning customer who wants last season's cleaning again. They ask for a date, not a quote.
- The shopper. They ask the price in the first minute and hang up if they do not get one. Decide in advance what the agent says to that.
Gutter details the agent should capture
You do not need everything on the first call. This is what saves the most time for whoever does the visit:
- Address and whether it is a house, townhome, apartment block or storefront.
- Number of stories and any deck, garage or porch that forces a ladder move.
- How many sides of the building have gutters and whether there are runs the customer cannot see.
- Whether there are guards, buried downspouts or a rain barrel connection.
- What the customer sees: water over the edge, a drip at one corner, a sagging run, plant growth.
- Whether it has rained since the problem started or whether they want it done before the next rain.
- Pets, a locked side gate or someone who needs to be home.
- A phone number and the best window for a callback.
Sorting the queue with three labels
1. Urgent. Water overflowing, a section hanging or a visible leak. The agent notifies a person right away and does not offer a slot.
2. This week. Leaves built up, pre-winter cleaning, a repeat cleaning. Book it.
3. No rush. Pricing questions, guards, replacement. Collect the details and flag for a callback.
That way, on storm Monday you open the list and start at the top instead of listening to thirty voicemails.
Example call in the middle of a surge
Caller: Hi, I saw your ad. The corner of my gutter is packed with leaves and it rained yesterday. Nothing's pouring over yet, but I don't want to wait for that.
Agent: Got it. Right now there's no water coming over the edge, is that right?
Caller: Right, it's just full.
Agent: Perfect, I'll note it for this week. How many stories is the house, and how many sides have gutters?
Caller: Two stories, three sides.
Agent: Thanks. Is there a locked gate or a dog in the side yard? And what's the address so I can find you a slot?
Common mistakes and how to avoid them
- Booking an overflow for Thursday. If water is getting in, the customer will not wait. Set the urgent branch to notify a person.
- Letting the agent quote a price per foot without your rates. Load your rules, or have it only collect details and call back yourself.
- Giving safety advice or saying the roof will hold. The agent does not climb or assess. Your crew does.
- Forgetting multi-property callers. Add a follow-up question to log each address.
- One script for every caller. One question per call type is enough; you do not need a long questionnaire.
What to load into the knowledge base
Cities or zip codes you cover, what your standard cleaning includes and whether debris haul-away is separate, how many days ahead you need in peak season and your rain-cancellation policy. For how to structure it, see /blog/how-to-prepare-a-knowledge-base-for-an-ai-voice-agent.
How to set it up
1. Build three branches in the visual builder: urgent, this week and no rush.
2. Set the urgent branch to notify a person and skip the calendar.
3. Connect your calendar for the this-week visits (see /blog/can-ai-voice-agent-connect-to-google-calendar).
4. Load your service areas, rates if you want them mentioned and what to do about rain cancellations.
5. Test with a local number on the Free plan before you move your main line.
Pricing
Free includes 100 credits. Pro is $79 per month with 250 credits. One credit equals 60 seconds of call time, so a short intake call uses few credits. See /blog/ai-voice-agent-pricing.
Frequently asked questions
Can the agent sort calls after a storm?
Yes, with separate branches by call type. You decide what counts as urgent and who gets notified.
What happens if a customer describes roof damage?
The agent records what they say and flags it for a person on your team to assess. It does not diagnose.
Can it handle several addresses in one call?
You can set up a follow-up question to collect each address separately.
Can it tell the customer when you will arrive?
Only if you load that information. If your routes change daily, it is better to offer a window or have a person call back.
Can I try it for free?
Yes. The Free plan includes 100 credits.