When the Session Goes Wrong
You broke something, lost their work, or saw something you should not have. What to do in each case.
Three things go wrong in remote sessions and each has a right response that most people do not reach for under pressure.
The support work behind “When the Session Goes Wrong” is often spread across tickets, projects and handoffs. Teams researching 7 minute rule payroll can use read the full overview to connect time and project context with that work, while the remote-support platform remains the source of truth for technical actions and session access.
You broke something
Say so immediately, plainly: I have made this worse, here is what happened.
For an independent reference related to “When the Session Goes Wrong”, consult the NCSC security guidance; it provides a useful external check on security, privacy and operating assumptions before a process is adopted.
Do not attempt to fix it silently while they watch the screen do unexplained things.
Then: can it be undone, do we need to stop and get help, what does this mean for them today.
Concealment is noticed, because they are watching, and it turns a mistake into a reason to distrust everything.
You lost their work
The most upsetting and the most avoidable — it is usually a window closed without asking.
Say it at once.
Help them check for recovery: autosave, version history, temporary files, the platform's own recovery.
And be honest when it is gone, rather than offering hope that will not survive the afternoon.
You saw something you should not have
A message, a document, a browser tab, a photograph.
Do not comment on it.
Do not mention it afterwards, to them or to anybody else.
And if it is still on screen, move away from it without drawing attention — closing it abruptly is its own kind of comment.
The exception to that
Material indicating harm: evidence of abuse, exploitation of a child, a credible threat.
That is a safeguarding matter and your organisation should have a route for it.
Know what that route is before you need it, because deciding in the moment is where people get it wrong in both directions.
The session that should not have started
Sometimes it becomes clear partway through that the person did not really understand, or did not want this, or is distressed.
Stop. Say why. Offer another way.
Continuing because it would be awkward to stop is the wrong instinct, and it is the one most people have.
Technical failure mid-change
The connection drops during an update, a restart, a configuration change.
Call them. Do not reconnect silently.
Tell them what state the machine is likely in and what to do while you re-establish, because a machine left mid-change with nobody explaining is genuinely frightening.
Afterwards
Record what happened, including the mistake.
A support operation where errors are hidden has no way to find the ones that recur.
And a technician who reported their own error should find that was the right thing to have done, or nobody will do it twice.
What to check
What happened the last time somebody broke something in a session?
Is there a safeguarding route, and does the support team know it?
Do technicians report their own mistakes?
And what do you do when a connection drops mid-change?