Customer updates
Customers keep calling to ask if their repair is ready. What should we tell them?
Repair-status update scripts for diagnosis, approval, parts, testing and collection—including what to say when there is no confirmed completion date.
In this guide
THE SHORT ANSWER
Tell the customer the verified repair stage, what happens next, whether you need a decision from them, and when they will hear from you again. Keep a completion estimate separate from a promised update. If the date is unknown, say so and give a realistic next-update time with a named owner.
“Is it ready yet?” can mean several things: the customer has heard nothing, the last estimate has passed, or they need the item for a particular date. The person answering needs a current job record before they need a clever script.
Use this structure: where the job is, what happens next, anything the customer needs to do, and when you will update them. Only give a completion date when the record supports it.
Download the repair-update sheet for the scripts and a shared job/update log you can adapt for your team.
Give an update time even when the finish date is unknown
Compare these two replies:
“We're waiting for a part. We'll call you.”
“The replacement part is ordered, but the supplier has not confirmed an arrival date. Maya will check with them tomorrow and update you by 3 pm, even if the date is still unknown.”
The second answer gives a next step someone owns. It makes no claim that the repair will be ready tomorrow. Use a time the team can actually meet and record the commitment before ending the call.
Keep three dates separate in the job record:
- Estimate: the current expectation, with its source and uncertainty.
- Confirmed collection or delivery: a time the business is ready to honour.
- Next update: when someone will contact the customer, including when nothing has changed.
A supplier's expected parts delivery is not a finished-repair date. “Repair complete” may still require testing, payment arrangements or an agreed collection window. Define what “ready” means in your own workflow.
Use wording that matches the actual repair stage
These examples assume staff have checked the latest record and are authorised to share it. Replace every bracket and adapt the wording to the customer's preferred contact method. For a voicemail or message preview, keep details minimal until you know the right person is receiving them.
Diagnosis is still in progress
“We're still checking the fault on job [reference]. We don't have a confirmed repair plan yet. [Name] will update you by [day/time] with the findings or the next check.”
If the customer needs it for a deadline, record that separately: “I understand you need it by Friday. That date isn't confirmed. I'll ask the technician whether it's possible and update you by [time].”
You need the customer's approval
“The assessment is complete. We've sent the proposed work and quote to [agreed channel]. We're waiting for your approval before starting that work. Would you like me to explain the scope or resend the quote?”
Check whether the quote was actually sent and what approval is required. An internal status reading “waiting” is not enough to conclude that the customer caused the delay. For unclear charges, use the service-charge explanation guide.
A part has been ordered
“The part was ordered on [date]. The supplier currently estimates [arrival window], which is not yet confirmed. After it arrives, we still need to fit it and test the repair. We'll update you by [time].”
If there is no estimate, replace that sentence with “The supplier hasn't given us a reliable arrival date yet.” Avoid “It should be ready soon” when you cannot say what “soon” rests on.
The repair is under way
“The part has arrived and the repair is in progress. The next step is [remaining work/testing]. We haven't confirmed collection yet. [Name] will update you by [time].”
Do not describe an unstarted job as under way just because the part is in the building. Staff should be able to see when the stage was last checked and who confirmed it.
The work is finished but testing is not
“The repair work is finished. We're completing [the recorded final check] before confirming it's ready. We'll contact you by [time] with the result and collection arrangements.”
If a check fails, update the record and the customer. A failed test is new information; repeating yesterday's “nearly ready” answer hides what changed.
It is ready for collection
“Job [reference] is ready for collection. You can collect it [confirmed hours or appointment]. [Explain the agreed payment or collection requirements]. Please contact us if that arrangement doesn't work for you.”
Confirm any outstanding approval, account or handover requirement before sending this message. For delivery or an on-site visit, use the confirmed booking instead of collection wording.
Keep the status and the customer update together
The job record needs enough detail for the next person to give the same answer:
Job reference:
Verified stage — checked by / at:
What is blocking the next step:
Completion estimate — source / confirmed or provisional:
Customer action required:
Last customer update — channel / time / what was said:
Next update — owner / due time / backup:
Customer deadline or concern:
RepairShopr's ticket documentation shows one implementation of this separation: status changes and logged customer communications can be recorded together, with stages such as waiting for parts. The template here is our simpler adaptation; you can use it in the repair system or shared record you already have.
Before sending another update, check whether a colleague has already contacted the customer. Record attempted contact separately from confirmed receipt or a reply. A sent message is not proof that the customer read it.
If the record is stale, say “I need to confirm the latest position with the technician” and arrange a callback. Don't make the customer resolve a disagreement between an old note and a newer conversation.
When a promised update has already been missed
Start with the missed commitment, then provide the verified position:
“We said we'd update you yesterday and didn't. I'm sorry. The current position is [verified facts]. [Name] owns the next check, and we will contact you by [time].”
Check that the new owner knows about the promise. When there is no credible repair estimate, discuss the customer's options through the authorised service lead rather than inventing a date to end an uncomfortable call. Existing terms, complaint routes and any applicable obligations still govern those options.
Review the pattern behind the calls
For a manageable sample of status enquiries, note the repair stage, the last promised update and what the customer said was missing. A customer may not have received a message, may not have understood it, or may be asking for a decision the message never addressed. Leave the reason unknown when you cannot establish it.
Fictional example: six reviewed calls concern jobs waiting for parts. Four job records show an overdue promised update; two show an update sent on time, with receipt unknown. The first check is the four missed commitments. The other two need investigation before blaming the wording or the customer.
Call Nerd can help surface recurring questions and the transcripts behind them. Staff still check the repair record for the current stage and own the promised update. It does not track parts, change job status or send these stage-specific messages automatically. Use the weekly-report structure to give the review one action, an owner and a date.