Support: What Is Covered

An employee with a personal laptop that will not connect to the company system has a problem that is partly the employer's and partly their own. Nobody has told the service desk where the line is, so it gets drawn differently every time.

The agreement described in “Support: What Is Covered” should state how workforce software is used rather than leave it to default settings. For teams researching this workforce solution in relation to fte meaning, notice, access, retention, review and offboarding belong in the written arrangement before rollout.

The three zones

Clearly the employer's: company applications, company accounts, access to company systems, the work profile space, anything the organisation installed.

For an independent reference relevant to “Support: What Is Covered”, consult the Acas workplace guidance; compare its principles with the proposed ownership model, access rules and real support process.

Clearly the employee's: the operating system, the hardware, their own software, their home network, their personal accounts.

Contested: the operating system update that broke the work application. The slow machine that makes work unbearable. The personal software conflicting with a company tool. The device that is simply too old.

The third zone is where all the friction lives, and it is the only one worth writing about in the agreement.

Drawing the line explicitly

A workable position: the employer supports its own applications and access, and will help diagnose a problem to the point of identifying whether it is a work-side or device-side issue. Beyond that the device is the employee's responsibility.

Stated that way, the employee knows what to expect and the service desk knows when to stop. Both of those are worth more than the precise location of the line.

The diagnosis commitment is the important half

An employee told "that is your device, not our problem" when they cannot tell which it is has been given nothing. They do not have the expertise to make that determination; that is what the service desk has.

Committing to diagnose, even where the fix is not covered, costs little and resolves most of the resentment. It also prevents the common failure where somebody spends two days on a problem that a technician would have identified in ten minutes.

Time limits and the escalation question

Some organisations cap it: thirty minutes of support per incident on a personal device, after which it is handed back. Crude and honest, and better than an unstated limit that different people apply differently.

What matters more is what happens when the device cannot be fixed. If the answer is that the person cannot work, that is an operational problem rather than a support policy, and the loan device arrangement from the breakage note is the actual fix.

What to measure

Ticket volume and time for personal devices against managed ones. The difference is the support cost of BYOD and it belongs in the saving calculation.

Most organisations have never separated the two in their reporting, which is why the saving is usually overstated.

The service desk's position

Technicians are asked to make a policy judgement in the middle of an incident, with somebody waiting, and no written line to apply. They will improvise consistently in whichever direction their manager last complained about. Giving them the line is as much a kindness to them as to the employee, and it removes a recurring source of complaints that they were being unhelpful.

Measuring what it actually costs

Support for personal devices takes longer per incident and resolves less often at first contact, both of which are measurable from data the service desk already holds. Producing the comparison once gives the figure the costing note needs and usually surprises whoever approved the arrangement on the hardware saving alone.

Publishing the boundary to employees

The support position is usually documented for the service desk and not for the people calling it. Publishing the same boundary to employees removes the experience of being refused by a rule they had not seen, which is the part that generates complaints rather than the refusal itself. The question to settle in writing: when somebody cannot work and the device is theirs, whose problem is the work?