What the Desk Supports at Home, and What It Does Not

Thursday, 14:30, at Bluewater Bank. Owen has been on the phone for forty minutes with Farah, an underwriter who works from a converted conservatory. The ticket has grown while he talked. It started as "the printer at home will not print the statements". It is now also the wireless connection that drops whenever the washing machine runs. It includes the question of whether her son's laptop can use the bank's VPN for his course. And it includes a request for a second monitor like the one her colleague was given. Owen has restarted the printer twice, found the manufacturer's support page, and is now reading it aloud to her. Nadia, the desk lead, is listening from the next desk and has written one word on her pad. The word is "stop".

Owen is not doing anything wrong. He is doing what a kind technician does when nobody has told him where the desk's responsibility ends and the household begins. That is everything, slowly, by phone. The home support scope is the written statement of what the desk supports in a remote worker's home. It also says what the desk helps with partly and what it leaves alone. It gives the reason for each line and what the person can do instead. This article is part of our Supporting Remote Workers series. The series covers the design of a desk whose users are not in the building. This is the article about the edge of that desk, and about saying where the edge is without sounding like a wall.

It starts with why the boundary has to be written and the three rings of home support. Next come the organisation's devices, the household network that the desk supports partly, and the personal printer and everything else it leaves alone. Then it covers the standard home kit as the boundary made physical, saying the boundary kindly, and exceptions and who decides them. It closes with keeping the scope honest against the tickets, a short war story, and the home support scope itself as a template.

Why the Boundary Has to Be Written

In the building, the boundary of the desk's responsibility was the building, and nobody had to write it down. The network was the organisation's, the printer was the organisation's, the desk was the organisation's, and the technician could touch all of them. A home is none of those things. The router belongs to the household or the provider. The printer was bought for the children's homework. The other devices on the network are a television, a games console and a neighbour who has the password. The desk can see, change and be responsible for none of it. The laptop is the only thing in the house that is the organisation's. The boundary has moved from a wall to a device, and that is a boundary somebody has to draw.

If the desk does not draw it, the kindest technician on the phone at half past two will, and will draw it somewhere different every time. Owen draws it generously, so Farah's printer gets forty minutes. His colleague draws it tightly, so the next underwriter is told "that's your home network" and hangs up feeling abandoned. Neither is following a rule, and both are doing their best. The desk has two boundaries, which is to say none. Within a quarter the remote staff have learned which technician to ask for. The hours spent on household printers are invisible because they are inside tickets labelled "printing". The desk has made a promise it never agreed to. An unwritten boundary is not a flexible one. It is one somebody else is drawing for you.

The written scope does three things at once. It tells the remote worker what to expect before they raise the ticket, which removes most of the disappointment. It gives the technician a sentence to say that is the desk's sentence rather than a personal refusal. And it makes the exceptions visible. That is because an exception to a written rule is a decision somebody can see, while an exception to an unwritten one is just Thursday. The scope is not the desk being mean. It is the desk being the same for everyone.

The Three Rings: Owned, Helped, Left Alone

The clearest way to draw the boundary is as three rings around the laptop. The inner ring is what the desk owns: the devices the organisation issued, the software on them, the accounts and the connection into the organisation. The desk supports these fully, at home exactly as in the building, and ships a replacement when they fail. The middle ring is what the desk helps with: things it does not own and cannot change but can advise on, because the organisation's work depends on them. The household network is the whole of this ring. The outer ring is what the desk leaves alone: the household's own devices and services. The desk neither supports nor advises on those, because it has no standing to and no hours for it.

Each ring has a different verb, and the verb is the point. For the inner ring the desk fixes. For the middle ring the desk checks its own side, explains what the evidence shows, and suggests; it does not configure, visit or promise. For the outer ring the desk declines, kindly, with the reason and with whatever alternative exists. A technician who knows which ring a request is in knows which verb to use before they pick up the phone. That is most of the forty minutes saved. The table later in this article puts the common requests in their rings. The sections before it explain why each one lands where it does.

Ring One: The Organisation's Devices

The inner ring is everything the organisation put in the person's home. The rule is that the desk supports it as if it were on a desk in the building. The laptop on the standard build. The dock, the monitor, the keyboard, the mouse and the headset the organisation shipped. The VPN client and the second-factor app, wherever the second factor lives. The accounts, the mail, the applications. If it came in a box from the desk, the desk owns it, including when it fails at home and has to come back by courier. That is the subject of Shipping and Swapping Hardware.

