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


A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

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














