Insights & updates from our experts
The Support URL field used to be included in the ‘Custom Links‘ section of the Settings console. There it was mostly overlooked, despite the fact that it can be quite useful. This field makes it possible for support organizations to provide another means of contacting them when someone is not able to access Xurrent to submit a request (e.g. when he/she is struggling to set a Xurrent password).
To make sure that a suitable value is entered in this field shortly after the creation of a new Xurrent account, this field has been moved to the ‘Account Settings’ section.

The Support URL field also got a more informative hint text. This should make it clear to account owners that they can enter a website URL, email address or telephone number in the Support URL field.
The easiest way to test whether the value that was entered in the Support URL field is presented correctly is to go to {{account_id}}.Xurrent.com/get_access. After you submit your email address there, you will see a page that contains the support URL. By default, the value in the Support URL field is also included in the following email templates:
- Get Access
- Email Verification
- Enable Two-Factor Authentication
- Enabled Two-Factor Authentication
- Disabled Two-Factor Authentication
- Two-Factor Authentication Recovery Code Used

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)














