Your tech rolls up to a commercial job at 8 sharp. The gate's locked, there's a keypad nobody gave a code for, and the loading dock around back needs a badge to get past the guard. So the tech calls the office. The office calls the customer. The customer's on a plant floor and doesn't pick up. Twenty minutes gone before a single bolt gets turned, and that's a good day.
On a bad day it's a plant that requires a safety orientation nobody mentioned, or a property manager who has to buzz you in and left at noon. The work itself might be an hour. Getting to the work took two.
None of this is a scheduling problem or a crew problem. It's an information problem, and the information almost always exists. The customer knows the gate code. They just never got asked for it in a way that made answering easy. Fix that one handoff and you claw back real hours every week.
Ask five things, and stop there
The intake that works is short. Every extra question is one more reason the customer sets the text aside for later, and later is the morning your truck's stuck at the gate. Ask only what actually changes whether the tech gets in and gets started.
- The gate or door code, or the name of whoever unlocks it and when they show up.
- The on-site contact, a real person with a cell phone who'll be there, not the number that rings the front desk.
- After-hours access, if the job could run past closing or you booked it for early morning.
- Where to put the truck, parking, the right dock, or where to stage so you're not blocking a bay.
- Any check-in you can't skip, a guard badge, a sign-in sheet, or a safety orientation the plant requires before anyone touches equipment.
Skip anything you already have on file. If it's a customer you've served for years, you might only need to confirm the code hasn't changed. The goal is the shortest possible ask, because a short ask gets answered before lunch.
Make the answer one tap, not a chore
Text beats email for this, and both beat a portal login. Your customer is a facilities manager with a hundred things going; they'll tap a reply from the truck cab or the plant floor, but they will not dig up a password to fill out a form.
Where you can, give them buttons instead of a blank box. A quick automated text can offer a few choices and let one tap do the work.
- For access: Gate code? with a spot to type it, or a tap-back option like I'll meet the tech.
- For the contact: let them reply with a name and number, or tap Same as booking contact if it hasn't changed.
- For parking: a couple of presets like Front lot or Rear dock covers most sites.
Keep the whole thing to one message with a clear reason attached, something like: so our tech gets right to work Thursday, a few quick access questions. People answer fast when they can see it saves them a phone call later.
Send it the minute the job is booked
Timing is the quiet part that makes this work. Fire the intake text automatically the moment a job hits the schedule, while the customer's still thinking about it. Wait until the day before and you're competing with everything else on their plate.
Give yourself a buffer. If the reply doesn't come within a day, send one polite nudge, then let it flag for a human. Two automated touches is plenty; a third starts to feel like nagging, and you've got a phone for the ones that go quiet.
Here's where to be honest about what automation does and doesn't do. It's great at asking the same five questions every time, on time, without anyone having to remember. It's bad at reading a rambled voicemail or deciding whether the usual spot is good enough. So let the software collect the clean answers and hand the messy ones straight to a person.
Flag the blanks before you build the route
This is the part that saves the morning. A booked job with no access info isn't ready to route, it's a bounce waiting to happen, and you want to know which jobs those are before dispatch plans the day.
Set it up so every job carries a simple status: access confirmed, or access missing. The evening before, your dispatcher looks at one list and sees exactly which sites still have a blank where the gate code should be. Those get a phone call before the route locks, not after the truck's already parked at a chain-link fence on the far side of the Loop.
- Every new commercial job starts marked access missing.
- A complete reply flips it to confirmed on its own.
- Anything still missing by end of day shows up on the dispatcher's check-before-you-route list.
- Those few get a quick human call, and the rest of the board's already done.
Put the answers where the tech will see them
Collecting the gate code does no good if it's buried in an email thread the tech never opens. The answers have to land on the work order itself, in the same field the tech checks on the way out the door.
Whatever you dispatch with, the access details belong right on the job: code, contact name and cell, dock and parking, and any check-in note in plain sight. If your tech can read gate code 4417, ask for Marcus at the dock, sign in at the guard shack before leaving the shop, the trip to the site is boring, which is exactly what you want a trip to a site to be.
One more habit worth building: when a tech learns something new on site, a code that changed or a contact who moved on, capture it back onto the account. Next time, the intake starts from what's true.
Worth doing this week
You don't need a big system to start. Pick your most common commercial job type and set up the handoff for that one first.
- Write your five questions as one short text. Read it out loud; if it takes more than fifteen seconds to answer, cut something.
- Turn on an automatic send the moment a commercial job is booked, with a single nudge a day later if it's quiet.
- Add an access confirmed or access missing flag to your jobs and make checking it the last step before you build tomorrow's route.
- Make sure the answers print on the work order where the tech actually looks, not just in your inbox.
- Give it two weeks, then count the gate-code phone calls your office still makes. That number is your before-and-after.
If you'd rather have someone wire the texts, the flags, and the work-order handoff together for you, that's the kind of setup we build for Houston field-service shops at AI Agency Houston. Either way the win is the same: your crew spends the morning turning wrenches, not idling at a locked gate.