Good field service customer communication means telling customers what will happen before it happens: a confirmation when they book, a reminder before the visit, a heads-up when the tech is on the way, an immediate notice if you'll be late, and a clear summary when the work is done. Most complaints come from uncertainty, so the goal is to make sure the customer is never wondering.
A homeowner who waits in for a four-hour window and hears nothing is anxious by hour two and annoyed by hour three. If the tech arrives at the end of the window and does excellent work, the review still mentions the wait. Meanwhile, the same homeowner who got a call at 10:15 saying "Mike's running 30 minutes behind, he'll be there by 11:45" usually leaves a good review even though the visit was later.
That's the mechanism behind this whole guide. Customers can tolerate delays. They can't tolerate not knowing.
The eight touchpoints
Every job has the same moments where the customer either knows what's happening or doesn't.
| # | Touchpoint | When | Purpose |
|---|---|---|---|
| 1 | Booking confirmation | Right after scheduling | Confirm date, window, address, what to expect |
| 2 | Reminder | Day before | Reduce no-shows, confirm access |
| 3 | On the way | When the tech leaves the previous job | Set a specific arrival time |
| 4 | Delay notice | As soon as you know | Reset expectations before they're missed |
| 5 | Arrival | At the door | Introduce, explain the plan |
| 6 | Options and approval | Before work begins | No surprises on price or scope |
| 7 | Completion summary | At the end of the visit | What was done, what's next |
| 8 | Follow-up | A few days later | Check satisfaction, ask for a review, next service |
You don't need software for any of these. A phone call or a text from the tech's or office's phone works. What matters is that each one happens every time, and that somebody owns it.
What to say at each touchpoint
Keep messages short and specific. The customer should be able to read each one in a few seconds.
1. Booking confirmation
"You're booked for Tuesday, March 10, between 8 and 10 a.m. at 214 Elm St. Our technician will call when he's on the way. Reply or call [number] if anything changes."
Include the window, the address, and what to do if plans change. If there's anything the customer needs to do (clear access to the unit, keep pets inside) say so here.
2. Day-before reminder
"Reminder: your appointment is tomorrow between 8 and 10 a.m. Please make sure someone 18+ is home. Reply C to confirm or R to reschedule."
The reminder's real job is to catch cancellations while there's still time to fill the slot. A no-show discovered at the door is a wasted truck roll. One discovered the day before is a slot you can give to someone else. See no-show rate.
3. On the way
"Hi, this is Mike from [Company]. I'm leaving my last job now and should be there around 9:15."
This is the most valuable touchpoint, because it replaces a window with a time. Have techs send it when they leave the previous job, not when they're five minutes out.
4. Delay notice
"Mike is running about 40 minutes behind on an earlier job. New arrival time is around 10:20. Does that still work, or would you like to reschedule?"
The rule: send a delay notice as soon as the projected arrival falls outside the promised window, not when the window has already passed. Offer a choice. Most people will wait if asked. Few will forgive being left to find out.
5 and 6. Arrival and options
At the door, the tech introduces themselves, confirms what the customer reported, and explains what they'll check. Before any work beyond the diagnosis, the customer hears the options and price. This is where trust gets built or lost. The quoting and estimates guide covers presenting options.
7. Completion summary
Before leaving, the tech walks the customer through what was found, what was done and anything that needs attention later. A written summary with photos is better than a verbal one, because the customer can share it with whoever wasn't home. It also becomes part of the service history.
8. Follow-up
A short check a few days later: "Is everything working well?" If yes, ask for a review. If no, you've found a problem before it became a bad review or a callback. This is also the natural time to mention maintenance agreements.
The arithmetic of "where's my tech?" calls
Silence doesn't just cost goodwill. It costs office time. Every customer who doesn't know when the tech is coming eventually calls to ask.
Daily cost of status calls = calls per day × minutes per call × office cost per minute
The percentages are illustrative. Count your own for a week: every inbound call that's really "when are you coming?" Most offices are surprised. And each of those calls interrupts a dispatcher who should be running the board.
Arrival windows: make them narrow and true
The arrival window is the biggest communication decision you make, and it's made at booking. A wide window is a message: "We don't know when we'll get there."
Windows are wide for a reason. If the scheduler doesn't know the drive between jobs, they pad the window to cover it. We explain the mechanism in why arrival windows are so long. The fix isn't to promise a narrower window and hope. It's to know the drive at the moment you promise. That's what CrewLink does: it builds live travel time into availability, so a promised time already accounts for getting there from the previous job. The shrink your arrival window article covers other ways to tighten windows honestly.
Two rules for windows:
- Never promise a window you can't usually hit. Track your on-time arrival rate against the window, not against the start of it.
- A narrow window you miss is worse than a wider one you hit. Narrow the window only as fast as your on-time rate allows.
Who owns each message
Communication fails when everyone assumes someone else sent it. Assign each touchpoint:
| Touchpoint | Usual owner |
|---|---|
| Confirmation, reminder | Office / CSR |
| On the way, arrival, options, summary | Technician |
| Delay notice | Dispatcher (they see it first) |
| Follow-up | Office |
The delay notice is the one most often dropped. The dispatcher sees the problem, assumes the tech will call, and the tech assumes the office will. Make it the dispatcher's job explicitly.
Consent, channels and the rules
Text messages are fast and most customers prefer them for status updates. But automated or marketing texts and calls are regulated, and the rules on consent and opt-out are specific. Ask customers at booking how they want to be contacted, record it, and have an attorney check your texting and calling practices before you automate anything. Keep status messages separate from marketing.
Commercial customers
Commercial clients need the same touchpoints plus a few more: a named contact at your company, check-in with the site contact on arrival, and a written service report that their facilities team can file. If they're under an SLA, response and resolution times are part of the contract. See the service level agreements guide and commercial vs residential field service.
Measure it
Track a few numbers monthly:
- On-time arrival rate against the promised window
- Status calls per 100 jobs
- No-show rate and how many were caught by the reminder
- Customer satisfaction score or net promoter score from follow-ups
See the field service management guide for how communication fits with the rest of the system.
What to take away
- Customers tolerate delays. They don't tolerate not knowing. Most complaints are about uncertainty.
- Cover eight touchpoints on every job, and give each one a named owner.
- The on-the-way message replaces a window with a time. The delay notice goes out as soon as the projected arrival leaves the window.
- Count your "where's my tech?" calls for a week. They're a direct cost of silence.
- Narrow arrival windows only as fast as your on-time rate allows. Knowing the drive at booking is what makes narrow windows honest.
Common questions
How should field service companies communicate with customers?
Plan for eight touchpoints on every job: booking confirmation, day-before reminder, on-the-way notice, delay notice when needed, arrival introduction, options and approval, completion summary and follow-up. Keep each message short and specific, and assign an owner to each one.
When should a technician tell a customer they're running late?
As soon as the projected arrival falls outside the promised window, not after the window has passed. Give a new estimated time and offer the option to reschedule. Customers who are told early are much more forgiving than those who find out by waiting.
How long should an arrival window be?
As short as you can reliably hit. Measure your on-time arrival rate against your current window, and narrow it only when you're hitting it consistently. Windows are usually wide because the drive between jobs isn't known when the time is promised.
How do I reduce "where is my technician" calls?
Send an on-the-way message with a specific time when the tech leaves the previous job, and a delay notice as soon as you know about a delay. Count status calls for a week before and after to see the effect.
Is it okay to text customers about appointments?
Most customers prefer texts for appointment updates. Ask for and record each customer's contact preference and consent at booking, keep status messages separate from marketing, and have an attorney review your practices before automating texts or calls.