Insights & updates from our experts
As the number of data transactions in Xurrent is steadily increasing, it is important to keep monitoring the most used transaction types and optimize those, to reduce resources and speed up delivery. One such transaction type is the outbound email for team assignments of requests. If a team consists of 10 members, for example, 10 emails are created and sent to 10 different people.
The salutations for these team assignment notifications are now no longer directed to the individual recipients of the email, but to the team that the request is assigned to. In the case of the example above, only one email is now created, sent to a group of 10 people.

This change affects the following notifications:
- Request Assigned to Team
- Problem Assigned to Team
- Task Assigned to Team
- Project Task Assigned to Team

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)











