Sharpen Browser Readiness Check
Overview
Checks the browser settings that stop the agent desktop working. These are the failures a speed test cannot see: the connection is fine, but the browser is quietly blocking something SharpenQ depends on.
Results are grouped by how much they matter:
Group | What it covers |
|---|---|
Will stop SharpenQ working | Cookies, third-party cookies, local storage, and the WebSocket connection that carries interaction updates |
Likely to cause problems | Popup blocker, audio alerts, desktop notifications, cached site data, and clock accuracy |
Environment | Browser and exact version, operating system and version, processor, memory, window size, and whether the session is virtualised |
Every failing check comes with a plain explanation of what will break and what to change, rather than just a red mark. A "Copy results" button produces plain text formatted for pasting into a ticket, which saves asking an agent to hunt through browser menus for their version numbers.
It reports the real machine details. Browsers deliberately misreport the operating system and processor in the information most tools read, so a modern Mac will often be described as an old Intel machine. This tool reads the accurate values instead, including the exact browser build, the true operating system version, and the processor model.
It flags virtual desktops. If the session is running through Citrix, VMware, Parallels, or a similar remote environment, it says so. Audio and WebRTC behave differently there, and headsets usually need the remote client's own redirection, so knowing this early avoids a long and pointless network investigation.
Embed this one rather than linking to it. Third-party cookies, a common cause of embedded CTI and iframe login failures, can only be tested while the page is itself embedded in another site. Run from its own tab, and the tool will say that check was skipped.
This is a snapshot, not a source of truth. It reads the browser profile in use at that moment. A different profile, a guest window, or an extension enabled later will change the result, and some settings are set by group policy rather than by the person at the keyboard.
This article is part of a series on Admin Configuration topics.