Remote Support for People Working From Home

Wednesday, 08:40, at Stonebridge Insurance. Yusuf, a claims handler who works from a kitchen table two hours from the office, phones the desk. His laptop has been sitting on "Applying settings" since he turned it on at eight, and he has a customer call at nine. Mei picks up ticket 6210 and reaches for the remote support tool, then stops, because there is nothing to connect to. The laptop has not finished starting, so nothing on it is listening. The company network cannot see it. The tool cannot see it. Mei can see Yusuf's kitchen in her mind and nothing else. "Yusuf, can you take a photo of the screen with your phone and send it to me as a reply to the ticket e-mail? The whole screen, if you can." Ninety seconds later the photo is in the ticket. The message under "Applying settings" says the machine is waiting for a network it cannot find.

Mei talks him through it by phone. Is the little light on the router steady or blinking? Has anyone else in the house got internet this morning? Has the router been turned off and on since yesterday? His daughter's tablet has no internet either. He restarts the router. The laptop finishes starting at 08:52. Mei, now able to connect, asks if she may and watches him click allow. She checks the network settings while he gets a coffee for the nine o'clock. Remote support for home workers is support for a person on a network you do not manage, often on a device you only partly control. Nobody is nearby to lean over and look. Sometimes there is no working computer at all for your tool to reach. The five principles of remote control done securely all still apply. Every one of them gets harder. The day the tool cannot connect, the desk needs a second method ready before the user is. This article is part of our Remote Support Tooling series. This article is about that second method as much as the first.

It covers what changes when the desk is not in the building. Then comes the home network, and what the desk may and may not ask of it. Next come personal devices and where the boundary sits, and why consent and identity are harder at home. Then come the fallback ladder for when remote control fails and the phone-and-photo method in detail. After that come the loan device and the swap, and a table of common failures and their fallbacks. Last come a short war story and the home-worker support card to copy.

What Changes When the Desk Is Not in the Building

Three things change, and each of them removes something the desk relies on without noticing. The network is theirs, not yours. The connection between the user's laptop and your tool crosses a home router you have never seen, a broadband line from a provider you did not choose, and a stretch of the public internet. Any of those can be slow, down or shared with a teenager streaming something. The device may be theirs, or partly theirs. A company laptop on a kitchen table is still a company laptop, but the same laptop might be used by the household at the weekend. The personal computer the user falls back to when it breaks is not yours at all. And the person is alone. In the office, a colleague leans over and says "oh, that's the thing where you hold the button down". At home, there is nobody, and the desk is the only help they have.

The fourth change is the one that matters most on a bad day: there is no walk-over. In the building, every remote session has a fallback that costs a flight of stairs. For a home worker, the fallback is a phone call, a photograph, a courier or a drive. If the desk has not decided in advance which of those it will use and when, the decision gets made at 08:40. It gets made by a technician with a tool that will not connect and a user with a call at nine. The brochure calls this "seamless hybrid support". The user calls it "the laptop won't turn on".

None of this makes remote support for home workers unusual. It is now the ordinary case on many desks. The habits that handle it well are the same habits as for the third floor with two extra steps. Those are a boundary about devices and networks, said in advance, and a fallback ladder the whole desk knows. The rest of this article is those two things.

The Home Network

The home network belongs to the household, and the desk treats it the way it would treat a neighbour's garden: you may ask, you may advise, you may not climb over the fence. The session crosses that network and the internet, so it must be encrypted end to end. That is the fifth principle and the one that matters most here. A tool that was acceptable inside a building where the desk owns every cable is not necessarily acceptable across a user's broadband. Check that yours encrypts every session by default and that nothing a technician does can switch that off. The questions to put to a vendor are in the last article of this series, on choosing and reviewing the tool.

What the desk may ask of the home network is a short list, and it fits on the card at the end of this article. Is the router's light steady? Do other devices in the house have internet? Has the router been turned off and on? Can the laptop be moved nearer the router or plugged into it with a cable? And is the laptop's own wireless switched on? Those five questions settle most home connection problems, and all of them are things the user can do with no help and no risk. Home networks are managed by whoever set up the router, who is usually the router.

