SysDesks is a simulated IT help desk. When you sign in, you are not looking at a course or a quiz — you are looking at a working service desk console: a ticket queue, a directory of simulated employees and devices, remote sessions into those devices, a company mail client, a phone dialer, chat, and the infrastructure consoles a real Tier 1 or Tier 2 technician would use. Every ticket in the queue was generated to feel like a real request, with a real cause somewhere in the simulated environment, and every fix you apply is checked against the actual state of that environment rather than taken on trust.
This article is about the product itself: what exists, where it lives, and how the pieces connect. If you are looking to learn general IT troubleshooting, account administration, or interview skills, the SysDesks blog covers that separately. This Help Center is scoped to explaining SysDesks — think of it as the manual for the simulator, not a course in IT support.
Creating an account
- Go to the sign-in page and choose New User Setup.
- Enter an email address and a password, or continue with Google.
- Choose a technician handle. This is the name shown on the leaderboard and on any documentation your resolved tickets publish, so pick something you would not mind an employer seeing.
- Pick an avatar and finish setup. You land on your technician profile.
- Open Tickets from the sidebar. Your queue is already populated — new technicians are seeded with a small starting batch so there is always something to work.
Everything in SysDesks is tied to your account: your career points and role progression, which tickets you have claimed or completed, your course and documentation progress, your interview history and skill profile, and your subscription status if you have one. Sign in from a different browser or device and the same shift picks up where you left it, because the simulation state lives on your account rather than in local browser storage alone (some fast-moving UI state, like exactly which window is open in a remote session, does not sync and resets each time you connect — see the Remote Desktop article for what that means in practice).
You can create an account with an email and password, or continue with Google — both land you in the same username-and-avatar setup step, and both produce an identical account afterward with no functional difference between them. Whichever you choose, you also pick a public handle: a short, unique name shown on the leaderboard and on any documentation your resolved tickets publish. It does not have to match your real name, and you can revisit it later from your technician profile if a chosen handle is already taken or you simply want to change it.
Think of "the queue" as an ongoing shift rather than a fixed pile of homework. New technicians start with a small seeded batch of tickets so there is always something available immediately, and as you close tickets, new ones are generated to replace them, gradually increasing in difficulty as your career points grow. There is no point at which the queue runs dry and no point at which it stops matching your current skill level — it is designed to keep pace with you rather than front-load every incident on day one.
What is in the sidebar
- Tickets — the incident queue and the ticket workspace where you investigate and resolve.
- Mail — your own inbox for requester follow-ups, tied to whichever ticket a thread is linked to.
- Interview — mock interview practice with an AI hiring manager.
- Active Directory, Server Room, Remote Desktop — the infrastructure and endpoint consoles.
- Knowledge — Documentation (a searchable knowledge base fed by your own resolved tickets) and Courses (structured lessons).
- Asset Management and Ship Management — hardware inventory and shipping records.
A dock in the bottom-right corner of the console follows you everywhere. It gives you one-click access to your assigned tickets, your mail, the phone dialer, and messages, so you never have to leave the console you are working in to check whether a requester has replied.