How to Add a View in Zendesk

Your support queue is a mess. Tickets from five different channels piling on top of each other, no clear priority, no structure. Your team is firefighting instead of resolving.

That’s what Zendesk Views are built to fix.

A View is a filtered, organized snapshot of your ticket queue. Set it up right, and your team stops guessing what to work on next. They just open the view and get to work.

This guide walks you through exactly how to add a view in Zendesk — from the basics to advanced conditions — so your support operation runs tighter starting today.

What Is a View in Zendesk?

A View in Zendesk is a saved, filtered list of tickets that match specific conditions you define. Think of it as a smart inbox for your support team.

Instead of showing every open ticket to every agent, Views let you slice your queue by priority, status, assignee, tag, channel, or any combination you need.

Why this matters:

• Teams using structured ticket views resolve issues significantly faster than those working from a single unfiltered queue
• 89% of customers have switched to a competitor after a poor service experience (Salesforce State of Service)
• 60% of customers define “immediate” as under 10 minutes — a cluttered queue makes that impossible
• Zendesk serves over 100,000 businesses globally, and Views are one of its most-used organizational features

Views don’t just organize tickets. They set the foundation for how fast and accurately your team responds.

Types of Views in Zendesk

Before you build one, know what kind of view you’re creating.

Shared Views Visible to all agents or specific groups. Admins create and manage these. They’re ideal for team-wide queues like “All Open VIP Tickets” or “Escalations Today.”

Personal Views Created by individual agents for their own workflow. An agent might build a view showing only tickets assigned to them, sorted by urgency. Only they can see it.

Default Views Zendesk comes pre-loaded with a set of default views (like “All Unsolved Tickets” and “Recently Updated Tickets”). You can use them as-is or customize them.

Group-Specific Views Restricted to a specific agent group — useful when your billing, technical, and onboarding teams each need their own filtered queues.

How to Add a View in Zendesk

Here’s the step-by-step process to create a new view from scratch.

Log Into Your Zendesk Admin Panel

Go to your Zendesk Support account and click on the Admin icon (gear symbol) in the left-hand sidebar.

Navigate to Views

Under the Manage section in the left menu, click Views. This opens your full list of existing views.

Click “Add View”

At the top right of the Views page, click the green Add view button. A new view setup page opens.

Name Your View

Give it a clear, descriptive name. Be specific — “Urgent Unassigned Tickets” beats “New View 3.” Your agents will thank you.

Set the View Conditions

This is the core of your view. Conditions determine which tickets appear.

You’ll see two condition types:

Meet ALL of the following conditions Every condition must be true for a ticket to appear. Think of it as an AND filter.

Meet ANY of the following conditions At least one condition must be true. Think of it as an OR filter.

Common conditions to add:

• Status → is → Open / Pending / Solved
• Assignee → is → (specific agent or group)
• Priority → is → Urgent / High
• Tag → contains → vip, escalation, billing
• Ticket channel → is → Email / Chat / Phone
• Created at → less than → 2 hours ago

Choose Who Can See the View

Under Available for, select:

• All agents — everyone on your team sees this
• Agents in specific groups — limit it to relevant teams
• Only you — personal view, no one else sees it

Set the Columns

Choose which ticket fields appear as columns in the view. Standard columns include Ticket ID, Subject, Requester, Assignee, Priority, and Updated. Add or remove based on what your team needs at a glance.

Set the Sort Order

Choose how tickets are sorted within the view. Most teams sort by:

• Priority (High → Low) for urgency-based queues
• Created at (Oldest first) for FIFO handling
• Updated at (Most recent) for monitoring active conversations

Save the View

Click Save at the bottom of the page. Your new view appears immediately in the Views list and in the left sidebar for agents.

How to Add Conditions to Sharpen Your View

Generic views create noise. Tight conditions create clarity.

Here are the most effective condition combinations used by high-performing support teams:

Escalation View

• Status → is → Open
• Tag → contains → escalation
• Priority → is → Urgent

Unassigned High-Priority View

• Status → is → Open
• Assignee → is → (nobody)
• Priority → is → High OR Urgent

SLA Breach Watch View

• Status → is → Open
• Hours since created → greater than → 4

VIP Customer Queue

• Status → is not → Solved
• Organization → is → (VIP org list)
• Priority → is → High

The more precise your conditions, the faster your team can prioritize and act. Studies show that teams with structured, role-specific views reduce average first response time by up to 23% compared to teams working from a single catch-all queue.

How to Edit or Delete an Existing View

Conditions change. Priorities shift. Views need updating.

To edit a view:

Go to Admin → Manage → Views, hover over the view you want to change, and click Edit. Adjust your conditions, columns, or sort order, then hit Save.

To clone a view:

Hover over a view and click the dropdown arrow. Select Clone. This creates an identical copy you can modify without touching the original — useful when building a similar view for a different team.

To delete a view:

Hover over the view, click the dropdown arrow, and select Delete. Zendesk asks for confirmation before removing it permanently.

To reorder views in the sidebar:

On the Views list page, drag and drop views into the order you want. The order here mirrors what agents see in their sidebar.

Best Practices for Zendesk Views That Actually Work

Most teams create views once and forget about them. Here’s how to make yours permanently useful.

Audit views quarterly. Stale views clutter the sidebar and confuse new agents. Every 90 days, review your views list and delete anything outdated.

Name views for action, not identity. “Billing Team Queue” is weak. “Open Billing Tickets — SLA at Risk” is a prompt that drives behavior.

Limit shared views to under 12. Research shows agent productivity drops when sidebars contain more than 12 active views. Trim ruthlessly.

Use group-specific views instead of role-based ones. Zendesk Views filter by group (not individual role), so align your views with your actual agent groupings.

Build a “My Tickets” view for every agent. Agents work faster when they have one focused view of tickets assigned specifically to them, separate from the team queue.

Set realistic column counts. More than 6 columns in a view creates cognitive overload. Show only what agents need to make a decision — subject, priority, requester, time open.

The Limit of Inbound: What Views Can’t Fix

Zendesk Views make your inbound queue more manageable. But no amount of ticket organization addresses the real growth challenge: you’re waiting for customers to come to you.

The highest-growth teams aren’t just running tight support queues. They’re proactively reaching decision-makers before a support ticket ever gets filed — building pipeline through systematic outbound before the competition does.

That’s the shift. Managed inbound on one side. Scalable outbound on the other.

LinkedIn outbound consistently delivers 15–25% response rates compared to cold email’s 1–5%. With 65+ million decision-makers active on LinkedIn, the pipeline is there. The question is whether you’re reaching it.

Conclusion

Adding a view in Zendesk is one of the fastest ways to turn a chaotic ticket queue into a structured, prioritized system your whole team can work from.

The steps are straightforward: navigate to Admin → Views, hit Add View, define your conditions, set visibility and columns, and save. But the real value comes from how you design those conditions — tight, specific, and aligned to how your team actually works.

Start with three views: one for unassigned urgent tickets, one for your team’s active queue, and one personal view per agent. Build from there as your volume and complexity grows.

And while you’re optimizing inbound — don’t let outbound sit idle. The teams growing fastest aren’t just managing support better. They’re proactively building pipeline through LinkedIn outbound, reaching 65+ million decision-makers with campaigns that convert.

Book a strategy meeting with Salesso to see exactly how we build that outbound engine for you.