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.

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

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)














