ilert Alternatives

I've been using JSM for a while now, and overall it's been a solid experience. It's not without its quirks, but for an ITSM tool that sits inside the Atlassian ecosystem, it does the job well and the team has largely adapted to it

Ticketing itself is nice and we do appreciate how flexible the workflows are for different ticket queues and teams, but it can be complex to implement and troubleshooting these during implementation is a bit confusing. Asset management is a potential use case for Freshservice as well, but we've found it to be extremely lacking in both information gathered and ease of implementation (with the scanning server application still requiring internet explorer on its backend).

BMC have been great to work with since we went live with Helix. Their training team are helpful and adaptable, and the product is easy to configure.

User Experience From an end-user perspective, SysAid is intuitive, easy to navigate and user friendly. The interface makes it straightforward to log support tickets and track their progress throughout the entire lifecycle. I also appreciate the regular notifications and updates, which keep me informed on the status, approvals and closure of tickets. The integration with Microsoft teams through the SysAid bot is a significant advantage because it is a convenient and efficient way to access the platform and interact with service desk without having to switch platforms. Overall, I am satisfied with the user experience. Developer Experience From a developer standpoint, I connect to the SysAid API to retrieve data for downstream reporting and analysis. Initially, understanding the developer documentation and establishing API access was challenging. I had a lot of back and forth with your team trying to establish access to the APIs. But after several interactions, everything was successfully configured. One area where the documentation could be enhanced is in documenting the relationships between the various APIs and data entities. In the developers manual, it will be convenient to create the necessary mappings of how each API or 'table' relates to each other. Establish primary and foreign keys so that one can cipher which column in one API relates to another. Since much of the raw data is made up of IDs, understanding these relationships is essential for correctly joining datasets and producing accurate analysis. This, I believe, would make integration significantly easier. But overall, Sysaid has significantly streamlined our ticket management process with its ease of use, effective notifications and integration with Microsoft teams while enhancements to the developer documentation would make API integrations and data analysis more efficient.

Having implemented ServiceNow ITSM for our EU-based manufacturing client, the imact on our efficiency has been massive. This platform has streamlined our core processes in such a way that we are able to provide fast turnaround for standard service requests, access provisioning and defect tracking. I must mention the in-built capability of AI which provides automated suggestions and prompts which helps our teams to give quick and quality solutions. This level of consistency from the AI capability is helping us to keep documentation sharp and operations very smooth. Post ServiceNow implementation we have observed high visibility on overall improved quality.

Ease-of-use, effectiveness and efficiency are getting better day by day.

Since going live, the overall experience with Halo ITSM has been positive. Compared to our previous ITSM solution, the platform has given our org significantly more flexibility, visibility and control across service management processes, while still remaining relatively straightforward to administer and develop internally. One of the strongest areas of the platform is its flexibility. Workflows, forms, automations and service processes can be adapted quickly as operational requirements change, without requiring large scale redevelopment work or heavy reliance on third party consultancy. This has allowed us to continually refine processes post implementation rather than treating the go-live state as fixed. The automation and integration capabilities have also delivered tangible operational benefits. We have been able to streamline ticket routing, approvals, notifications and asset-related processes, reducing manual handling and improving consistency for support teams. Integration options and API availability have supported wider development work around our self service offering, including continued enhancement of the our chatbot experience and virtual agent functionality. Another positive aspect has been the pace of platform development. Regular updates continue to introduce new functionality and improvements, and Halo has generally shown a willingness to engage with customer feedback and feature requests. The product feels actively developed rather than static. From an administration perspective, the system provides a strong balance between configurability and usability. Reporting, custom fields, service catalogue configuration and asset management capabilities have all improved our ability to tailor the platform to organisational requirements across multiple teams and service areas. As with any implementation, there have been areas requiring workarounds or additional configuration, particularly where legacy process alignment or data migration complexity existed. However, overall the platform has enabled us to modernise and consolidate a number of service management functions more effectively than was possible previously, and the overall experience has been very positive.

If you are looking for a solution that you can setup over the weekend, SMAX is NOT that. That said, if you want a solution that forms the centre of all your operations, IT and Non IT, that does not require a re-build every two years, then the investment is worth your while. Also, with the premium licenses, EVERYTHING is included, it's not and another module at an exorbitant cost like Service Now.