Insights & updates from our experts
The Service Desk console has been improved to help service desk analysts be even more efficient and to ensure that the search results are more likely to include useful items.
The first thing that you will notice in the Service Desk console is that the Search box asks for a subject.

So, rather than entering a few key words, the service desk analysts are now invited to enter a short description of what the requester is asking for.

Typing in a subject instantly triggers a fuzzy search. The search results are continuously updated as the service desk analyst continues to type. When a useful match is found, the service desk analyst can stop typing to select it. But before selecting it, the service desk analyst is now able to open a preview to make sure that it is really applicable. What’s new here, is that you are now able to scroll in the preview to see all the information.

If none of the search results are helpful, the service desk analyst can simply continue by pressing the New Request button. To make sure that the flow is intuitive, the New Request button has been moved to the left of the Search box.
After pressing the New Request button, a new request is opened and the subject that was entered in the Search box is placed in its Subject field to avoid the need to retype it.

Because the cursor is placed by default in the Search box, it should feel more natural to start the registration of a new request right there. End users will also see that the Search box is already in focus when they access Xurrent Self Service. That should encourage them to take advantage of Xurrent’s super-fast search functionality more often.


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.

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)














