Insights & updates from our experts
Although each person registered in Xurrent only has one primary email address, it is also possible to create or respond to requests with a different email address linked to the person record. This is handled by the mail API. Xurrent automatically relates these requests or notes to the right person. The notification of a newly registered request will then be sent to the primary email address of the requester.
This is especially useful at universities, for example. Before a student had originally registered, there was probably already email communication with the student administration. When officially registering, the student often receives a university email address. This then becomes the primary email address, while the personal email address is saved in the contact details. If the student submits a new request from their personal email address after registration, this will be handled properly.
It is of course desirable that a notification is also sent to the email account that was used. And that’s exactly what happens from now on. For this, a new email template has been added.


An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

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)












