Before You Connect: What to Say
Four sentences that change the whole session, and the reason each one matters more than it appears.
The session is decided before it starts. What is said in the preceding minute determines whether the person is cooperating or submitting.
The support work behind “Before You Connect: What to Say” is often spread across tickets, projects and handoffs. Teams researching how to calculate idle time can use the official product page 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.
The four sentences
"Here is what I think is wrong and what I am going to do."
For an independent reference related to “Before You Connect: What to Say”, consult the NCSC security guidance; it provides a useful external check on security, privacy and operating assumptions before a process is adopted.
"You can end this at any time — here is how."
"I will tell you what I am doing as I go."
"Please close anything private before we start."
A minute, and almost nobody says them.
Why the first
It gives the person a reference to check against.
They cannot verify a command, but they can notice that you said you were checking printer settings and are now in their documents.
Without a stated intention there is nothing to notice against, which is the whole of the verification problem.
Why the second
Most people do not know they can stop it.
That knowledge changes the relationship from one of permission granted to one of permission continuing, which is a materially different thing.
And it is the single most useful fact a person can carry into any future session, including one they should not have agreed to.
Why the third
Narration is the only running account the person has.
Its own note covers how to do it without being tedious.
Why the fourth
Everybody has something open they would rather not show.
Asking saves the awkwardness, protects them, and signals that you are not interested in anything else.
Ten seconds, and it is the sentence people most appreciate afterwards.
What else to establish
How long you expect it to take.
Whether anything will be installed, and whether it stays.
Whether the session is recorded.
Each is a thing people would want to know and would not think to ask.
In a workplace
The same four, plus the organisational context: this is logged, here is who can see it, here is the reference number.
Formality helps here, because it distinguishes a legitimate session from the kind that begins with a phone call out of the blue.
When helping a relative
The same four, slower.
Especially the second: teaching somebody that they can end a remote session, and how, is a protection they keep for life.
It is the most useful ten seconds you will spend with an older family member's computer.
What to check
Do you say all four, or none?
Does the person know how to end the session?
Do you say how long it will take?
And does anything get installed without being mentioned?