Insights & updates from our experts
When the Service Desk Analyst role was given the ability to update a request’s requester (see Update the Requester of a Request), the Specialist role also got an extra capability. Specialists were already able to use the Xurrent App and Xurrent Self Service to submit a new request on behalf of someone else, but they were not able to do this in the Service Desk console.
To align this better, specialists can now select someone else in the Requested for field when they are registering a new request in Xurrent’s Service Desk console.

Specialists still cannot select another person in the Requested by field to discourage them from acting as service desk analysts. Or rather, to ensure that they are still encouraged to refer end users to Xurrent Self Service or the service desk when they contact a specialist directly to submit a new request.
If a specialist does need to be able to act as a service desk analyst, he/she can be given the Service Desk Analyst role by someone who has the Account Administrator role.

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)














