Insights & updates from our experts
Support for Next Business Day Targets
The target definitions of a service level agreement (SLA) are specified in a service offering. This makes it possible for providers to define multiple service offerings for each of their services. A provider may, for example, offer its Email service at three different levels, e.g. Bronze, Silver and Gold. The availability, reliability, RTO, RPO, standard requests, etc. may be different for each of these three service offerings. The same is true for the response and resolution targets that are defined in them.
Different response and resolution targets can be specified for each impact level, for RFCs, for RFIs, and for each standard request. And a different support hours calendar can be associated with each set of response and resolution targets. This gives providers the flexibility they need to be very specific about the SLA targets they commit to, while also making it easy to maintain the service offerings that their customers can choose from.
There was one target, however, that Xurrent did not yet support. That is the ‘Next Business Day’ target, which is commonly offered by managed service providers (MSPs). This is why it is now possible for service level managers to indicate for each target whether it is defined in ‘Hours’ or ‘Business Days’.

To understand how a target is calculated when it is defined in business days, let’s use the example of a request for a new mailbox. The support hours for this standard service request are from Monday through Friday, from 9am until 5pm. A response target has not been defined, so we can concentrate on the resolution target.
If a request is submitted on Friday at 10am, its resolution target will be at the end of the following business day. That would be Monday at 5pm. Likewise, if the request is submitted on Friday at 4pm, the target will also be Monday at 5pm. Even when the request is submitted on Sunday at 11pm, the target will still be Monday at 5pm.
Because the next business day starts on Monday, the target will be Tuesday 5pm if the request is submitted on Monday morning at 0:01am. The target will also be Tuesday 5pm the the request is submitted on Monday night at 11:59pm.

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)














