What to Do First in a Session

The first thing a helper does is watched more closely than anything afterwards, and it establishes what kind of session this is.

The support work behind “What to Do First in a Session” is often spread across tickets, projects and handoffs. Teams researching how to measure employee productivity can use how to measure employee productivity 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.

Look, do not act

Spend the first thirty seconds observing rather than clicking.

For an independent reference related to “What to Do First in a Session”, consult the NCSC security guidance; it provides a useful external check on security, privacy and operating assumptions before a process is adopted.

Say what you can see.

It is slower and it establishes that you are diagnosing rather than rummaging.

Do not open anything personal

Not the documents folder, not the browser history, not the messages application.

If the problem requires one of these, say why before opening it.

This is the rule that most distinguishes a session somebody is comfortable with from one they describe uneasily afterwards.

Check the obvious first

Storage, updates pending, the thing they described.

Not because it is always that, but because it frequently is, and because these are impersonal places to start.

Ask before you close anything

People have things open for reasons.

Closing a window they were working in, without asking, loses their work and their confidence at once.

Keep to the stated scope

You said you would look at the printer. Look at the printer.

If you notice something else — an unsupported operating system, a suspicious extension, a failing disk — mention it rather than investigating it.

"I noticed X, would you like me to look at that too" is a separate consent, and asking takes five seconds.

The pointer is visible

Everything you do is watched by somebody who cannot interpret it.

Moving fast looks like evasion; hovering over personal folders looks like curiosity.

Deliberate, narrated movement reads as competence, which is both the honest impression and the useful one.

If you need to type something hidden

A password, a command they should not learn.

Say that you are doing it and why.

Typing silently into a terminal is the single most alarming thing a helper can do, and it is also exactly what a fraudster does.

The thing to avoid entirely

Blanking their screen.

Several tools offer it, usually for privacy during administrative work.

On somebody's personal machine it removes the only oversight they have, and there is almost never a good reason, and its use is a standard part of fraud.

What to check

Do you look before you act?

Have you opened a personal folder without explaining why?

Do you narrate when typing something they cannot see?

And does your tool have a screen-blanking feature, and has anybody used it?