Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
In Xurrent it is possible for someone to have SLA coverage for more than one instance of the same service. For example, a manager of a multinational organization may be covered for several payroll environments. Each environment will have a setup that is specific for one of the countries in which the organization employs people. When this manager starts to submit a new request in Xurrent Self Service and selects the ‘Payroll’ service, the manager is asked to choose one of the payroll instances.
Xurrent used to guide the requester by asking:
- Which of the following service instances is most relevant for your request?
But because most end users are not familiar with the term ‘service instance’, this question has now been simplified to:
- Which of the following is most relevant for your request?
This should make Xurrent Self Service sound a little less technical to end users who are covered for multiple instances of the same service.
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.
5 Mins
September 10, 2026
Incident Management
Service Management
News
Enterprise
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.
8 Mins
May 30, 2026
Service Management
Enterprise
Integrations