.webp)
Blog
Insights & updates from our experts
.webp)
.webp)
When a specialist opens a request that was submitted by someone from another account, the name of the account in which the requester’s person record is registered is now displayed next to the name of the requester. This is especially helpful for managed service providers (MSPs) that work with enterprise customers that have their own Xurrent account. Displaying the account name of the requester makes it easier for the MSP’s specialists to see which organization submitted the request.
When someone submitted the request for someone else and both persons are registered in the same Xurrent account, the account name gets displayed only once, next to the name of the ‘Requested for’ person.
To ensure that this information is displayed only when it adds value, the account name does not get displayed when the specialist who is looking at the request is working in the account that the requester’s person record is registered in. It also does not get displayed when the specialist is working in a support domain account that belongs to the directory account in which requester’s person record is registered.
A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.
3 Mins
July 1, 2026
News
Partners
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
