This article is about problems with SysDesks the product — the site not behaving correctly — not about problems inside the simulation, which are the tickets themselves. If a simulated printer won't print or a simulated account is locked, that's the job, not a bug; this page is for when the console itself misbehaves.
Browser and device requirements
- A current version of Chrome, Edge, Firefox, or Safari. SysDesks is a modern web application and does not support legacy browsers.
- JavaScript enabled — the entire console, including the ticket queue and remote sessions, runs in the browser.
- A stable internet connection. Calls, mock interviews, and AI-graded responses depend on a live connection to run inference in real time.
- A working microphone for voice calls and voice-mode interviews. Text-based chat and text-mode interviews do not require one.
Common problems and what to check
- A call or voice interview won't start — check that your browser actually granted the microphone permission prompt rather than silently denying it; browser settings can also block mic access at the site level even after you've allowed it once, which is worth checking directly.
- A ticket won't resolve even though you believe it's fixed — reread the specific failure message the Resolve button shows. It names the exact condition that still isn't satisfied; this is almost always more useful than trying the same action again, since it's telling you precisely what state the checker is still seeing.
- A remote session seems stuck or won't connect — confirm the ticket you have open actually authorizes a remote session for the device in question (see How Remote Desktop Works); a ticket that doesn't need endpoint access will not open one, which is correct behavior, not a fault.
- The console looks broken or a page is behaving strangely after an update — a hard refresh (reload while bypassing the cache) resolves most stale-asset issues after a new release ships.
- You're signed in but a feature or ticket seems unexpectedly unavailable — check your plan and daily usage from your technician profile; some actions are metered per plan as described in Account and Subscription Help.
SysDesks keeps some session state in your browser's local storage as well as on your account, so clearing site data for sysdesks.com in your browser can occasionally help with a stuck local UI state — but do this as a last resort, since it clears local caches and preferences for the site (your actual account progress lives on the server and is unaffected).
A few symptoms are worth naming specifically because they look like bugs but are actually the platform working as designed: a remote session that won't open for a ticket that seems endpoint-related is often correctly refusing because the ticket's category doesn't actually authorize one (see How Tickets Work); a resolve attempt that keeps failing on the same condition after you're sure you fixed it is usually pointing at a second, related setting you haven't corrected yet rather than a broken check; and a requester who seems to "already know" something you haven't told them yet is the shared-memory model working correctly across chat, calls, and mail, not a leak of information it shouldn't have.
If none of the above resolves what you're seeing, contact support with your account email, the page or feature involved, and the approximate time it happened — that context is what actually lets an issue get diagnosed quickly. A screenshot or the exact wording of an error message is more useful than a general description of "it's broken," the same standard of evidence the platform expects of you in a ticket's own resolution notes.