Insights & updates from our experts
Since a few weeks, the information that is necessary to identify a request in a supplier’s service management system that is different from Xurrent, is no longer stored per request but per account. This ensures that this information is no longer overwritten when a request is assigned to another, trusted account.
The Supplier and Supplier request ID fields are now also shown in the affected SLAs (ASLAs) that are visible from the SLA reports, whenever that information is relevant. The supplier of the SLA between the supplier and customer is also added, as ‘SLA supplier’. This is now also shown in the preview of the ASLA, when the provider of the service of the service offering related to the SLA is an external service provider.


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)

.webp)












