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 supports the current and previous version of Chrome, Firefox, Safari and Edge. Keeping browsers updated is not a formality here: older versions do lose features, particularly in the Agent Workspace.
What actually 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. An agent with thirty tickets open in one browser is asking a lot of a laptop. 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.