What the desk may not do is reach into the household's equipment. Never ask a user to log into their own router and change settings. Not even a small one. It is their router, their provider, and your afternoon, because the setting that fixed the laptop will have broken the television and the call about that will come to you. If the home connection genuinely cannot carry the work, the answer is a different connection. That could be a mobile data hotspot from a work phone, a trip to the office, or a visit to a nearby site. It is not a redesign of the family's network by phone. Write the boundary on the card so that it is a fact the user already knows rather than a refusal they hear for the first time when they are already stressed.

Personal Devices and the Boundary

A personal device is one the organisation does not own or manage. The boundary around supporting it belongs to the scope the desk has published, which is the subject of BYOD and Personal Devices. This article adds only the remote control part of that boundary, and it is simple to state. The desk connects by remote control to devices the organisation manages. It connects to a personal device only where the published scope explicitly allows it and the device's owner, who may not be the user, has agreed. A home worker's company laptop is in scope. The family computer they borrowed when the laptop died is, on most desks, not.

The reason is not unhelpfulness. A remote session onto a personal device puts the technician's cursor among the household's photographs, banking, children's homework and whatever else lives on a machine nobody at the organisation has ever configured. The technician cannot know what they will see or what the tool will change. The user who asks "can you just remote onto my own laptop and set up my work e-mail?" is asking something reasonable. The honest answer is "I can't connect to a personal machine, but here is what I can do", followed by the alternatives. Those are the web version of the work applications, which needs no connection to the device, or a phone call with the user driving. Or, if the work genuinely needs a managed device, the alternative is a loan laptop by courier.

Say the boundary before it is needed. A home worker who reads on their card, on day one, that the desk supports the company laptop and not the household's devices will plan around it. Most will keep the company laptop in working order precisely because they know there is no second option. A home worker who learns the boundary at 08:40 on the day the laptop died hears a refusal. Same rule; different morning. The card is how the rule gets to them on a good day.

Consent and Identity Are Harder at Home

Everything in Consent, Every Time applies at home, and two parts of it get harder. The first is identity, in the direction the desk usually forgets: the user's ability to tell that the caller is really the desk. Home workers are alone, which is exactly who an impostor phones. "This is IT, we've detected a problem with your laptop, I need you to install something so I can fix it" sounds, to someone alone at a kitchen table, like help arriving. The desk's defence is the same four lines as in the office, printed on the card and repeated at every opportunity. We only connect on a ticket you raised or can see. We never cold-call to install software or read out a code. If anyone does, hang up and call the desk on the number on this card. And you will see a prompt you click, every time, and a banner while we are connected.

The second is the visible session, which at home has an audience the technician cannot see. The laptop is on the kitchen table, a partner is making breakfast, a child is doing homework beside it. The ask includes one extra question: "Is anyone else able to see your screen at the moment, and are you happy for them to?" It is the user's home and their decision, and most will say "it's fine". But asking is what makes the session theirs rather than something done to them. The technician also narrates slightly more than usual, because the user is alone and the narration is the only evidence they have that the cursor is doing what it says.

Consent given in advance deserves a word, because home workers often offer it: "just connect whenever, I'm always here". That is a kind offer and still not consent to any particular session, because the technician cannot know what is on the screen or who is in the room at the moment of connecting. The answer is "thanks, I'll still message you first each time so you know it's me", which takes a second and protects the user. It has the useful side effect of teaching them that anyone who does not message first is not the desk.

When Remote Control Fails: The Ladder

Remote control fails at home for reasons it rarely fails in the office. The laptop will not start, the home internet is down, or the tool's connection is too slow to use. The device may be a personal one the desk will not connect to. Or the user may be on a train with a phone and no laptop at all. A fallback ladder is the ordered list of methods the desk uses when the one above it does not work, with a time limit on each rung. That way, the technician climbs rather than persists. The ladder for a home worker has six rungs, and the desk should be able to recite them.

The first rung is the remote session, attempted once, with a limit of about five minutes to get connected. The second is the phone call with the user driving: the technician describes, the user does, the user reads back what the screen says, one action at a time. The third is the phone-and-photo method, which is the second rung with pictures, and the subject of the next section. The fourth is a video call from the user's phone pointed at the laptop screen. That is the photo method for problems that move: a message that flashes, a sign-in that loops, a screen that changes before anyone can read it. The fifth is the swap: a loan device sent by courier or collected from the nearest office, with the broken one coming back. The sixth is the visit, by the user to an office or by a technician to the user, which is expensive and rare and sometimes right.

