If you have ever helped a family member fix a laptop over the phone, you know the hard part is not always the computer. It is the guessing. “Click the gear icon.” “What gear icon?” “The one near the top.” “I do not see a top.”
What you want is simple: see what they see, then talk them through the next click. Installable remote-support tools can be useful, but an install is a big ask when the person already needs help.
Linkside fits the lighter version of tech support: they show you their screen, you guide them by voice, and nobody installs anything. It is not remote control. That distinction matters.
The flow, end to end
This is the part that can feel backwards at first: the person whose screen needs to be seen should be the host. In Linkside, the host creates the room and shares their screen. You, the person helping, join as a guest.
Walked through on the phone:
- Have them open Linkside. “Open your browser and go to linkside dot io. Choose the option to start sharing.”
- Have them click Create room. “There’s a button that says Create room. Click it.”
- They send you the invite link. Once they are in the room, the header shows an Invite link control. “Click Invite link near the top of the page, then text or paste the copied link back to me.”
- You click their link. That opens the join page in your browser. Enter a name and join their room.
- They click Start sharing. Tell them: “On your end, there is a Start sharing button. Click it. Your browser will ask what you want to share.” Walk them through picking the right window, tab, or screen.
- You see what they see. Voice continues on the phone while you watch.
That is the whole loop. No software install. No account for either side. Just a room link and a call.
The role assignment is the important detail. The helper is the guest, not the host. For support, that is usually the right shape: the person with the problem shows the screen, and the helper watches.
A phone script that actually works
Most failure modes in remote support are communication problems. A few useful phrases, in roughly the order you will need them:
- Opening: “We are going to set this up in your browser. You do not have to sign up or download anything. I will walk you through it.”
- Getting them to create the room: “Open your browser - Chrome or Edge if you have it - and go to linkside dot io. Choose Start sharing, then click Create room.”
- Getting the link back: “Near the top of your screen there is a button called Invite link. Click it. Then text or paste me what it copied.”
- You join, then ask them to share: “OK, I am in. Now there is a button on your end called Start sharing. Click it. Your browser is going to ask what to share. Pick the window or screen you want me to see.”
- When the browser prompt appears: “Your browser is asking permission. This is the browser checking with you. Click Share when you are ready.”
- If they are nervous: “I can watch the screen you choose, but I cannot click or type on your computer. If anything feels wrong, stop sharing or close the tab.”
The “browser is asking” line is the most useful one. Screen sharing uses the browser’s own permission prompt, and the host chooses what to share each time.
What you can do
A short list of support tasks Linkside is good for:
- Diagnose UI confusion. “Click the third item in the menu” works better when you can see whether the menu is open.
- Catch typos in URLs and passwords. Often the only fix is “look at what they typed and notice the
0that should be anO”. - Walk through settings panels. Network preferences, browser settings, app preferences - the kind of nested UI where verbal directions go off the rails.
- Verify what they’re seeing. “I see what you mean about the error” is more useful than “describe the error to me again, slower”.
If both people unmute in the session, you can use Linkside for voice too. For many family-support calls, staying on the phone is simpler.
For the best host experience, use desktop Chrome or Edge. Firefox and Safari may work with caveats, and mobile browsers are usually better for joining than hosting.
What you can’t do (and why that’s a feature)
Linkside is show-only. As the guest watching, you cannot move their mouse, click buttons, or type into fields. The host is the only person controlling the machine.
This is a deliberate constraint, not a missing feature. Two reasons:
- Trust. “I can watch, but I cannot control your computer” is easier to understand than “install this so I can help.” The host keeps control the whole time.
- Scope. Many support calls only need a second set of eyes. If the task needs someone else to type, click, or change system settings directly, Linkside is the wrong tool.
Be precise with the person you are helping: “I can see the screen you choose. I cannot touch anything. You will do the clicking.” That framing keeps the boundary clear.
What Linkside does with the session
For a private support call, trust is not just about who can click. It is also about where the stream goes and what remains afterward.
Linkside is peer-to-peer first. By default, the screen share travels directly between browsers using WebRTC. If a direct connection is blocked by the network, Linkside can fall back to an encrypted TURN relay; the media remains encrypted in transit.
Linkside does not record sessions. There are no chat logs or persistent room histories. Rooms are temporary and disappear when the session ends. The service needs to know that a room exists while it is live, roughly when guests join, and how long the session lasts, but it does not see the screen contents.
When you actually need remote control
If the task requires you to do something on the other person’s machine - not just watch and guide - use a remote-control tool. Examples:
- Entering commands they should not have to type themselves.
- Repeating a long sequence of precise clicks.
- Helping someone who cannot comfortably use the keyboard or mouse while you guide them.
Use a remote-control product when control is what the task actually needs.
For the much larger category of “I just need to see what they are doing,” a link is enough.
What changes when the install isn’t required
The reason browser-based screen sharing matters for support is that the bar for “let me help you” drops. When you ask someone to install software, you add extra decisions before the real work starts. Which download is correct? Is the installer safe? What happens after the call?
A browser-only flow keeps the setup inside a familiar place: their browser, their click, their choice of what to share. The tradeoff is that the person getting help has to create the room and start the share themselves. Walked through calmly, that is usually a small price to pay.
If that fits the support task you’re trying to do, try the flow yourself first: open a room and send the link to your other browser. The next time someone calls for help, you’ll have the script in muscle memory.