Plan requirement
| Subscription | Any plan |
| Access | Agent |
Zendesk runs in a browser, so the requirements are modest. The things that catch people out are cookies, extensions and network rules.
Browsers
Zendesk asks for the latest stable version of Chrome, Firefox, Safari or Edge, with JavaScript, cookies and local storage enabled. Not the current and previous one: the latest. Keeping browsers updated is not a formality here, because older versions do lose features, particularly in the Agent Workspace.
Stable is the operative word. An alpha, beta, nightly or development build is not supported on any browser, including a Firefox Nightly that somebody runs because they like it.
Contact Center is the exception: there it is the latest two versions of Chrome, Edge and Firefox, and Safari is not supported at all.
Not on a mobile browser
Viewing Zendesk through a phone's browser is not supported. The agent interface is the mobile app; everything else needs a desktop browser. So the answer to "can I just check a ticket on my phone" is yes, in the app.
What causes trouble
In practice, four things account for most of the odd behaviour agents report.
- Blocked third-party cookies. Safari and Firefox restrict these by default, and some parts of Zendesk depend on them. Symptoms are vague: panels that stay empty, sessions that drop.
- Browser extensions. Ad blockers and privacy extensions block the widget and parts of the workspace regularly. Testing in a private window with extensions off is the quickest way to prove it.
- Firewall and proxy rules. Corporate networks that filter by domain can break attachments, voice and messaging while leaving the rest working.
- Memory and connection. Zendesk asks for Windows or macOS with 8 GB of RAM and 10 Mbps. An agent with thirty tickets open on a machine at that floor is asking a lot of it, and slowness is often this rather than Zendesk.
Voice needs more
Phone calls run over your internet connection, so the requirements are stricter than for ticketing. Bandwidth, latency and packet loss all matter, and a headset makes an audible difference. If you plan to use Talk, treat the network requirements as a separate exercise rather than assuming what works for tickets will work for calls.
Comments
0 comments
Article is closed for comments.