When a customer says the technician never came

Two people, both sure

It arrives two days later, usually by email, usually calm. Nobody came out on Thursday. We waited all afternoon. We are not paying for a visit that did not happen.

So you pull the ticket. Closed 2:14 PM. Notes: unit cycling normally, no fault found, recommend monitoring. You call the tech, who remembers the job, remembers the dog, remembers that nobody answered the side door so he checked the condenser and left. He is not lying. He is also not able to prove any of it, and neither are you.

Notice what the ticket actually is. It is a record your company made, on your company’s software, describing your company’s work, at a moment chosen by the person being asked about. Every word of it may be true. None of it is the kind of thing a doubtful customer has any reason to accept, because they are being asked to resolve a dispute by trusting one side’s paperwork about the disputed event.

The industry that already tried to fix this

Home care ran into this problem at national scale, and the response was regulation rather than advice. Under section 12006 of the 21st Century Cures Act, every state had to put an electronic visit verification system in place for Medicaid personal care services by January 2020. Such a system is meant to capture the date, the location, who delivered the service, what kind it was, who received it, and the start and end times. Telephone check-ins and GPS-enabled apps both qualify. On paper, the whole question of whether somebody showed up is settled.

In November 2025 the U.S. Attorney’s Office for the Eastern District of Pennsylvania announced an indictment of a Pennsylvania home-care company and four of its owners and managers, on one count of conspiracy to commit health care fraud and twenty counts of health care fraud. The indictment alleges that each of them personally completed electronic visit verification calls, attesting that they were providing care, while not actually being present with the client. The case was investigated by the FBI and the Department of Health and Human Services Office of Inspector General. These are allegations. They are charges, not convictions, and everyone charged is entitled to the presumption of innocence.

Read it for the mechanism rather than the outcome, because the mechanism is the part that transfers to your business. The system was mandatory, funded, and specifically designed to answer the question you are stuck on. What it collects is an attestation: somebody states they are at a place doing a thing. An attestation delivered through an app is still an attestation.

What a clock-in records, and what it leaves out

Most service businesses reach for a location clock-in first, and it is a genuine improvement over a paper timesheet. But it is worth being exact about what arrives in your database when a tech taps the button: a timestamp, a coordinate, and an identity. Those three things describe a phone. They do not describe a boiler, a panel, a drain, or a customer’s hallway.

Which matters because the complaint you actually receive is rarely just about attendance. “Nobody came” and “somebody sat in a van for four minutes and left” feel like one accusation to the person making them. A clock-in speaks to the first. What speaks to the second is a picture of the equipment, and that is a separate artifact you either collected at the time or did not.

Change what the record is made of

Nothing about the route or the paperwork has to change. The tech does not download anything and does not learn a new system. One artifact gets added at the job, and it is made somewhere other than the phone.

A text reaches the tech at the address, carrying a link. Opening it puts him directly into a camera view with no path back to stored images, so last August’s picture of a similar condenser has no route into today’s job. Submitting sends the photo to us, and its arrival is timed by our clock instead of the handset’s. Coordinates are stored with it wherever the tech shares location, and a reading can be made mandatory before anything is accepted.

Those elements, together with where the file is kept, fold into a single SHA-256 fingerprint. Alter the record afterwards and the fingerprint ceases to describe it. That is the work the word tamper-evident does: an alteration stays possible and stops being invisible.

If the dispute is already open and you have none of this

Most people reading this are not planning next quarter. There is an email sitting in the inbox right now, the visit was three weeks ago, and no photograph exists. Everything above is advice about a record you did not make, which is not much help on a Tuesday.

So, honestly: you are going to have to argue this one on circumstantial material, and it is worth gathering all of it before you reply. The tech’s phone location history for that afternoon, if he still has it and is willing. Fuel or mileage logs. The parts van inventory, if something was consumed on that call. Toll or vehicle-tracking data if you run it. Whatever the tech wrote to dispatch at the time, which is weaker than a photograph but stronger than a memory reconstructed under pressure three weeks later. None of it is conclusive on its own. Assembled and dated, it is a good deal better than a closed ticket and an assertion.

Then reply quickly, because the clock is often shorter than people expect. If the customer has gone to their card issuer rather than to you, the case runs on a card network’s timetable and the response window can be a matter of days, not weeks. The practicalities of answering one are their own subject, covered in winning a chargeback with photo proof. The relevant part here is that the deadline arrives whether or not your file is ready.

And consider conceding it. Not as a moral position, as arithmetic: a contested service call is often worth less than the hours you will spend contesting it, and a chargeback lost on evidence costs more than the invoice. The reason to build the habit is not this dispute. It is that this dispute is the fourth one this year, and the same conversation is currently scheduled to happen again in November with a different address in it.

The version where your technician is right

It is worth saying plainly, because the fraud allegations make this sound like a surveillance problem: most of the time the customer is mistaken and your tech did exactly what he says he did. Somebody was out at an appointment. Somebody heard the van and assumed it was next door. An adult child two states away is relaying a story third-hand and filling the gaps with suspicion.

In every one of those, the person a sealed record protects is the technician. He gets to stop defending his own memory against a stranger’s. The invoice stops being a thing you negotiate and goes back to being a thing you send. And on the rarer occasion the visit really did not happen, you learn it the same day, from your own dashboard, rather than six weeks later from a card network that has already taken the money back. Both outcomes are better than the argument.

This is also why the record has to be built before you need it. Nobody can retroactively photograph last Thursday. The habit is worth something precisely because it runs on the ordinary calls where nothing goes wrong, which is what makes it available on the one that does. The same reasoning behind keeping dispute-ready vendor records applies to every trade that sends somebody to an address.

What it settles, and what stays open

Keep the claim small, because a service manager who oversells this in a dispute loses ground he had already taken. A sealed capture establishes two narrow things: the image was made through the camera at the job rather than picked out of storage, and the file has been undisturbed since sealing.

It does not establish that the diagnosis was right, that the correct unit was serviced, that the work met the standard in the contract, or that the four minutes on site were enough. Those remain arguments between people who understand the trade, and they should. What changes is the starting point. The conversation stops being your word against theirs and starts from something neither of you authored.