Stage the session
An operator starts a session from the console or from a support request. Anslation Remote creates a 9-digit code and shows it once.
Anslation Remote
Your team stages a session and shares a one-time code. The person you help joins in their browser, allows the session when asked and shares a screen. They can stop or leave at any time.
In short
Your team stages a session and gets a 9-digit code that works once and lasts 15 minutes. The person you help opens the join page in a desktop browser, types the code, allows the session when your policy asks and picks a screen or window to share. You watch and chat; they can stop sharing or leave at any time, and your team ends the session.
What happens on each side of a support session, in order.
An operator starts a session from the console or from a support request. Anslation Remote creates a 9-digit code and shows it once.
Read the code out, or send the join link that carries it after a # sign. The code works once and expires after 15 minutes.
The person you help opens the join page in a desktop browser and types the code. No account, no install.
If your policy asks them, they allow the session on the join page. Other policies wait for an admin or a second approver, or start at once.
They click Share my screen and pick a screen or window in the browser’s own picker. You see it live.
Chat and leave pointer notes while you look. They can stop sharing or leave at any time; your team ends the session. Joining, consent and leaving all land in the audit log.
The same session from the console and from the join page.
| Moment | Your team | The person you help |
|---|---|---|
| Before they join | The code’s last digits, its expiry and a waiting status | A box for the 9-digit code |
| After the code | That they joined, and whether consent or approval is still pending | Who is helping them, and an allow or decline choice when the policy asks |
| While sharing | The shared screen live, the chat, notes your team keeps to itself and the live view tools | Their own screen as usual, the chat, your pointer notes, and any text or file you send, to accept |
| When it ends | The session history: who joined, approvals, chat and timing | A message that the session has ended |
Available in the console while someone shares. Voice, text and files go peer to peer between the two browsers, text and files on registered devices whose policy allows them, and each use writes a line to the session’s activity log without its content. The share stays view-only: a browser cannot send input to another computer.
Ask the person to share another screen or window. The browser’s own picker opens on their side, and they choose.
Send text to their clipboard tray, or receive theirs; they copy it with a click. It is on where a registered device’s policy allows it.
Send or receive a file during the session, where a registered device’s policy allows it. Nothing arrives until the other side accepts it.
Either side turns on its own microphone and talks while the screen is shared. The voice goes peer to peer, and Anslation keeps none of it.
Automatic, Sharp, Smooth or Data saver, plus the round-trip time and the video’s live numbers, so you can tell a slow network from a stuck app.
Save a screenshot or a local recording of the shared screen in your own browser, onto your own computer. Anslation keeps no copy.
15 minutes, and it works once. If it expires before the person joins, your team can make a new code for the same session.
Open the join link in Chrome, Edge, Firefox or Safari on your laptop, type the 9-digit code, then click Share my screen and choose the screen or window to show.
Only what you pick in the browser’s picker: a whole screen or a single window. Your support agent can ask you to switch, but you choose again in the picker, and you can stop sharing from the join page at any time.
Not from the browser. The screen share is view-only: your support agent sees what you share and talks to you in the chat, or by voice once you turn on your microphone. A session set up for mouse and keyboard help can offer the Anslation Remote Helper (preview), a program you run yourself: it asks you first, and Ctrl+Alt+Shift+P (Ctrl+Option+Shift+P on a Mac) pauses it. Commands can run only on a computer your team manages with the optional device agent, in a terminal session an admin approved or an access rule allows.
No. You need only the code. The members of your support team sign in to the console.
It stays with the session for your support team, beside the approvals and the timeline. Notes the team writes for itself are never shown on the join page.
Tell us about your team and how you help people today. We read every request and reply by email.
Office hours: Monday to Saturday, 10:00–18:00 IST+91 74158 85838