Likelihood to Recommend Well suited in an IT environment where you have limited staff. It can be managed by one administrator. Reliability of the SaaS environment has been excellent. Flexibility in developing automated workflows to open, manage, and close Incidents. Change Management due to ability to modify OOB to meet the needs of our staff. Contract Management allowing us to be notified when a contract or license is up for renewal and setting reminders. Integrations are not easy to create and manage.
Read full review Great to manage your issues in a clear and centralised way. If your development teams work with
Jira , it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
Read full review Pros Cherwell's email handling automation works flawlessly. The only time that I have ever needed to reset the automation service that drives it is when my own server that houses the small connecting agent has some kind of problem and disconnects us from our hosted Cherwell instance. It just works. Emails to a certain address always result in a new ticket or update to an existing ticket. Cherwell is literally 100% customization in so many ways that it would be pointless to try to enumerate them. There is a very sizable list of already-created customizations (called "mApps") that you can download and apply to your instance. If you don't like them you can roll them back in seconds. But you can add and configure entire modules using one of these pre-defined, completely free, add-on packages. It's so easy to add features this way that I check the list of available mApps every month or so just to see what functionality I can add. Read full review Manageable workflow to ensure all users follow the same process. Can ban boards for easy visual of ticket status. Very flexible tool that can adapt to lots of different uses outside of the traditional service desk model. Added communication tools help you get out of e-mail jail. Read full review Cons Cherwell lacks modern UI capabilities such as responsive forms and CSS styling for web portals. Built-in reporting engine is hard to use and resource intensive to run. No patching model for small platform fixes, must upgrade to receive platform code changes. Read full review Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem). No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability. Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive. Request forms are very basic and there is no native dynamic field ability available. Read full review Likelihood to Renew Cherwell is still the best tool for the job in the market. Even though Ivanti bought them and are trying to convince everyone to move over to Neurons for ITSM, they have stated Cherwell will remain supported indefinitely and have a roadmap for future Cherwell development. Unfortunately, ISM is not as flexible as Cherwell (and the UX is atrocious), hence why many people are sticking with Cherwell (and why many Cherwell customers never purchased ISM originally)
Read full review Usability I enjoy the layout and configuration of our Cherwell Service Management instance. It did take me a bit to get used to, as with any new ticketing system, but now that I understand the system more, I thoroughly enjoy it! There are just so many options and the UI is very intuitive.
Read full review I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.
Read full review Reliability and Availability Almost always available, with exception for a handful of outages due to infrastructure related issues
Read full review Performance The browser client is mostly acceptable in terms of performance, but still lacks parity with the rich client. The rich client is not very performant at all. It's built on old architecture and relies heavily on a fast internet connection, good caching and database indexing. There are several unwritten rules with form design (and form arrangement) which most users are not aware of, but can severely impact performance in the rich client. This is where the flexibility of Cherwell can come back to bite you if you step outside the boundaries of these unwritten rules
Read full review Support Rating We generally have a good time with Cherwell support, however, there are the few niche cases where I have to explain how Cherwell works to the customer support agent on the other end. A little more product education for tier 1 support could go a long way in helping expedite support requests from SaaS customers.
Read full review I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.
Read full review In-Person Training I didn't partake in the in-person training, but it was available. I preferred the online method instead, which was a great experience. It was nice to have someone available to bounce questions off of and demonstrate how certain functions worked.
Read full review Online Training The training was great! We got together to review the system, its UI, and how to perform basic functions. Then there was plenty of time to ask questions and test out the system while there was someone available to assist.
Read full review Implementation Rating Implementation is a breeze. Each time I've implemented it, we had an outsourced vendor overseeing it & assisting where needed. However, Cherwell OOTB is ready to go, and configuring it for LDAP/SAML, etc. for authentication and user-imports is really straight forward. The infrastructure needed for Cherwell is extremely simple too - and installing the server & database takes no more than 20 mins
Read full review Alternatives Considered Much more customizable than other products, especially when ran in a self-hosted environment. Cherwell [Service Management] allows for greater flexibility of custom development and integrations to allow for automating tasks that traditional ITSM apps are not well suited for. Cherwell [Service Management] gives you the freedom to develop your own objects with minimal licensing costs.
Read full review When I evaluated
Spiceworks , it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did.
JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and
JIRA was the better option since it was less expensive and geared towards being a ticketing system.
Read full review Contract Terms and Pricing Model We have had great contracts with Cherwell and love the concurrent licensing model
Read full review Scalability We have never had any major show-stopper issues with Cherwell itself - more so with the infrastructure it sits on. Moving from in-house cloud (on Cherwell's side), to AWS then to Azure has caused multiple problems over the years (some still on-going), however the product has remained fairly stable
Read full review Professional Services As mentioned, they were always great to work with (minus the project management side). My only feedback would be to push back on requirements that don't make sense
Read full review Return on Investment As with any standard ticketing system, it helped decrease the time before first contact with clients. Our department was always concerned with keeping a low budget, and it was cheaper than most. My supervisor could easily tell how many resources were being put into each employee, so we had more visibility of our team's capabilities at a given time if we needed to take on something complex. Read full review JIRA has been incredibly useful. Our work is more organized and easier to view by the team members as well as upper-level people. Our work is correctly assigned and when there are issues, they can be immediately addressed within the tool. Users can attach screenshots or files of issues that help clarify the ticket. Developers can attach relevant data as well. Read full review ScreenShots Jira Service Management Screenshots