Did the tech show for the tune-up? Check without calling him off a roof

It is 2pm on a Tuesday in July. A maintenance-agreement customer calls the office: nobody came for the tune-up. You pull up the schedule and yes, that address was on Marcus’s route this morning. So you call Marcus. He does not pick up, because Marcus is on a roof at that exact address with an amp clamp in one hand, right in the middle of the job the customer says never happened.

You call again. He steps off the ladder, wipes his hands, answers, tells you he has been there since 12:40, and climbs back up. You call the customer back, tell them the tech is on site right now, and everyone moves on. Fifteen minutes gone. Marcus’s rhythm broken. And you will do the whole thing again tomorrow with a different address and a different customer, because this is not a Marcus problem. It is a “how do I know where my guys are” problem, and every small shop pays this tax daily. Like the rest of the proof and getting paid guides, the fix is a record that answers the question for you, not another call to your busiest man.

The call is a tax on your one working person

Here is the part that stings. The did-anyone-go-out-there call always lands on the person who is actually working. The office is not on the roof. You are not on the roof. Marcus is. So when the question comes in, the only way you have to answer it is to interrupt the one guy generating revenue and make him prove he is where he is supposed to be.

On a two- or three-tech shop you feel this most, because you are usually one of the techs. You are elbow-deep in a condenser and the phone buzzes with a customer who wants to know if the crew showed up two towns over. You cannot see it, so you call, and now two jobs are interrupted instead of one. The habit that got you here, phone calls and radio-style check-ins, worked when it was just you in one truck. It quietly broke the day you put a second truck on the road, because a phone call only answers one location at a time and you now have more than one.

This is the same wall a group text hits when the company grows, covered in how one lost text turns into a two thousand dollar callback. A live phone call is a fine tool for a conversation and a terrible tool for a record. The customer’s question is not really “is Marcus a good guy.” It is “can you show me he was here.” That is a record question, and you are answering it by starting a phone tree.

What the interruption actually costs

Put a number on it, because it is bigger than it looks. Say the did-anyone-go-out call comes in twice a day across your shop. Each one costs about fifteen minutes: the office chasing the tech, the tech stopping and answering, the callback to the customer, and the few minutes it takes the tech to find his place again on the job. Call it fifteen minutes of real disruption per call.

Two a day, five days a week, is ten interruptions and about two and a half hours gone. Most of that time is bled off a billable tech mid-job, which is the most expensive time you own. At a loaded shop rate, that is well over a hundred dollars a week in pure interruption, and that is before you count the tune-up Marcus rushed to get back on schedule, or the second job that stalled because you had to step off it to make the call. None of it shows up on an invoice. It just quietly eats the margin on a service you already sell thin, covered more in tracking maintenance agreements so PM visits happen.

The frustrating part is that the answer already exists. Marcus knows he is there. He just has no low-effort way to make that fact visible to you and the customer without stopping work to say it out loud.

The low-drama habits that answer it

You do not fix this by texting your techs “you there yet” all day. That is just the interruption pointed the other direction. You fix it by making arrival leave a mark on its own, so the answer is already sitting there when the customer calls. Three small habits do the whole job.

An arrival check-in. The tech taps once when he pulls up, before he grabs the gauges. Not a phone call, not a sentence he has to compose. One tap that stamps the time on the job.

An arrival photo. The tech shoots the unit or the front of the equipment when he gets there. This is a habit worth building anyway, and it is the same muscle as getting every tech to shoot the nameplate on every call. The photo carries its own timestamp and lands on the job, so it doubles as proof of arrival and the start of the service record.

A visible timestamp on the job itself. The key word is on the job. A photo in the tech’s camera roll proves nothing until someone digs it out and remembers which customer it belongs to. The arrival mark has to live on that specific work order so anyone in the office can pull it up by address, not scroll a wall of images hoping to find it.

Notice that none of these ask the tech to stop and report. He is not narrating his day to the office. He arrives, taps, shoots the unit, and starts working, and the record builds itself as a byproduct of the job he was already doing.

When the 2pm call comes now

Run it back with those habits in place. The customer calls at 2pm: nobody came. You do not call Marcus. You open the job for that address and you see it plainly: arrived 12:41pm, one photo of the condenser stamped the same minute. You read the customer the time and, if they want it, you send the arrival photo of their own unit. The call is over in a minute, Marcus never knew it happened, and the tune-up finished on schedule.

Better still, half of these calls stop coming at all. A customer who gets a note when the tech arrives, or who knows the shop can produce it, learns fast that the crew shows up. The ones who still call are usually the ones setting up a disputed-callback argument later, and now you have the timestamp that ends it before it starts, the same way before/after photos end disputed callbacks.

This is exactly what a Crewmigo thread is built to hold. Each tune-up is its own job thread with the address at the top, so an arrival tap and a photo of the unit land on that job and stay there, findable by anyone in the office without calling anyone off a roof. The thread shows the work, not a dot following your tech around a map. We are new, so put one route on it next week: have the crew tap in and shoot the unit on every stop, and the next time a customer says nobody came, answer them in one tap while your tech keeps working.