How Do I Get Plumbers to Present Repair vs Replace Options?

The homeowner never got to decide

Almost every plumbing call has a fork in it. Fix the shutoff valve or replace the assembly. Snake the drain or scope the line and talk about the root problem. Replace the element or replace the heater. Patch the one section of galvanized or talk about the repipe. The tech stands at that fork on every call, and most of the time he picks a side in his own head and quotes only that.

He picks the cheap side because it is faster, because he does not want to sound like a salesman, and because nobody has ever shown him the words for the other side. The homeowner hears one price, says yes, and thinks the tech was honest. He was. He was also silent about the option that would have saved them a Sunday flood and doubled the ticket.

You told the techs to present options. Some do. Look at the tickets and you will see which ones, and you will see that the tech who presents options has a ticket that looks nothing like the tech who does not, on the same kind of call.

Why "present options every time" does not change anything

An instruction is not a skill. A tech who has been told to present options still has to know what to say when the homeowner asks why the cheaper one is not fine, or says "just fix it for now," or says the neighbor's plumber said the heater has years left. Without those words ready, the tech tries it twice, gets an awkward silence, and goes back to quoting the cheap fix. That is not stubbornness. It is what people do with a skill that has been explained and never rehearsed.

There is a second reason. Nobody can see whether the fork was presented. The invoice shows what was sold, not what was offered. So the tech who skips it and the tech who runs it look the same on paper until month end, and by then the pattern is a habit. Only 29% of companies can see whether training changed what their reps do. In plumbing that number is probably generous, because the conversation happens in a basement.

Write the fork down as steps

Take the fork out of the tech's head and put it on paper as your process. Diagnose fully before quoting anything. Explain what was found in words the homeowner uses, not trade terms. Present at least two options with prices side by side. Recommend one and say why, tied to what the homeowner said about the house and how long they plan to stay. Ask which one they would like to do today. If they hesitate, handle the objection and ask again.

The recommendation step matters most and gets skipped most. Two prices with no recommendation is a menu, and homeowners pick the cheaper item on a menu. Two prices with a plain reason is advice from a professional, and homeowners take advice. "Given the age of the pipe and that you are planning to stay ten years, the repipe is the one I would do in my own house" is a different sentence from "here are your two options."

• Diagnose fully before quoting
• Explain the finding in homeowner language
• Present two options with prices side by side
• Recommend one and say why
• Ask for a decision today, and ask again after the objection

Give techs the words and make them say them out loud

The objections at the fork are predictable, so they are trainable. "Just fix it for now." "That is more than I expected." "I want to get another price." "Let me talk to my husband." Each one needs a short, honest response the tech has said out loud dozens of times before a homeowner says it. Honest is the point. Techs will not use a line that feels like a trick, and they are right not to.

Practice has to happen daily, before the first call, not once at a meeting. In Revenue OS, techs run the fork against an AI homeowner by text or live voice, with 5 personas plus custom personas built on your market at 3 difficulty levels. Each run is scored in about 60 seconds on script adherence, objection handling, close attempt, energy and tone, and follow-up setup, 20 points each, with a coach's note. 70 clears. A new tech runs the easy homeowner who takes the recommendation. A veteran runs the one who has a quote from a competitor and a spouse who wants to wait.

Score the real call on the fork

Practice tells you whether the tech has the words. Only the real call tells you whether he used them. Record visits from the tech's phone with the homeowner's consent, and score them against your written steps. The question is not "was the call good." It is "did he present two options, did he recommend one, did he ask." When your process is 60% of the score, a skipped fork shows up as a number, timestamped, without anyone listening to the whole visit.

A weak call should turn into practice on the exact moment it failed, fast. A visit that scores under 80 becomes a redo due 6pm the next business day, against an AI homeowner seeded with the words the real homeowner used. The tech who let "just fix it for now" end the conversation on Tuesday runs that exact objection Wednesday morning until it comes out right. The manager gets a queue sorted by urgency instead of a stack of recordings.

What changes in 30 days

Week one, publish the steps and start the daily practice. Week two, the practice scores show which techs have the recommendation sentence and which are reading a menu. Week three, the real-call scores show who is running the fork under pressure and who runs it only in the app. Week four, the tickets start to separate, and the techs who present options are visible to the whole team on a nightly number.

You did not ride along. You did not argue with anyone about whether they present options. The steps, the practice score, and the call score did the arguing. The tech who fixes the leak and leaves now has a number next to his name, and so does the tech who presents the repipe. That is what it takes to move the average ticket and break your revenue record.