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
PagerDuty
Score 8.6 out of 10
N/A
PagerDuty, Inc. (NYSE:PD) provides digital operations management. Serving organizations of all sizes, PagerDuty aims to help them deliver a perfect digital experience to their customers, every time.
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's the most effective when you need to alert someone specifically or a team. It sends notifications everywhere, like email, phone, and SMS, ensuring critical issues are never missed. The feature, like the event orchestrator, allows us to set logic-based rules that automatically suppress non-emergency alerts.
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)
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 UI is more complex than I would like. Part of the challenge is that most users use PagerDuty infrequently; I don't remember how I changed a policy last time. Another part of the challenge is that some users expect alerting to be a trivial feature, and are reluctant to invest any time in reading the documentation.
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.
PagerDuty is reliable and easy to set up. It gives an effective way to notify the team about critical incidents which results in a faster turnaround time on issues. users can customize their alerts rules based on their preferences. Overall it's effective and easy to use which adds great business value.
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.
I have not use the 2 technologies for as long as I have used PagerDuty but in my opinion PagerDuty makes things a lot easier. The other tools got the job done and got alerts out but PagerDuty just seemed to make the setup for on-call alert schedules and integrations easier than the others. This isn't to say the others are difficult, just that PagerDuty was slightly better. I also have noticed that more tools have options to integrate to PagerDuty over the other tools.
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.
![Screenshot of Similar Incidents [Apple iPad], Open Incidents [iPhone 8], On-Call Schedule Menu [Apple Watch])](https://media.trustradius.com/product-screenshots/kf/M5/L6SIK3HGD31M.png)
