Insights & updates from our experts

Wherever we can, we try to minimize the amount of administration required from support specialists. We don’t just do that to make the support specialists happy, though. It saves organizations real money when their people can work more efficiently.
Recently we found a way to make it a little easier to complete requests of the category ‘Complaint’, ‘Compliment’ or ‘Other’.
Since these types of requests are not related to a specific service, they do not get considered during the problem management reviews for any of the services (i.e. they will not show up in a problem manager’s Requests for Problem Identification view). Instead, such requests are typically reviewed on a periodic basis by the service desk manager with the objective to identify support improvement opportunities.
That means that the Completion reason field is not needed for these requests to identify potential problems. In turn, that means that there is no reason to ask support specialists to select a completion reason when they complete such requests. So, from now on, the Completion reason field will no longer become visible when a request of the category ‘Complaint’, ‘Compliment’ or ‘Other’ is set to the status ‘Completed’.

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)














