Status = New; Create this view so you have the ability to quickly view all of your New tickets.

Part of your daily workflow is ensuring this view is empty because you have responded to/handled all new tickets!

Create views to organize types of work. 

Projects are a common example of work that you may not need to see in your default view.

A critical decision here is how to filter these projects. We recommend filtering by project statuses, Link Types, Ticket Custom Fields, or Ticket Tags.

Create a view for each team member to see only the tickets assigned to them. This helps them focus on the tickets that they're responsible for.

Add Group By = Status to group tickets so your team members can see which tickets are in which part of their lifecycle. "Customer Reply" will populate at the top so they can be sure to address any replies from your end users!

Some Syncro Users like to set this view as their team member's default view.

If you have multiple Organizations in Syncro, you can create views to quickly see all tickets from those Organizations. For example:

• All tickets from the "Finance Department" (business-unit based)
• All tickets from “Acme - Chicago” (location-based)
• All tickets from “Goldthread” (a specific VIP client).

Create views based on the purpose, or the names of specific software packages that your company uses.

Purpose-based examples include: “Accounting & Financial,” “Communication & Collaboration,” or “Development & IT.”

Software-based examples include: “QuickBooks, ”Slack," "SharePoint," and “Google Workspace.”

Create individual views to easily see all the tickets that match a specific Issue or Type, such as: 

• Onboarding,
• Requests, 
• Incidents, 
• Move Add Change, or 
• Deskside tickets.

Ticket Tags provide a great way to create customized views. 

For example, if a ticket contains the tag “Security Team,” those tickets can appear in a Ticket View so that the security team can easily see things that they should take care of.

And, since it's possible to tag tickets using Ticket Automations, you never have to manually tag a ticket.

Create a view to quickly see tickets that need escalation.

Typical workflows put these tickets in an "Escalated" status or use an “Escalated” ticket tag. Use either of these filters to separate these tickets into their own view.

Create a view for tickets with specific billing statuses to help ensure that all billable items on tickets are invoiced.

If you have a billing/accounting team member that only needs a view of these types of tickets, this view will help them see only the tickets they need to focus on.