Warranty callback or new problem? Sorting the leak that came back

The call comes in on a Tuesday. Same customer, same house, and the words you never want to hear: “It’s leaking again, right where your guy was.” You pull the job off the truck’s memory, which is to say you try to remember. You did that one in March. Was it the trap under the kitchen sink, or the supply line, or the shutoff? You are pretty sure it was the trap. The customer is sure it is your fault. And you have not even driven over yet.

That standoff at the front door is the one every small plumbing shop knows. On a three to fifteen man crew, the guy who did the first repair might be on another job, might be off that day, might not work for you anymore. So the argument gets decided by whoever sounds more certain, and the customer is always certain. What almost never gets pulled up, in the moment, is a clear record of exactly what was fixed the first time. That missing record is the real fight. Warranty disputes are rarely about plumbing. They are about who can prove what was done.

The fight is a record fight, not a plumbing fight

Think about what a warranty callback actually asks you to decide. Is this the same failure you already repaired, or a new failure somewhere near it? That is a factual question with a real answer. The water either came back at the fitting you touched, or it came from something you never touched. A good plumber can usually tell in five minutes standing in front of it.

The problem is not the plumbing. The problem is that five-minute answer arrives after you have already committed to the wrong posture. You told the customer on the phone you would “make it right,” which they now hear as “free.” Or you got defensive and said it could not be your work, which makes you the bad guy when it turns out it was. Either way you argued before you had the facts, because the facts were on someone’s phone, or in someone’s head, or nowhere at all.

For the same pain from the other direction, see he said, she said: winning the callback argument with a photo trail. This is the whole idea behind the proof and getting paid guides: the record settles what talking cannot.

The questions that separate a callback from a new call

When the leak comes back, you are really answering a short list. Get these answered off a record instead of off memory and the standoff ends fast.

What exactly did we fix the first time? Not “we were out there.” The specific component: the P-trap, the supply riser, the closet flange, the quarter-turn stop. If you cannot name the part, you cannot say whether it failed.

Where is the water coming from now? Point at the joint. Same fitting you worked, or a different one nearby. Two feet of copper can hold three fittings and a valve, and “under the sink” is not an address.

Was the new leak in scope the first time? You fixed the trap. The customer never mentioned the shutoff, so nobody looked at it, and now it is weeping. That is a new problem you are seeing for the first time, not a repair that failed.

Do we have a photo from the first visit? This is the one that ends it. A dated shot of the fitting you replaced, taken the day you replaced it, tells you and the customer whether the water is coming from your work or from the next joint over.

A leak that came back, and the photo that decided it

Here is how it goes when the record is there. A shop replaces a corroded kitchen P-trap in March. Six weeks later the customer calls, water under the same cabinet, “your repair failed.” On the phone it sounds open and shut: same sink, same wet spot, same plumber’s fault.

But the first visit’s thread has three photos on the task: the old trap out, the new trap in, and a wide shot of the whole under-sink assembly. The tech pulls them up before he even leaves the shop. In the wide shot you can see the trap he replaced, clean and new, and two feet away the old galvanized shutoff he was never asked to touch. He drives over, looks under the cabinet, and the water is tracking from that shutoff, not the trap. Different fitting, different failure, and it was there in the March photo, dry but clearly original and clearly not part of the job.

Now run the math on having that photo versus not having it. Without it, this is a free callback you eat to keep the peace: a truck roll, an hour of a tech’s time, call it a hundred and fifty in labor and drive you never bill, plus the part if you replace the shutoff for free to look generous. Do that on four or five “your work failed” calls a year and you have given away most of a thousand dollars in work that was never yours. With the photo, it is a five minute conversation at the door and a fresh, fair invoice: “Different piece, the old shutoff, here is what it was next to your trap in March, here is the fix.” You get paid for real work and you keep the customer, because the record is calm and you are not arguing.

The photo did not just win the money. It changed the whole tone. Nobody had to be called a liar. You showed the picture, the customer nodded, and it was a new job instead of a fight.

Why the group text cannot settle this

The reason most shops do not have that photo ready is not that they do not take photos. Your tech probably shot the new trap in March. The problem is where it landed. It went into the shop group text, in a stream of a dozen jobs, with no caption, and by six weeks later it is buried under a hundred other messages and belongs to no job anyone can name.

So when the callback comes, the office scrolls the thread and cannot find it, or finds a photo but cannot tell which house it was, or the tech who took it is on another job and not answering. The group text has no place to keep a photo attached to the job it proves. It is one long stream, and a stream cannot tell you what was fixed at 114 Maple in March. That is the same wall the group text hits everywhere once you pass three or four people: it holds messages, not records. For the fuller version of that failure, see why your job site runs on a group text, and where it breaks.

The fix is not “take more photos” or “be more disciplined in the thread.” Your crew is already taking the photos. They just have nowhere to land where they stay attached to the job and stay findable a year out. The same gap shows up before the leak ever comes back, when the rough-in gets covered and no one can prove what is behind the wall: see photographing rough-in before drywall covers it forever.

Where Crewmigo fits

Crewmigo gives every job its own thread that remembers. The photos your tech already shoots land on the task they prove, in the thread for that house, and they are still there six weeks or a year later when the leak comes back. When the callback call comes in, you pull up the first repair’s thread, see exactly what was fixed and what was sitting two feet away untouched, and you know before you drive over whether this is your warranty or a new invoice. The record belongs to the company and you can export it if you ever need it in writing. We are new, so put one job on it: the next repair you finish, drop the photos on the task, and the first time a leak comes back you will have the answer at the door instead of an argument.