Two items sit on the ring's edge and need a line each. The first is the phone that carries the second-factor app. If the organisation issued the phone, it is inner ring. If the app is on the person's own phone, the desk supports the app and the enrolment and nothing else about the phone. The practice for that split is in the mobile series. The policy that allows a personal phone to carry work at all is in BYOD and Personal Devices. The second is the peripheral the person bought themselves because the standard one was not to their liking. The desk will plug it in and try it, once. If it does not work with the standard laptop the answer is the standard peripheral. That is what the desk owns and will ship. A monitor the organisation did not buy is a monitor the organisation cannot replace. It is kinder to say so before it fails than after.

Ring Two: The Household Network, Partly

The household network is the middle ring on its own, because the organisation's work cannot happen without it and the desk cannot touch it. The desk can see one side of the connection, the laptop's, and can read what the laptop reports about signal, speed and the VPN. It cannot see the router, the provider's line, the other devices sharing the connection, or the loft the laptop is being used in. "Partly" means exactly this: the desk checks everything on its own side first and explains what the readings point to. It suggests what the person can do or ask their provider for, and then stops. It does not reconfigure the router, call the provider on the person's behalf, or send anyone to the house.

The triage itself, the household bandwidth, the distance from the router, the VPN factor and the ten-minute self-check the person can run before raising a ticket, are the subject of The Home Network Variable. This article takes that method as given. What belongs here is the order of operations the scope commits the desk to: its own side first, every time, before a word about the house. A desk that opens with "it's probably your Wi-Fi" has skipped the laptop, the VPN and the question of whether every remote colleague is seeing the same thing this morning. That desk will be wrong often enough to lose the right to be believed when it is right. Check the organisation's side. Then say what the evidence shows. The house comes last, and it comes as a finding, not a verdict.

The honest sentence about the middle ring is one the whole desk uses. It goes in the scope so the words are the desk's rather than the technician's. "Your home connection is yours or your provider's, so we cannot change it, but we will always check our side first, tell you what the readings show, and suggest what usually helps." That sentence has never once made a remote worker angry. "That's your network" has, every time, because it sounds like the desk has found the exit.

Ring Three: The Personal Printer and Everything Else

The outer ring is the household's own equipment. The personal printer is its emblem because it is the item the desk gets asked about most and can help with least. The desk did not buy it, cannot replace it, does not know its model, has no spare for it and has no way of knowing what the household has done to it. More to the point, the organisation's laptop has a standard build that may or may not allow a printer to be added. Whether it does is a security decision rather than a support one. The scope's line is short: the desk does not support personal printers, and the knowledge base says plainly what, if anything, the standard laptop allows. The person who needs to print for work gets the organisation's answer to that. It is usually a printer the organisation provides for the role or a reason the role does not print. It is not forty minutes of a technician reading a manufacturer's page aloud.

The rest of the outer ring follows the same logic. The family computer, the son's laptop that wants the VPN, and the television that will not reach the wireless are not the organisation's. Neither are the smart speaker, the games console, or the provider's own app. A desk that touches one has taken responsibility for it without the authority, the spares or the hours to carry that through. The son's laptop is worth a specific line, because the request is common and the answer is a security one. The organisation's VPN is for the organisation's devices, and a personal device on it is the policy question that BYOD and Personal Devices answers. The desk does not answer it at half past two on the phone. It points to the policy and, if the policy allows it, to the process.

Leaving the outer ring alone is not unkindness, and the scope should say why in one sentence, because the person asking will want to know. The reason is that the desk can only promise what it can deliver. A desk that helps with the printer once has promised to help with it every time, for every remote worker, with every printer, for as long as the organisation exists. Nobody at the desk agreed to that. (The printer, naturally, is counting on nobody having noticed.)

The Standard Home Kit Is the Boundary Made Physical

