Your crew rolls up to a triple-decker on a side street. Three doorbells, no names on any of them. Cars parked bumper to bumper both sides. Which unit is the job? Nobody in the truck knows.
So they call the office. The office calls the customer. Customer's at work and doesn't pick up. Now two guys are sitting at the curb, meter running, waiting on a text that might come in ten minutes or might come after lunch.
The address got you to the building. It didn't get you to the job. Which unit, where to park, is there a gate code, is there a dog, who's home to let you in, none of that made it out of the booking call. That gap costs you an hour, and sometimes the whole trip.
The address is the easy part
Booking software captures the name, the number, the street. Good. That's enough to put the job on the calendar. It's not enough to work it.
The details that decide whether the visit goes smooth live in the customer's head. Park in the driveway, not the street, the neighbor tows. Unit 2, side door, not the front. Lockbox on the rail, code's 4-1-1-2. Dog's friendly but loud. Text my wife, she's the one home during the day.
You could ask all that on the booking call. But the call's usually short, the customer's rushing, and half the time you booked it off a voicemail anyway. So it doesn't get asked. Then the crew pays for it.
Send one text the minute the job is booked
Here's the fix, and it's boring on purpose. The second a job lands on the calendar, an automatic text goes out to the customer asking for the access basics. Nobody has to remember to send it. The booking triggers it.
Automatic text just means a short message your system fires on its own when a job gets scheduled, so it happens every time whether the office is slammed or empty.
Keep it short. People answer short texts from the parking lot at work. They ignore the long ones.
"Thanks for booking us for Thursday. Quick stuff so the crew rolls right up: which unit, where should they park, any gate or lockbox code, a dog we should know about, and who'll be there to let them in? Text it back whenever."
One more move worth making: fire the same text again the day before if they never answered the first one. Folks book, forget, then the reminder catches them when the job's actually on their mind. Two nudges, then let it go.
What to actually ask for
Five things cover almost every headache. Ask for these and nothing else.
- Which unit. First floor, second, rear. On a triple-decker this is the whole ballgame.
- Where to park. Driveway, street, a specific spot. Matters more than you'd think on a packed block with a truck and a trailer.
- Gate or lockbox code. If there's a code, get it now. Nothing worse than standing at a locked gate calling a number nobody answers.
- A dog. Not because you're scared of dogs. Because the crew should know before they open a basement door.
- Who's on site. Best contact the day of, and whether they're home or leaving a key. Sometimes it's the tenant, not the person who booked.
That's it. Resist the urge to tack on ten more questions. Every extra one drops your answer rate.
Let the answers ride to the crew
Getting the reply is half of it. The other half is making sure the guy driving actually sees it. A text sitting in the office inbox does the crew no good at the curb.
- Drop the answers straight onto the job in your scheduling software, in the notes field the crew already checks.
- Or forward them to the lead tech's phone the morning of the job.
- Or both. Belt and suspenders.
However you wire it, the rule is the same: the access info lives with the job, not in a separate thread nobody opens.
Where it helps, and where it won't
This pays off hardest on multi-unit buildings, gated spots, tight city parking, and anything where the person who booked isn't the person who'll be home. City work, rentals, property managers, second homes. If you mostly do single-family houses with a driveway and the owner's always there, you'll get less out of it. Still nice to know about the dog.
Be honest about the limit. Some people won't text back. You'll still make the occasional call to confirm, and you'll still hit the odd locked gate. The goal isn't to kill every surprise. It's to knock out the eight-in-ten that a two-line text solves, so your crew eats a wasted hour a lot less often.
Don't lean on it for emergencies either. A midnight no-heat call isn't waiting on a parking question. This is for scheduled work, where there's time between the booking and the truck.
Worth doing this week
You don't need new software to start. You need one message and a habit.
- Write the five-question text. Steal the one above. Keep it under four lines.
- Pick the trigger. Every new booking gets it, automatically if your system can, by hand if it can't, yet.
- Decide where answers land, the job notes or the lead's phone, and tell the crew that's where to look.
- Run it two weeks and count the wasted trips. Compare to the two weeks before.
If you'd rather have it wired so it fires on its own and drops the answers right on the job, that's the sort of thing we set up for Massachusetts trades at Mass AI Agency. Either way, get the details before you roll.