Your tech pulls up at 9:15 and the gate's chained shut. No answer at the buzzer, and the number on the ticket rings out. He waits, calls dispatch, and twenty minutes later somebody finally explains that the manager who booked the job is off today and never told the front desk anyone was coming.
That's a wasted roll. On a spread-out Houston route that's an hour each way, easy, plus the slot you turned down to hold that window. Parts are still on the truck, the tech's still on the clock, and half the time the customer still wants the work, just not today.
Here's the thing: most of these were avoidable. The appointment was real when it got booked, then a shift got covered or a building went to one person's cell and nobody closed the loop. A short confirmation the day before catches most of it while there's still time to move the truck somewhere useful.
What the confirmation actually asks
This isn't the same as collecting a gate code up front. Gate codes get you through the fence. A confirmation answers a different question: is the appointment still on, and will a live human be standing there with access when the truck arrives?
So the text asks for a reply, not just an acknowledgment. Something like:
- "This is [Company] confirming your service visit tomorrow, Thursday, between 8 and 10 AM."
- "Reply YES if someone will be on site with access to the equipment."
- "Reply RESCHEDULE if the time no longer works."
Short, specific, and it puts the ball in their court. You're not asking them to remember an appointment. You're asking them to promise someone will open the door.
The reply is the signal, not the reminder
A plain reminder tells the customer something. A confirmation asks them to tell you something back, and that difference is the whole point. The reminder makes you feel covered. The reply is what actually tells you whether to send the truck.
When somebody texts back YES, you've got a small commitment on record and a warm number you can call in the morning if the tech's running behind. When they text RESCHEDULE the night before, you just saved a roll and freed a slot you can sell to the next call that comes in.
And when they say nothing at all, that silence is information too. It's the pile you work by hand.
Working the no-replies
The list of people who didn't answer is the real product here. Everybody who replied YES sorts itself out. The no-replies are where a two-hour dead trip hides, so that short list is exactly what your dispatcher should see first thing.
Keep the follow-up simple:
- Pull the no-reply list the evening before or first thing that morning.
- Call each one. A live voice sorts out most of them in under a minute.
- If you can't reach them, decide by the job. A long-standing PM account probably still holds. A first-time visit way out past the Beltway is worth a second call before you commit the drive.
- Move or reslot anything that's clearly dead so the tech's day stays full.
That's twenty minutes of phone work that can keep a couple of trucks from rolling out to locked doors. Do the math on that against a single wasted roll and it pays for itself the first week.
Timing and wording that gets a reply
Send it the afternoon before, not at 6 AM on the day. People check their phones between things in the afternoon, and if there's a problem you want to hear about it while the schedule's still soft enough to change.
A few things that help:
- Name the day and window in the text. "Tomorrow" is fine, but "Thursday between 8 and 10" is harder to misread.
- Give one clear thing to do. Reply YES. Don't bury it under three questions.
- Use the name they know. Your company name, not a random number, or they'll write it off as spam.
- Text the person who books, and think about the person who unlocks. On commercial jobs those are often two different people, and the office manager may need to warn the site you're coming.
Where the automation helps, and where it doesn't
Software's good at the boring, on-time part. It can pull tomorrow's schedule, send every confirmation at the same hour, sort the replies into yes, reschedule, or no answer, and hand your dispatcher a clean no-reply list. That's the repetitive work that quietly slips when the front desk gets slammed on a hot afternoon.
What it shouldn't do is make the judgment call. Whether to eat the drive on an unconfirmed job depends on the customer, the distance, and what else is on the board that day. That's a dispatcher's read, and it should stay one.
Be honest with customers, too. A text is a nudge, not a contract. Some people never reply and still show up, and some reply YES and then forget. The confirmation shrinks the pile of surprises. It doesn't erase it, and anyone who tells you it does is selling something.
Worth doing this week
You don't need a new system to start. You need a habit and one short message.
- Write your confirmation text today. Three lines: the day and window, reply YES for access, reply RESCHEDULE to move it.
- Pick who owns the no-reply list and when they work it, the evening before or first thing in the morning.
- Run it by hand for a week off tomorrow's schedule, even if that's copy and paste. See how many reschedules and dead trips you catch.
- Count the saved rolls at the end of the week. If it's paying off, that's when it's worth wiring it into your scheduling so it sends itself.
Do that and the truck stops rolling to locked doors on days you could've known better. If you'd rather not build it yourself, that's the kind of thing we set up for Houston shops.