The simplest test of which ring an item is in is whether the organisation shipped it. That is why the standard home kit, the fixed set of equipment the organisation provides to a remote worker, is the boundary in physical form. If it came in the box, it is owned. If it did not, it is helped with or left alone. The kit's contents, what is reimbursed rather than shipped, and the ergonomic question handled kindly are the subject of Home-Office Equipment: What the Organisation Provides. The scope links to it rather than listing the items again. What the scope adds is the rule: the kit is the ring. A request for support on something outside the kit is a request to move it inside. That is an equipment request, not a support ticket.

One item in the kit does more boundary work than the rest. It is a network cable long enough to reach from the router to the desk. Half the middle-ring tickets are a laptop at the edge of a wireless signal. The cable turns a household network problem the desk cannot fix into a piece of owned equipment the desk shipped. It costs almost nothing, ships in the same box as the laptop, and changes the conversation from "your Wi-Fi" to "try the cable we sent". Put it in the kit. Put it in the scope. Mention it first when the connection drops.

Saying It Kindly and in Writing

The boundary fails in the saying more often than in the drawing, and the saying has a shape. First, what the desk checked on its side, specifically. Second, what the evidence shows, in plain words, without blame. Third, what the person can do, cheapest first, including anything the organisation provides. Fourth, what the desk will do next, even when the honest answer is "nothing more on this, but I will look again at the laptop readings on Monday". A reply with the first three and not the fourth reads as a door closing. The craft of the alternative, and why a no without one is a wall, is in Offering an Alternative Instead of a Wall. The home scope is where that craft gets used most.

Here is the shape applied to Farah's printer, in the reply Nadia asked Owen to send. "I've checked the laptop and the print service on our side and both are fine, so the statements will print to any printer the laptop can see. The laptop is built so that a home printer can't be added by the desk, which is a security setting rather than something I'm choosing. Two things will work. The statements can go to the secure print at the Harbor Street branch for collection. Or your manager can raise an equipment request for a provided printer, which the underwriting team has for people who print regularly. I'll leave this ticket open until you tell me which you'd like, and I've linked the equipment request form." The reply says no to the printer and yes to printing, which is what she asked for.

The scope lives where the remote worker will see it before they raise the ticket: in the knowledge base, readable without signing in. It is linked from the remote team's request form and from the home-office equipment policy. If you run QuerySolv, the remote team can raise its tickets on a form of its own. The scope can sit in QuerySolv's knowledge base as an article visible to everyone, so the two are a link apart. In any tool, the aim is that the person reads "we check our side first, we don't support home printers" before they type, not after. A scope nobody can find is a scope the desk is going to explain by phone, which is where this article started.

Exceptions, and Who Decides Them

A scope with no exception path is a scope people will go round. So the path is written into it, with a named decider and a bounded answer. The genuine exceptions are few and recognisable. One is a person whose home connection cannot carry the work at all. The honest answer may be a mobile data device the organisation provides or a different working arrangement. That is a manager's decision. Another is an adjustment for a disability or a medical need. That goes through whatever process the organisation has for adjustments and comes back to the desk as owned equipment. There is also a role that genuinely prints at home. That is an equipment decision for the role, not a support decision for the printer. And there is the executive who would like the home office wired. That is a decision for someone above the desk and is handled the way any request from above is handled. The decision is escalated to its owner, the alternative is offered meanwhile, and the answer is recorded on the ticket.

The technician on the phone does not decide any of these, and the scope says so, which protects the technician as much as the rule. "That's not a call I can make from the desk; the person who can is your manager for the connection, and I've put a note on the ticket for them" is a sentence that ends the forty minutes without ending the help. Every exception, granted or declined, goes on the ticket in the decider's words, with its end date where it has one. The quarterly review reads them together. Three exceptions for the same thing are a line in the scope that needs changing.

Keeping the Scope Honest

The scope drifts in two directions, and the tickets show both if someone looks. It drifts outward when technicians help with outer-ring things anyway, because the person was nice and the fix looked quick. In that case, the hours vanish inside tickets labelled "printing" or "connectivity". It drifts inward when technicians say "not supported" to middle-ring tickets to save time. In that case, the remote workers stop raising them and start living with a connection that the desk's side could have improved. Neither drift is visible in the ticket count. Both are visible in a quarterly read of thirty remote tickets, each one asked two questions: which ring was this, and did the desk do the ring's verb.

