NewAvailable on Windows now
Remote support software with your name on it, not ours. The customer clicks Allow, you see their screen, and the tool deletes itself.
How it works
A support request is a conversation. Seeing the screen is one step inside it, not a separate tool you have to talk someone through.
Straight there
Screen and input go directly between the browser and the PC, end to end encrypted.
When direct fails
The relay is used only when a direct connection cannot be made, and it sees ciphertext.
They open your page and type. No install, no account, no meeting code read out over the phone.
One click, next to the message you are already reading. The request carries your name, not ours.
A small tool downloads and asks on their own computer. Looking is one question, control another.
When the session ends it removes itself. Nothing is left behind on a machine you were only visiting.
Two halves
Most of support is talking. Some of it needs the screen. They are the same thread in the same console, which is the whole point.
A customer writes on your page and a thread opens. Replies, sessions and what happened in each one belong to it, it can be resolved, and none of it can be edited away afterwards.
Ask inside the thread and they allow it on their own machine. You see one screen, and typing and clicking is a second question. A banner they cannot hide stays up until it ends.
Consent
Permission is checked where the screen is. Nobody can switch it on from our side, including us.
Allow Max Muster from Acme IT to see your screen?
Your screen only, no control. A banner stays on screen and Stop ends it at any time.
The tool on their computer decides what to send. Our server only passes the question along and writes down the answer.
Letting you look does not let you type or click. Asking for control before they have allowed you to look is refused.
It stays on their screen for the whole session, and it has a Stop button.
Stop ends it. So does saying no, and so does losing the connection.
Ways in
One console, one tool, three ways to start.
| Way in | The customer | You |
|---|---|---|
| Branded web page | Opens your page and chats. No install to start. | A run once tool downloads only when you need the screen. |
| Helper app | Opens the support app installed under your own name. | The conversation history stays, and they can see who is online. |
| Managed device | Nothing. Servers and fleet PCs are enrolled once. | Unattended access, including the login screen, governed by policy. |
White label
Every company gets its own page and its own branding, and it carries through to the tool that runs on the customer's computer.
How can we help?
Tell us what is wrong. A technician answers here.
Your name
What can we help with?
Start chat with Acme ITA slug of your choosing, and a customer page branded with your name.
Branding is applied at download time, not by rebuilding. The signature stays valid.
The consent prompts and the banner the customer sees carry your brand and your technician's name.
Records
The conversation is the ticket. Messages and what happened in each session belong to it, and that record cannot be edited or deleted.
Who asked, who allowed, when control was granted and when the session ended, written into the thread as it happens. Every connection to a managed device is logged too.
Screen and input go directly between the browser and the PC, end to end encrypted. The relay sees ciphertext only, and it is used only when a direct connection fails. Postgres is in Zurich.
Ticketing and support
Support is a thread, not a queue of screen sharing sessions. Everything that happens for one customer happens in one place, and it is still there afterwards.
A customer writes on your page and a thread opens. Replies, the screen sharing and what happened in each session all belong to it, and it stays there once the session has ended.
Chat, the screen, control and the record are the same thread in the same console. There is no second tool to move to and nothing to reconcile afterwards.
Start for freeA small app the customer keeps, with the conversation still in it, so the next problem carries on where the last one stopped rather than starting again from nothing.
Servers and fleet PCs enrol once and are connected to without anyone at the keyboard, including at the login screen, under a policy you set. Every one of those connections is written into the record too.
Set up your organisation, add your branding, and send a customer the link. It takes a few minutes, and there is nothing to pay: billing does not exist yet.
Windows first
No install to start
Two step consent
The tool deletes itself