Plan requirement
| Subscription | Any plan |
| Access | Admin |
Building a view takes two minutes. Deciding what it is for, and who else needs it, is the part worth thinking about.
Create a view
- Open Admin Center, then Workspaces, then Views.
- Click Create view.
- Give it a name that says what is in it, not what it is called internally.
- Set the conditions: which tickets belong.
- Choose who the view is available to: everyone, a group, or you alone.
- Set the columns and the sort order.
- Preview the result before saving. The preview shows real tickets and catches most mistakes.
- Save.
Name it for the reader
Agents choose from a list of names all day. "Unassigned, over 4 hours" tells them what they will find; "View 3 - escalation" does not. Where you have several, a shared prefix keeps related views together in the list.
Columns are part of the design
A view is a working list, and the columns decide whether someone can triage from the list or has to open each ticket. Requester, subject, status, group and time since last update cover most needs. Adding twelve columns makes the list unreadable on a laptop.
Preview before you save
The preview is the difference between a view that works and one that quietly returns nothing. If it shows tickets you did not expect, or none at all, the conditions are wrong, and it is far easier to see that now than after your team has been ignoring an empty list for a week.
Comments
0 comments
Article is closed for comments.