All ideas

We have a lot of retail colleagues who don't necessarily have contact details, so can be hard to liaise with when DA has been taken, the likely scenario is they would call our internal IT Service Desk to reset their credentials after DA by QC is t...

Darren Chapman (Quorum Advisory Services) and I were reviewing the Clarity dashboards last week, putting together a Board pack that will go to the Board one a quarter. We thought it would be useful if you could filter the following sections by tic...

Why is it useful? This idea aims to reduce the volume of repetitive notifications and enhance the clarity and urgency of communication. By streamlining the email notification process, customers can better manage and prioritize their responses, lea...

This would be useful as it prevents the need to have a separate system for when a ticket is passed over to internal SOC, and keeps all comms both internally and with QC in one place.

If someone changes phone numbers, admins to the clarity portal should be able to reset the 2fa so that the user can log back in again and reset it up. Also it would be useful to see the last login time a user logs into the portal so I can review u...

we currently show dates for Date Created and Date Resolved under the MTTH and MTTR KPIs, it would be helpful if we presented the timestamps too (e.g. from 2024-12-18 to 2024-12-18 12:34 for both fields).

Should be pretty self-explanatory this one, but sometimes you make a typo and it would be good to be able to go back and fix it without having to clarify what you meant by adding an additional comment.

When an incident only affects a single user it would be useful to see their username in a column, and have incidents searchable by that user. This would to show all incidents involving a specific user and to find incidents when the number is not k...

We would like to be able to generate tickets when an email is submitted; idea of flow: email is sent to a QC mailbox ticket is generated in Clarity (service request, incident) email response noting ticket reference

The current search functionality is limited to specific fields (ID, Summary, Cause, and Resolution at the moment, I think) so I can't easily find tickets based on information contained in other fields, such as Description, Entities, Notes, Assessm...