Saved support queue views
Keep a useful review view without rebuilding its filters.
Save personal or shared ticket views with supported filters and sorting while each reader's ticket permissions remain in force.
A saved view describes a question, not a new access role.
Support reviews repeat: which high-priority cases are still open, which requests wait for our team, and which targets need attention? A saved view preserves a useful filter and sort configuration. Name it for the review it supports. Saving or sharing the view does not assign tickets, grant access to another team or certify that the visible subset represents all support work.
Save supported filters with a practical sort order.
Use the ticket list's supported filter vocabulary, such as status, priority, team, assignee, channel or tags, and choose an appropriate sort. Due order can support response review; updated order helps inspect recent changes. Keep the view focused enough to be useful and test it against known cases. A view with contradictory filters can be empty while important requests still exist elsewhere.
- Supported ticket filters and saved sorting
Keep personal review and shared policy distinct.
Personal views belong to their creator. Shared views appear for the support organization and require settings authority to create or maintain. Do not publish every temporary personal experiment as a shared convention. A common view should have a clear purpose and a maintainer who can review it after team, tag or process changes. Reader access to the underlying tickets remains independent of the view's ownership.
- Personal ownership and settings-controlled shared views
Review the view when the organization changes.
Update the name, filters, sorting or position when the review task changes, and remove obsolete views. Results and counts still follow the current reader's visibility, so comparing two users requires understanding their permitted scope. Open a ticket before responding and inspect its current status. A saved view is a navigation aid to live work, not a frozen snapshot or a complete performance report.
- Maintained views over current permission-bound ticket data
A concrete workflow
Choose question
Define the recurring review the view should support.
Set filters
Choose and test the supported conditions and order.
Save scope
Keep it personal or publish with the required settings authority.
Review changes
Update the view after team or process changes.
An illustrative working example
Illustrative scenario: the technical team's waiting work
A lead defines a shared view of the technical team's waiting requests with an appropriate sort. Agents test known tickets and confirm what the filters exclude. A separate personal view helps one agent review their own urgent cases. The same shared view does not expose another team's hidden requests. After responsibilities change, the lead updates the shared configuration rather than letting its familiar name conceal an outdated selection.
Questions about this topic
Can a saved view grant ticket access?
No. Underlying ticket visibility remains independently enforced.
Who can maintain shared views?
Shared view creation and maintenance require the relevant settings authority.
Is a saved view a static export?
No. It stores a configuration over current ticket data, not a frozen set of historical rows.
Why do colleagues see different counts?
Their permitted ticket scope can differ. A shared configuration does not equal shared unrestricted access.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Zendesk
Application concept: Compare a Zendesk saved view's real review purpose with the supported filters and visibility in Tsumira.
Intercom
Application concept: Separate an Intercom team's saved workflow questions into personal and shared review views with named maintainers.
Microsoft Teams
Application concept: Plan a Teams explanation of a shared view's filters so colleagues understand why their permitted counts differ.