Cherwell Software was a full suite of service management tools competing with BMC Remedy, ServiceNow, and IBM SmartCloud. It was acquired by Ivanti, and has reached EOL.
N/A
SymphonyAI IT Service Management
Score 9.1 out of 10
N/A
Symphony SummitAI, formerly the Summus IT Management Suite, is an ITSM and system monitoring offering from the company of the same name in Palo Alto.
N/A
Pricing
Cherwell Service Management (discontinued)
SymphonyAI IT Service Management
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Cherwell Service Management (discontinued)
SymphonyAI IT Service Management
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Cherwell Service Management (discontinued)
SymphonyAI IT Service Management
Features
Cherwell Service Management (discontinued)
SymphonyAI IT Service Management
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Cherwell Service Management (discontinued)
10.0
53 Ratings
20% above category average
SymphonyAI IT Service Management
8.7
20 Ratings
6% above category average
Organize and prioritize service tickets
10.052 Ratings
8.920 Ratings
Expert directory
10.041 Ratings
8.815 Ratings
Service restoration
10.035 Ratings
8.418 Ratings
Self-service tools
10.051 Ratings
7.917 Ratings
Subscription-based notifications
10.038 Ratings
7.915 Ratings
ITSM collaboration and documentation
10.048 Ratings
9.317 Ratings
ITSM reports and dashboards
10.051 Ratings
9.720 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
Cherwell Service Management (discontinued)
10.0
44 Ratings
20% above category average
SymphonyAI IT Service Management
9.0
20 Ratings
9% above category average
Configuration mangement
10.042 Ratings
8.420 Ratings
Asset management dashboard
10.041 Ratings
8.920 Ratings
Policy and contract enforcement
10.031 Ratings
9.615 Ratings
Change management
Comparison of Change management features of Product A and Product B
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.
It is best for handling daily incidents and change records in the organization. And also provide features like which incident will have higher priority, and which have less and on the basis of that developer do their daily activities to resolve them. It also helps in managing our compliance change logs, which help the compliance team.
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.
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)
The overall satisfaction is great and it offers great features. By expanding to using AI feature of Symphony Summit, we look forward to automate even ticket tracking and ticket resolution. The support provided by the symphony SummitAI team is also robust compared to industry standards and the team also conducts regular reviews to find out any dissatisfaction from the clients.
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.
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
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.
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.
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.
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
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.
The main reason for choosing Symphony Summit is the customization. We wanted to have a separate tool for our business unit. Compared to ServiceNow, which requires a license to approve a request, Symphony does not require a license. In addition, it is much easier to customize and scale.
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
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
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.