Before/after photos that end disputed callbacks

The call comes in on a Tuesday, three weeks after the install. The customer’s air handler is doing something it should not, and the first sentence out of their mouth is “it worked fine before your guy touched it.” Now you are standing in your office trying to remember a job you finished on a busy Thursday, and the only record you have is whatever the tech happened to think of. Maybe he shot a photo. Maybe he did not. You do not know, and until you know, your word is the whole case, weighed against a customer who has a bill in hand and no plans to pay it.

That is the shape of a disputed callback, and here is the hard part. When there are no photos, you almost always eat it. Not because you were wrong, but because you cannot prove you were right, and a return visit is cheaper than a fight and a bad review. So the tech drives back out, spends an hour confirming the unit is doing exactly what it was doing when he left, and you write off the visit. A disputed callback with no photos is a free repair. It is that simple. Like the rest of the proof and getting paid guides, the answer is a record that lives with the job, not with whoever happened to be there.

Why “my guy is careful” stops working around the third truck

On a one-truck shop, you can hold the whole history in your head. You did the job, you remember the readings, you know what you left behind. The record is your memory, and for a while that is enough.

Then you add a second tech, then a third, and the record scatters. The photos that do exist live on three different phones. The tech who did the install is on another job, or he quit in the spring, and his camera roll left with him. When the callback comes in, you are not checking a file, you are texting a guy on a roof asking if he remembers a specific evaporator coil from a month ago. He does not. Nobody does. This is the same failure that shows up when your guys say they never got the message: the information existed for a moment and then had nowhere to live.

Careful techs are not the problem. The problem is that “careful” does not survive being spread across a growing crew with no shared place to put the proof. You need the record to live with the job, not with the person who happened to do it.

The five shots that settle it worked when we left

You do not need forty photos per call. You need five, in the same order, every time, so that six weeks later the file answers the question before the customer finishes asking it.

The nameplate. The model and serial on the equipment, readable. This ties every other photo to a specific unit in a specific house. Without it, a great set of photos still might belong to some other job. Getting the crew to do this one automatically is its own small battle, worth making the first shot on every call.

The readings. Static pressure, subcooling or superheat, temperature split, whatever the call demanded, shot on the gauge or the meter. This is the numbers saying the system was operating in spec when the tech walked away. Verbal readings evaporate. A photo of the gauge does not.

The condition of the surrounding work. The disconnect, the whip, the condensate line, the drain pan, the plenum, whatever your tech did not touch but is standing right next to. This is how you prove the failure that came back was not yours. If the float switch was already corroded or the drain was already half-clogged, the photo shows it was that way when you arrived.

The before. The state of the thing you were called out to fix, before you fixed it. The iced coil, the tripped breaker, the reading that was out of range.

The after. The same view, corrected. Coil clear, reading in range, system running. Before and after side by side is the whole argument in two frames: this was broken, we fixed it, here is the proof.

Shoot these five in that order and the file reads like a short story with a beginning, a middle, and an ending nobody can argue with. For the trades logic of pairing the two ends of the job, the six photos that end most callback arguments covers the general version of this same discipline.

What one missing shot actually costs

Put a number on it. A commercial customer calls back three weeks out: the new system cannot hold the back of the building and the bill jumped, and they are sure your tech caused it. You send a man out. Ninety minutes round trip, an hour on site, so call it a half-day burned by the time he is back on a billable job: two and a half labor-hours, plus the truck and the fuel. Round it to 380 dollars of no-charge time.

He gets there and finds the real problem in ten minutes. The return duct is undersized and the filter the customer installed is choking it. Static pressure is through the roof, and it always was. The system is doing exactly what it did the day you left. But you had no static pressure photo from the install, so when the customer said “it was fine before,” you had no way to say otherwise except to drive out and show them live. One reading, captured once, on the day of the job, would have turned that entire visit into a text: here is the static pressure we measured when we finished, here it is again now, nothing changed on our end.

That is 380 dollars for a single missing photo. Run three or four of those a season across a crew and you are into real money, all of it spent proving in person what a file could have proved for free. The version of this argument every HVAC shop has lived is the customer on a forum swearing “the tech broke it, it ran perfect until he showed up,” said with total confidence about a system that was failing before anyone knocked on the door. You do not win that by arguing. You win it by having shot the before.

Make the proof land on the job, not a camera roll

The photos only help if you can find them when the call comes in, and that is exactly where the camera roll fails you. Five good shots buried in a phone with four thousand other pictures, unlabeled, mixed across a dozen jobs, are almost as useless as no shots at all. When the ex-tech’s phone walks out the door, so does the proof. If that risk is live for you, your job photos on an ex-employee’s phone is worth the ten minutes.

What ends disputed callbacks is not just taking the five shots. It is having them attached to the specific job, in order, where anyone in the office can pull them up while the customer is still on the phone. The argument stops being a memory contest the moment the proof is a link instead of a recollection.

That is what a thread per job is for. In Crewmigo, each work order is its own thread that remembers, so the nameplate, the readings, the before, and the after land on the closing task instead of scattering across phones. The tech marks the task done, you can look at what he attached, and when the callback comes three weeks later you open the job and the five shots are sitting right there in order. We are new, so put one install on it and see how the next disputed callback goes. The difference is that this time you answer it with a link.