A view in Zendesk is a saved, self-updating list of tickets that match a condition. The five default views, and where admins create and manage them.
-
/
3 min watch
Chapters
How views organize the ticket queue in Zendesk
One shared queue gives an agent no obvious place to start. A view fixes that by holding a saved list of tickets that match a condition and keeping it current on its own.
This walkthrough opens the agent workspace and works through the five default views: by owner, by assignment, by status, by what is waiting on a customer reply, and by recent activity.
Each list carries its own count, and any view can be sorted or filtered further by requester, priority, or last update. It closes in Admin Center under Agent tools, where an admin creates a view and sets the conditions that decide which tickets land in it.
Two automations on a ClickUp list read a project's Service Type and apply the matching task template, so a new project arrives with its action items already on it.
A custom object is the record type Zendesk does not ship: assets, contracts, subscriptions. How to define one, and the lookup field that puts it on a ticket.
A macro is a saved reply plus the ticket changes that go with it. What sits inside a macro, how to build one, and what an agent sees when they apply it.
