
My team used Remedy IT Service Management during project and deployment planning for a very large payroll centralization project. Because we were facilitating a large enterprise deployment with multiple phases/waves (subject matter expertise did not exist in the legacy systems), my team drove the majority of the post-live support model design elements, as well as overseeing the change management activities as we planned to bring not only the customer live on the new product, but had to prepare the Help Desk to support the new systems and understand the diagnostic process for support inquires. Review collected by and hosted on G2.com.
I noticed during a post-live volume spike that there seemed to be problems or process gaps linking enterprise tickets to the parent ticket (example: the team learned of a global configuration setting problem in the payroll system we were supporting, and after receiving the first set of calls, we continued to get inundated with new calls for the same global issue. The help desk staff seemed to have difficulty linking all calls to the parent issue, and this seemed to be an ongoing continuous education issue, because the steps were not always clear and/or intuitive in the tool directly. Review collected by and hosted on G2.com.