Insights & updates from our experts
As a follow-up to the recent improvement of the Source labels that are displayed in the request reports, the default values that Xurrent specifies in the Source field of requests have now also been adjusted to make them a little easier to understand.
Henceforth, the Source field of a request that was registered in the Service Desk console will be set to ‘Xurrent’ rather than ‘web’. Similarly, requests that were registered in Xurrent’s self service interface or the Xurrent App will get the Source field value ‘Xurrent Self Service’ instead of ‘self service’. And if the request was submitted by sending an email to Xurrent, its Source field will be ‘Email’ instead of ’email’.
Note that the Source field values of existing requests remain unchanged. If desired, organizations can update the Source field value of those requests by performing a full export, removing all columns from the export file except for the column that contains the request IDs and the Source column. The values in the Source column can be then updated by performing a search/replace, after which the file can be imported to update the Source field values of those requests.

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)











