Insights & updates from our experts
Incident-respondents are like superheroes. They get distress-calls at all times of the day, and they try their best to resolve the problem before the fire spreads. Like any superhero, they have skills and knowledge to attend to most issues they encounter. But just like other superheroes, they sometimes need allies to have their backs.
In this spirit, Xurrent IMR allows incident responders to tag other “Responders” to incidents. They can do so to keep some people (who manage a specific service for example) in the loop, or just to get help on something they don’t have expertise on. Keeping services online is a team exercise, and asking teammates to pitch in when you can’t solve something yourself should be easy. The tagged responders get an alert for the incident according to their notification rules, and can come in and acknowledge/resolve the incident themselves. Read the documentation about responders here
This method of transparent, quick and effective collaboration can help your team resolve incidents faster and fix the problem for the long run. It makes post mortem simpler and effective, as the right stakeholders have been able to follow the incident while it was still occuring. Allowing your on-call engineers to add responders from the right teams is the smart move.

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)













