A field service visit starts before the technician reaches the customer’s location.
I’ve seen appointments become unnecessarily difficult because one small piece of information never reached the customer.
Nobody knew exactly when someone needed to be available.
The equipment was behind a locked door.
The technician arrived at the wrong entrance.
The person who understood the problem wasn’t there.
None of these are complicated technical failures.
They’re communication failures.
And they can turn a perfectly manageable service call into a wasted visit.
I Don’t Want to Overload the Customer
There’s a balance.
The customer doesn’t need every internal detail about dispatching, routing, technician assignments, or service operations.
They need information that helps the visit happen successfully.
I focus on practical questions:
When should I expect service?
What needs to be ready?
Does someone need to be present?
Which equipment is being serviced?
Has anything changed?
Everything else is secondary.
The Arrival Window Needs to Mean Something
Customers plan their day around service appointments.
That’s why I take timing seriously.
A wide service window may be operationally necessary, but it should still give the customer enough information to prepare.
If circumstances change significantly, communication becomes even more important.
Silence creates uncertainty.
Uncertainty creates unnecessary calls.
I Avoid Creating False Precision
At the same time, I don’t want to promise an exact arrival time when field conditions don’t support one.
Technicians work in the real world.
The previous repair can take longer than expected.
Traffic can change.
An urgent situation can affect the route.
I’d rather communicate a realistic expectation than give the customer a precise time that becomes inaccurate twenty minutes later.
Site Entry Can Be a Bigger Problem Than the Repair
This is especially important for commercial service.
The technician may arrive at the correct address and still be unable to reach the equipment.
Maybe there is:
- A security desk
- A locked service area
- A loading entrance
- A restricted floor
- A gate
- A required site contact
- A check-in procedure
These details can be incredibly valuable before dispatch.
Five minutes of preparation can prevent thirty minutes of searching and phone calls.
I Make Sure Someone Can Identify the Equipment
“It’s the unit in the back” may make perfect sense to the customer.
It may mean nothing to the technician.
Locations with several similar units create even more confusion.
When possible, I want enough information for the correct equipment to be identified quickly.
The technician’s time should go toward solving the problem, not conducting a scavenger hunt.
The Person Who Reported the Problem Can Be Valuable
Sometimes the equipment appears to work normally when the technician arrives.
That’s when the original observer becomes important.
What exactly happened?
When?
How often?
Was there a sound?
An error?
A shutdown?
Did the problem occur only under certain conditions?
If the person who experienced the issue won’t be present, useful details should ideally be captured beforehand.
I Tell Customers When Preparation Is Required
Some visits require more than opening the door.
The technician may need the area around the equipment to be accessible.
Operations may need to be paused.
Items may need to be moved.
A responsible person may need to be present.
Whatever the requirement is, discovering it after arrival wastes time.
I Treat Schedule Changes as Customer Information
Internally moving a job is only half the work.
If the expected timing changes enough to affect the customer, the external expectation needs attention too.
This is where a connected field-service process matters.
ServicePower isn’t only about putting jobs onto technicians’ schedules.
The service experience also depends on keeping operational activity and customer expectations reasonably aligned.
I Don’t Make the Customer Decode Internal Terminology
Customers shouldn’t need to understand our internal workflow to know what’s happening.
I prefer communication like:
“The technician is expected later than originally planned.”
rather than internal status terminology that means something to the service organization but very little to the customer.
Clear beats technical.
I Explain What the First Visit Is Supposed to Accomplish
Not every service appointment guarantees immediate completion.
Sometimes the first visit involves diagnosis.
Sometimes the work is already well understood.
Sometimes additional components may be required after inspection.
I don’t want the customer assuming every appointment automatically means:
“Everything will definitely be repaired today.”
Setting realistic expectations early makes later communication easier.
I Avoid Promising Outcomes the Technician Hasn’t Confirmed
This is another common trap.
Before diagnosis, I don’t want to tell a customer:
“It’ll be a quick repair.”
Maybe it will.
Maybe the visible symptom has a completely different underlying cause.
The field technician should have room to inspect the actual equipment before conclusions become promises.
Customer Updates Should Answer “What Do I Do Now?”
That’s my favorite test for service communication.
After reading or hearing an update, does the customer know what they need to do?
For example:
Technician scheduled: Be available during the expected period.
Timing changed: Adjust availability accordingly.
Site preparation required: Prepare the service area.
Additional visit required: Wait for confirmation of the next service step.
Useful communication leads to a clear action or expectation.
I Think About the Customer’s Entire Day
For us, the appointment may be one job among dozens.
For the customer, it may be the reason someone has to remain at a location for several hours.
That perspective changes how I think about updates.
A small scheduling change internally can create a much bigger inconvenience externally.
I can’t eliminate every disruption.
I can avoid making it unnecessarily confusing.
My Pre-Arrival Communication Checklist
Before a field visit, I want the customer to understand:
✅ Expected service timing.
✅ Which equipment or issue is being addressed.
✅ Whether someone needs to be present.
✅ Any site-entry requirements.
✅ Any preparation needed around the equipment.
✅ Whether the visit is expected to involve diagnosis, repair, or follow-up work.
✅ Any meaningful change to the original plan.
What I Try Not to Do
❌ Give precise arrival promises I can’t support.
❌ Send internal terminology without context.
❌ Assume the technician will figure out site entry after arrival.
❌ Forget that multiple similar units may exist at one location.
❌ Make repair promises before diagnosis.
❌ Change the operational schedule without considering the customer.
❌ Send long updates that don’t tell the customer what actually matters.
Good Field Service Is Partly an Information Problem
The technician can be highly skilled.
The required tools can be ready.
The schedule can be carefully planned.
But if the customer isn’t prepared for the visit, all that preparation can still fall apart at the front door.
That’s why I see customer communication as part of field operations rather than something that happens around them.
A ServicePower workflow may help coordinate the operational side of field service, but the real-world appointment still involves two sides:
the team sending the technician
and
the customer receiving the technician.
When both sides know what to expect, the technician can spend less time resolving avoidable confusion and more time doing the work they actually came to do.