Update Customers Before They Chase You

A homeowner in Riverview took the morning off for an 8 to 10 window. At 10:20 nobody has called. She is not angry yet. She is shopping. The next company that answers gets the job you already scheduled.

Late arrivals happen. Storms, a longer first stop, a part that was not on the truck. What costs you the customer is the silence. A short, early update keeps the slot, the review, and the rest of your day from turning into a pile of "where are you" calls.

Silence turns a delay into a cancellation

Most service owners treat a slipped window as an operations problem. The customer treats it as a respect problem. They cleared a room, waited with a dog, or sat in a hot house. No message means they assume you forgot them.

That assumption is expensive. They call your office. They post in a neighborhood group. They tap the next HVAC or plumbing ad. You still have the original job on the board, plus a frustrated person, plus a hole in the afternoon if they cancel while you are driving.

The fix is not a perfect schedule. The fix is a rule: if the window will miss by more than 20 minutes, the customer hears from you before they start looking at the clock.

What a good update actually says

A useful message is short and specific. "Running behind" is not enough. It leaves them guessing and still on the phone.

Give them four facts in one text or call:

• You still have their job today, or you do not.
• The new arrival window, in real clock times.
• Why it moved, in one plain sentence.
• What they can do if the new time does not work.

Example: "This is Gulf Breeze Cooling. We are still coming to 412 Oak today. The first stop ran long, so the new window is 1:30 to 3:00. Reply 1 to keep it or 2 and we will offer the next open morning."

That message takes 30 seconds to send. It answers the question they were about to call and ask.

Who is allowed to send it

Delays die in the gap between the truck and the office. The tech knows the first job is not wrapping. The office knows the next customer is waiting. Nobody is assigned to tell that customer, so nobody does.

Pick one owner for the update. On a small Tampa Bay crew, that is usually the office or the owner-operator, not the tech who is still on a roof. The field person flags the slip. The office sends the message within 10 minutes.

Write the handoff in one line the crew can follow:

1. Tech texts the office as soon as the current job will blow the next window.
2. Office sends the customer the four-fact update.
3. Office marks the new window on the shared schedule.
4. If the customer declines, the slot is offered to the next ready job the same day.

If the same person drives and answers the phone, the rule still works. The trigger is the clock, not a free moment later.

A simple delay playbook you can run this week

You do not need new software to start. You need a written playbook and one place the status lives.

1. Define "late." Twenty minutes past the published window is a clean line. Earlier is better if you already know.
2. Save two text templates: keep-the-job-today, and move-to-another-day.
3. Put the customer number on the job card, not buried in a thread.
4. Send the update before you leave the current driveway when you can.
5. Log the new window where the next person will look, not only in your head.
6. If they cancel, fill the slot the same morning. Do not let a quiet gap sit on the board.

Test it on the next three delayed jobs. If a customer still calls to ask where you are, the message was late or too vague. Tighten the trigger, not the apology.

How this played out for a Tampa HVAC crew

A two-truck cooling company in Hillsborough County ran 8 to 10 and 12 to 2 windows through a hot September week. Afternoon storms and a long capacitor job pushed the second window most days. The office found out when the homeowner called, often after they had already texted a competitor.

They added one rule. If a job would miss by 20 minutes, the tech flagged it before leaving the current house. The office sent the four-fact text. In the first two weeks they moved four jobs to the next morning and kept nine that would have been silent cancellations.

The phone got quieter after 10 a.m. The reviews stopped mentioning "never showed." Same crew, same weather, same traffic. The only change was that the customer heard the new plan first.

Check your last five delayed jobs

Pull last week's schedule and mark every window that slipped. Then score each one:

• Did the customer hear from you before they called you?
• Did the message include a new clock time, not just "soon"?
• Could they accept or move the job in one reply?
• Did the board show the new time so the next tech was not surprised?
• If they cancelled, did you fill that slot the same day?

Three or more "no" answers means the delay is not the main leak. The update process is. Fix that before you buy another dispatch tool or rewrite the website copy about "on-time arrival."

The website promise has to match the field

Customers remember what your site told them. If the service page says a two-hour window and the booking confirmation repeats it, that is the promise. A late truck with no text breaks the promise even when the work is excellent.

Keep the public window honest. Do not advertise 8 to 10 if your first stop almost always runs long. Pair that honest window with a booking flow that captures a mobile number you will actually use when plans change.

A focused system does the rest. The site sets one clear arrival window. The booking record holds the number and the address. A simple internal card tells the office when to send the update. That is how a small crew stays reliable without adding a dispatcher for every truck.

Start with the 20-minute rule on the next late job. Send the four facts. Put the new time on the board. You will feel the phone get lighter the same week, and you will keep work that used to walk to the next company on the list.