All ideas

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).

Please embed an AI chatbot into Clarity, so that we may ask it questions about certain incidents. Have it available as a side-bar in an incident. Questions may include: was enough done, how should I action, tell me more about specifics (eg. malwar...

Single queue and location for better visibility (instead of having to click into each individual queue/tab on the left navigation panel). Examples of different queues are Cyber Incidents, Self Service Hub, Threat Hunts, Health Alerts, and Other In...

The Clarity Automation offers a wall of KQL in the ticket comments which is messy. I feel this should be separated to another tab (perhaps "evidence" as an option?) so the comments can be maintained as a cleaner location for comments.

We have Entra Verified ID already within the organisation and this can be extended to our customer base to allow them to verify QC staff are who they say they are when interacting (I understand customers are asking for this already). We have the i...

I want the ability to restrict users viewing certain content/sub sections in the clarity portal for example, restrict some members with access to only view cyber incidents and some members to only view data security incidents tickets and some both...

Having a pop-up for the customer advising that they will not receive any emails if they remove all their contacts from Clarity would be helpful in creating friction and hopefully stopping customers from removing all their contacts.Also possibly ha...

Could a feature enabling us to schedule how long an analyst is first priority, second priority, etc or Do not contact. This would enable us to automate our on-call schedule within the clarity contacts tab rather than requiring us to manually updat...

An incident maybe raised as a P1, over the life of the ticket it might be realised that that was incorrectly raised as a P1. We need the ability for the Severity to be changed to be actually reflective of what it is.

On the dashboard under Root Cause Overview, there is a high number of tickets with the root cause as Undetermined. It would be very useful if these could be parsed out into something more meaningful. Thanks!