Insights & updates from our experts
Customer Satisfaction Reports
Requesters are encouraged to let their support organization know whether or not they are satisfied with the way their requests were handled. To capture more responses, the ability to provide feedback is now available from within completed requests for 28 days. End users can do this in Self Service and support specialists can do this when they are in Xurrentâs full UI.
To ensure that support organizations are equipped to analyze these responses, the following two reports were already available:
Now two more reports have been added to the âReportsâ section of the Analytics console:
- Customer Satisfaction
- Service Desk Customer Satisfaction
The âCustomer Satisfactionâ report tracks the number of positive and negative responses over time. From these numbers, the report also calculates the satisfaction percentage, i.e. the number of positive responses divided by the total number of responses.

In addition, this report tracks the response rate. This is calculated by taking the number of requests that have a value in their Satisfaction field and that were completed during the reporting period and dividing that by the total number of requests that were completed during the same reporting period.
The âService Desk Customer Satisfactionâ report provides the same information but takes into account only the requests that were completed by the service desk without the help of any other team.
The service desk is the team that is selected in the Service desk team field of the first line support agreement (FLSA) that covers the Xurrent account in which the report is run. This can be an external team from a managed service provider (MSP) that takes care of the service desk function for its enterprise customers. For such MSPs the trends that this report shows makes it possible to stay in control of the perceived value that each of their service desks provides.

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)














