Insights & updates from our experts
Xurrent automatically generates notifications. These notifications may inform a requester that his request has been completed, tell a specialist that someone added a note to a task that is assigned to her, etc. These notifications show up in the user’s Notification Center.

If a user has specified in the Notification Settings that her notifications should also be sent via email, she will find a new notification in her Notification Center for each email she receives from Xurrent. And when there is an unread item in the user’s Notification Center, the user sees a blue dot over the toolbar icon of the Notification Center.
To make it easier to manage the new items in the Notification Center, each email notification now has a web beacon embedded in it. This beacon ensures that, as soon as a user opens an email that was generated by Xurrent, the corresponding notification in the user’s Notification Center is automatically marked as read. That means that this notification is automatically moved from the Notification Center’s ‘New’ view to the ‘All’ view.


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)














