Insights & updates from our experts
SLA Breach Notifications for Standard Requests
Since a few months it is possible to define SLA Notification schemes and relate these to the ‘Response and Resolution Targets’ section for incidents with impact ‘Low’, ‘Medium’, ‘High’, and ‘Top’. This is done to notify certain people when an SLA target is about to be breached, so that everything can be done to prevent this from happening. It is now also possible to add SLA Notification schemes to standard service requests in the Service Offering form.

Notification schemes can be set up in the ‘SLA Notification Schemes’ section of the Settings console by a person who has the Service Level Manager or Account Administrator role.

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)











