Cherwell Service Management vs Zendesk comparison

"Clear processes with transparent responsibilities led to more efficiencies within the teams."

"Its integration features, orchestration features, and discovery tools are the most valuable. It is also pretty stable, and it can be as scalable as you want."

"The most valuable features are problem management and change management."

"The dashboard is very useful to get a quick overview of current tasks."

"All our activities are carried out in the one place."

"The dashboard and the reporting functionality are the solution's most valuable features."

"The most valuable features of Zendesk Support are collaboration, reports, and a self-service portal. The customer and team can see all the information needed from the portal."

"Zendesk Support has a lot of good APIs."

"It's a very stable tool, very powerful."

"What is cool about Zendesk Guide is how it works together with others Zendesk products. Especially with support and with the analytics. Put those together for a small or medium-sized company and it's a really powerful tool."

"I found the user experience with vendors on Zendesk to be straightforward, especially when it comes to understanding and searching for specific tickets. The search and navigation tools are easy to use, and I haven't encountered any issues with delays or communication gaps in ticket resolutions."

"One of the most valuable features is that Zendesk gives you a lot of configurability, and a lot of leeway in terms of customizing the look and theme. Zendesk offers you the facility to design your own landing page, as well as the look and feel of the entire knowledge base. At the same time, they offer themes that you can simply purchase and implement. Either way, it can really be turned into the right look and feel of the knowledge base required by our company, which is very important—if you have a bland-looking page, most of the time, people will lose interest. Zendesk also allows you to test the customizations before you publish it. It gives you a sandbox location where you can test everything new that you're trying to create and publish, which is very interesting."

"The product offers very good management. It has a great ability to assign tickets based on content."

"It is very easy to connect back and forth between the requester and the person fulfilling the ticket."

"Access is only available if we're on VPN."

"Areas for improvement would be the service catalog and customer catalog, which is not very user-friendly. The shopping cart experience is also terrible - you submit and go straight to the cart, you can't continue shopping or see your overall cost."

"Application service mapping, GRC, SecOps, and things like that need improvement."

"The stability, specifically in the on-premises deployment model, could be improved."

"The solution could integrate better with QR codes from some websites such as Facebook."

"If I write an article, and I have a team of 30 people, and they all have a Zendesk account, when I write an article, I send them an email. "Hey guys, I just wrote this article. It's one of the most popular topics this month on which we are not covered. Please check it and make sure that you include it in your resolutions". The issue is, once I send it to those 30 people, and they open it, the next morning, that article is the most popular article."

"Zendesk Guide's customization could be improved. I would like it to be easier and maybe open-sourced, so that if you have a developer in your company, you can do it yourself. Right now, that isn't allowed, so you need to have it done via the integrator. Another improvement—this is nit-picking—is that it could be less easy to make changes. Some things are so easy that they sometimes look a little amateur-ish. Most of the templates are built-in so they can be used directly, so they are very simple."

"There is always a network issue with Zendesk. But we don’t know whether it is managed. The network issue is that when I call, it does not let us."

"The price of the solution should be reduced."

"The data you get when logged in to Zendesk Support differs from the data you get when you programmatically query Zendesk Support through its API because of a sync time delay."

"Sometimes if there was a way to just flag the actual issue out of those email chains - that would be really helpful."

"One of the drawbacks of Zendesk is that it doesn't provide a secure way for us to send data. So, we usually use a secure SharePoint folder link. We put that in the Zendesk ticket so that the requester has a secure way of getting to their data."

"For an ITIL user, the cost is probably about 50 bucks a month."

"We pay for the solution on a yearly basis and my understanding is that the cost is about $30,000. That's the cost for 24 to 25 agents."

"You have to pay extra for better support. So it's not only the license that you pay for, but you have to pay extra for the support as well."

"Zendesk's licensing is not cheap. For Enterprise, we are paying $200 per agent. It's a per-month cost, so it's pretty steep. There are some services you need to pay extra for. For example, with Zendesk Guide, we had to buy the most expensive offering in order to get Multibrand and everything. We also had to pay a lot of money for themes."

"There are different plans that are offered. We are using the entry-level plan. The overall price of the solution should be reduced. The price is too high."

"The price is very competitive."