Insights & updates from our experts
A subtle but for knowledge management important change has been made to the way knowledge articles are stored within a request. One of the strengths of Xurrent® is the ease of assigning requests to teams of other, trusted accounts. Just as some other information of those requests, which can differ depending on the account from which the request is viewed, the application of knowledge articles (KAs) to a request is now also stored per account.
Imagine, for example, an incident which was first assigned to the first line support team of an account, but then forwarded to a team from a trusted account, and that both accounts can see and use the same knowledge articles. When that last team completes the request using one of the knowledge articles, this is then visualized in the report ‘Knowledge Article Link Rate’ in their account.

Until now, the application of the knowledge article would also count as a ‘Request completion with knowledge article’ in the account of the first line team, even though they did not apply the knowledge article. This has now changed. This also means that the application of a KA by a team of a trusted account is also only counted in the ‘Usage’ section of the article in that trusted account.


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)














