For people who do support for a living

Remote support, when it is your job

Ten sessions a day is a different problem from one a month. This is the side you need: every client station in one place, access you can withdraw at any point, and a record of each connection that was accepted.

What changes

Three things that only matter at volume

The time between sessions

At one session a month, a minute lost getting connected is nothing. At ten a day it is an hour a week. What matters is how fast you get from the phone call to the client screen.

The client is not technical

The person at the other end does not know what a port is, and has no reason to. All they do is open the app and press Accept — no installers, no router settings, no passwords read out over the phone.

Answering who, and when

Working on someone else's computers, the question comes up sooner or later. Every session is recorded — who connected, which station, how long — without ever storing what appeared on the screen.

Tools

What you use every day

The fleet, in one portal

Claim, rename and remove stations from a single place. See which one is online right now, without making a call to find out.

Session history

Usage and session history for every device. Useful for invoicing, and necessary the day somebody asks what happened on Tuesday.

Unattended access you can revoke

Reach authorised stations without anyone pressing Accept — through a cryptographic authorisation, not a shared password. And revoke any device remotely, at any time.

Several stations at once

Every session lives in its own window. Watch a long update run on one station while you work on another.

Clients ask for help in one click

They request assistance from inside the app and the notification reaches you. No more explaining over the phone where to click to give you access.

Files and clipboard, in session

Send an installer or pull a log file without a separate tool. Copy on one side, paste on the other, as though it were the same computer.

What it looks like

A clean session with a client

Four steps, the same every time. Not because it is complicated, but because repeatability is what turns help into a service.

  1. The client requests assistance from the app, or you ask them to open it.
  2. You connect. They see who is asking and press Accept — or decline.
  3. You work. Their screen stays on throughout; there is nothing they cannot see.
  4. You end the session and tell them what you did. It stays in the history, if it is ever needed.

At no point in those steps do you ask for their password. You do not need it — and the habit matters, because it teaches them what normal looks like when the next caller is not helping at all.

How to help someone remotely without asking for their password →

Plans

Which plan you need

Working on your own

Pro is licensed for commercial use by a single user, with unlimited session time and unattended access. It starts with a 7-day trial, no card required.

There are several of you

Team adds users working in parallel and fleet administration. The price depends on how many of you there are, so we settle it in a short conversation.

Try it on a real station

It takes under a minute and needs no card. If there are several of you, write to us and we will work out what fits.