A client asks to see one workflow. You have five minutes before their next call. This is the wrong moment to introduce an installer, an account form, or a meeting lobby.
Use the conversation as the starting point. Create a room, paste the invite into chat, and show the product. Linkside keeps the setup short: host and guest use their browsers, with no Linkside account or software to install.
Prepare the path, not a presentation
Choose one useful outcome for the remote demo. If the client wants to see how an approval works, start with an item ready to approve. Do not spend the first minute creating sample data or moving through settings that do not answer the question.
Before you send the link:
- Open the exact account, record, or workspace you will demonstrate.
- Put the product in its own browser window or tab.
- Close customer data, internal dashboards, and unrelated messages.
- Silence notifications that could appear over the shared area.
- Write down one closing question, such as “Would this fit your current review step?”
Host from desktop Chrome or Edge, Linkside’s recommended setup for screen sharing. If one state depends on unreliable test data, keep an approved screenshot of that state nearby and return to the live product for the rest of the path.
For a fuller setup rehearsal, use the 30-second room walkthrough before the client call.
Send the demo link in the chat you already use
Create a Linkside room, then select Invite link in the room header to copy it. Paste it into your active sales or support thread with one direct line:
Open this link in your browser. There is nothing to install and no account to create.
With the default room settings, the client opens the invite, keeps or changes the generated nickname, and selects Join room. Linkside does not ask for their email address or an account password. The nickname belongs to this room; there is no lasting Linkside profile to configure. The reasoning behind that choice is covered in why Linkside requires no account.
Do not start sharing while you wait. Confirm that the right product state is open, then select Start sharing after the client joins.
Run the live product demo in five minutes
Use the five-minute limit as an agenda for one question and one product path, not as a promise about connection time. Start the clock once both people are in the room, after any browser-permission or network troubleshooting:
| Time | What to do |
|---|---|
| 0:00–0:30 | Confirm the question: “You wanted to see how approvals reach the owner?” |
| 0:30–1:30 | Show the finished outcome first, so the client knows where you are going. |
| 1:30–3:30 | Walk through the shortest realistic path that creates that outcome. |
| 3:30–4:30 | Repeat the step that answers their concern and pause for one question. |
| 4:30–5:00 | Agree on the next action, owner, and timing. |
Narrate decisions, not cursor movement. “I am assigning an owner so the request cannot sit unclaimed” gives the click meaning. “Now I click this button” merely describes what the client can already see.
Share the narrowest useful surface. For a flow contained in one product tab, choose that tab in the browser’s picker. If the flow crosses product tabs, put them in a dedicated window and choose that window instead of the whole desktop. Our guide to sharing one browser tab explains how to keep inboxes and other work outside the frame.
Give a short, accurate trust answer
If the client asks where the screen goes or whether the session is recorded, give them the practical answer first:
Linkside tries to send the screen share directly from my browser to yours. The browsers encrypt the media in transit. If the network blocks a direct connection, Linkside can route the encrypted media through a relay. Linkside does not record or transcribe the session. When I end the room, it closes immediately.
The more precise boundary is this: Linkside uses WebRTC’s DTLS-SRTP encryption on both the direct path and the relay fallback. Its signaling service can observe that a room exists, roughly when a guest joins, and how long the session lasts, but it does not carry the media. If TURN relay fallback is needed, the relay sees encrypted packet routing but does not hold the browser-managed media keys. After End room makes the room unavailable, the signaling service keeps a terminal record for a five-minute tombstone period and then deletes it. For more detail, read how screen-sharing encryption works.
There will be no Linkside recording to send afterward. Capture approved notes and next steps in the client system you already use.
Plan for the two interruptions that matter
If Linkside reports that a messaging or social app’s built-in browser is unsupported, ask the client to copy the same invite into Chrome or Edge. A supported mobile browser can join as a viewer, but hosting and sharing require a desktop browser.
If a restrictive network prevents the direct connection, Linkside can fall back to the encrypted relay. A free room gets five minutes of relayed media; a licence removes that time limit. If the demo may run longer, test from the same host browser and network first. When that test needs the relay, activate the licence before the client joins.
End with the promised next action, then select End room. The agenda has one test: did you answer the opening question and record who owns the next step? If so, stop there.