Stop Letting Small Interruptions Run Your Business
EPISODE 13
You arrive with six jobs to finish. By closing time, you have answered fourteen calls, helped somebody find a password, checked a delivery twice and explained why a laptop cannot be repaired while it is still in the customer's kitchen. You have been busy all day. The six jobs are still looking at you.
For a repair shop, callout technician or MSP, interruptions can quietly become the working day. Customers need help and colleagues need answers, but every request cannot take priority over the job already promised. Give incoming work a clear place to go and protect enough time to finish what you started.
The quick question that brings friends
“Can I just ask you something?” sounds harmless. Sometimes it is. Sometimes it opens a discussion about a printer bought in 2009, a neighbour's Wi-Fi and whether an email from a mysterious prince looks genuine. By the time you return to the bench, you need to work out where you stopped.
The problem is bigger than the conversation itself. You might have been tracing an intermittent fault, checking a connector or confirming a test result. Picking that work up again requires attention. Rushing back because you feel behind can create a mistake that adds another job to tomorrow.
When you must stop, leave a useful note: what you checked, what happened and what comes next. Put loose parts somewhere secure and leave the equipment safe. “Still broken” is a description of your mood, not a handover.
Give incoming requests somewhere to land
Choose a normal route for repair enquiries and support requests. That might be your booking form, service email or ticket system. Tell customers where to use it and make it straightforward. A complicated form simply encourages people to phone and ask you to fill it in.
When a request arrives through another channel, record it in the same working queue. Avoid leaving one job in a text message, another on a sticky note and a third somewhere inside a conversation you had while carrying a box. Memory is a poor booking system, especially before lunch.
Record enough to act: the customer, the device or service, the issue, the urgency and the promised next contact. Whoever handles it should be able to see what was agreed. Customers should not need to start the story again because somebody else answered.
Decide what deserves an interruption
Some things need immediate attention. A safety concern, a suspected active security incident or a serious business outage may require you to stop. Agree how those situations reach the right person. Keep that route available when routine notifications are quietened.
Other requests can wait for a sensible callback. Someone wanting to know whether their ordered mouse has arrived should not automatically displace a booked business recovery job. Ask what has stopped working, who is affected and whether there is a usable alternative. A loud voice is not a priority rating.
For an MSP, keep response handling consistent with the service commitments you have made. For a shop, explain when routine enquiries will be answered. Never sell immediate access and then quietly decide that nobody can interrupt you.
Protect a useful block of bench time
Start with a period you can realistically protect. Perhaps one person covers the counter while another completes a diagnosis. Swap afterwards so the same colleague does not spend the entire day absorbing everyone else's interruptions.
If you work alone, set clear callback expectations and use voicemail when you cannot safely answer. Tell people when to expect contact, then honour it. Do not promise a callback in ten minutes when you are about to begin a job that needs an hour.
Quiet routine notifications during that protected period. Keep the urgent route you have agreed. You do not need to disappear into a bunker. You need enough uninterrupted attention to complete a useful piece of work without your phone conducting the orchestra.
Turn free diagnosis into a proper booking
A short conversation can establish whether you offer the right service. It does not have to become a full remote repair squeezed between two paid jobs. When an enquiry needs testing, access or detailed investigation, explain the next step and any charge before proceeding.
Try this: “I can help with that. It needs a proper diagnostic appointment so I can check it properly. Let me explain the booking and the cost.” That gives the customer a clear route and gives the work the time it deserves.
Stay friendly. People often do not know how much work sits behind their question. You can explain the boundary without making them feel foolish. The aim is a useful appointment, not a competition to see who can end the call fastest.
Finish work before opening more work
Five half investigated laptops can make a bench look impressively busy. They can also make every job harder to follow. Keep each device with its ticket and accessories, and make its next step obvious.
If a repair is waiting for approval or a part, record that clearly and move it into a suitable holding area. Choose the next job that can genuinely progress. Do not keep reopening the same blocked ticket as though staring at it might persuade the courier to accelerate.
Before taking on an extra job, check what you have already promised. An honest booking date is more useful than “leave it with us” followed by several days of awkward silence.
Make the routine fit your business
In a shop, agree who handles the counter and who owns callbacks. Keep customer information available to authorised staff so every question does not require the technician to stop.
For callout work, allow time between visits for notes and messages. Return calls when safely parked, rather than trying to run a helpdesk while driving or halfway through another customer's appointment.
For an MSP, route ordinary requests through the support queue and define escalation clearly. A technician's personal messages should not become an invisible second helpdesk that nobody else can cover.
Start with the next working day
Choose one useful block of focused work, decide who handles incoming requests and give waiting customers a realistic next contact. Keep a short stopping-point note whenever you must switch jobs. These are small changes you can actually follow when the workshop gets noisy.
You do not need a calendar full of colour coded ambition. You need customers to know what happens next and enough space to do the work well. Finish the repair, record the result and move it towards collection. That is a better ending than another evening spent wondering where the day went.
Next episode, we will make the customer's whole journey clearer, from their first enquiry to collecting the finished job.
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.
Comments