Set Expectations Early and Keep Customers Updated

EPISODE 17 | TECH FOR TECHS
The part is delayed. That happens. The customer finding out after their third chase call is the bit you can control. Useful updates say what you know, what you are waiting for and when you will contact them again. Silence leaves plenty of room for the customer to write their own, considerably angrier, script.
Imagine two repair jobs waiting for the same screen. One customer hears nothing. The other gets a short message explaining the supplier delay and a confirmed next update. Both laptops remain broken. Only one customer has to spend lunch hunting down the technician. You cannot invent a delivery date, but you can own the communication. Put the promised update in the job record so it survives the person who made it going home.
Make the process work in real life
An update needs to explain progress, the next step, any change to cost or timing and the next contact. Keep it short and accurate. A clear message can prevent several chase calls, which is a respectable return on a few minutes of attention.
A short update can save a long argument
Your terms should say how long temporary copies are normally retained, why the period exists and what the customer must do at collection. Do not promise indefinite storage.
Terms should explain diagnosis, quotes, approvals, data, backups, abandoned equipment, uncollected devices, special-order parts, warranty limits, contamination and what happens when additional faults appear. They should be readable.
At completion, was the original fault reproduced and then shown to be resolved? Were disturbed functions tested? Was the device cleaned appropriately? Did the ready message state price, collection process and opening hours?
We will contact you again by [next update date], even if the supplier has not changed the estimate. You do not need to chase us before then, but please reply if your circumstances change.

What the real jobs taught me
Customers judged Chips on communication as much as technical ability. They wanted punctuality, plain-English explanations, prices that matched expectations and updates when something changed. Silence creates its own story, and customers rarely write a flattering one for you. A short, honest update is usually far better than a perfect answer that arrives three days too late.
Give an update a useful shape
A useful message explains the present position, what is blocking progress and when you will contact the customer again. Say that the supplier has delayed the screen, rather than saying the job is ongoing. If the delivery date is uncertain, say so. Offer a choice when one genuinely exists, such as waiting for the agreed part or considering an alternative quote. Do not promise a collection time until the repair and testing can support it. You can be honest about uncertainty and still sound organised. Pretending to know creates the next complaint.
Make the update part of the job status, rather than a separate task somebody might remember. When a quote is waiting for approval, record who contacted the customer and when the next contact is due. When a supplier changes a delivery estimate, update the job record before promising anything different at the counter. That prevents the morning technician and the afternoon receptionist giving contradictory answers.
For business clients, agree which contact receives routine updates and which issues need escalation. An end user may need practical information about a loan device while the authorised manager needs to approve a cost. Those are different conversations. Send the right information to the right person and keep unnecessary private details out of routine messages.

Promise the next update rather than an invented finish time
The useful distinction is between a confirmed commitment and an estimate. If you have not diagnosed the fault or confirmed parts availability, say so. Tell the customer when the next update will arrive and what it should establish. If a supplier date changes, communicate the change before the customer spends another lunch break chasing you. A brief message can say what is known, what remains uncertain and whether you need approval. It does not need a paragraph of technical camouflage.
This matters especially for business customers with a stopped workstation or a repair handled through an MSP. Agree who speaks to the end user and whether a loan device or different plan is needed. Make your ticket reflect what was promised, including the date of the next contact. When a support agreement ends, explain separately when assistance stops and which subscriptions remain active.
Customers should not have to infer that distinction from a direct debit cancellation. Check a sample of recent jobs for missed updates and correct the process that allowed them, rather than merely asking staff to try harder.
The Terminator says “I'll be back.” A technician should also say when, why and whether the replacement screen has actually left the distributor. A dramatic voice is not shipment tracking.
Fit the approach to your business
Repair shop: A shop can send automatic booking and completion messages, supported by personal updates when diagnosis, parts or approval change the plan.
Callout technician: A callout technician should confirm the appointment window, advise when travelling and record any follow up work before leaving.
MSP: An MSP should use ticket updates and service notices that explain impact, action and next review time without flooding clients with technical noise.

Give the next job a better process
Choose standard update points for every service.
Promise the next contact time rather than an uncertain completion time.
Tell customers about delays before the expected deadline passes.
Use templates for structure but add the specific facts of the job.
Give customers one reliable route for replies and questions.
Check before you carry on
Which statuses should trigger an update?
Who owns the next contact date?
What information does the customer actually need?
How are missed promises reviewed?
The next useful move
Silence is an update, but rarely the one you intended to send.
Keep the promise you can make, even when the part refuses to cooperate.
About the author
Written by Philip Griffiths of Tech For Techs Group Ltd, drawing on his experience of owning and operating a nationally award winning computer repair business.

Join us at TechMAX27
Meet technology suppliers, see live demos and talk shop with fellow repair businesses and MSPs at TechMAX27.







Comments