How a 4-Truck Plumbing Company Stopped Losing Weekend Calls and Added 11 Jobs Per Month

A plumbing business in the Greater Toronto Area had four trucks, six technicians, and a call volume problem that the owner could not see.

He knew calls were getting missed. Every Monday morning, there were a handful of voicemails from the weekend. Some callers left a number. Most did not. The ones that did leave a number got called back, but by that point they had already booked elsewhere.

He estimated the problem was costing him maybe five jobs a month. The actual number, when we ran the audit, was closer to fourteen.

That gap , between what an owner estimates and what the data shows , is the most common thing I encounter in Front Door Audits. The voicemails you can count. The calls that hung up without leaving a trace, those are invisible. And they are always the majority.

This is the account of what changed, why it worked, and what the economics looked like after 90 days.

The Starting Point

The business ran a tight operation. The owner, a plumber by trade who had started the company twelve years earlier, managed dispatch himself during business hours. His wife handled the office line from 8 AM to 5 PM Monday through Friday. Evenings and weekends, calls went to voicemail.

The practice was not unusual. Most small plumbing operations in this size range operate exactly the same way. The owner and his wife were not being negligent. They were doing what small plumbing companies have always done.

The problem is that consumer behavior has changed. People do not call during business hours for a burst pipe on a Saturday morning. They call when the problem happens. And they do not leave voicemails. They call the next number on Google Maps.

When we pulled the call log data during the audit, the picture was clear:

• Total inbound calls over 90 days: 412
• After-hours calls (outside 8 AM to 5 PM weekdays): 163
• Answered after-hours calls: 22
• Missed after-hours calls: 141

A voicemail was left on 31 of those 141 missed calls. The other 110 callers hung up and called someone else.

Of the 31 voicemails, 12 received callbacks within 4 hours. Of those 12, 4 converted to booked jobs.

The math: 141 missed calls, 4 booked jobs. A 2.8 percent conversion rate on after-hours call volume.

The owner's estimate of 5 lost jobs per month was based on the voicemails he could count. The actual loss was the 110 calls that left no trace.

What the Revenue Loss Looked Like

Plumbing emergency jobs in the GTA in this period averaged $680 for first visits. Weekend and after-hours calls are higher-urgency, higher-ticket. The average emergency ticket for this business was $820.

Using the call data and a conservative 35 percent close rate on answered calls:

• 141 missed after-hours calls per 90 days = 47 missed calls per month
• At 35 percent close rate: 16.4 potential booked jobs per month not captured
• At $820 average: $13,448 in missed monthly revenue
• Annualized: $161,376

The owner had built a steady business doing approximately $720,000 per year in revenue. His after-hours call problem was costing him the equivalent of more than 20 percent of his gross revenue.

He had not seen it because the lost jobs never appeared anywhere. There was no report. There was no alert. The calls simply never returned.

The System That Was Installed

The solution had two primary components: a voice AI that answered every after-hours call and a missed-call text-back for any call that went unanswered during business hours.

Voice AI for after-hours and overflow.Starting at 5 PM on weekdays and all day on weekends, every inbound call was answered by a voice AI within three rings. The system introduced itself as the after-hours answering service for the company and asked three questions: the caller's name, their address, and a brief description of the issue.

For urgent issues , burst pipes, sewage backup, gas-adjacent plumbing emergencies , the system flagged the call as emergency-tier and immediately sent the caller's information to the on-call technician via SMS and to the owner via push notification. The technician could call the customer back within minutes.

For non-urgent issues , slow drain, minor leak, quote requests , the system captured the information and confirmed that the business would contact them the next business day at the front of the queue. It sent an immediate confirmation text to the caller.

Missed-call text-back.During business hours, when a call went unanswered for any reason, an SMS was automatically sent to the caller within 90 seconds: "Hi, this is [Company Name]. We just missed your call. We're calling you back right now. If you need immediate help, reply here and we'll get someone on it." The message was sent under the business's own number.

This single text-back captured a significant fraction of mid-day missed calls that would otherwise have gone to a competitor.

The First 30 Days

The system went live on a Tuesday. By that Friday, the owner had already seen a difference.

He received push notifications on Saturday morning for three calls that came in between 7 AM and 10 AM. All three were customers with legitimate plumbing issues. Under the old system, all three calls would have gone to voicemail. Under the new system, the on-call technician saw the details within 90 seconds of each call and called back in under five minutes.

All three booked.

That single Saturday represented more recovered weekend jobs than a typical prior full month of voicemail-based callbacks.

By the end of the first 30 days:

• After-hours calls answered by voice AI: 61 out of 64 (95.3 percent answer rate)
• Emergency-tier calls flagged and dispatched: 18
• Emergency-tier calls that converted to booked jobs: 14
• Non-urgent calls logged for next-day follow-up: 43
• Non-urgent follow-up conversion rate: 28 percent

Compared to the prior period, the business went from 4 converted after-hours calls per month to 14 emergency conversions alone in the first month.

90-Day Results

After 90 days, the data told the full story.

Metric Before After 90 Days

After-hours answer rate 13.5% 95.8%

Emergency calls booked per month 4 14

Non-urgent after-hours booked per month 1 11

Total additional jobs per month -- 20

Revenue added per month -- $16,400

Monthly system cost -- $497

Net monthly ROI -- $15,903

The system added an average of 20 additional jobs per month. At an average ticket of $820, that was $16,400 in recovered monthly revenue on a system that cost $497 per month.

