Supported browsers and devices

WorkZerk runs in the browser you already have. There is nothing to install on your side, and nothing for the people you onboard either: their link opens in whatever browser their phone came with.

Browsers

Chrome, Safari, Firefox and Edge all work, in any version from roughly the last two years. If you have not deliberately frozen your browser, you are on a supported one. The Chromium-based browsers under other names (Brave, Vivaldi, Arc, Opera) behave like Chrome and need nothing special from us.

Internet Explorer is not supported in any version. Microsoft retired it, and nothing here is tested against it. On a locked-down work machine that still opens IE by default, switch to Edge.

The reason for the two-year line is that the app leans on a handful of things older browsers do not have: modal dialogs, live updates over a single connection, and some recent CSS. A browser too old for those does not degrade gracefully: it looks wrong or stops responding.

Devices

The admin side wants a laptop. The requests panel, the people list and the settings tabs are dense by design, and they assume a keyboard and a window at least 1024 pixels wide. Everything works on a tablet, and most of it works on a phone, but the layout is built for the bigger screen.

The portal side is built for a phone, because that is where it gets opened: on site, one-handed, by somebody who was sent a link. Large tap targets, a single column, file uploads straight from the camera roll. It works fine on a laptop too.

So the usual split is you on a laptop, them on a phone, and neither of you needing to think about it.

On a tablet, an iPad in landscape is close to the desktop layout and is the comfortable posture. Portrait stacks the panels below each other. An external keyboard is worth having for any session where you are writing request wording or terms.

Two things that break it, both fixable

An extension that blocks scripts. Aggressive privacy extensions and some corporate browser policies stop the page's own JavaScript from running, and the symptom is not an error message: buttons do nothing, panels never open, and the page looks fine. If a screen is inert, try it in a private window with extensions off. If that fixes it, the extension is the cause and allow-listing the site is the fix.

A proxy that downgrades the connection. Live updates need a modern connection to the server, and a corporate proxy forcing an old protocol can leave the page loading but never refreshing on its own. A reload always shows the current state, so this shows up as "I have to keep refreshing" rather than as an error. Worth raising with whoever runs the network.

What to check before writing in

If something looks broken, in this order:

1. Reload the page. More things than you would expect are one stale tab.
2. Try a private window. That rules out extensions and cached files in one step.
3. Try a different browser or your phone. If it works there, the problem is the first browser rather than your account.

If it fails everywhere, it is worth a ticket.

Getting help

Say which browser, which version and which device when you open a help ticket, plus a screenshot. Most of the awkward ones are specific to one setup, and that combination is usually what identifies it.