Insights & updates from our experts
The work hours of teams, as well as the service and support hours of service offerings, are maintained in the ‘Calendars’ section of the Settings console by Xurrent account administrators. There the administrators can add holidays to calendars to exclude specific periods from these calendars.
All holidays linked to a calendar used to be visible when the calendar was opened in View mode. Over time the list of holidays became quite long for many calendars. To ensure that the holidays that are still relevant can be spotted more easily, past holidays are no longer displayed. These holidays, which have an end date and time in the past, remain hidden even when a calendar is placed in Edit mode.
In addition, disabled teams no longer show up when a calendar is opened in View mode, even though there may be several disabled teams that still have this calendar selected in their Work hours field.
Similarly, the service offerings presented in a calendar now no longer include the ones that have been discontinued, even though some of those may still have the calendar selected in their Service hours field or in one of their Support hours fields.

As a result, calendars provide only the links to the related records that are still relevant. That makes these links useful, even when a calendar has been in use for many years and is linked to many past holidays, disabled teams and discontinued service offerings.

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)














