What Are Zendesk Views? How to Create and Organize Your Ticket Queue

A Zendesk view is a saved, self-updating list of tickets that match conditions you set, such as "status is Open AND assignee is me," and admins create one in Admin Center under Workspaces > Agent tools > Views. Each view needs at least one core property (Status, Status category, Type, Group, Assignee, Requester or Support type), shows up to 15 columns, and the Views list shows your first 100 shared views and first 10 personal views.

These mechanics are checked against Zendesk's own documentation on September 24, 2026. Views are one of Zendesk's core business rules and organization tools, and they sit right on top of the ticket itself, so if you're fuzzy on what a ticket is, start there.

What are Zendesk views?

A view is a dynamic, saved list of tickets that meet a set of conditions: a standing query over your tickets that updates itself in real time. You define the conditions once ("status is Open AND assignee is me"), and from then on the view shows every ticket that currently matches, dropping tickets as they stop matching and adding new ones as they qualify. Nobody maintains the list by hand.

The key word is dynamic. A view isn't a folder you drag tickets into; it's a live filter. The moment a ticket's status flips from Open to Solved, it leaves your "open" view on its own. That's why views are the natural home for a support queue: they always reflect the current state, and each one is a saved set of conditions over ticket fields like status, priority, group, assignee and tags.

How do Zendesk views work?

Every view is built from four ingredients. Getting each one right is the difference between a queue that works and one that's noisy or empty.

Conditions (meet all / meet any)

Conditions are the filter. A view must include at least one of these core ticket properties: Status, Status category, Type, Group, Assignee, Requester or Support type. That gives it something concrete to anchor on. You then add as many other conditions as you need (priority, tags, hours since update, custom fields and more).

Zendesk splits conditions into two blocks:

• Meet all of the following conditions: AND logic. Every condition must be true for a ticket to appear. Use it for precise queues like "Open and High priority and in the Billing group."
• Tickets can meet any of the following conditions: OR logic. A ticket appears if it matches any one of them. Use it to widen a net, such as "priority is High or Urgent."

Most useful views combine the two: a tight "all" block to scope the queue, plus an optional "any" block to broaden one dimension. One caveat from the docs: the "Hours since..." conditions aren't available in the "any" block.

Columns

Columns control what each ticket row shows: subject, requester, priority, group, time open, a custom field, whatever your team scans for. You can display up to 15 columns and drag them into order. Multi-select fields can't be used as columns. The right four or five columns beat a cluttered fifteen.

Sorting and grouping

Two controls shape the layout:

• Group by clusters rows under headers (by priority, group or status), so a long queue reads as tidy sections instead of one endless list.
• Order by sets the sort within the view, ascending or descending: oldest first to attack the backlog, or priority first to triage by urgency.

Shared vs. personal views

This is the one most new admins miss. There are two scopes:

• Shared views are created by admins (or agents with the right permission) and are available either to all agents or to all agents in a specific group. These are your team's standard queues, and everyone sees the same list.
• Personal views are created by an individual agent for their own use. Nobody else sees them, which makes them good for a private "things I'm watching" list that doesn't clutter the shared sidebar.

Rule of thumb: if more than one person needs it, make it a shared, often group-scoped view. Personal views are for individual workflow, not team process.

How many views does the Views list show?

Zendesk caps how many views are accessible in the Views list. The list shows the first 100 shared views and the first 10 personal views in collapsible sections, up from the old default of 12 shared and 8 personal (Zendesk: accessing your views). On Enterprise plans, admins can use the "Reduce view count" permission on a custom role to hold agents to that older 12 and 8 limit. The practical point hasn't changed with the number: the list is finite and ordered, so the views near the top get worked and the ones buried at the bottom get ignored. Order matters as much as the cap.

What's the difference between views, search and filters?

These three get conflated constantly, and it's a common search query in its own right.

The mental model: a view is a saved, standing queue; search is an ad-hoc question. You build views for recurring work, the queues your team lives in. You reach for search when you need to find something specific, especially older or archived tickets, which views leave out. In-view filtering sits in between: you click Filter on the view you're already looking at (say, show only High priority), the filters appear as tags above the list, and they stay until you sign out (Zendesk: sorting and filtering a view). They don't change the saved view for anyone else.

So "zendesk views vs filters" has two answers depending on what someone means by "filter": search is the separate, ad-hoc tool, while filtering within a view is a throwaway refinement of a queue you already saved.

How do you create a view in Zendesk?

Creating a view takes a couple of minutes:

1. In Admin Center, go to Workspaces > Agent tools > Views (admins manage shared views here; agents create personal views from the Views list).
2. Click Add view and give it a clear name. The name is what agents read in the sidebar, so "Unassigned: Tier 1" beats "View 7."
3. Under Tickets must meet all of these conditions, add your scoping conditions, including at least one core property like Status or Group. Add an any block if you need OR logic.
4. Set Columns (up to 15), then choose Group by and Order by.
5. Set availability: shared with everyone, shared with one group, or personal.
6. Preview the matched tickets to sanity-check them, then Save.

A little thought on conditions and columns here saves the whole team time every day.

Which views should every support team have?

You don't need many. You need the right few:

