Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
Another AI powered feature is available and ready to power your business: AI Automation Rule creation. If Xurrent +AI is enabled in the ‘Account Settings’ section of the Settings console of your account, you will now see a text prompt at the top of the Automation Rules designer. Enter a narrative description in your own language of what the automation rule should accomplish and let the AI do the rest.
As an example, let’s create an automation rule where a note gets added to a request for Top impact incidents adding the service owner to the request:
After pressing Run, Xurrent+AI will automatically translate your message into an automation rule.
It’s worth noting that the AI is not perfect (though it’s pretty darn smart!). It is always recommended to review and test the logic prior to activating the rule in production. Once activated – the automation rule can execute as designed.
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.
5 Mins
September 10, 2026
Incident Management
Service Management
News
Enterprise
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.
8 Mins
May 30, 2026
Service Management
Enterprise
Integrations