The customer has no phone, and still calls
A repair shop's customer has a problem other businesses do not. The thing that is being repaired is often the thing they would use to get an update. So they borrow a partner's phone to ring, or email from work, or come into the shop in their lunch break to ask. Each time a technician or the counter stops to find the job.
Laptop and tablet customers wait longer, sometimes days for a part, and hear nothing between drop-off and the ready message.
Updates depend on someone remembering to send them
Most repair systems can send a message when a job is ready. Few shops use them for the steps in between. The customer's own mobile number is often the device being repaired, and nobody asks for an alternative. Delays, such as a part coming later than expected, are passed on only if someone thinks to.
- Only the ready message is sent.
- Messages go to the device that is in for repair.
- Part delays are not passed on until the customer asks.
- Walk-in status enquiries interrupt the bench.
- Nobody can see what the customer has already been told.
The cost of silence
Every status call or walk-in pulls a technician away from the bench or stops the counter serving someone who wants to buy. Customers who hear nothing feel neglected, even when the repair is going well. And customers who find out about a delay only when they turn up to collect are the ones who leave the harshest reviews.
Small repair shops feel this most. When one or two people run both the counter and the bench, every interruption stops a repair halfway. A screen replacement that should take a steady stretch of work gets broken into pieces, which is when adhesive is left to cure too long, screws go missing and mistakes creep in. Fewer interruptions is not only about customer service; it is about the quality of the work.
Updates sent from the ticket at every stage
We connect a messaging service to your repair tickets.
- At check-in the counter asks how the customer wants updates: an alternative mobile, an email, or the device's own number if it will work during the repair.
- When a technician moves the ticket to a new stage, such as diagnosing, waiting for part, repairing or testing, a short message goes out automatically.
- If the ticket's expected date changes, the customer is told the new date and the reason.
- Each message links to a status page for that repair, which shows the current stage and the expected date.
- Replies go to one shared inbox, attached to the ticket, so anyone can see the conversation.
- When the repair is ready, the message includes the amount due, opening hours and anything to bring, such as ID for collection if your process asks for it.
| Ticket stage | Customer receives |
|---|---|
| Booked in | Ticket number and expected time |
| Waiting for part | Which part and the new date |
| Repairing | Your device is on the bench |
| Ready | Amount due and opening hours |
Fewer interruptions, calmer customers
Customers know what is happening without asking. Status calls and walk-ins drop, which gives technicians longer uninterrupted time at the bench. Delays are explained before they become complaints. And because every message and reply is on the ticket, anyone at the counter knows what the customer was told.
There is a sales benefit as well. A customer who was kept informed during a repair is more likely to trust you with the next one, to buy a case or screen protector at collection, and to recommend you. The status page can also show your opening hours and any accessories for their model, without turning into a sales pitch.
Where a repair is quick, while-you-wait work, the messages can be switched off or reduced to a single ready message.
Do customers keep asking about their repair?
- Customers call from borrowed phones to ask about progress.
- People walk in during lunch to ask whether their device is ready.
- Only the ready message is ever sent.
- Part delays are discovered by the customer at collection.
- Staff do not know what the customer has been told.