The return on investment was 3,200 percent in the first 90 days.

The owner said it this way during a follow-up conversation: "I used to think the weekend was just dead time. We were there if someone needed us, but we couldn't really serve them. Now the weekend is like a second business day."

What the Owner Did Not Have to Change

A meaningful aspect of this outcome is what was not required.

The owner did not hire additional staff. He did not change his on-call schedule. He did not purchase new equipment. He did not change his pricing, his service area, or his marketing.

The system sat between the phone and the team. It handled the first contact. The team handled the work.

The owner's wife found her workload slightly reduced because follow-up calls on already-captured leads were more organized. Instead of calling back unknown numbers from a voicemail log, she had a queue with caller name, address, issue description, and urgency level ready each morning.

The on-call technician's experience changed most. Previously, when he was on call, he would occasionally check his personal phone for voicemails and call back what he found. Now he received a structured push notification with all caller details and could make an informed dispatch decision within seconds of the call.

The Second Problem This Revealed

About 60 days into the system being live, a secondary issue became visible.

The business was capturing more leads. But the booking process during business hours was still manual, and when call volume spiked, some booked jobs were being missed in the dispatch system. A customer would call, book a 10 AM appointment, and the job would not be logged correctly because the office was handling three calls simultaneously.

The next phase added automated booking confirmation: every booked appointment received an SMS confirmation immediately after the call, and a reminder 24 hours and 2 hours before the appointment.

No-shows dropped from 12 percent to 4 percent over the following 30 days. That additional recapture was worth approximately $2,800 per month in appointments that had previously been lost to forgotten bookings.

What This Looks Like for Your Plumbing Business

The numbers in this case study are specific to one business in one market. But the structural problem is universal.

If your plumbing company is running fewer than 5 trucks, managing after-hours coverage through personal cell phones or voicemail, or experiencing any calls that go unanswered on evenings and weekends , the revenue gap almost certainly exists. The size depends on your call volume, your market, and your average ticket. But the pattern is consistent enough that we have not run a Revenue Leak Diagnostic for a plumbing business of this size without finding a significant after-hours loss.

The system cost is the same regardless of market. The revenue it recovers scales with your volume.

FAQ

What is the typical after-hours call loss for a small plumbing business?

Small plumbing companies with fewer than 5 trucks typically miss 30 to 50 percent of after-hours inbound calls to voicemail. Of those missed calls, 70 to 85 percent do not leave a voicemail and do not call back. The revenue loss from this pattern typically ranges from $8,000 to $25,000 per month depending on market and call volume.

Do I need to have someone on call for the voice AI to work?

For emergency dispatch, yes , a technician needs to be reachable to take the callback. The voice AI handles the first contact, captures the caller's information, and sends it to whoever is on call. The actual work decision remains human. For non-urgent calls, no on-call staff is needed. The system captures the inquiry for next-day follow-up.

How long does it take to set up an AI answering system for a plumbing business?

Most implementations at The Quiet Protocol are live within 5 to 7 business days from contract signing. The system is configured to the specific business's hours, service area, and dispatch protocol before going live.

What happens if the voice AI cannot answer a question?

The system is configured to handle first-contact intake, not full technical consultation. If a caller asks a question outside its scope, it acknowledges the limitation and confirms that a team member will follow up. It captures the caller's information and routes it appropriately.

How much does this type of system cost for a plumbing business?

The front-door system for a plumbing company of this size starts at $497 per month. This includes the voice AI, missed-call text-back, automated booking confirmation, and CRM routing. For most businesses with more than 30 inbound calls per month, the system pays for itself within the first week of operation.

Will customers find it strange to talk to an AI?

In our experience, callers experiencing a plumbing emergency care about two things: being heard and knowing someone is coming. The voice AI handles both. The majority of callers in emergency situations do not ask whether they are speaking to a human. They provide their information, receive confirmation, and wait for the callback.

*To see what your plumbing business is currently losing in after-hours call volume, request a Revenue Leak Diagnostic at thequietprotocol.com. The 15-minute diagnostic produces a specific revenue figure.*

Before the Next Sales Call

Use this section as a quick buyer check. A plumbing company owner does not need another vague automation pitch. They need to know which part of the front door is leaking, what the system will change, and how they will measure whether the fix is working.

Source method: compare the article against your own call log, CRM notes, booking calendar, missed-call records, web form timestamps, and Google Business Profile review recency. Those records are more useful than a generic benchmark because they show what buyers actually experienced in your business.

What proof should I look for in my own business?

Look for proof in the places where demand either moved forward or stalled: missed calls, short calls, unbooked forms, slow callbacks, no-show recovery, old leads, and reviews that were never requested. If the business cannot see those moments clearly, the first improvement is better tracking and routing.

How do I know whether this is a marketing problem or an operations problem?

If people are already calling, filling forms, asking for prices, requesting appointments, or comparing reviews, the problem is usually operations. More marketing will not fix a front door that lets warm demand wait. The better move is to capture and route the demand already arriving.

What should happen after the first response?

The first response should create a next step: booked appointment, estimate path, intake handoff, callback window, review request, or reactivation sequence. A response that only says someone will get back to you is not enough when the buyer is comparing several providers at once.

Where does The Quiet Protocol fit?

The Quiet Protocol fits when the business already has demand but too much of it depends on manual attention. We connect AI receptionist coverage, web intake, missed-call recovery, booking logic, follow-up, review requests, and reactivation into one managed front-door system.