Insights & updates from our experts

When representatives from Xurrent, customers, and partners convene in the city where East and West coalesce, you can be fairly certain that it will involve lively conversation and an inspiring ambiance. And great conversations were had, in the Bosphorus Palace Hotel in Istanbul, about SIAM, ESM, Self Service, and automation, amongst many other topics. It was also a beautiful location to welcome some of our new Turkish customers and partners, in the region where Xurrent is expanding rapidly.

Decisions were made too, of course, because that is why the yearly Customer Advisory Board meeting is organized in the first place: to involve organizations that use Xurrent on a daily basis in determining the direction the platform should take for the coming year. Whereas in previous editions the emphasis was mostly on developing new features, this year the main focus was on improving existing functionalities. This is completely in line with our tagline: ‘The Complete Service Management Platform’: all relevant capabilities are already present in Xurrent.
Apart from several presentations about newly introduced functionalities (many of these requested during last year’s CAB) and strategic direction, there was ample time for feature requests by our customers, and for the consecutive discussions and voting. Some of the highest prioritized enhancement suggestions were:
- A tool to migrate configurations from QA to production
- The ability to schedule and email dashboards
- Making all Xurrent Self Service pages customizable

Of course, there was also plenty of time to have individual discussions during the lunches and dinners, or the boat trip and sight-seeing tour to the old city center with its ancient structures like the Grand Bazaar, the Hagia Sophia and the Basilica Cistern.
Once again, it was great to see the high level of involvement and expertise among all the participants, and we heartily thank everyone for that. It was this that made the 2022 CAB a resounding success that will be hard to top next year. Needless to say, we will try.

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)














