Insights & updates from our experts
When the category of a request is set to ‘Incident – Request for Incident Resolution’, the following four impact levels are available:
- Low – Service Degraded for One User
- Medium – Service Down for One User
- High – Service Degraded for Several Users
- Top – Service Down for Several Users
When 2 requests are grouped together, Xurrent automatically increases their impact from ‘Low’ to ‘High’ if it concerns a degradation of service, or from ‘Medium’ to ‘Top’ if it concerns a service outage.
But there are rare scenarios where the impact of a request group only affects a single user. For example, when a monitoring tool generated a request in Xurrent about an issue with a PC, the manager of the affected user send an email to Xurrent to create another request for the same issue, and the user also submitted a request for this, it may be best not to complete 2 of these requests as duplicates. When they are grouped, all 3 of these requests will receive the same updates and once the group is completed, the requesters are automatically notified.
To support such use cases, it is now possible to lower the impact level of a request group, and thereby the impact level of the requests that are grouped in it, to ‘Low’ or ‘Medium’.


An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)














