The McKinney Plumber's Missed-Call Turnaround: How a Typical DFW Service Business Recovered 9 Jobs a Month

A ringing phone is a sales opportunity, but it is also a distraction when you are under a sink, on a roof, or helping a customer at the counter. For a typical DFW plumbing business, missed calls can quietly become missed jobs.

This fictional but realistic composite follows a 7-person plumbing company serving McKinney, Allen, Frisco, and nearby neighborhoods. The owner did good work and had steady demand. The problem was simple: calls came in faster than the team could answer them, especially during lunch, after hours, and while technicians were driving.

The company did not need a complicated technology project. It needed a dependable first response, a better way to collect the details a dispatcher asks for every day, and a short list of calls that deserved a human callback first.

1 The problem was not a lack of phone calls

The McKinney company received about 120 inbound calls in a typical month. Around 30 came during busy periods when no one could answer: the owner was quoting a repipe, the dispatcher was already on another call, or a technician was finishing a job. Another 20 arrived after the office closed.

Some callers left a voicemail. Many did not. A homeowner who hears a generic greeting and has no idea when someone will call back may dial the next plumber in the search results. That is especially true for a leaking water heater, a clogged drain, or a move-in repair that feels urgent to the customer even when it is not an emergency.

When the owner reviewed the phone log, the loss was hard to see. The company counted booked jobs, not unanswered opportunities. A missed call was just an empty line in a report. The first improvement was to measure that line.

2 What changed at the front door

The business added an AI receptionist as a first layer for missed calls and overflow. It did not pretend to be the owner. It used the company’s approved service list, hours, service area, emergency guidance, and scheduling rules to keep the next step clear.

When a call could not be answered, the receptionist offered a choice: leave details for a callback, answer a routine question, or follow the company’s emergency instruction. It asked for the caller’s name, phone number, city, type of problem, and preferred timing. It repeated the details back so the customer could correct a mistake.

For a non-urgent request in Allen, the handoff might say: “We can help with drain cleaning in your area. I can note the issue and preferred day for the team. A dispatcher will review it during office hours.” For a potential gas smell or other dangerous situation, it did not troubleshoot. It directed the caller to the business’s approved safety instruction and marked the call for immediate human attention.

The owner also set a boundary around pricing. The assistant could explain that a service call or estimate may have a fee when that was approved, but it could not promise a final price. That small rule prevented a fast answer from turning into a bad promise.

3 The before-and-after numbers

Before the change, about 50 calls a month were either missed or returned without enough information to schedule the next step. The team spent roughly 12 hours a week calling back, asking the same basic questions, and trying to reconstruct which opportunity was most urgent.

During the first 30 days, the assistant handled the first response on 44 overflow or after-hours calls. Thirty-one callers provided complete details. The dispatcher marked 22 as qualified opportunities and reached 18 of them in the planned callback window.

Over the next two months, nine of those recovered opportunities became jobs each month on average. At a 35% close rate, that translated to about three extra jobs per month. Using the conservative $1,250 average job value, the planning estimate was $3,750 in additional monthly booked revenue.

The time result mattered just as much. The dispatcher spent about four fewer hours each week gathering basic details. The owner used some of that time for estimates and some to leave the office on time. This was not a promise that every business will see the same numbers. It was a measurable test tied to calls, callbacks, and booked work.

4 What made the handoff work

The assistant succeeded because the company treated it like a front-door process, not a one-time purchase. The owner wrote down what a dispatcher already knew by heart and reviewed the first conversations every week.

• A short approved answer list: service area, office hours, common services, scheduling expectations, payment basics, and when to call a person.
• A clear priority label: urgent safety concern, qualified estimate, routine question, or incomplete request.
• A single callback list: name, number, city, job type, timing, summary, and assigned person in one place.
• An honest voice: no invented prices, no fake guarantees, and no claim that a technician was already on the way.
• A weekly review: the team corrected confusing answers and removed questions that should always go straight to a human.

That last point is important. A useful AI receptionist is not the one that talks the most. It is the one that knows when to stop and make the handoff easy.

5 What to do this month

Owners in Plano, Frisco, Garland, Richardson, Mesquite, Arlington, and Fort Worth can test the same idea without changing every system at once. Start with the phone problem you can measure:

1. Count missed and overflow calls for 30 days. Include lunch, evenings, weekends, and calls that went to voicemail.
2. Review 20 call records. Write down the questions callers ask, the details dispatchers need, and where the handoff breaks.
3. Choose three safe first tasks. For example: collect job details, answer hours and service-area questions, and create a callback request.
4. Set the human rules. Decide what goes to a person immediately: safety concerns, complaints, price negotiations, unusual jobs, and anything outside the approved answer list.
5. Run a 90-day scorecard. Track missed calls, complete requests, callbacks, qualified opportunities, booked jobs, average job value, and dispatcher hours saved.

6 What this looks like next quarter

By the end of month one, the owner should know where calls are being lost and which questions create the most phone tag. By month two, the team should have a consistent first response and a callback list that does not depend on one person’s memory.

By month three, compare recovered jobs and saved hours with the baseline. If the numbers are positive, expand one step at a time: appointment requests for a dental office in Allen, delivery questions for a supplier in Dallas, or pickup instructions for a shipping store in Garland. If the numbers are not positive, fix the handoff before adding more features.

The goal is not to make the business feel automated. The goal is to make sure a good customer reaches the right person before the opportunity goes cold.