Show them where to click, without a code to read out
Screen help between you and your contacts, and the way Xuda supports you: see the screen, talk it through, point at the button, and when they ask, take the wheel. No install, no nine digit code for a stranger to phone in, and every action written down.
A click is sent as "click Save", not a mouse position
See, point, drive one app, or the whole machine, each its own yes
Every action written as a sentence when the session ends
Sessions start between people Xuda already knows, so none to read out
It knows what you are pointing at
Every other tool sends a picture of the screen and a mouse position, so all it can do is move a cursor and hope. Xuda drew the screen, so a remote click is sent as the thing it means: click the Save button on the Orders form. That one change is why help here can be written down in words, refused by rule before it happens, correct even when the layout is mirrored for a right to left language, and usable on a slow connection where moving a cursor by pixels is not.
From stuck to sorted, on their terms
Four steps, and the person being helped says yes to each one.
- 01
Start from a person, never a code
A session opens between a contact and a contact, or between you and a verified Xuda person, against an identity the platform already holds. There is no number to read out to a stranger on the phone, which is how this kind of tool is usually abused.
- 02
They see the request, in their words
A prompt names who is asking, what they will be able to do (see your screen, or move your mouse and type), the app, and for how long. It also says what they cannot do: see your passwords, or submit anything without asking you first.
- 03
Point first, drive only if asked
The default is a halo on the button and a voice explaining it. Taking the wheel is a separate yes, for one app or one window, that expires on its own. A banner shows the whole time, and Escape ends it instantly.
- 04
A receipt lands when it is over
You get a summary in your language: who was in it, what was done as plain sentences, everything that was refused and why, and a link to the recording with a "this was not me" button. Remote help is frightening because it is opaque. This is the answer.
Built so the person being helped stays in charge
The parts that matter when the screen is not your own and the stakes are real.
Point at the exact thing
Draw a halo on a button, scroll it into view, and sketch on the shared screen. It touches nothing, needs no install, and it is the whole of what most support calls need.
An AI that can read the screen
On the higher tier, the assistant watches the shared screen, answers "what am I looking at" and "why did this fail", talks it through, and points, all without ever taking control.
A receipt of every action
Because a click is a named intent, the log reads "opened Settings, changed the invoice prefix, saved", not a video nobody watches. Every refusal is listed too, so the limits are visible.
Your passwords never leave
Password fields and anything Xuda marks sensitive are blacked out before the picture leaves your machine, driven by the form itself, so a field added tomorrow is hidden today. A helper who needs a password asks you to type it.
A session can be replayed
A run of named actions becomes a how to article with real screenshots, a macro to repeat, or a task an agent can run. Every other tool throws the session away when it ends.
A grant that expires
Control is given to one named person, for one scope, with a clock on it, and it is revoked the instant you move your own mouse. Nobody is left with standing access they forgot to switch off.
Being helped is free. What you buy is a seat that helps
Anyone can be assisted on any tier, including a customer with no Xuda account. A paid tier adds the seats that give assistance and how much they can do.
Included
Included with every account, and how Xuda helps you
- Be assisted on any Xuda screen, always free
- Xuda support can see your screen and point
- One person on your account who can help others
- Point, scroll and draw, no control
Assist
PlannedFor a team that helps its own customers
- Everything in Included
- Three helper seats, more available
- Take the wheel inside one Xuda app, with consent
- An itemised receipt after every session
- Recordings kept for thirty days
Assist Pro
For a support desk that runs on it
- Everything in Assist
- Ten helper seats, more available
- An AI that watches the screen and points
- Whole screen control where the account allows it
- Recordings kept for a year
Xuda Assist is not on sale yet. These tiers describe what each rung will include; none can be bought today, and the dashboard shows them as coming soon rather than letting a purchase through. Being assisted is planned to stay free on every tier, on every Xuda screen, even for someone with no Xuda account.
Where this wins, and where it does not
The last row is not flattering, because a comparator that ticks all its own boxes is one nobody believes.
Xuda Assist Usted | A typical remote tool | |
|---|---|---|
| A grant that names one person and expires | ||
| Passwords blacked out before they leave the machine | ||
| What the audit shows | Every action as a sentence | A video, if it was recorded |
| A receipt sent to the person who was helped | ||
| No code for a stranger to phone in | ||
| Works on any machine today, no Xuda needed | Xuda screens first | Yes |
The things people ask before they trust this
Helping someone should not mean handing over the keys
Assist rides inside a Xuda Meet room, so the screen, the voice and the pointer are one connection. What is different is everything around it: a grant that names one person and expires, a screen that redacts your passwords before they leave your machine, and a receipt of every click when it is over.