Insights & updates from our experts
In the View mode of a service offering, any request templates that have been disabled are displayed in a strike-through font, like this: 𝖯̶𝗋̶𝗈̶𝗏̶𝗂̶𝖽̶𝖾̶ ̶𝖾̶𝗑̶𝗍̶𝖾̶𝗋̶𝗇̶𝖺̶𝗅̶ ̶𝗁̶𝖺̶𝗋̶𝖽̶ ̶𝖽̶𝗂̶𝗌̶𝗄̶ ̶𝖽̶𝗋̶𝗂̶𝗏̶𝖾̶. In the ‘Standard Service Requests’ section of the Service Offering form in Edit mode, this indication did not exist. This has now been aligned.

To be able to see immediately which request templates are enabled and which are disabled, makes it much easier for a service level manager to decide which standard service requests should be removed from a service offering, for example.
A similar alignment has been made on the Request Template form, where discontinued service offerings are now displayed in strike-through font as well.

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)












