Categorizing views

Hi Martin,

We use emojis to give them transparency. In fact we also clustered them according to the status:

New

- limited to the group or splitted in case of several topics (process orientated for example)

Open, pending, waiting

- personal tickets and group/ groups you are not working at but because of transparency

- tasks

- escalated tickets (limited to the group)

Closed

- group/ own tickets

Views for reports and special proactive work

Regards,

Stephan

Hey @martin23 - 

Love @stephan12's suggestion, but would also suggest you take a moment to consider the purpose of each view, and if any can be consolidated.  By leveraging dynamic elements in view configuration, such as 'Tickets in {current users} groups,' and then grouping by 'group,' you may be able to reduce the overall number of groups.  Additionally, take time to ensure that each view's visibility is set to only the audience that needs it (ie Tier 3 Tickets is only visible to agents int he Tier 3 Group).  Hope this helps!

Brandon

Absolutely Brandon, we are also practicing to use the same view for every group, limiting the numbers of tickets to the users group only. Really a good and necessary hint. Thank you for mentioning.

Cheers,
Stephan