How Clearwater Plumbing Co. Booked 22 Jobs Without Answering a Single After-Hours Call

Carlos started Clearwater Plumbing Co. in Tampa 11 years ago. Two crews, a solid Google rating, and more work than he could comfortably handle in peak months. From the outside, a successful small business.

From the inside: Carlos was the phone. Every call in, every call out, every booking, every question about availability. While he was on a job site — which is where he spends most of his day — calls piled up. After 6pm, they went to voicemail and stayed there.

“I’d look at my phone after a job and have eight missed calls,” he said. “I’d return some of them. Half wouldn’t answer. By the time I got to them the next morning, half of those had already hired someone else.”

In the 30 days after setting up the AI Intake Stack, 22 jobs were booked from leads Carlos never personally spoke to during intake.

The Problem Was the Owner, Not the Business

This is a common pattern with owner-operated service businesses: the owner becomes the bottleneck.

Carlos wasn’t losing jobs because of bad service or poor reputation. He was losing them because he physically couldn’t answer the phone while using both hands on a job — and because in Tampa’s competitive plumbing market, a homeowner with a slow drain or a dripping pipe isn’t going to wait three hours for a callback. They Google “plumber near me” and call the next listing.

Before Numbers

We started by pulling 60 days of call data from his phone provider:

24 leads per month, vanishing. At an average job value of $340, that’s $8,160/month walking away — just from calls that weren’t answered.

The emergency jobs were the most painful losses. Burst pipe calls, water heater failures, flooding — those callers don’t leave a voicemail. They call the next plumber.

What We Built

The intake audit ran first: mapping where calls came from, what questions Carlos asked to qualify a job, and how he dispatched across two crews.

Three things shaped the build:

1. Emergency escalation was non-negotiable. Any call involving flooding, no hot water in a home with young children, or potential pipe failure needed to reach Carlos immediately — not queue until morning. We built a separate emergency path with a real-time text alert to his cell.

2. Service area filtering. Tampa has clear geographic zones and Carlos had strong crew coverage in specific zip codes. The AI asks for the service address early and confirms it’s within range before investing further in intake.

3. Booking into real crew availability. Carlos used a simple calendar to manage his two crews. We connected the AI directly to it so it could offer actual available windows — not generic “we’ll call you to schedule.” The prospect picks a slot. It’s confirmed. No phone tag.

Build time: 17 days from kickoff to live.

Month One

The AI went live on a Monday. Carlos’s instruction to his team: “don’t tell anyone we changed anything. Let’s just see what happens.”

30-day results:

Revenue from AI-captured bookings:

• Standard jobs: 16 × $340 average = $5,440
• Emergency jobs: 6 × $555 average = $3,330
• Total: $8,770 in booked revenue from leads Carlos didn’t personally field

The six emergency escalations included two burst-pipe calls on a Saturday night. Both became same-day jobs. One was a commercial property that turned into a multi-day repair.

What Changed Week Over Week

Carlos described the first week as disorienting. “I kept reaching for my phone expecting to deal with calls, and there was nothing to deal with. The bookings were just showing up in the calendar.”

By week three, the operational shift was more concrete:

Morning routine changed. Instead of starting the day returning missed calls from the night before, Carlos opened his calendar to confirmed bookings and his CRM to a ranked list of leads that needed a personal touch — complex jobs, large commercial inquiries, customers who had specifically asked to speak with someone.

He stopped being the dispatcher. The AI handled scheduling across both crews within the parameters he’d set. Carlos reviewed the week’s calendar Sunday evening rather than managing it reactively throughout the week.

The office assistant shifted focus. She had been spending several hours a week on call-return follow-up. That time moved to customer check-ins and review coordination — work that actually builds the business.

Carlos tracked his own time for the first two weeks after launch. His estimate: 8 hours per week recovered from phone management. For an owner billing $115/hour on direct work, that’s $920/week in recovered productive time.

The Investment Conversation

Month one recovered revenue from AI-captured bookings: $8,770.

At that rate, the setup cost pays back in roughly six weeks of normal operation. Year two ongoing cost is $9,600 — less than one average month of recovered revenue.

Carlos’s assessment after 90 days: “I should have done this two years ago. I was working harder to answer my own phone than it would have cost to let a system do it.”

Is Your Service Business in the Same Position?

If you’re an owner-operator handling your own phones, or running a small team where intake falls through the cracks after hours, the pattern Carlos experienced is probably familiar.

The math question is always the same: what are you losing each month to unanswered calls, and what would it take to get that back?

Our AI Readiness Audit answers that question specifically for your business — two weeks, a flat fee, a written ROI model with your actual numbers. Carlos went through the audit before any build started.

See what the audit includes for local service businesses →