The limits are what make it a ladder rather than a list. A technician who spends ninety minutes on the second rung, talking a user through network resets by phone, has done ninety minutes of work that a photo at minute five would have made unnecessary. The war story below is about exactly that. Set the limits as a desk and write them down. Allow five minutes to connect, fifteen on the phone before asking for a photo, and thirty with photos before considering video. Make a decision about a swap within the first hour for any device that will not start. The fallback is not a failure. It is a channel, with its own place in the ticket like any other.

The Phone-and-Photo Method

The phone-and-photo method is the technician on the phone, the user at the broken device, and the user's own phone camera as the technician's eyes. It needs nothing installed, works on a laptop that will not start, and produces a record in the ticket that a verbal description never could. It is the single most useful technique for home-worker support and the one most desks reach for last, because it feels less professional than a tool. It is more professional than ninety minutes of "what does it say now?".

Ask for the photo in a way that gets a usable one. "Take a photo of the whole screen, straight on, with the room lights off if there's glare, and send it as a reply to the e-mail you got about this ticket, from your phone." The reply-to-the-ticket part matters. The photo lands in the ticket, under the right number, and not in the technician's personal inbox or a chat thread that will be gone by Friday. (The first photo will be of the wrong screen, or blurred, or of the technician's own name on the user's phone. Ask again, kindly. The second one is usually good.) If the problem moves, ask for a short video instead, or a video call with the phone's camera on the screen.

Direct the user one action at a time, in words that name what they will see rather than what it is called. That is the discipline in Skipping the Jargon. "Press and hold the button with the circle and the line through it until the screen goes black, then let go" beats "hard power-cycle it". After each action, ask them to read the top line of the screen or send another photo. Write what they read into the ticket as you go. The ticket ends up with a sequence of photos and read-backs that is, in effect, a session note for a session the tool never saw. That note belongs in the same place as every other session note. If you run QuerySolv, the photos and the technician's lines sit in the ticket's event history in the order they happened. That is what makes the record readable a month later. The note's format is in Logging and Session Records, with "call started" in place of "connected".

Know when the photo has told you enough. A photo of a disk error, a hardware diagnostic or a message saying the device cannot start is a photo that says "swap". In that case, the right move is to stop troubleshooting and start the courier, however early in the hour it is. I once spent forty minutes on a home worker's connection before asking whether the charger was in the wall. It was in the laptop. The other end was in a drawer. A photo of the desk would have taken ten seconds, and I now ask for one of the whole setup before I ask anything else.

The Loan Device and the Swap

A swap is sending the user a working device and getting the broken one back. For a home worker it is the equivalent of the walk down the corridor with a spare laptop, with a courier where the corridor would be. It works only if the spare exists before the failure: a small pool of loan devices, set up with the standard build, kept charged, with a box and a prepaid return label beside each. A desk that supports home workers and has no loan pool has decided that every hardware failure is a multi-day outage for the user. That is a decision it should at least make on purpose.

The swap has a procedure, and it is short. The user is told, in the ticket, what is coming, when, what to do when it arrives, and how to send the old one back. The technician sets the loan device up so that signing in once is all the user needs, and tests that before it ships. The broken device is wiped or examined on return according to whatever the organisation does with devices that may hold work data. And the ticket records the asset moving both ways, because the day someone asks where loan laptop seven is, the ticket is where the answer will be. The desk that tracks devices through tickets rather than an asset system will recognise this. The method is in Linking Devices Without an Asset System.

Decide the swap threshold in advance, as a desk, so that no technician has to decide alone at 08:40 whether this is worth a courier. Here is a reasonable rule for a small desk. Any device that will not start after the photo method triggers a swap the same day. So does any hardware fault shown in a photo, or any problem that has consumed an hour of phone time without progress. The courier costs less than the second hour. The user's day costs more than both.

Common Failures and Their Fallbacks

The table lists the failures a desk sees most from home workers and what the user describes. It also lists the first rung of the ladder that fits, what to ask the user for, and when to stop climbing and swap. Pin it next to the ladder. Most of these the desk will recognise by the second sentence of the call.

