Views are the primary way of managing tickets in Zendesk. The tickets displayed in a view respect an agent's ticket privilege, so agents only see the ticket that they are authorised to process.
When creating views, you should keep in mind the following.
Shared views are visible to all agents or all agents in a group. Before making a view shared, you should ensure that it is relevant to all the agents. The number of shared views listed in the sidebar is limited to a maximum of 12.
To see more views, the agent must go to the Manage View screen- click 'More' at the bottom of the views list.
Adding more shared views cause agents to miss important information and may clutter their screen.
For example, if you create a view that includes a condition based on the ticket group, there is little value in making the view shared to all agents as agents with no access to the group will always display no tickets.
Home screen views
Zendesk provides default views from the agent home screen:
- Tickets requiring attention
- Tickets assigned to you
- Tickets assigned to your groups
- Satisfaction statistics
While these views cannot be customized, they do provide ticket details to all agents. To access the default views, click the home button on the sidebar:
There is no need to create additional views to duplicate these details.
Always give clear and accurate descriptions to view titles. For example, ' Urgent, Unsolved Tickets' could describe the ticket conditions that make up the view. It would be misleading to name the view 'Unsolved Tickets' or 'Urgent Tickets'. It would be unhelpful to name the view 'Ticket Listing'. If you later modify the conditions in a view, you should consider modifying the title of the view to reflect the new conditions.
Once you have created your view conditions, always consider the ticket fields that are most relevant to the view. If your view concerns old tickets, you may want to include the request date or the date when the ticket was last updated.
Adding too many columns makes the screen cluttered and difficult to read. For example, if your view only includes urgent tickets, you may not want to include the ticket priority in the formatting, as you know from the view title that all tickets listed are urgent.
Sorting within views
You can apply a different sort order when formatting the view, but normally views read easier when sorted left to right. For example, if you create a view to review agent performance, you may want the assignee as the the first column and sort by assignee.
If you have many fields in your view and some with long descriptions, you may find the view clearer by grouping tickets. For example, grouping by assignee will place a heading of the agent's name then list tickets under each agent. The view will be sorted by assignee then by the first ticket column or the field you specify when formatting.
Agents can re-sort a view by clicking on a column heading. This toggles the sort order from descending to ascending on the selected column.
From time to time, you should review your use of views and your group's use of views. To ensure that priority items are visible to agents when processing:
- Views that are used most often should be placed near the top of the view list
- Views that focus on urgent tickets should be in near the top of the list
- Views that are infrequently used or that deal with low priority tickets can be placed lower down the order
- Views that are no longer required can be inactivated or deleted
This presents the most important views to agents while processing tickets where they are more likely to see and act on priority tickets. At most, the first 12 shared views and first 8 personal views are displayed on agent processing screen. Ensure priority views are within that range.
If you are responsible for a group of agents, ask which views they use and find most useful. Establish if the views need to be refined or new views added.
For views that are not visible to agents in the sidebar, you can bookmark its URL from the view edit page. When editing a specific view, look for the 'Permalink Copy to Clipboard' link.
The resulting URL will be in the format:
Using this URL will return you to the view edit screen.
You can also create and bookmark a URL to take you directly to the view ticket listing. Take the number at the end of the edit view URL,123456 in the above example, and use it in the following URL:
Reporting from views
You can export ticket listings from views to a comma separated values (CSV) file. Open the file in a spreadsheet or any reporting tool to further analyze tickets. However, once a ticket has been closed for 120 days it is archived and will no longer appear in any view. Consequently, ticket views are not designed to export tickets over long date ranges for reporting. Views are intended for actively managing tickets.
Avoid large complex results
Views will only ever display 30 tickets per page at a time. If your view returns hundreds of tickets the results will be spread across many pages. Consequently, you are unlikely to review all the results. If you find you that you routinely only look at a subset of tickets, consider refining the view's conditions to restrict results and simplify the query.
- Add more criteria to the 'meets all conditions' section
- Remove criteria from the 'meets any conditions' section
If you find that your view is slow to refresh, consider removing conditions that include search for:
- Null values, for example, 'Ticket Assignee is '-'
- Is not' values, for example, 'Ticket Assignee: is not: 'Phil'
- Strings, for example 'Ticket Description: Contains the following string: 'Willow Farm'
Review the audit log
Administrators on the Zendesk Enterprise plan can review their audit log for changes to views. Check to see if agents are maintaining their views and look for any updates to shared views.
If your need for views is particularly demanding, there is Quickie, by Lovestock & Leaf, a free app on the Zendesk Marketplace to organize and access views. Apps must be installed by your Zendesk Administrator.
For an in depth look at views, check out this webinar .
Por favor, entrar para comentar.