Insights & updates from our experts
To show the language preference of a person, Xurrent used to display a circle over the person’s picture with a flag that symbolized this language. This was mainly useful for multilingual service desk analysts when they accepted a call from their CTI client. It allowed them to start the conversation in the caller’s preferred language.
We have since learned, however, that flags can stir up emotions in people. Canadians may not want to see the flag of the United States over their picture, German-speaking persons in Switzerland may not understand why the German flag is displayed in their record, people in Flanders may not identify with the Dutch flag, etc.
That is why the graphical language indicator has been removed from Xurrent. It is no longer displayed in the person records, and neither is it visible any more for knowledge articles.
To ensure that service desk analysts can still see the language of a caller or knowledge article, and that specialists can still easily look up the language of a requester when they update an existing request, the graphical language indicator has been replaced with the name of the language that the person selected in his or her Xurrent preferences.


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)















