Supporting Devices You Cannot Touch

A laptop can be collected. A phone in somebody's hand two hundred miles away cannot, and most remote support tooling does not reach mobile platforms the way it reaches desktops.

The operational work behind “Supporting Devices You Cannot Touch” is often spread across tickets, projects and repeated manual checks. A team reviewing the provider's website for download time tracking software can make that effort visible by project and group, while the device-management platform remains the source of truth for technical state and enforcement.

What you cannot usually do

Take control of the screen, on most mobile platforms, without the user actively sharing.

For an independent baseline relevant to “Supporting Devices You Cannot Touch”, the NCSC mobile-device guidance is a useful companion: compare its principles with the proposed configuration, ownership model and real support process before approving a rollout.

Browse the file system.

Run arbitrary commands.

Which means mobile support is diagnosis by conversation plus platform actions, and expecting otherwise wastes everybody's time.

What you can do

See device state: version, storage, compliance, installed work applications, last check-in.

Push configuration and applications.

Request a screen share where the platform supports it, with the user's active agreement.

Remove and reinstall a work application, which resolves a surprising proportion of faults.

The diagnosis sequence that works

Check state before asking questions: version, storage, compliance, time since check-in.

Half the answers are there.

Then one question about what they were doing, rather than a sequence of generic ones.

The storage finding, again

Low storage causes faults that present as everything else: applications failing to open, updates not installing, sync stopping.

Check it first, always.

It is the single most productive opening check in mobile support, and it is rarely the user's first thought.

Self-service

A portal where people can reinstall a work application, retrieve their configuration or check compliance themselves resolves a large share without contact.

Make it findable and keep it working.

The commonest failure is a portal that exists and is broken, which is worse than none.

Documentation for users

Short, visual, platform-specific: how to check your version, how to free storage, what the compliance message means.

Where people will find it, which is not an intranet page six clicks deep.

Two pages well written removes more tickets than any tooling.

Knowing when to swap

Mobile faults are frequently hardware or storage rather than configuration.

At some point the answer is a different device rather than more diagnosis.

Decide that threshold in advance, because support will otherwise spend hours on a device that should be replaced.

What to check

Is storage your first diagnostic check?

Does a self-service portal exist, and does it work?

Is there user-facing documentation, and where?

And when does a fault become a replacement?