Insights & updates from our experts
Nowadays, it is not uncommon for a large IT department to support more than a hundred services. Email is often cited as an example of a service, but each department of a modern enterprise seems to rely on a whole set of specialized application services. The finance department has its applications, but so does HR, the sales team and the people responsible for the manufacturing process. All these applications need to be hosted, supported and maintained.
The sheer number of services is a challenge for the IT department, but it can also be difficult for the end users to find the service for which they need to obtain support. This gets even harder for the end-users when they can request support not just for IT services, but also for the services provided by HR, facilities management and the legal department.
Xurrent Self Service has the advantage that end users only see the services that are relevant for them (e.g. an end-user who works in marketing should not see the services used by the R&D department). Also, these services are nicely grouped by support domain and category. But in many cases, the user just knows that there is an issue with SAP or Salesforce CRM. In such cases, it would help if the user could simply search for ‘SAP’ or ‘CRM’ to find the service.
That is now possible. The scope of the Search functionality in Xurrent Self Service and Xurrent Mobile has been extended to ensure that it also looks for matches in the service names and service descriptions.

So when searching, end users not only see the request templates that match their search criteria; they also see the services that might be relevant. This provides another quick way to get help from the right specialists.

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)