Mark the ring on the ticket, if the tool has a field or a tag for it, and the read becomes a filter rather than a reading. A rising count of outer-ring tickets means the scope is not being seen before people type. The fix is where the scope is linked from. A rising count of middle-ring tickets means the home-network self-check is not being found, or the cable is not in the kit. A technician whose outer-ring tickets run long is being kind in a way the desk cannot afford. In that case, the conversation is about the sentence to say, not about the kindness. The whole measurement of remote support, including what the ring counts belong beside, is the subject of Measuring Remote Support. The scope only needs the two questions.

A Short War Story: The Router in the Loft at Meridian Parts

At Meridian Parts, a buyer called Aled worked from a loft office at the far end of a long house. Over three months the desk's most patient technician, Bea, spent eleven hours across nine tickets on his connection. She walked him through router settings by phone and tried two different wireless channels. She suggested a mesh unit he bought and she then helped configure. Once she stayed on a call for ninety minutes while he moved the router between rooms. Every ticket was logged as "connectivity", and every one was closed as resolved. Every one came back within a fortnight, because the house was long and the loft was far and none of what Bea was touching belonged to the organisation. The desk lead found the pattern only when Aled, reasonably, asked why the fix never held and whether someone could come out. The hours were added up for the first time. The written scope that followed put the household network in the helped ring, with the desk's side checked first and the cable mentioned first. Aled's next ticket was answered with a cable long enough to reach the loft, which worked in an afternoon. Eleven hours had been spent being kind about a problem the desk could not own, when the kindest thing had been in the stock cupboard all along.

The Home Support Scope

The template below is the scope itself, written once by the desk lead and the person who owns the home-office equipment policy. It is published where remote workers raise tickets and reviewed quarterly against the ring counts. Section A is the owned ring and the promise that goes with it. B is the helped ring and the order the desk commits to. C is the left-alone ring with its reasons and alternatives. D is the exception path with its deciders, and E is the sentence every technician uses. Keep it to one page. A scope longer than a page is a scope the remote worker will not read before typing. The whole point is that they do.

HOME SUPPORT SCOPE — ONE PAGE
Organisation: ______________________   Owner: ______________________   Reviewed: ____________

A. WHAT THE DESK OWNS (supported at home exactly as in the building)
   [ ] The laptop on the standard build, and everything installed on it
   [ ] The dock, monitor, keyboard, mouse, headset and cable the organisation shipped
   [ ] The VPN client, the second-factor app, the accounts and the applications
   If it fails: phone-and-photo checks first; a swap by courier the same day if they fail.
   Replacement is from the standard kit. Spares are kept ready: yes / no

B. WHAT THE DESK HELPS WITH (the household network)
   The desk cannot change your home connection, your router or your provider's service.
   The desk will, every time and in this order:
   1. Check the laptop, the VPN and whether other remote colleagues are affected
   2. Tell you what the readings show, in plain words
   3. Suggest what usually helps: the cable from the kit, placement, timing, what to ask your provider
   The self-check to run before raising a ticket: ______________________ (link)

C. WHAT THE DESK LEAVES ALONE (with the reason and the alternative)
   Personal printers ........ the standard laptop allows: ______________________
                               printing for the role is arranged by: ______________________
   Household devices ........ family computers, televisions, consoles, the provider's own equipment
   Personal devices at work . see the personal-device policy: ______________________ (link)
   Reason: the desk can only promise what it can replace, repair and be responsible for.

D. EXCEPTIONS AND WHO DECIDES
   A home connection that cannot carry the work ..... decided by: ______________ (manager)
   An adjustment for a medical or access need ........ through: ______________________
   A role that must print at home ..................... equipment decision by: ______________
   Anything else .................................... escalated to: ______________; alternative offered meanwhile
   Every exception is recorded on the ticket in the decider's words, with its end date.

E. THE SENTENCE EVERY TECHNICIAN USES
   "Your home connection is yours or your provider's, so we can't change it, but we will always
    check our side first, tell you what the readings show, and suggest what usually helps."

Nadia published Bluewater's scope the following week, with the cable in section B and the printer in section C. Owen's next printer call lasted four minutes, ended with an equipment request, and was logged in the helped ring by mistake. The quarterly read caught that, and nobody minded. Farah chose the provided printer. The washing machine, which was never the desk's, still drops the wireless in the conservatory. Farah now works through a cable that reaches it.

Frequently Asked Questions