Splashtop SOS: Attended Sessions and Handoff Documentation
An educational overview of how attended remote sessions are documented: consent, defined scope, activity notes, and structured closure. This page explains documentation practice only and does not offer real technical support.
Understanding Attended Remote Sessions
In an attended session, the end user stays present at the device while a technician connects for a limited purpose. In the Splashtop SOS model, connection typically begins when the user shares a short-lived session code, and it ends when either side closes the session window.
Because the user remains at the screen, attended sessions are a documentation exercise as much as a technical one. The record should state who participated, what the session was allowed to cover, what was observed, and how the connection was closed. Nothing on this page is an offer of support services: it is a study of how such interactions are written down so that a later reviewer can reconstruct them.
Consent and Session Scope
Consent in an attended session is specific, not general. Before viewing anything, the technician restates the reported problem and names the parts of the system the session may touch: a settings panel, a print queue, or a single application window. The user can narrow that scope or end the session at any moment.
A well-kept record notes the scope as agreed, not as assumed. If the review drifts toward material outside the stated purpose — personal files, credential prompts, unrelated applications — the correct documentation action is to stop and re-confirm boundaries, never to proceed quietly.
Scope, consent status, observations, and closure status are recorded as separate fields rather than one narrative note.
What a Handoff Record Captures
Whether or not the reported issue is resolved, the closing record for an attended session documents the same core elements.
Participants & Consent
Who took part, who authorized the session, and the moment consent was confirmed.
Observations
What was actually seen during the session, kept separate from guesses about root cause.
Closure
When the connection ended, who ended it, and confirmation that nothing was left behind.
Next Owner
If the issue is unresolved, a named responsible specialist and the open questions they inherit.
Educational Context Only
This page describes documentation conventions for attended sessions in general terms. It is not affiliated with any vendor and does not provide, sell, or arrange remote technical support. For editorial questions, use our Contact Information or see the Disclaimer.