Remote IT support exposes an assumption most support models never had to state: that a technician can walk over. Look at a traditional support arrangement and it is built around that idea — a desk visit for the laptop that will not boot, a swap from the cupboard for the broken keyboard, a quick look at the printer, a new starter set up in person on their first morning. For a hybrid or fully remote team, none of those are available, and an arrangement that worked well for an office full of people quietly degrades into long phone calls, couriered laptops that arrive a week later, and staff who stop reporting problems because fixing them is more disruptive than living with them.
This guide covers the operational changes that make support work for people who are not in the building. It explains how the walk-over assumption breaks, zero-touch provisioning so a new device can be set up wherever the user is, diagnosing problems without physical access when the fault might be in the device, the home network, the broadband line or the service, running a spare device pool and courier logistics so a hardware failure costs hours rather than days, security that does not depend on a trusted office network, and how service levels should be redefined around time to a working device rather than time to first response. A broader overview of the subject sits in our earlier guide to IT support for remote teams; this one concentrates on the mechanics.
How the walk-over assumption breaks
Four things change when staff are distributed, and each one undermines a different part of the traditional model.
Physical access disappears. The fastest fix for many problems is someone looking at the device: reseating a cable, noticing the laptop is on the wrong Wi-Fi network, swapping a faulty dock. Without that, every diagnosis has to be done through what the user can describe and what management tools can see, and the quality of remote tooling becomes the quality of support.
The network is no longer yours. In the office, the network was managed, monitored and known. At home, staff connect through consumer broadband, consumer routers, shared Wi-Fi with family devices, and occasionally a coffee shop or a train. A large share of remote tickets turn out to be about the connection rather than the device, and the support team has no visibility of the router in someone’s spare room.
Hardware swaps involve logistics. A failed laptop in the office is a ten-minute swap from stock. A failed laptop in Inverness for a company based in Reading is a courier booking, a delivery window, a return package and a user without a working device in the meantime. Without a deliberate process, hardware failure becomes the most disruptive event in a remote worker’s month.
Problems go unreported. In an office, colleagues notice and mention issues, and technicians spot problems while passing. Remote staff are more likely to tolerate a slow laptop or a flaky connection than to raise a ticket that will consume an hour of their day. The result is a support desk that sees fewer tickets and a workforce that is less productive than the ticket numbers suggest.
The common thread is that support has to move from reacting in person to managing at a distance: devices that can be built, monitored, patched and repaired remotely; a hardware process designed around delivery rather than a cupboard; and service levels measured by how quickly someone can work again rather than how quickly a ticket was acknowledged.
Before changing any tooling, ask one question of your current support arrangement: if a remote employee’s laptop died at nine on a Monday morning, when would they next be working, and what would they be doing until then? If the honest answer involves the next working day or later, and borrowing a personal device in the meantime, you have found both the biggest productivity gap in your support model and a security problem, because work done on personal devices is work done outside your controls.
Where office-built support fails remote staff
The grid below groups the gaps we find when reviewing support arrangements for UK organisations with hybrid or remote workforces. Badges reflect how much each gap costs remote staff in lost working time or exposes the organisation to risk.
The second row of the third card deserves particular attention because it has become a real attack route. Criminals increasingly impersonate IT support — through Teams messages from external accounts, phone calls and emails — and persuade staff to start a remote assistance session or approve a sign-in. Remote workers are especially exposed because they cannot walk over to confirm the request is genuine, and because legitimate remote support has trained them to expect exactly this kind of contact. A clear, published way for staff to verify that a support contact is genuine is now a security control, not a courtesy.
The first card’s first row is the one that most often turns a simple event into a disruptive one. Building each new laptop by hand in the office means every new starter and every replacement involves a technician’s time, a delay, and a shipment from one location. Zero-touch provisioning removes all three, and it is covered in detail below.
Remote support in UK businesses — the numbers
The figures below reflect what we find reviewing support arrangements for UK organisations of 20 to 400 staff where at least a third of the workforce works remotely most of the time.
The first figure is the one that should reshape support budgets. Three working days without a device after a failure is the typical result where replacements are built on demand and shipped from the office. With a small pool of pre-enrolled spares and an agreed next-day courier, the same failure costs perhaps half a day. Over a year and a distributed workforce, the difference is substantial, and the spare pool frequently pays for itself in recovered working time.
The second figure explains why remote support feels harder than it should. Getting on for half of remote tickets are about connectivity — home Wi-Fi coverage, a struggling consumer router, broadband faults, a VPN that dislikes a particular network — rather than the device the support team actually manages. Without a structured way to separate those layers, technicians spend a long time investigating a laptop that is working perfectly.
The fourth figure is where productivity and security meet. A quarter of remote workers fell back on a personal device when their work device failed, which means business data and sign-ins on machines with no management, no patching guarantee and no remote wipe. Fast hardware replacement is therefore a security control as well as a productivity one.
Office-centric against distributed support
The comparison below highlights the distributed model. The qualification is that hybrid organisations with a busy office still benefit from on-site support on office days; the distributed model does not replace it so much as stop treating remote staff as an afterthought to it.
Office-centric support
Built around a technician who can walk over
Distributed support
Built around devices managed from anywhere
The service level row is the one that changes behaviour. Measuring support by time to first response rewards acknowledging tickets quickly, which is easy and says little about whether anyone can work. Measuring by time to a working device — for hardware failures, from report to the user being productive again — rewards the things that actually matter remotely: spare stock, courier arrangements, zero-touch provisioning and remote diagnosis. It also gives the business a figure it recognises.
The security row reflects a shift that applies whether or not a provider has caught up with it. When staff work from home, the office firewall protects nobody, and security has to follow the user and the device: strong authentication, device health checks before access is granted, encryption, and the ability to wipe a lost device remotely. That is the same principle that underpins zero trust approaches, covered in our guide to zero trust network access.
What remote tickets are actually about
The chart below shows the root cause of remote worker tickets across UK organisations we support, after diagnosis rather than as initially reported. The gap between what users report and what turns out to be wrong is itself informative.
Home Wi-Fi and broadband together account for more than any single device category. Users usually report these as the laptop being slow or Teams dropping, which sends investigation in the wrong direction. A support process that checks the connection first — signal strength, whether the device is on the right band, a wired test where possible, the broadband line itself — resolves a large share of remote tickets faster than any amount of device troubleshooting.
Hardware failure at six per cent is small in volume and large in impact. It is the ticket type that can leave someone unable to work for days, which is why it deserves its own process even though it is rare. Sign-in and MFA issues at nineteen per cent reflect how much more remote work depends on identity; when the network no longer establishes trust, authentication does, and anything that disrupts it stops work entirely.
The VPN row is small and falling, and that is a sign of progress. Organisations that have moved files and applications to cloud services see far fewer remote access tickets, because there is less to connect back to. Those still running VPNs to reach on-premises systems see this category grow with every additional remote worker.
The number that decides whether remote devices are manageable
If one figure determines whether a remote workforce can be supported properly, it is the proportion of devices enrolled in central management — and therefore patchable, visible, configurable and wipeable from anywhere.
Sixty-three per cent fully enrolled means more than a third of organisations have at least some remote devices they cannot patch, configure or wipe centrally. Those devices typically belong to people who joined during a rush, received a laptop bought outside the normal process, or were set up before management was introduced. They are the devices most likely to be out of date, least likely to meet security requirements, and impossible to wipe if lost.
Enrolment is the foundation for almost everything else in this guide. Zero-touch provisioning depends on it, remote diagnosis is far easier with it, compliance checks before access require it, and remote wipe is impossible without it. It is also increasingly expected by Cyber Essentials assessments and cyber insurers, both of which ask about the ability to manage and secure devices wherever they are — a point covered in our guide to Cyber Essentials and insurance.
Closing the gap is usually more administrative than technical. Most UK SMEs on Microsoft 365 Business Premium already hold the licences for device management. The work is enrolling the stragglers, which frequently means arranging a short remote session with each person or swapping their device for a properly provisioned one, and then making enrolment non-optional for every device issued from that point.
Zero-touch provisioning: devices set up wherever the user is
Zero-touch provisioning means a new or replacement device can be shipped directly from the supplier to the user, still sealed, and configure itself when they switch it on and sign in — with applications, security settings and policies applied automatically, and no technician touching it.
For Windows devices this is typically achieved by registering devices with Microsoft’s provisioning service at the point of purchase, usually by the reseller, so that the device knows it belongs to your organisation from the first boot. Apple and Android devices have equivalent enrolment programmes. Combined with a device management platform, the user signs in with their work account and the device builds itself to your standard over the following hour.
The advantages for a distributed workforce are considerable. New starters receive a laptop at home and are working on day one without a visit. Replacements can be dispatched by the supplier the same day rather than built in the office. Every device is configured identically, which removes a whole category of “works on mine, not on theirs” problems. And because no technician time is involved per device, the cost of setting up a laptop falls substantially.
Three things make it work in practice. Buy through a reseller who registers devices for zero-touch at purchase, because retrofitting registration is more work. Define the configuration once — applications, settings, security baseline — and test it on a single device before relying on it. And keep a small number of pre-registered spares, so that a replacement can go out immediately rather than waiting for an order.
The limitation worth knowing is that zero-touch provisioning depends on the device management configuration being well built. A poor configuration applied automatically to every device is worse than a poor configuration applied by hand to a few, because it spreads faster. The time spent building and testing the baseline is what determines whether automation helps.
Diagnosing problems without physical access
When a remote worker reports that “Teams keeps dropping” or “the laptop is really slow”, the cause could be in any of five layers. A structured approach that works through them in order resolves most problems faster than troubleshooting whichever layer the technician happens to know best.
Layer one: the service
Check first whether the problem is wider than one person. Is a cloud service degraded, is a business application down, are other users reporting the same thing? Service health dashboards and a quick look at other tickets answer this in a minute and avoid investigating an individual device for a problem affecting everyone.
Layer two: identity and access
Sign-in failures, expired passwords, MFA prompts that never arrive, conditional access blocking a device that has fallen out of compliance. These are frequently reported as connectivity problems because the symptom is that nothing works. Sign-in logs usually show the cause directly.
Layer three: the device
Device management tools show patch status, compliance, disk space, recent crashes and installed software without needing the user to describe anything. A remote assistance session, through a tool that verifies both the technician’s and the user’s identity, lets a technician see the screen and work directly. Most software and configuration issues can be resolved this way.
Layer four: the home network
Wi-Fi signal strength, the band the device is connected to, interference from neighbours, a router struggling with a household’s worth of devices, or a work laptop sharing bandwidth with someone streaming. A short test — moving closer to the router, trying a wired connection, running a speed test at the router and at the desk — separates Wi-Fi problems from broadband problems. Simple written guidance for staff on home network basics prevents a surprising number of tickets.
Layer five: the broadband line
If a wired connection at the router is also poor, the problem is the line or the provider. That is outside the support team’s control, and the useful response is to help the user raise it with their provider, suggest a mobile hotspot as a temporary workaround, and record it so that persistent cases can be addressed — sometimes by contributing to a better home connection for people whose role depends on it.
Working through the layers in this order matters because the cheap checks come first. Service health and sign-in logs take seconds; device inspection takes minutes; home network testing needs the user’s time and cooperation. Starting at the bottom wastes the user’s morning on a problem that a dashboard would have explained.
Moving to a distributed support model in twelve weeks
The sequence below takes an organisation from an office-centric support arrangement to one that serves remote staff properly. It assumes Microsoft 365 is in use and that device management licences are available, as they are for most UK SMEs on Business Premium.
Weeks two and three are the foundation, and they are where shortcuts cause lasting problems. A device baseline that has been tested properly makes zero-touch provisioning, compliance checks and remote support straightforward. One that has not will spread its problems to every new device automatically, which is worse than the manual process it replaced.
The leavers process in the final step closes a gap that remote work has widened considerably. When staff worked in an office, collecting a laptop on the last day was natural. Remote leavers frequently keep devices for weeks or never return them, and a device that is neither returned nor wiped is a device holding company data in the hands of someone who no longer works for you.
Remote support readiness — where most UK organisations sit
Combining the assessment areas gives an indication of how well an organisation’s support arrangement serves staff who are not in the office. The gauge reflects a first review of a UK organisation with a hybrid workforce and a support model originally designed around an office.
A score in the high thirties is consistent with an organisation that moved to hybrid working quickly and adapted its support informally. Software support scores reasonably, because remote assistance tools are widely used. Device management scores moderately, with enrolment usually incomplete. Hardware logistics score poorly, because spare pools and courier arrangements were never set up. Security and leaver processes score lowest, because they still assume the office network and an in-person last day.
The useful feature here is that most of the improvement uses capabilities organisations already pay for. Device management and zero-touch provisioning are included in licences most UK SMEs hold. The additional costs — a few spare devices and a courier account — are modest compared with the working days they recover. The work is primarily process design, which is why it is so often left undone.
Spare pools and hardware logistics
Hardware failure is rare and disproportionately disruptive for remote staff. The difference between losing half a day and losing three comes down to a few deliberate arrangements.
Size the spare pool to the fleet
A practical starting point is one spare device for every fifteen to twenty-five remote users, adjusted for fleet age and how critical a working device is to each role. Spares should be the standard model, enrolled for zero-touch provisioning, charged and ready to ship. Older devices retired from users can sometimes serve as spares if they still meet the baseline, though a pool of mismatched aging hardware tends to cause its own tickets.
Agree courier arrangements in advance
An account with a courier offering next-day delivery and timed slots, with collection arranged in the same visit where possible, removes the improvisation that otherwise turns each failure into an afternoon of phone calls. Keep prepaid return packaging on hand so faulty devices come back promptly rather than sitting in someone’s hallway.
Wipe, repair and return to the pool
Returned devices should be wiped remotely or on receipt, repaired under warranty where applicable, and re-provisioned into the spare pool. Without this loop, the pool drains and the next failure reverts to an on-demand order.
Do not forget peripherals
Docks, monitors, headsets and keyboards account for a meaningful share of remote tickets and are frequently issued informally. Recording what each person holds, keeping a few spare docks and headsets, and including them in leaver returns prevents both lost equipment and the inconsistent setups that make diagnosis harder.
Plan for location
Where staff are spread across the UK, next-day delivery is generally achievable; remote areas and some islands may take longer. For staff working abroad, even temporarily, hardware replacement becomes considerably more complex, and policy on where staff may work remotely should take that into account.
What distributed support costs
The table below sets out indicative UK costs for the components that make remote support work, excluding VAT. Device management is usually already licensed for organisations on Microsoft 365 Business Premium or equivalent; check your plan.
| Component | Indicative UK cost | Frequency | Note |
|---|---|---|---|
| Device management and zero-touch provisioning | Often included in existing licences | Per user, ongoing | Included in Business Premium and many enterprise plans |
| Spare device pool | £700–1,200 per spare laptop | One-off, replenished | Roughly one spare per 15–25 remote users |
| Next-day courier, outbound and return | £25–60 per round trip | Per incident | Timed delivery slots cost more and are often worth it |
| Verified remote assistance tooling | £0–4 per user per month | Ongoing | Some built in; identity-verified tools may be an add-on |
| Baseline build and enrolment project | £2,000–6,000 | One-off | Scales with fleet size and number of unenrolled devices |
The spare pool is the line most often rejected on cost and the one that most clearly pays for itself. For a fleet of 100 remote users, five spares at around £5,000 in total sound like a significant outlay. Against roughly three working days lost per hardware failure without them, and a handful of failures a year across that fleet, the recovered time typically exceeds the cost within the first year — before counting the security benefit of nobody falling back on a personal device.
The first row is the important one to check before budgeting for anything else. Many organisations pay for device management capabilities they have never configured, and the cheapest improvement available is using what is already licensed. Broader comparisons of support models and their costs are covered in our guide to in-house versus managed IT support.
Security that does not depend on the office network
Traditional security assumed that inside the office was trusted and outside was not. For remote staff that assumption provides no protection at all, and security has to move to the user and the device.
Identity first. Strong, phishing-resistant authentication for everyone, with Conditional Access policies deciding what each sign-in may reach based on the user, the device and the risk. Our guide to phishing-resistant MFA covers the options.
Device health as a condition of access. Devices enrolled in management, encrypted, patched and running protection should be the condition for reaching company data. A device that falls out of compliance — missing updates, protection disabled — loses access until it is fixed, wherever it is.
Encryption and remote wipe. Laptops in homes, cars and trains are lost and stolen more often than laptops in offices. Full-disk encryption makes a lost device a hardware cost rather than a data breach, and remote wipe ensures company data can be removed from a device that is not coming back.
Verified support contacts. Staff need a simple way to confirm that a support request is genuine before granting screen access or approving a sign-in, because impersonating IT support is now a common attack route. Publishing how genuine support will contact people, and what it will never ask for, is a small piece of communication with a significant security effect.
Less dependence on VPNs. Moving files and applications to cloud services reduces the need for remote access back into an office, along with the VPN tickets and the exposure of an internet-facing gateway. Where on-premises systems remain, application-level access controls are generally preferable to broad network access.
Benchmarks — remote support practice against what we find
The figures below show how often each practice is in place across UK organisations of 20 to 400 staff with substantial remote or hybrid working.
Distributed IT support practice in UK organisations
Ninety-one per cent use remote assistance, which is why software problems are generally handled acceptably. The figures fall sharply for everything involving physical hardware and process: spare pools at twenty-seven per cent, courier arrangements at thirty-one, time-to-working-device service levels at fourteen. Those are precisely the elements that determine whether a remote worker with a failed laptop is back at work by lunchtime or by Thursday.
The leaver figure at forty-four per cent is the security gap with the most direct exposure. More than half of organisations have at least occasionally failed to recover or wipe a departing remote worker’s device, leaving company data on equipment in the hands of someone with no continuing obligation to protect it.
Redefining service levels for a distributed workforce
Most IT support contracts measure response time — how quickly a ticket is acknowledged or a technician engages. That measure made sense when a technician could walk over and fix most things within the response window. For remote staff it measures the wrong thing.
Measure time to a working device
For hardware failures, the outcome that matters is how long the person is unable to work. A service level expressed as time from report to the user being productive again — on a replacement device if necessary — captures everything that determines it: spare stock, courier speed, zero-touch provisioning and remote setup. Next working day is a reasonable target with a spare pool in place; same day is achievable in some locations.
Align support hours with how people work
Remote and hybrid staff often work patterns that differ from the old office day — earlier starts, later finishes, compressed weeks. Support hours fixed to nine to five can leave people without help when they are actually working. Reviewing ticket timestamps against support hours shows quickly whether there is a mismatch worth addressing.
Track remote staff separately
Reporting support performance across the whole workforce can hide a poor experience for remote staff behind good results in the office. Splitting satisfaction, resolution time and repeat tickets by working pattern shows whether remote workers are being served equivalently, and whether the under-reporting described earlier is distorting the picture.
Include the things remote staff cannot do themselves
Remote workers cannot pop into the office to collect a cable, swap a monitor or have a technician look at a dock. Service definitions should state explicitly how peripherals are replaced, how equipment is returned, and how new starters receive their kit, so that these are handled as standard rather than negotiated each time.
Common mistakes in supporting remote staff
The errors below recur across UK organisations whose support arrangements were built for an office. Most are not technical failures but processes that never adapted.
- Building every device by hand in the office. It delays new starters and replacements and consumes technician time. Zero-touch provisioning ships devices direct and configures them on first sign-in.
- Having no spare device pool. Without one, hardware failure means roughly three days without a working device and a strong temptation to use a personal machine.
- Leaving remote devices unenrolled. Unmanaged devices cannot be patched, checked, configured or wiped centrally, and they are usually the least secure in the fleet.
- Troubleshooting the device first. Getting on for half of remote tickets are connectivity problems. Check service health and sign-in, then the home network, before spending an hour on a working laptop.
- Relying on the office network for security. It protects nobody at home. Security must follow the user and the device through identity, device compliance and encryption.
- Giving staff no way to verify a support contact. Impersonating IT support is a common attack route, and remote workers cannot walk over to check.
- Using unverified remote assistance tools. Tools that do not confirm who is on each end are easy to misuse. Prefer tools that verify both technician and user identity.
- Measuring support by response time alone. A fast acknowledgement does not get anyone working. Add time to a working device for hardware failures.
- Forgetting peripherals. Docks, monitors and headsets cause a meaningful share of tickets and go missing at leaver time if nobody records them.
- Not recovering leavers’ devices. Send prepaid returns automatically, lock devices on the last day, and wipe remotely if a device is not returned.
Be particularly wary of unsolicited remote support contacts. Attackers increasingly message staff through collaboration tools from external accounts with names suggesting IT or help desk, sometimes after flooding the person’s inbox with spam to create a plausible reason to help, and then ask them to start a remote assistance session or approve a sign-in prompt. Remote staff are especially exposed because legitimate support works the same way. Publish exactly how your support team will contact people, restrict external collaboration where it is not needed, use remote assistance tools that verify identity, and tell staff plainly that genuine support will never ask them to approve an unexpected sign-in request.
The 12-point remote support checklist
Items one to four establish device management. Items five to eight build the hardware and diagnostic processes. Items nine to twelve cover security and the service model.
- Inventory every device used by remote and hybrid staff. Owner, age, operating system, warranty, enrolment status, and any personal devices in use for work.
- Build and test a device baseline. Applications, security settings, encryption and update policy, tested on a single device until it builds cleanly.
- Enrol every remote device in central management. And make enrolment a condition of accessing company data.
- Set up zero-touch provisioning through your reseller. New and replacement devices shipped direct to users and configured on first sign-in.
- Maintain a spare device pool. Roughly one pre-enrolled spare per fifteen to twenty-five remote users, ready to ship.
- Agree courier and return arrangements in advance. Next-day outbound delivery, prepaid return packaging, and a loop to wipe and re-provision returned devices.
- Adopt a layered diagnostic process. Service, identity, device, home network, broadband — cheapest checks first.
- Publish home network guidance for staff. Router placement, wired connections, the right Wi-Fi band and what to do about broadband faults.
- Require device compliance and strong authentication for access. Security based on identity and device health, not the office network.
- Use verified remote assistance and publish how genuine support contacts staff. A security control against support impersonation.
- Add time to a working device to your service levels. And align support hours with how remote staff actually work.
- Automate leaver device recovery. Prepaid returns on resignation, remote lock on the last day, remote wipe if not returned.
If only three items are completed, make them three, five and ten. Full enrolment makes every remote device manageable, patchable and wipeable. A spare pool turns the most disruptive event in a remote worker’s month into a short interruption. And verified remote assistance with a published way to confirm genuine contacts closes one of the most common current attack routes against remote staff.
What this looks like in practice
A UK recruitment agency with 120 staff had moved to hybrid working, with around half its consultants working remotely most of the week from locations across England and Scotland. Its managed support provider handled tickets well when staff were in the London office and less well otherwise. A consultant in Leeds whose laptop failed waited four working days for a replacement, built by hand in London and couriered when a technician had time; she used her own laptop in the meantime to keep her pipeline moving.
A review found the pattern behind that case. About a quarter of remote devices were not enrolled in device management, mostly laptops issued during a hiring push. There was no spare pool. Courier bookings were made individually each time. Remote tickets took noticeably longer to resolve than office ones, and around forty per cent of them turned out to be home broadband or Wi-Fi problems after the technician had first spent time on the laptop. Two leavers in the previous year had never returned their devices, and neither had been wiped.
The agency and its provider changed the model over about ten weeks. A tested device baseline was built and the unenrolled laptops brought into management, largely through swaps for properly provisioned devices. The reseller began registering new laptops for zero-touch provisioning and shipping them direct to users. Six spares were bought and kept pre-registered, with a next-day courier account and prepaid return packaging. The support desk adopted a layered diagnostic script that checked service status, sign-in and the home connection before the device, and the agency published simple home network guidance. Remote assistance moved to a tool that verified identity, and staff were told exactly how support would contact them. The service agreement added a next-working-day target for a working replacement device.
The old arrangement was fine if you sat in the London office, and we had half our people somewhere else. What changed things was the spare laptops and the courier account — the next time someone’s machine died in Glasgow they had a new one by ten the following morning, already set up. And nobody uses their own laptop for work any more, which our insurer was rather pleased to hear.
Remote resolution times fell to roughly match the office, and hardware failures went from several days lost to under one. The two unrecovered devices could not be retrieved retrospectively, but the new leaver process sends a prepaid return box automatically and wipes any device not back within fourteen days. Two points generalise. The first is that the largest gains came from logistics rather than technology: spares and a courier account delivered most of the improvement. The second is the connectivity finding, because putting the home network check before the device check shortened a large share of remote tickets without any new tooling at all.
At a glance — IT support for remote and hybrid teams
| Question | Short answer |
|---|---|
| Why does office-built support fail remote staff? | It assumes physical access, a managed network, a stock cupboard and staff who report problems in person |
| Typical downtime after hardware failure | About 3.2 days without a spare pool; under a day with pre-enrolled spares and next-day courier |
| Commonest root cause of remote tickets | Home Wi-Fi and broadband — around 41 per cent combined |
| Diagnostic order | Service health, identity and sign-in, device, home network, broadband line — cheapest checks first |
| Foundation for everything else | Full enrolment in central device management — only about 63 per cent of remote fleets |
| Zero-touch provisioning | Devices shipped direct from the reseller, configured automatically when the user signs in |
| Spare pool size | Roughly one pre-enrolled spare per 15–25 remote users |
| Indicative costs | Spares £700–1,200 each; courier £25–60 per round trip; device management often already licensed |
| Security model | Identity and device health as conditions of access, encryption and remote wipe — not the office network |
| Support impersonation risk | Use identity-verified remote assistance and publish how genuine support will contact staff |
| The service level that matters | Time to a working device for hardware failures, not only time to first response |
| Personal device fallback | About one in four remote workers used one during their last hardware fault — a security gap |
| Leavers | Prepaid returns sent automatically, remote lock on the last day, remote wipe if not returned |
| Where the biggest gains come from | Logistics and process — spares, couriers, enrolment — more than new tools |
| Hybrid offices | On-site support still helps on office days; the distributed model stops remote staff being an afterthought |
How Cloudswitched supports remote and hybrid teams
Cloudswitched provides IT support for UK organisations whose staff work from home, the office and everywhere in between, and we design the support model around people who are not in the building rather than treating them as an exception. In practice that means a tested device baseline with every device enrolled, zero-touch provisioning with direct shipping, a spare device pool and agreed courier arrangements, a layered diagnostic approach that checks the connection before the laptop, identity-verified remote assistance with a published way for staff to confirm genuine contacts, service levels that include time to a working device, and automated leaver device recovery. On office days we are there in person; on every other day, remote staff get the same standard of support.
Support that works wherever your people do
We enrol and manage every device, keep spares ready to ship, diagnose problems from the connection inwards, and measure ourselves by how quickly your people can work again.
Talk to an IT Support SpecialistFrequently Asked Questions
How is IT support different for remote and hybrid staff?
It cannot rely on physical access, a managed network or a stock cupboard. A technician cannot walk over to look at a device, the home network is outside the organisation’s control, replacing failed hardware involves courier logistics, and remote staff report problems less readily than office staff. Support therefore has to manage devices centrally wherever they are, diagnose problems through tooling and structured questions, handle hardware swaps through spare pools and couriers, and secure access through identity and device health rather than the office network.
What is zero-touch provisioning?
A way of deploying devices so they can be shipped sealed from the supplier directly to the user and configure themselves when the user switches them on and signs in with their work account. Applications, security settings and policies are applied automatically from your device management platform. It requires devices to be registered for your organisation, usually by the reseller at purchase, and a well-tested configuration baseline. For a distributed workforce it removes the delay and technician time of building devices in an office before shipping them.
Do we need device management for remote staff?
Yes. Without central device management you cannot reliably patch remote devices, check their compliance, push configuration, or wipe them if they are lost or not returned. It is also the foundation for zero-touch provisioning and for making device health a condition of access to company data. In our reviews only about 63 per cent of remote fleets are fully enrolled. Many UK SMEs already hold the necessary licences through Microsoft 365 Business Premium or equivalent plans and have simply not completed enrolment.
How quickly should a remote worker get a replacement laptop?
A reasonable target with the right arrangements is the next working day, and same day is achievable in some locations. Without a spare pool, replacements built on demand typically leave someone without a working device for around three working days. With a small pool of pre-enrolled spares, a next-day courier account and zero-touch provisioning, the replacement arrives ready to use when the user signs in. Measuring support by time to a working device makes this visible and accountable.
How many spare laptops should we keep?
A practical starting point is one spare for every fifteen to twenty-five remote users, adjusted for the age of the fleet and how critical a working device is to each role. Spares should be the standard model, registered for zero-touch provisioning, charged and ready to ship. Returned devices should be wiped, repaired where necessary and fed back into the pool so it does not drain. The cost is usually recovered within the first year in working time saved after hardware failures.
Why are so many remote IT problems actually broadband or Wi-Fi?
Because home connectivity is the part of the remote setup least under anyone’s control. Weak Wi-Fi coverage, interference, consumer routers struggling with a household of devices, and broadband line faults together account for around 41 per cent of remote tickets in our experience. Users often report them as the laptop being slow or calls dropping. A diagnostic process that checks service health, sign-in and the home connection before investigating the device resolves these much faster, and simple home network guidance prevents many of them.
How do we keep remote workers secure without an office network?
Move security to the user and the device. Require strong, phishing-resistant authentication; use Conditional Access to decide what each sign-in can reach based on user, device and risk; make device compliance — enrolment, encryption, patching, protection — a condition of access; and ensure every laptop is encrypted and can be wiped remotely. Reducing dependence on VPNs by moving files and applications to cloud services also removes a common source of tickets and exposure.
What is IT support impersonation and how do we prevent it?
Attackers pretend to be IT support, often messaging staff through collaboration tools from external accounts or phoning them, and persuade them to start a remote assistance session or approve a sign-in prompt. Remote staff are especially vulnerable because genuine support contacts them in similar ways and they cannot walk over to check. Publish exactly how your support team will make contact, restrict external collaboration where it is not needed, use remote assistance tools that verify identity, and tell staff that genuine support will never ask them to approve an unexpected sign-in.
Should staff use personal devices when their work laptop fails?
Ideally not, because personal devices are outside your management, patching and remote wipe, and business data and sign-ins on them are outside your controls. In our experience about one in four remote workers has done so during a hardware fault, usually because the replacement would take days. The effective fix is not a policy prohibition alone but fast replacement: when a ready-configured spare arrives the next morning, the temptation largely disappears.
How do we get laptops back from remote leavers?
Make it automatic. When someone resigns, send prepaid return packaging and instructions as part of the leaver process, lock the device remotely at the end of their last day, and set an agreed period after which a device not returned is wiped remotely. Record each device’s return or wipe. Fewer than half of organisations we review recover or wipe every remote leaver’s device, which leaves company data on equipment outside the organisation’s control.
Should our IT support SLA change for remote staff?
Yes, in two ways. Add time to a working device as a measure for hardware failures, because a fast response does not help someone who cannot work for three days. And check that support hours match how remote and hybrid staff actually work, since many keep different patterns from the old office day. It is also worth reporting support performance for remote and office staff separately, so a poorer remote experience is not hidden in an overall average.
Is remote IT support more expensive?
Not necessarily, and it can be cheaper overall. Device management and zero-touch provisioning are often included in licences organisations already hold, and zero-touch removes technician time per device. The additional costs are a modest spare pool and courier charges per incident. Against those, faster hardware replacement and quicker diagnosis recover substantial working time. The bigger cost is usually the hidden one: remote staff losing days to slow fixes and under-reporting problems because raising a ticket is too disruptive.
Related reading
More guidance on supporting, securing and managing UK business IT:
Remote staff deserve the same support as the office
Cloudswitched builds IT support around people who are not in the building — managed devices, spares ready to ship, diagnosis from the connection inwards, and service levels measured by time to a working device.
Talk to an IT Support Specialist
CloudSwitched
London-based managed IT services provider offering support, cloud solutions and cybersecurity for SMEs.
