Skip to content
Anslation

Anslation Remote

How a session works, on both sides.

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

How does a remote support session work?

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.

Six steps, start to finish.

What happens on each side of a support session, in order.

  1. 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.

  2. Share the code or the link

    Read the code out, or send the join link that carries it after a # sign. The code works once and expires after 15 minutes.

  3. They open the join page

    The person you help opens the join page in a desktop browser and types the code. No account, no install.

  4. Consent or approval

    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.

  5. They share a screen

    They click Share my screen and pick a screen or window in the browser’s own picker. You see it live.

  6. Help, then end

    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.

What each side sees.

The same session from the console and from the join page.

What your team and the person you help see during a session
MomentYour teamThe person you help
Before they joinThe code’s last digits, its expiry and a waiting statusA box for the 9-digit code
After the codeThat they joined, and whether consent or approval is still pendingWho is helping them, and an allow or decline choice when the policy asks
While sharingThe shared screen live, the chat, notes your team keeps to itself and the live view toolsTheir own screen as usual, the chat, your pointer notes, and any text or file you send, to accept
When it endsThe session history: who joined, approvals, chat and timingA message that the session has ended

Tools in the live view.

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.

  • Switch screen

    Ask the person to share another screen or window. The browser’s own picker opens on their side, and they choose.

  • Clipboard text

    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.

  • Files, accepted first

    Send or receive a file during the session, where a registered device’s policy allows it. Nothing arrives until the other side accepts it.

  • Voice

    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.

  • Quality and connection

    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.

  • Saved on your computer

    Save a screenshot or a local recording of the shared screen in your own browser, onto your own computer. Anslation keeps no copy.

About the code.

  • Shown onceThe code appears once, when the session is staged. Anslation keeps only a keyed hash of it, so nobody can read it back later.
  • Works once, for 15 minutesA used or expired code stops working. If it runs out before the person joins, your team can make a new code for the same session.
  • No hints for a wrong codeEvery wrong or expired code gets the same answer, and each network address gets 10 tries a minute. A code that was already used gets its own answer, which tells the person to ask for a new one, and so does a code for a session in a paused or archived workspace.

Joining a session, answered.

How long does a support code last?

15 minutes, and it works once. If it expires before the person joins, your team can make a new code for the same session.

Screen share kaise kare laptop par?

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.

Does the support agent see my whole screen?

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.

Can the support agent move my mouse or type?

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.

Do I need an account to join?

No. You need only the code. The members of your support team sign in to the console.

What happens to the chat after the session?

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.

Ready for a first session?

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