Notice how often "phone and photo" is the first rung and how rarely the answer is "try the remote tool again". Once the tool has failed to connect, trying again is the rung most technicians stay on longest, and it is the one that produces the least. Climb.

A Short War Story: The Three-Hour Phone Call at Larkspur Media

At Larkspur Media, a designer called Beatriz working from home phoned the desk on a Monday morning. She called because her laptop had shown a message she described as "something about a device" and then gone dark. A technician called Owen spent the next three hours on the phone with her trying to reach the laptop with the remote tool. He reset the connection to the company network and talked her through restart after restart. That was because the tool was what he knew and the laptop occasionally stayed on long enough to make connecting seem possible. At no point did anyone ask for a photograph of the message. When Beatriz finally sent one unprompted at lunchtime, the message read in full that the storage drive had failed and the device could not start. A loan laptop sent by courier at nine would have reached her the next morning. One sent at one o'clock reached her two days later. The client presentation she had been building was delivered late, with the agency's director phoning the client personally to explain. The desk's ladder now has "ask for a photo of the screen" as the second step, with a time limit on the first. Beatriz's photo is pinned above Owen's desk, not as a reproach but as a reminder: the photo is the first step, not the last, and three hours of phone is what it costs to find that out.

The Home-Worker Support Card

The card below is for the user, not the desk. It is a single page they keep by the laptop, printed or saved on their phone. The phone is the only device that will still be working on the morning they need it. The card carries the desk's contact details and the four lines about what the desk will never do. It also carries the five home-network questions so that the user can try them before calling. It explains how to send a photo to the ticket and what happens when the laptop will not start. It states the boundary around personal devices as a fact rather than a refusal. Fill in the blanks, give one to every home worker on their first day, and send a fresh one whenever the details change.

HOME-WORKER SUPPORT CARD — KEEP THIS BY YOUR LAPTOP
Desk phone: ______________   Desk e-mail: ______________   Hours: ______________
Out of hours: ______________

HOW TO GET HELP
  1. Raise a ticket by e-mail or the portal; you will get a ticket number.
  2. If you cannot, phone the desk; we will raise the ticket for you.
  3. Have ready: your ticket number, the laptop's asset tag (on the
     underside), and your phone with its camera.

WHAT THE DESK WILL NEVER DO
  Connect to your screen without asking you first, every time.
  Phone you unexpectedly and ask you to install software or read out a code.
  Ask for your password.
  Stay connected after the job is done.
  If anyone does any of these, hang up and call the desk number above.

WHEN WE CONNECT TO YOUR SCREEN
  You will see a prompt to allow it; click it only after we have spoken.
  You will see a banner while we are connected. You can end the session
  at any time by ______________. Tell us if someone else can see your screen.

BEFORE YOU CALL ABOUT THE INTERNET, TRY THESE
  [ ] Is the router light steady?  [ ] Do other devices in the house have internet?
  [ ] Turn the router off, wait thirty seconds, turn it on, wait two minutes.
  [ ] Move nearer the router, or plug in with a cable if you have one.
  [ ] Is the laptop's wireless switched on?
  We will never ask you to change settings inside your router.

IF THE LAPTOP WILL NOT START
  Take a photo of the screen, straight on, lights off if there is glare,
  and one of the whole setup including the charger. Send both as a reply
  to the ticket e-mail from your phone. If the device cannot be fixed by
  phone, we will send a loan laptop by courier; typical arrival: ______.

YOUR OWN DEVICES
  The desk supports the company laptop. We do not connect to personal
  computers or household devices. If your laptop is down, we will set you
  up with web access to ______________ by phone until the loan arrives.

Ticket numbers to keep: ______________   Loan laptop (if issued): ______________

Yusuf's card was in the drawer under the kitchen table, and he had not read it, which is normal. He read it at 08:41 while on hold and got as far as the router light. He had already turned the router off and on by the time Mei picked up. The ticket for 6210 has his two photos, Mei's read-backs, the session note from 08:52, and his line at 09:40 saying the nine o'clock went fine. The card did not fix anything. It made the first four minutes of the call unnecessary, which on a morning with a customer waiting is the kind of fix that counts.

Frequently Asked Questions