Insights & updates from our experts
In certain emergency situations it is important to be able to immediately contact the right person within an organization. That would be the case for incidents related to cybersecurity, for example. Compliancy directives such as NIS2 or CMMC, even aim to make it required for service management organizations to publish their emergency contact information. Xurrent now supports this by adding the ‘Emergency’ contact type to the Telephone and Email fields of the ‘Contact Details’ section in the Organization form.


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)











