Update Them Before the Window Closes

A promised window is a contract, even when it is only two hours long. When the truck is late and nobody says a word, the homeowner does not wait politely. They call the next company on the list and they tell the neighbor what happened.

You cannot remove every delay. Traffic on I-275, a parts stop, or a job that ran long will still happen. What you can remove is the silent wait. A short update before the window closes keeps the job, the afternoon route, and the referral.

Silence costs more than a late arrival

Most owners treat lateness as a field problem. The real leak is the gap between the promised time and the first honest message.

A late truck that texts at 9:40 for a 8 to 10 window still feels professional. A truck that rolls up at 10:20 with no notice feels careless. Same delay. Different story. The second version is what shows up in one-star reviews and quiet cancellations.

The customer already took time off, crated the dog, and cleared the garage. When the window closes with no word, they assume you forgot them. That is when they start shopping again.

What the homeowner is actually waiting for

They are not waiting for a perfect schedule. They are waiting for a decision they can plan around.

They want three facts, in plain words:

• You still have the job on the board.
• A new arrival window they can trust.
• What they should do in the meantime.

If you cannot give a new window yet, say when you will know. “We will text by 11:15 with a firm time” is better than “running behind.” Vague updates create more calls than no update at all.

A simple rule your crew can keep

Do not wait until you are already late. Set a hard internal trigger: if the tech will miss the window by more than 15 minutes, the customer hears from you before the window ends.

Use this checklist on every booked stop:

1. Confirm the window the night before, with a start and end time.
2. Send an on-the-way note when the truck leaves the prior stop.
3. If the prior job runs long, send the delay text before the next window closes.
4. Give a new two-hour window, or a callback time if you still do not know.
5. Offer a reschedule option in the same message so they do not have to hunt for a number.
6. Log the update on the job so the office is not guessing later.

Six steps is enough. If a step lives only in someone’s head, it will fail on the first stacked Tuesday.

How this played out for a Tampa HVAC crew

A two-truck AC company in Brandon booked tune-ups in 8 to 10 and 10 to 12 windows all summer. July heat made every first stop run long. The second homeowner of the morning sat in a warm house and watched the clock.

By 10:05 many of those customers had already called a bigger shop that promised “a tech is nearby.” Some canceled while the original truck was still on the previous roof. The owner saw no-shows and angry voicemails. The techs saw a calendar that no longer matched the street.

They added one rule and one text template. If the first job was not wrapping by 9:30, the office sent the 10 to 12 customer a new window of 11:30 to 1:30, plus a same-day swap if that did not work. The tech did not have to write the message from the attic.

No-shows on second stops dropped within two weeks. Review comments started mentioning the texts. The trucks were still late some mornings. The difference was that the customer was in on the plan.

Write the message once, then reuse it

Do not ask a tech on a hot roof to invent customer service copy. Give the office two short templates and stick to them.

When you know the new time: “This is Bay Line HVAC. We are still coming today, but the 8 to 10 window will not hold. We can be there between 11:30 and 1:30. Reply YES to keep it or call us if you need a different day.”

When you do not know yet: “This is Bay Line HVAC. The stop before yours is running long. We will text you a firm window by 11:15. If that does not work, we can move you to tomorrow morning.”

Name the company. Name the old window. Name the next fact. Leave one easy reply. That is the whole message.

Decide who sends it before the day starts

The update fails when everyone assumes someone else sent it. Pick one owner for the morning board.

On most small crews, the office should send the delay text. The tech flags the delay with one tap or one short note. The office writes the customer message and updates the calendar. If you have no office person that day, the lead tech sends the same template. What you cannot do is leave it optional.

Put the rule on the dispatch board where both sides can see it. “Window closes in 20 minutes and we are not rolling? Customer gets a text.” No debate on the job.

Measure the habit, not the traffic

You will still hit I-4 backups. That is not the scoreboard. Track three numbers for two weeks:

• How many jobs missed the original window.
• How many of those customers got an update before the window closed.
• How many of those jobs still finished the same day.

If missed windows stay high but same-day finishes rise, the habit is working. If customers still cancel after an update, the new window is too loose or the message is still vague. Tighten the promise. Do not add a longer apology.

A focused system makes the rule automatic

The weak point is not the wording. It is remembering to send it while three other fires are going. A shared job board, a booking flow that stores the window, and a one-tap delay note give the office something to act on. The website and the confirmation text should show the same window the dispatch board uses. When those pieces match, the customer hears one story and the crew stops guessing.

You do not need a full software overhaul to stop silent waits. You need one visible window, one owner for the update, and a message that goes out before the clock runs out. That small system protects today’s job and the next one that customer would have sent your way.