Why Your Technicians Still Call You (and How to Fix the Field Service Bottleneck)
By Mike Bandar, Co-founder of Waybook.
Your technicians call you because the answer lives in your head and nowhere they can reach from a truck. That is the whole problem, and it has a short fix: tally a week of calls, write down the answers that repeat, give each one an owner who is not you, and put them where a technician can open them on a phone at the customer's door. Below is how to run that tally, what belongs in a truck-side playbook, how to hand decisions to lead technicians without losing the standard, and what two dispersed teams got back when they did it. It applies whether you own the business or run its operations.
Last updated: September 2026
Start your free trial at Waybook
SOP software for growing teams
A week of calls from the trucks
Before writing anything, count. For one week, log every call or message from a technician mid-job: what they asked, what you answered, how long it took. Most owners and operations managers who do this find the same thing: eight or nine questions account for most of the calls, and almost none of them needed a decision. They needed information nobody had written down. A typical week looks like this.
The call | What it actually needs | Who should own the answer |
|---|---|---|
"Customer wants an add-on, what do I charge?" | A price list and a rule for anything off it | Owner sets, lead technician maintains |
"The part isn't on the truck." | The truck stock list and the supplier run procedure | Lead technician |
"Nobody's home." | A wait time, a door tag, a rebook step | Dispatcher |
"This turned into a bigger job." | The change order form and who approves it | Owner or operations manager |
"How do I close this out?" | Photos, sign-off, payment, notes in the app, in that order | Lead technician |
"Is this a warranty call or do we bill it?" | The warranty rules and the escalation line | Owner decides the rule, then it's written |
"Can I come back tomorrow to finish?" | What a lead technician can approve without calling in | Lead technician, within written limits |
"Do I need a permit for this?" | The permit list by job type for your area | Operations manager |
Only two rows in that table need the owner's judgment, and only the first time. Everything else is a written answer waiting to exist.
How do I stop being the bottleneck in a field service business?
Take the tally and write the answers, one procedure per call, in the words you'd use standing next to a new technician. Each one under five minutes to read on a phone. Photos of the right and wrong way where it's hands-on, a short video shot on the job where it's a sequence. Give each procedure an owner from the table above, and from that day answer every repeat call with the link, not the answer. The calls fall away in a few weeks, because technicians learn where the answer lives and that it opens faster than you pick up.
One rule matters more in field service than anywhere else: if it doesn't open on a phone in a truck with one bar of signal, it doesn't exist. A binder in the office or a PDF in a shared drive is not a procedure. It's a place where a procedure used to be.
What goes in the truck-side playbook
Truck stock and morning check. What every truck carries, how it's counted, what to do when it isn't there.
The first two minutes at the door. How we introduce ourselves, what we ask before we touch anything, what we never promise on the doorstep.
Job close-out. Photos before and after, the customer sign-off, payment or invoice step, notes in the app. The order matters and it's the same every time.
When to call and when not to. The short list of things that always get a call, and the written answer for everything else.
Week one for a new technician. Who they ride with, which procedures they read by Friday, and what they can do alone by the end of it. Flatwater Homes gives new hires 30 days of required reading and turns a learning path on before they start; the ride-along becomes a check, not the whole training.
Safety, licensing and the inspector
Field service carries a class of procedure the office-based business doesn't: the ones a licensing board, an insurer or an inspector can ask you to prove your technicians read. Lockout and tagout. PPE by task. Permits and inspection sign-offs. Incident reporting. Confined space or working at height where it applies. These go in the playbook first, and they get two things the rest don't: read confirmation, so you can show which technician acknowledged which version and when, and a short quiz on the ones where a wrong answer hurts someone. "I told them in the yard" is not a record. A dated confirmation is.
Lead technicians, limits and the second truck
The bottleneck usually breaks for good when the first lead technician gets real authority. Not a title, a written set of limits: what they can approve on site (a return trip, a discount up to a set amount, a warranty call under a threshold), what they own (truck stock, close-out quality, the new technician riding with them), and what still comes to you. Written limits make delegation safe in both directions. The lead technician knows exactly how far they can go, and you know nothing outside the line was decided without you.
Pairing does the rest. Every new technician rides with a lead for their first weeks, follows the same week-one path, and is signed off by the lead, not by you. When the third and fourth trucks come, the procedure for adding a truck already exists, because you wrote it when you added the second.
Two teams that stopped calling the office
Flatwater Homes runs a team of twenty-plus across active builds. Not a service-call business, but the same problem: people working away from the office who need the answer where they stand. About 70% of everyday questions are now answered in Waybook, 100 documents are open to the whole team, and nobody prints a handbook. Jenna Beach, Project Manager:
If you print a handbook out and put it on a shelf, people don't reference it. With Waybook they do - they'll actually go in and search it. It should be able to replace about 70% of your HR repository, because a lot of the questions you get, HR and operational, are already in there.
Container Port Group runs more than 1,000 people across 30 terminals, about as dispersed as a workforce gets. Six months after moving their processes out of three places and into one, they had standardised more than 120 procedures, cut onboarding time by 30% and turnover by 75%. Alex Frye, VP of Customer Experience, Process and Training:
.png)
We had a fragmented system when it came to documented processes and procedures. Some were in cloud services, others in physical format, and much of it was simply in people's heads. As we grew, this wasn't sustainable.
Tools that work from a truck
The test for any tool here is the one-bar-of-signal test: can a technician open the procedure at the customer's door and follow it. Under five people a shared folder passes if it's tidy. Between ten and two hundred, you need read confirmation and a mobile app, or the playbook stays in the office.
Tool | Pricing (from) | From the truck | Honest limitation |
|---|---|---|---|
Waybook | Core plan includes 20 members; current prices on the pricing page | Mobile app, photo and video steps, read confirmation and quizzes on safety procedures, role-based onboarding paths, AI SOP creator and Shots for building the playbook | Not a dispatch, scheduling or invoicing system |
Trainual | Core $249/mo for 10 seats, +$3/seat, captured in-app August 2026, not published | Mobile app, curriculum-style training paths | Price rises with seats, narrower process documentation |
Notion | Free, or Plus $10/seat/mo billed annually | Mobile app, flexible pages | No read confirmation, no proof anyone acknowledged a safety procedure |
Scribe | Free, or Pro Team $13/seat/mo, 5-seat minimum billed annually | Fast capture of on-screen steps | Built for desk work; documents processes, does not manage them |
Shared drive or group chat | Free or included | Opens on a phone | Nothing is current, nothing is confirmed, the chat scrolls away |
Competitor pricing verified August 2026 from each vendor's live pricing page. Check the vendor's page before you buy. For a fuller breakdown see our SOP software comparison and the direct comparisons at Waybook vs. Notion and Waybook vs. Trainual. For what to look for in training itself, see employee training.
Start your free trial at Waybook
Frequently asked questions
As the owner or operations manager, how do I stop being the bottleneck in a field service business?
Log a week of calls from your technicians, write a short procedure for every question that repeats, give each one an owner who isn't you, and put them where a technician can open them on a phone at the customer's door. Then answer every repeat call with the link. The calls drop within weeks once the team knows the answer opens faster than you pick up.
What should a field service company document before anything else?
The safety and compliance procedures a licensing board, insurer or inspector could ask you to prove: lockout and tagout, PPE by task, permits and inspection sign-offs, incident reporting. Then the answers to your most-repeated calls: pricing an add-on, a part not on the truck, the customer not home, change orders and job close-out.
How much authority should a lead technician have on site?
Enough to keep the job moving without a call, written down: a return trip, a discount up to a set amount, a warranty decision under a threshold, and sign-off on a new technician's first weeks. Written limits protect the lead technician and the business equally, because nothing outside the line gets decided without you.
How do we prove technicians actually read a safety procedure?
Read confirmation with a date and a version, plus a short quiz on the procedures where a wrong answer causes harm. A message in the group chat or a briefing in the yard is not a record. A dated acknowledgement per technician is what an inspector or an insurer accepts.
Which SOP tool works for technicians in the field?
One that passes the one-bar-of-signal test: opens on a phone at the door, holds photo and video steps, and confirms who read what. Under five people a tidy shared folder can work. From ten to two hundred, a dedicated tool such as Waybook earns its place on the mobile app and read confirmation alone; it sits beside your dispatch and invoicing system rather than replacing it.
To see whether this fixes the problem, take the one call you get from the trucks most often, turn it into a procedure your technicians can open on a phone, and watch whether they use it instead of dialling. Start your 7-day free trial at Waybook and try it with your own week of calls.
