Internal IT
You support staff for one employer. A person at home, or a PC on the floor, needs a fix. Bring a computer the company already lets you open, and judge the session and the log before a seat goes on the desk.
Pilot
Book a 20-minute DeskZap Support pilot
We set the DeskZap Support pilot up with you, live, on one of your client machines, and you keep the workspace afterwards if it works.
01 / Who should book
A desk that reaches other people's computers.
The pilot is for technicians who connect to machines they do not own. Internal IT, an MSP, and a break/fix consultancy are the three desks that book it.
MSPs
You look after more than one organisation. A server the client has agreed can take an unattended host later. A director who will not install software can read a one-time code. The pilot uses one machine you name. We do not bring a demo image.
Break/fix consultancies
The work is often half a day on a computer you may not see again. The client gives a code or a link, you connect, the session is logged, and you leave. Nothing stays installed unless they ask you to keep that computer.
DeskZap Access is for computers your own organisation owns, and it starts with a 7-day trial on the pricing page. Support is for other people's machines, and it starts with this call.
02 / The twenty minutes
What happens in the 20 minutes
Three steps. One machine. You stay on the call the whole time.
- Step 01
You tell us the estate
The first minutes are the shape of the desk: how many technicians connect on a normal day, how many client organisations sit behind them, and what you open today. You then name the one machine we are allowed to use. A live ticket is ideal. Written permission on a computer you already reach is enough. We do not open a second computer in the same twenty minutes.
- Step 02
We connect to a machine you choose, with nothing installed on it
The person at that computer reads a Quick Support code, or opens the link you send them. The code is nine digits and it lasts five minutes. They create no DeskZap account. Host is not installed for this visit. You connect from the DeskZap client, and we talk through the screen you are seeing. File transfer can move one document either way. Remote print can send one job to a printer on the technician's side. Where the desk has more than one display, the session opens per monitor. When the code expires, a one-off ends and nothing is left installed.
- Step 03
You see the session log and the self-host option, and you decide
The activity log records the named technician, the machine and the time. That is the line for the ticket or the monthly report. The live screen is AES-256 end-to-end encrypted, and the relay cannot decrypt it. The log is held by the control plane. If client data has to stay on infrastructure you run, we open the self-host option: a control plane of the same class as DeskZap Advanced, on a machine you manage. You decide before the call ends. If it works, you keep the workspace. If it does not fit, we say so in the same twenty minutes.
03 / Before the call
What we need from you
Four facts. Rough figures are enough. An exact inventory can wait until the desk has seen one real session.
- 01
Roughly how many technicians
A seat is a named person. A shared login is not a seat, and a second person is a second seat. Choose 1, 2–5, 6–20, or 20+.
- 02
Roughly how many client organisations
One technician can cover unlimited client organisations, up to 250 managed devices. Another site does not add a machine licence. Choose 1–5, 6–25, 26–100, or 100+.
- 03
What you use today
Optional. Name the tool, or the mix, that you open when a client rings. We then spend the twenty minutes on the gap you feel, and we skip the introduction.
- 04
Whether client data has to stay in the UK
Yes, no, or not sure. Yes means we slow down on the self-hosted control plane. No means the hosted plane is acceptable for the pilot. Not sure means we explain where the log is held, and where the screen encryption starts and ends, so you can take a clear question back to the client.
What to have ready
Agree the machine with the client before the call. For a one-off, someone at that computer reads the code. For a computer you will support again, the owner agrees before Host is installed. The pilot can stop at the code if they are not ready to leave software in place. After that agreement you can connect when nobody is there to click, and the person at the machine still needs no DeskZap account.
Do not put passwords, licence keys, session codes or connection strings in the message. We will not ask for them. The code for the pilot is read on the call, and it expires after five minutes.
04 / The form
Tell us the shape of the desk.
The form takes about a minute. We use it to reply with two times that are worth your twenty minutes. Use the message for a deadline, the machine you already have in mind, or a question a client has asked about where the log is stored.
05 / If you go ahead
You keep the workspace from the pilot.
If Support fits, you keep that workspace rather than opening an empty account and starting again. Named technicians are added on it. A computer joins the estate only when the owner agrees to Host. A one-off client stays a one-off.
This form does not take payment. If the organisation count is large, we still send two times, and we say on the call whether one machine is a fair test. Bring one real ticket if you have one that week: a code for a machine that will not take an install, or a host you are allowed to leave in place.
The seat price and the comparison with Access are on the Support page. The Access trial is on pricing.
No card, no checkout, and if it is not a fit we say so on the call.