LiveDesk vs Splashtop

The customer, on their own machine, in answer to a request that arrives inside a conversation they already started. The program enforces it.

The customer, by running the app and reading out a code: they “download a small executable on the target computer with no installation needed, run it and get a 9-digit session code to tell the technician”. Possession of the code is what starts the session.

They open a page with your name on it and type. No code to read out, no account, and the request to see the screen appears in the same thread as the conversation.

Download, run, read out nine digits. It works, and it is one more thing to talk a frustrated person through on the phone.

Two separate questions, in that order.

SOS is a remote control product: the session is a control session. We could not find a statement in their public documentation about a view-only mode being a separate consent step, so this page makes no claim either way.

The tool removes itself when the session ends.

The SOS app runs without installation, which is the same intent. Their separate unattended products install a streamer that stays, which is what unattended access requires.

The conversation is the record: who asked, who allowed, when control was granted, when it ended, and it cannot be edited.

Splashtop keeps session logging and has extensive compliance material. We did not find a public statement about whether an administrator can delete those logs, so this page makes no claim about it.

Yours, on the page, the prompts and the banner, with the installer signature intact.

Splashtop offers branding on its support products. We could not confirm from a single official page which tiers include it and whether the customer-facing executable is rebranded, so check with them.

Postgres in Zurich. Screen contents never stored.

A US company with published compliance documentation covering GDPR and a list of industry regimes. Read theirs for residency specifics.

Nothing to pay. Pricing is not decided and billing is not built.

Priced per concurrent technician rather than per endpoint, which is a genuinely good model for a support desk. Figures move, so take them from their pricing page rather than from us.