Remote control & attended support sessions
How this is scored
What a technician can do in a session with a user who is present: starting a session from a code, link or small support client without admin rights, viewing and controlling the screen with good image quality at low bandwidth, multi-monitor switching, file transfer, clipboard, chat and voice, remote reboot with automatic reconnect, running as administrator and crossing UAC or elevation prompts, session handover to a colleague, whiteboard or annotation, screen sharing in the other direction, and which operating systems can be supported (Windows, macOS, Linux, iOS and Android, including control rather than only viewing of mobile devices).
0 — No remote control of another device; a meeting or chat tool with screen sharing only.
3 — Screen viewing and control of Windows or macOS with a session code; file transfer, reboot and reconnect, elevation and mobile support are basic or not described.
5 — Attended sessions by code or link with a support client that needs no installation, Windows, macOS and Linux supported, multi-monitor, file transfer, chat, clipboard sync, reboot and reconnect, running with admin rights, and viewing or controlling Android or iOS devices described.
8 — Elevation across UAC documented, session handover and invitation of a second technician, annotation and voice, control of Android devices from named makers and iOS screen sharing, performance at low bandwidth and high resolution documented, and browser-based technician and user sides.
10 — A session that handles everything a help desk meets: every major platform including headless Linux, mobile and rugged devices, every session feature documented per platform with its limits, accessibility of the technician console, and quality and latency figures published.
The Skeptic
Sessions start from an ID the user reads out after a client download — one capture says participation is only possible via the client, another that users can be supported entirely without installation, so the pages give different answers there. What is documented is broad: control of Windows, macOS, Linux, ChromeOS, Raspberry Pi, Android and iOS, control of any Android device regardless of maker, screen sharing for iPhones and iPads, file transfer, mobile-to-mobile sessions, a technician side that runs in any browser, and a global access network promising stable connections where bandwidth is low. We found no public information on crossing elevation prompts, handing a session to a colleague, annotation, voice or chat, multi-monitor switching, or reboot with automatic reconnect. 2 3 4