• Unassigned / needs triage. Status is New or Open and no assignee. This is your intake queue; if it grows, triage is falling behind.
• My open tickets. Assignee is (current user) and status is Open or Pending. The agent's personal work list.
• Breaching / at-risk SLA. Tickets approaching or past their SLA target. SLA targets are configured separately (see Zendesk SLAs explained), and a dedicated view surfaces the ones about to slip.
• Pending too long. Status is Pending with "hours since update" over a threshold: tickets waiting on a customer who may have gone quiet, so you can nudge or close them.
• Unsolved by group. Group is Billing, Tier 2 and so on, grouped by priority. The team-level queue each pod works from.

Do Zendesk views route or assign tickets?

No. A view is organization, not assignment. A view shows you the tickets matching its conditions; it never moves a ticket, sets a field or assigns an agent. If your "Unassigned" view is full, the view won't empty it. Something has to assign those tickets.

That something is a different feature. Triggers fire when a ticket is created or updated and can set the group, priority or tags, so a well-built trigger routes a ticket into the right team's queue. Omnichannel routing goes further and distributes tickets to available agents by group, skill and capacity. Routing decides where work goes; views decide how agents see and prioritize it once it's there.

This is also why a tidy view setup depends on clean tickets underneath. If triggers don't set priority and group consistently, even a perfect view shows a messy queue.

What mistakes make Zendesk views stop working?

A few patterns separate teams whose views help from teams whose views are noise:

• Over-creating. A sidebar with 40 views is a sidebar nobody reads. Keep shared views to the handful the team actually works, and put the most-used ones at the top.
• A view per person instead of per team. Scope shared views to groups so each pod sees its own queue; use personal views for individual quirks.
• Vague names. "Urgent: Billing: Unassigned" tells an agent everything; "Copy of View 3" tells them nothing.
• Treating a view as routing. A view that's always full is usually a routing problem. Fix it with triggers or omnichannel routing.
• Ignoring the list limit and order. Views buried below the cap effectively don't exist. Prune and reorder periodically.
• Only working queues, never watching them. A "New tickets older than 2 hours" view is an early warning that triage is breaking down.

Where does an AI agent fit alongside views?

Even a well-organized set of views assumes a human opens each queue and works tickets down by hand. An AI agent layer like Macha changes that math. Macha sits on top of your existing Zendesk; it isn't a help desk and doesn't replace one. It can triage and route incoming tickets (set type, priority and tags, assign the group) and resolve routine ones outright, so fewer tickets reach a manual queue. Your views still exist for everything that needs a person; they just stay shorter.

The trade-offs: it's another integration to manage, and it performs only as well as the knowledge and rules you connect to it. On cost, Macha bills per ticket, from $299 a month for 750 tickets: one charge per conversation however many steps it takes (triage, tag, route, look up data, draft, resolve), not per closed ticket, and setup and monitoring by the Macha team are included. The reason for that unit is that most of the work is triage and lookup along the way, not a single "resolution." If a permanently full intake view is your bottleneck, that's the gap an AI layer fills. You can try it with $50 of free usage, no credit card required.

Frequently asked questions

What are Zendesk views? A view is a dynamic, saved list of tickets that meet conditions you define: a live queue that updates itself as tickets start and stop matching. Views are where agents work day to day: "All unsolved tickets," "Your unsolved tickets," "Unassigned tickets" and so on. Each one is a set of conditions over ticket fields like status, priority, group and assignee.

What's the difference between Zendesk views and search (or filters)? A view is a saved, standing queue built from predefined conditions; it persists and excludes archived tickets. Search is an ad-hoc lookup across all your data and includes archived tickets, so it's how you find a specific older ticket. Filtering within a view is a temporary refinement that lasts until you sign out and doesn't change the saved view for anyone else.

How do I create a view in Zendesk? In Admin Center, go to Workspaces > Agent tools > Views, click Add view, name it clearly, set the conditions (at least one core property such as Status or Group), choose columns and sort and group order, set availability (shared with everyone, shared with one group, or personal), preview the matched tickets, and save.

How many active views can I have in Zendesk? The Views list shows the first 100 shared views and the first 10 personal views. The older default was 12 shared and 8 personal, and Enterprise admins can hold a custom role to that limit with the "Reduce view count" permission. Because the list is finite and ordered, keep your most-used views near the top.

What's the difference between a shared view and a personal view? Shared views are created by admins (or permitted agents) and are available to all agents or to a specific group; they're your team's standard queues. Personal views are created by an individual agent for their own use and aren't visible to anyone else.

Do views automatically route or assign tickets? No. A view only organizes and displays tickets that match its conditions; it never assigns an agent or changes a field. Routing is handled by triggers and omnichannel routing, which put tickets into the queues your views show.

What should a first set of Zendesk views look like?

Start with the five queues above: unassigned, my open tickets, SLA at risk, pending too long and unsolved by group. Make them shared and group-scoped, give each four or five columns, and put them at the top of the list. Leave routing to triggers and ad-hoc lookups to search. From there, see how the rest of the system fits together in the Zendesk business rules guide, and pair your views with SLA targets so urgent work doesn't slip.

View mechanics and limits checked against Zendesk's documentation on September 24, 2026. Zendesk changes these periodically, so confirm the limits in your own account.