How a remote support session actually works

Here is the short version, because this is the part that worries people: you click a link, a technician sees the screen you are showing them, you keep your own mouse, and you end the session whenever you like by closing a window. Nothing is installed permanently, and nobody can reconnect later without you going through the whole process again.

The rest of this article walks through each step: what the technician can and cannot see, what gets fixed well remotely, what still needs someone in the room, and the two minutes of preparation that make a real difference.

What happens, step by step

1. You call. We talk through the problem. A few minutes is usually enough to know whether a remote session is the right tool at all.
2. You get a link, by email or text. It comes from us, while we are already on the phone together.
3. You click it. A small program downloads and opens. On some systems you have to confirm once, and the program’s name is shown on screen.
4. A number appears. You read it out over the phone. Without that number nobody can connect, and it is different every time.
5. You accept the connection. A window asks for your explicit permission. Until you answer, nothing happens.
6. We work, staying on the phone. You watch the cursor move and you see everything that is done.
7. We finish. The program closes and removes itself. The connection no longer exists.

Notice the pattern: at no point does a technician simply arrive. It takes your call, your click, your code and your acceptance.

You keep the mouse, and the exit

This is the most common fear, and the answer is reassuring.

Your mouse and keyboard keep working throughout the session. If you move the mouse, it moves. You are not a spectator watching your own computer: you can take over at any moment, and a good technician will regularly ask you to do a step yourself, because that is how you come away having learned something.

To end a session there are always at least three ways, easiest first:

• close the little window belonging to the connection program;
• say “stop, I want to stop” on the phone;
• unplug the network cable or turn off Wi-Fi, which cuts everything instantly.

None of the three breaks anything. An interrupted session simply gets picked up later.

What the technician sees, and what they don’t

Let us be precise rather than reassuring at any cost.

They see whatever your screen is displaying. An open document is visible. Desktop icons are readable. If you open your email during the session, they see your email.

They do not see anything that is not on the screen: your other devices, your phone, a USB stick that is not plugged in. They also do not see the characters of a password in a field that masks them with dots.

What you should know anyway: a technician holding the keyboard has, technically, the same reach you have sitting at your own computer. They could open a folder. That is exactly why two rules exist: you stay in front of the screen for the whole session, and you close anything sensitive before you start. This is not suspicion, it is ordinary good practice, and a serious technician will suggest it before you do.

Most tools also log the date, time and length of every session. You are entitled to ask for that record.

Why nobody can reconnect tomorrow

This is the question we get asked most, and it is a fair one.

The program used for a one-off session is what is called a single-use module. It does not install like ordinary software: it downloads, runs for the length of the session, and deletes itself when it closes. The access code that goes with it is valid exactly once.

For a technician to be able to come back without you, they would have to install permanent access software. That is a separate, visible operation. It asks for your administrator password and it shows up in your list of installed programs. Businesses do it, for good reasons. It never happens without being told.

If you want to check afterwards, open the list of installed applications and look for the name of the program you opened. If it is not there, it is not there.

The difference from the stranger who called you

This is the heart of the matter, and the distinction is simple: who dialled the number?

A legitimate support session starts with your call, to a company you chose, whose name and address you know. You know why you are calling. You can hang up and call back later.

A scam starts with an incoming call, a red window on screen, or an alarming email. You are hurried, told not to hang up, asked to install something right now, and payment is in gift cards. The remote software can be exactly the same product: what separates the two is where the contact came from, not the tool.

If you did not place the call, it is not tech support. Spotting a tech-support scam goes through the signs, and it is worth reading before the next pop-up appears.

What gets fixed well remotely

A large share of everyday computer work needs nobody in the room:

• A slow computer, a clean-up, programs that launch themselves at startup.
• Updates that stall or have been failing for months.
• Email: an account that stopped receiving, a setup to redo, a password to change properly.
• Printing, when the problem is on the software side: a driver, a stuck queue, a printer that says it is offline while sitting there switched on.
• Backups: setting one up, checking it, restoring a file to prove it works.
• Cleaning up after a fake alert, to establish what was actually installed.
• Learning to use something. Showing you a procedure on your own screen usually works better than describing it over the phone.

The big advantage is speed. No appointment to fit between two other visits, no travel fee, and often the same day.

What genuinely needs a visit

It is worth being honest about this, because promising otherwise wastes everyone’s time.

• Hardware. A drive to replace, a broken screen, a computer that will not power on, a fan making noise.
• A computer that will not start. With no working system there is nothing to connect to.
• No internet at all. Obvious, but it needs saying: remote support needs a connection.
• Wi-Fi and coverage. Moving a router, measuring signal in the basement, running a cable: that happens on site.
• Physical setup. A television, an antenna, a printer still in its box, a desk to assemble.
• Someone who is not comfortable with the computer at all. If clicking a link is already the obstacle, a first visit in person is both kinder and faster.

Often the right answer is a mix: one visit to install and connect everything, then remote support for whatever comes after.

How to prepare in five minutes

1. Close anything sensitive. Online banking, personal documents, tax papers, a private conversation. This is the most useful item on the list.
2. Plug the computer in. A battery dying halfway through an update makes everything harder.
3. Keep the phone within reach, and ideally not on the same device being worked on.
4. Write the problem down in one sentence, with the exact error message if you have one. A photo of the screen taken with your phone is worth a great deal.
5. Avoid typing passwords during the session if you can. If one is unavoidable, say so: the screen view gets paused while you enter it.
6. Plan to be there. You are the pilot. Nobody should be working on a computer left alone in an empty room.

How long it takes, and what it costs

Most routine remote work runs between thirty minutes and an hour and a half. A well-described problem gets fixed faster than one discovered along the way.

At QC Tech Support the rate is $100 an hour for everything, remote or on site, and only a home visit adds a $75 travel fee. Remote support is available anywhere in Quebec, every day from 8 a.m. to 10 p.m. The details are on the pricing page, and the service itself is described under remote support.

If you are still hesitating, call and ask your questions before clicking anything at all. That is precisely what a cautious person does, and it is the right instinct.