Lesson 2: Organizing tickets and users

<div class="container">
<div class="row">
<div class="col-md-3">
<ul class="nav nav-underline flex-column">
<li><a class="nav-link" href="https://support.zendesk.com/hc/en-us/articles/4408884056346">Introduction: Getting started with Zendesk Support</a></li>
<li><a class="nav-link" href="https://support.zendesk.com/hc/en-us/articles/4408881925786">Lesson 1: Ticket Basics</a></li>
<li><a class="nav-link disabled" href="https://support.zendesk.com/hc/en-us/articles/4408883609370">Lesson 2: Viewing and Organizing</a></li>
<li><a class="nav-link" href="https://support.zendesk.com/hc/en-us/articles/4408882997530">Lesson 3: Solving Tickets</a></li>
<li><a class="nav-link" href="https://support.zendesk.com/hc/en-us/articles/4408885959066">Lesson 4: Business Rules</a></li>
<li><a class="nav-link" href="https://support.zendesk.com/hc/en-us/articles/4408883043226">Where to go next</a></li>
</ul>
</div>
<!-- .col-md-3 -->
<div class="col-md-9">
<p>Topics covered in this lesson:</p>
<div class="list-group">
<a class="list-group-item list-group-item-action" href="#views">Ticket views</a> <a class="list-group-item list-group-item-action" href="#h_01HS1KV1FX0J4C4W0PK15P82RZ">Segmenting agents and their tickets with groups</a> <a class="list-group-item list-group-item-action" href="#h_01HS1KV1FXTF03TSW7Z17Y5KK1">Organizing customers</a> <a class="list-group-item list-group-item-action" href="#h_01HS1KV1FXW9WMJ5JCAD7W5PQY">User roles</a>
</div>
<h2 id="views">Ticket views</h2>
<p>In the previous lesson, we introduced<span> </span><em>views</em>. Views are used to organize your tickets at all stages in the ticket life cycle. In this lesson, we'll take a more in-depth look at how views can be used to organize your tickets. We'll also look at the tools you have available for organizing users. Your users include both your customers and your support staff.</p>
<p>Let's begin with views.</p>
<p>Views are essential for managing the ticket workflow because they enable you to create meaningful groupings of tickets as they progress through the ticket lifecycle.</p>
<p>Zendesk provides some pre-defined, editable views. These views were created for the essential day-to-day running of Zendesk Support and are based on customer service best practices.</p>
<p>Click the<span> </span>Views<span> </span>icon (<img class="inline" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/views_icon.png" alt="">) in the sidebar to see the list of views. Every Zendesk account contains these views to get you started:</p>
<p><img class="inline img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/gsg_unassigned_tickets_new_thumb.png" alt=""></p>
<p>Since views organize tickets based on a ticket's properties, a ticket can appear in more than one view. For example, a new ticket can appear in the<span> </span>Unassigned tickets, All unsolved tickets, and New tickets in your groups views. This is because a new ticket meets all the criteria for how these views were defined.</p>
<p>You can create new views or modify the existing views to suit your needs.</p>
<h3 id="h_01HS1YG6F25VTCCWVDMCZNX66Y">Shared and personal views</h3>
<p>The pre-defined views provided in your Zendesk account are available to all of your agents. These are <em>shared views.</em> You can edit these views or create your own views and define who has access to them.</p>
<p>Admins can also create views that only a specific group of agents can see. These are referred to as <em>restricted views</em>.</p>
<p>Lastly, all agents can create <em>personal views</em> that no one else has access to.</p>
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/gsg_view_available_for.png" alt=""></p>
<p class="d-inline-flex gap-1"><button class="btn btn-dark" type="button" data-bs-toggle="collapse" data-bs-target="#createViews" aria-expanded="false" aria-controls="createViews"> Try it yourself: Create personal views </button></p>
<div id="createViews" class="collapse">
<div class="card card-body">
<h3 id="h_01HS1NKSSTV5XA70TK1ZZSY7T7">Create personal views</h3>
<p>In this video, you can see how to create a personal view for your solved tickets:</p>
<p><iframe src="//fast.wistia.com/embed/iframe/tnjmheynfa" width="560" height="315" frameborder="0" allowfullscreen=""></iframe></p>
<p>Creating a View (1:29)</p>
<h2 id="h_01HS1KV1FXC7FJ6C8MK8YQDMK0">Try it yourself</h2>
<p>Let's quickly create a new view for the tickets assigned to you, solved or not. Since you created a test ticket in the previous lesson, you'll have one ticket for your view.</p>
<ol>
<li>Click the<span> </span><strong>Views</strong><span> </span>icon (<img class="inline" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/views_icon.png" alt="">) in the sidebar.</li>
<li>At the bottom of the list of views, click<span> </span><strong>Manage views</strong> to open the Views<span> </span>page in Admin Center.</li>
<li>Click<span> </span><strong>Add View</strong>.</li>
<li>Enter a title for your new view (for example,<span> </span><em>My tickets</em>).</li>
<li>
<p>Conditions are used to define what tickets are shown in a view. You can think of conditions as a simple formula for selecting data in tickets. In this example, we're trying to create a view of the tickets that are assigned to you. To do that, click the drop-down list below the label<span> </span><strong>Meet all of the following conditions</strong>. Select<span> </span><strong>Ticket: Assignee</strong>. Two more drop-down lists will appear. The first should already be set to<span> </span><strong>Is</strong>. Now click the next drop-down list and select<span> </span><strong>(current user)</strong><span> </span>or your name (either will work) from the list of agents. You've just defined a condition.</p>
<p><img class="inline img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/support_intro_assignee.png" alt=""></p>
</li>
<li>If you want to immediately see the results of the condition you defined, click <strong>Preview</strong>. Your ticket will be displayed in a table.</li>
<li>When defining a view you can also define the formatting and who has access to it. For now, accept the default formatting. From the <strong>Who has access</strong> menu select <strong>Only you</strong>.</li>
<li>Click<span> </span><strong>Save</strong>. Congratulations, you've just created your first personal view.</li>
</ol>
<p>Your new view is listed in <strong>Your views</strong> under the list of pre-defined views in Zendesk Support.</p>
</div>
</div>
<h2 id="h_01HS1KV1FX0J4C4W0PK15P82RZ">Segmenting agents and their tickets with groups</h2>
<p>You may have noticed that several of the pre-defined views refer to<span> </span><em>groups</em>. In Zendesk Support you organize your agents into groups. When you assign a ticket to an agent you're also assigning it to a group that the agent belongs to (agents can belong to more than one group).</p>
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/aw_assignee_groups.png" alt=""></p>
<p>You can also assign a ticket to just a group and not a specific agent within the group. Doing this allows the agents within that group to determine who should be assigned to the ticket.</p>
<p>You can create groups of agents for any reason. Typically, groups are used to organize agents by specialty or expertise (product support vs advanced support for example) or by location or language.</p>
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/gsg_group_new.png" alt=""></p>
<p>You can create views that list all the tickets assigned to each of your groups.</p>
<p>It's up to you to think about how you want to organize your tickets and the views your team needs. For example, if you only have a few agents, you might just need an "Unassigned" view where agents can pick tickets to work on. If you have a larger team, it might be a good idea to set up views for each group and have tickets routed accordingly.</p>
<p>Think about how you want to manage your ticket queue and then create the views and groups you need to support that workflow.</p>
<h3 id="h_01HS1KV1FXEDE7Q2X2XK7JEJFC">The default group</h3>
<p>In Zendesk Support, you'll see a group called<span> </span>Support. This is the default group that you and any agents you add are automatically added to. You can create new groups and add or remove agents from any of the Zendesk Support groups. The default<span> </span>Support<span> </span>group is there because a group is required to assign and solve a ticket.</p>
<p class="d-inline-flex gap-1"><button class="btn btn-dark" type="button" data-bs-toggle="collapse" data-bs-target="#createGroup" aria-expanded="false" aria-controls="createGroup"> Try it yourself: Create a group </button></p>
<div id="createGroup" class="collapse">
<div class="card card-body">
<h3 id="h_01K5YA38TQ2GB06X16K1HDNVWQ">Create a group</h3>
<p>You can create as many groups as you need to support your unique ticket workflow. In this example, you'll create a new group for your advanced support group. To see how to create a group, take a look at this video:</p>
<p><iframe src="//fast.wistia.com/embed/iframe/zg43alc29a" width="560" height="315" frameborder="0" allowfullscreen=""></iframe></p>
<p>Creating a Group (0:57)</p>
<p>If you'd like to try creating a group, follow these steps:</p>
<ol>
<li>Click the<span> </span><strong>Admin</strong><span> </span>icon (<img class="inline" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/manage_icon.png" alt="">) in the sidebar, then select<span> </span><strong>Go to Admin Center</strong>.</li>
<li><span class="ph">In Admin Center, click (<img class="image" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/ac_people_icon.png">) <strong class="ph b">People</strong> in the sidebar, then select <strong class="ph b">Team &gt; Groups</strong>.</span></li>
<li>Click<strong> Create Group</strong>.</li>
<li>Enter a name for your new group (for example,<span> </span><em>Advanced support</em>).</li>
<li>Select your name the list of all Zendesk Support agents.
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/Create_Group_Get_Started.png" alt="" width="478" height="412"></p>
</li>
<li>Click<span> </span><strong>Create group</strong>.</li>
</ol>
<p>You now have two groups: the default<span> </span><em>Support</em><span> </span>group and the<span> </span><em>Advanced support</em><span> </span>group you just added. We'll show you how to use this group shortly.</p>
</div>
</div>
<h2 id="h_01HS1KV1FXTF03TSW7Z17Y5KK1">Organizing customers</h2>
<p>To help manage your support workflow, you can add each of your customers to one or more<span> </span><em>organizations</em>. You can then provide different types of support for each organization.</p>
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/gsg_org_list_new.png" alt=""></p>
<p>The default organization a user belongs to is associated with every ticket they create and can be used to automate how incoming tickets are handled.</p>
<p>Common uses of organizations include supporting a service level agreement you have with customers, tracking and managing tickets by company names or email domain, and by location or language.</p>
<p>You can also use organizations as a way to control access to Zendesk Support tickets. You can allow specific users to see all the other tickets in their organization, which gives them visibility into Zendesk Support issues that affect the entire organization. Doing this may prevent additional tickets from being created for a support issue that affects an entire organization (for example, an essential application being temporarily unavailable to everyone).</p>
<p>You can also add agents to organizations. You might do this to restrict an agent's access to only tickets from a specific organization (Note: you can also restrict an agent's access to the tickets in a specific group). And you can automatically assign tickets from an organization to a specific group.</p>
<h2 id="h_01HS1KV1FX0CAM1XFM75ZB7BP8">User and organization tags</h2>
<p>Both the user profile and organization profile can contain additional information that can be used to customize your Zendesk Support workflow. You can add<span> </span><em>tags</em><span> </span>to both and use these tags to automatically assign or track tickets.</p>
<p>For example, if you add a tag called premium_support to a user or an organization, that tag is automatically added to every ticket from that user or users within that organization. You can then, for example, use the tag to define a new view that tracks your premium support tickets.</p>
<p class="d-inline-flex gap-1"><button class="btn btn-dark" type="button" data-bs-toggle="collapse" data-bs-target="#createOrg" aria-expanded="false" aria-controls="createOrg"> Try it yourself: Create an organization </button></p>
<div id="createOrg" class="collapse">
<div class="card card-body">
<h3 id="h_01K5YA38TQ86Y3JKZH28Z14M28">Create an organization</h3>
<p>Zendesk Support doesn't contain any default organizations. If you choose to use organizations, you will need to create them. To see how to create organizations, take a look at this video:</p>
<p><iframe src="//fast.wistia.com/embed/iframe/1mozlsfu2b" width="560" height="315" frameborder="0" allowfullscreen=""></iframe></p>
<p>Creating an Organization (1:01)</p>
<p><span>If you'd like to try creating an organization, follow these steps:</span></p>
<ol>
<li>Open a new support ticket as you did before. Ensure that the ticket has a requester name that you haven't already added to an organization. You could create a new user for testing purposes.<br>
<p>You'll see that there are three tabs within the ticket. The first is the<span> </span><strong>Organization</strong><span> </span>tab, the second is the<span> </span><strong>User</strong><span> </span>tab, and the third is the<span> </span><strong>Ticket</strong><span> </span>tab.</p>
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/support_intro_org.png" alt=""></p>
</li>
<li>To create a new organization, click<span> </span><strong>Organization (create)</strong>.</li>
<li>You'll be prompted to enter an organization name. Enter a name. For example, you might just call this organization<span> </span><em>Customers</em>.
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/Create_Org_Get_Started.png" alt="" width="507" height="363"></p>
<p>You can additionally add one or more email domains, which will automatically add every other new user with the same email domain into this organization. You'd probably do that if you're providing support to specific companies and want to segment them into organizations. For example, every user from @somecompany.com could be added to an organization called Some Company. You can skip this for now and add it later if you need to.</p>
</li>
<li>Click<strong> Add </strong>and the new organization is created and added to the user's profile as associated with the ticket.</li>
</ol>
</div>
</div>
<h2 id="h_01HS1KV1FXW9WMJ5JCAD7W5PQY">User roles</h2>
<p>So far we've talked about agents and customers. These are the two primary user roles involved in Zendesk Support transactions. Customers have issues that need to be fixed and agents fix them. However, there are several other user roles that you should be aware of.</p>
<p>First, be aware that the term<span> </span><em>customer</em> is often used interchangeably with <em>end user</em>. Both refer to the people who use Zendesk Support to request assistance.</p>
<p>Now let's look at the Zendesk Support staff roles. You know about the <em>agent</em> role. Agents primarily solve tickets. However, you can assign specific permissions to agents to control their access to the different parts of your Zendesk. For example, you can allow just a few agents to manage and moderate your Help Center.</p>
<p>In addition to agents, there is the <em>administrator</em> role. You can have one or many administrators in your Zendesk account. You can think of this role as the manager of your Zendesk account. They set up your account with the channels you want to support, define new shared views, manage users, and so on.</p>
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/gsg_user_roles.png" alt=""></p>
<p>If you originally created your Zendesk account, you are the<span> </span><em>account owner</em>. This role is the super administrator role and can do everything that's possible to do in Zendesk.</p>
<h2 id="h_01HS1KV1FX2TBQ5XAV3EJEZPCY">Custom agent roles</h2>
<p>On Enterprise plans, you can create custom agent roles. In other words, you can craft a role specifically designed to support your workflow from a list of permissions. We've defined some common roles that you can use as is or customize.</p>
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/gsg_roles_enterprise.png" alt=""></p>
<p class="d-inline-flex gap-1"><button class="btn btn-dark" type="button" data-bs-toggle="collapse" data-bs-target="#newAgent" aria-expanded="false" aria-controls="newAgent"> Try it yourself: Add a new agent and assign them to a group and organization </button></p>
<div id="newAgent" class="collapse">
<div class="card card-body">
<h3 id="h_01K5YA38TRZEY61ESP0T5FR20M">Add a new agent and assign them to a group and organization</h3>
<p>Now that you have an understanding of the Zendesk Support user roles, let's add a support agent. To do this, you'll need to use an email address that hasn't already been used in your Zendesk account. In other words, you can't use the email address you used to create your Zendesk account.</p>
<p>This video shows you how to add an agent to Zendesk Support:</p>
<p><iframe src="//fast.wistia.com/embed/iframe/qdjy75gkkd" width="560" height="315" frameborder="0" allowfullscreen=""></iframe></p>
<p>Adding an Agent (1:15)</p>
<ol>
<li>In Support, position your mouse over the<span> </span><strong>Add</strong><span> </span>tab in the top toolbar, then click<span> </span><strong>User</strong>.
<p><img class="img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/support_intro_user_add.png" alt=""></p>
</li>
<li>Enter the name and email address of your new agent.</li>
<li>Select <strong>Staff member</strong> as the user type.</li>
<li>Click the<span> </span><strong>Role</strong><span> </span>drop-down list and select<span> </span><strong>Agent</strong>. Then, click<strong> Add</strong>.
<p>This new user's profile is displayed. Here you can add your new agent to other groups, define their access to tickets and other parts of your Zendesk account, and add any other user profile information you want.</p>
</li>
<li>Click the<span> </span><strong>Groups</strong><span> </span>field.<br>You're prompted to add the agent to another group. Select the<span> </span><em>Advanced support</em><span> </span>group you created earlier.</li>
<li>Now set the agent's access permissions. Click the<span> </span><strong>Access</strong><span> </span>field and select<span> </span><strong>Tickets in agent's org</strong>.</li>
<li>To complete the agent's access restriction, click the<span> </span><strong>Org.</strong><span> </span>field and select <em>Customers</em>.</li>
</ol>
<p>That's it, you're done. Zendesk automatically saves the changes you make to a user's profile. You've just added an agent, added them to a group, and restricted their access to only tickets within the<span> </span><em>Customer's</em><span> </span>organization.</p>
</div>
</div>
</div>
<!-- .col-md-9 -->
</div>
<!-- .row -->
</div>
<!-- .container -->
<p>
<script>
let link = document.createElement('link');
link.rel = 'stylesheet';
link.href = 'https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/css/bootstrap.min.css';
link.integrity = 'sha384-QWTKZyjpPEjISv5WaRU9OFeRpok6YctnYmDr5pNlyT2bRjXh0JMhjY6hW+ALEwIH';
link.crossOrigin = 'anonymous';
document.head.appendChild(link);

const style = document.createElement('style');
style.innerHTML = `
.col-md-3 {
padding-left: 0px;
}
.col-md-9 {
padding: 0px;
}
.nav-underline {
--bs-nav-underline-gap: 2px;
}
.list-group {
margin-bottom: 1.75rem;
}
.btn {
margin-bottom: 1rem;
--bs-btn-font-size: 1.25rem;
}
.collapse {
margin-bottom: 2rem;
}
.article-body .nav {
list-style-type: none;
padding-left: 0px;
margin-top: 0px;
}
.article-body .nav-link {
text-decoration: none;
}
`;
document.head.appendChild(style);
</script>
<script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js" integrity="sha384-YvpcrYf0tY3lHB60NNkmXc5s9fDVZLESaAA55NDzOxhy9GkcIdslK1eN7N6jIeHz" crossorigin="anonymous"></script>
</p>