The Update a Customer Wants That You Forget to Give
Why this matters
Every job has a handful of moments where the customer is quietly wondering what is happening, and a one-line update would settle it. Shops skip these not out of laziness but because none of them feels urgent in the moment. Miss enough of them and a technically perfect job still feels like being kept in the dark. This is the map of the updates customers actually want, when they want them, and the one line that closes each gap.
The principle: match the update to the anxiety
A good update is not a status dump. It answers the specific question the customer has right now. At each point below, they are anxious about one particular thing. Say the line that resolves that thing and you can move on. This is a field-card of the moments; for why the silence between them does real damage, see related: The Silence That Turns a Happy Customer Into an Angry One.
The update map, moment by moment
| Moment | What they're anxious about | The one line that settles it |
|---|---|---|
| Booking confirmed | "Did it actually go through?" | "You're on the schedule for [day], [window]. We'll text before we head over." |
| Day before | "Is this still happening?" | "Confirming we're still on for tomorrow, [window]. Reply if anything changed." |
| On the way | "When exactly?" | "On our way, about [X] minutes out." |
| Arrived and starting | "What's the plan?" | "Here now. Taking a look and I'll walk you through what I find." |
| Mid-job, if it runs long | "Is something wrong?" | "Going as expected, just takes a bit. On track to finish by [time]." |
| Anything changes | "Why the holdup?" | "Small change, [reason]. Here's what it means for time and cost." |
| Job done | "What did they actually do?" | "All wrapped up. Here's what we did and what to watch for." |
| Follow-up, a day or two later | "Will it hold?" | "Checking everything's still running right. Any concerns at all?" |
The three most-skipped, most-missed updates
If you fix only three gaps, fix these:
- The "on our way" message. The single highest-value update in field service. It ends the worst part of any service experience, the open-ended wait by the window. Customers who get it forgive almost any reasonable arrival time; customers who don't feel stood up at minute one.
- The "running long but fine" mid-job note. Silence during a job that overruns is read as "something broke." One line that it is normal and still on track prevents the anxious hover and the "everything okay in there?" interruptions.
- The completion summary. Driving off without telling the customer what you did wastes the value of the work. They cannot appreciate, remember, or repeat what they never heard. A thirty-second recap is what turns a repair into a reason to call you again.
Updates you can send with no news
The most common excuse for silence is "I had nothing to tell them." You almost never need news to send an update. "Nothing new, still on schedule" is a complete and welcome message. Reassurance is information. A customer would rather hear "no change" than hear nothing and wonder whether you forgot them.
Make the cadence automatic, not heroic
An update that depends on a tech remembering in a busy day will get skipped. Build the moments into the workflow so they fire on their own: an automated booking confirmation and day-before reminder, a one-tap "on my way," a job-close prompt to send the summary, and a scheduled follow-up. The shops that feel attentive are rarely the ones with better memories. They are the ones who made the routine updates happen without anyone having to remember.
References
- Trade-standard field-service communication practice
- See related: The Silence That Turns a Happy Customer Into an Angry One
- See related: Communicating ETA Changes Without Annoying the Customer
- SBA, customer experience and retention guidance