Prep texts that save the first hour

The job is booked. The truck is loaded. Then the tech spends the first hour waiting on a gate code, a locked side yard, or a customer who did not know the water needed to be off. That hour is not a small inconvenience. It is a paid visit that produces no work, and it pushes every later stop later.

A short prep text the day before fixes most of that. It asks for the few details only the customer knows, and it lands them in the job file before the crew rolls. The first hour stays on the work, not on phone tag.

Where the first hour actually goes

Most wasted starts look the same. The address is right. The scope is right. The access is not. Someone has to hunt for a lockbox, move a car, or wait while the homeowner drives back from work.

On a four-stop day, one delayed start does not stay on that job. It slides the whole route. The last customer gets a late window, the office fields the calls, and a simple maintenance visit turns into overtime.

The details that cause this are rarely technical. They are ordinary things the customer already knows and the office never asked.

What only the customer can tell you

Your intake form can capture the symptom, the address, and a phone number. It often misses the things that decide whether the tech can start.

Gate, garage, or lockbox code
Where to park, and whether a permit is required
Pets that need to be put up
Which adult will be home, and a backup number
Water, power, or attic access that must be ready
HOA or building rules about hours and vendor check-in

None of these belong in a group text at 7:40 a.m. They belong on the job the night before, where dispatch and the tech can both see them.

A prep text that people actually answer

Keep it short. Customers ignore a paragraph that sounds like a form. They answer three clear questions.

Confirm the arrival window in plain language.
Ask for the one access detail that blocks this type of job.
Tell them what to have ready, in one sentence.
Give a simple way to reply, and say who will read it.

A working version sounds like this: "We are scheduled tomorrow between 9 and 11 for the AC tune-up at 1840 Bay Court. Reply with the gate code and whether a dog needs to be put up. Please clear a path to the air handler. Text this number if the window no longer works."

That message does three jobs. It confirms the visit, collects the blocker, and gives the customer a clean way to reschedule before the truck is already on the road.

A Tampa Bay HVAC morning

Picture a two-truck HVAC company working St. Petersburg and Clearwater. Summer tune-ups are booked in two-hour windows. The office used to call each home the afternoon before. Half the calls went to voicemail. The tech arrived, found a locked courtyard, and sat in the truck while the office tried the customer again.

They switched to one text at 4 p.m. the day before, tied to the job. The reply went onto the job record, not into someone's personal phone. Gate codes, pet notes, and "we will be at work, use the side door" started showing up before the route was locked.

The change was not dramatic on paper. It was obvious on the route. Fewer 20-minute waits. Fewer "where are you?" calls. The second stop of the day started closer to the time the customer was promised.

What to ask, and what to leave out

A prep text fails when it tries to redo the whole estimate. Ask only for what changes the start of this visit.

Ask for access, parking, and who will be there.
Name the equipment or area the tech needs to reach.
State one prep step, such as moving storage off the water heater.
Skip price talk, upsells, and review requests in this message.
Skip questions you already answered on the estimate.

If the job is a restoration dry-out or a plumbing leak, the prep step changes. For a leak, you might ask them to clear under the sink and keep the water valve reachable. For a cleaning crew, you might ask which door to use and where to park the van. Same pattern, different one-line ask.

When to send it

Send the text after the route is real, not while the day is still a guess. For most local crews, late afternoon the day before is the right moment. The customer can still reply. The office can still move a stop if the answer is "we will not be home."

Same-day emergency work is different. Send the prep text as soon as the slot is confirmed, even if the arrival is in two hours. A gate code still matters when the tech is 20 minutes out.

If there is no reply by the morning dispatch check, one phone call is enough. Do not send three reminders. One text, one call, then a note on the job that access was not confirmed.

Put the reply where the tech can see it

The text only helps if the answer leaves the office phone. Gate codes buried in a personal thread help one person. They do not help the tech who is covering the route, or the owner who gets the callback the next week.

A simple rule works. Every reply gets copied onto the job before lock-up. Access notes sit next to the address, not in a separate chat. If the customer reschedules, the slot is released the same evening, not discovered at the curb.

That is the whole system. One message. One place for the answer. One person who checks unreplied jobs before the trucks leave.

What this gives back

Owners often treat arrival delays as a customer problem. Most of the time they are an intake problem. The customer was willing to share the code. Nobody asked at the moment they were likely to answer.

A prep text will not fix a bad route or a missing part. It will stop the quiet leak at the start of the day, the one that makes a full schedule feel short. Pair it with a job record the field can open, and the first hour goes back to the work you already sold.

If those notes still live in personal texts, the next useful step is a simple booking and job flow that sends the prep message and stores the reply on the visit. The crew should not have to ask for the gate code twice.