Zendesk Reviews

We run our support and customer services flow through Zendesk. The primary use for the solution is customer experience and assistance.

There are a lot of features to speak about. The solution has a strategic vision indicator that is a plus for me because I need to understand our customer's reason for contact, what kind of customers contact us, what issues are most frequent, what kind of issues we can solve in a better time, or the time of the day do we give support. This allows us to improve ourselves as a business.

The solution is very critical for us because we can extract information about Net Promoter Scores which is in general terms, the satisfaction of our customers, we can prioritize some developments or improvements that we need to make in our systems. 

The feature to move over my customer experience team tickets for different specialists is very valuable for my team.

The customization that is in place is really fast.

A very complete solution.

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

They do not have any operations in Brazil for invoicing, this forces us to deal with international invoices which cause us some difficulties to close accounts in our accounting department. Making invoices in Brazil would be beneficial, other companies allow this such as Amazon Web Services.

We have been using the solution for three years.

The stability is really good considering we are international and the internet works really well.

We never suffered any stability or any difficulty increasing our operation. Some parts of the month we have more flows of transactions and more cost. We can run with no problem, we do not have any delay operating. 

Currently, we are upgrading and going to be having more users inside our company. We are hiring more people and we are very satisfied.

We have 16 users currently and by the end of the months, we will have 23.

We had no problems with their technical support.

We started three years ago with their support solution for proof of concept. We made a small proof of concept to in our company. That proof concept ran really well and we started to apply it with our users. It all went so fast, the starting process and deploy were so easy. The deployment took about one week.

The price is very competitive.

My advice for others thinking about purchasing the solution is to understand the purpose. Zendesk is not a solution for sales. I know that they tried to have a solution for sales but it is a customer services solution. They designed the solution for customer services and adapted it for sales. When we used this solution it turned out to be very poor. Zendesk is a very good world-class solution for customer services, not for sales. For sales, there are better solutions such as Salesforce. 

We tried to find a solution better and cheaper than Zendesk locally and we have not found any solution so complete and flexible as Zendesk.

I rate Zendesk Support a nine out of ten.

We are in support. Zendesk is being used by the IT group help desk and also by our team. We are an internal team that supports SharePoint, Salesforce and Tableau. So we use it for tickets for customers' issues. And then of course I see folks use it for the help desk for everyone else internally.

In terms of the most valuable features, we like the SLA options and the reporting feature because it runs a report.

Additionally, it has good management, the ability to sign tickets based on content, multi-channel support, the self-service portal, the integration with Salesforce, the setup process, and the product features as we are currently using them.

We go in there and we set up our requests for how we want it for each of our groups, meaning for the Salesforce team, and so forth. And then we change it accordingly, adding different features or attributes based on the need, and then run reports.

In terms of what could be improved, it was not easy to set up so we're only using a third of all of the features, and we wanted something that was easier to configure and set up. I asked my director how come we don't just keep Zendesk because it doesn't cost anything, we're already paying for the file. Why would we turn around and buy a Cadillac, like ServiceNow for IT? He said because we're only using some of the features. We don't have anyone who has the skill set to do the configuration. And the way the service model is with ServiceNow, we have a team that uses it in our organization. So we have the internal expertise instead of relying on a vendor for support.

I have been using Zendesk Guide for probably three years. I believe we've been on the Core Optimization package.

Zendesk has been very stable. Which is why I was trying to understand why we were switching. The director said that there are other features that we want that ServiceNow offers and Zendesk doesn't. So instead of me learning about the new features, he wanted to go with ServiceNow from an infrastructure standpoint.

We are a service IT company. We have Zendesk for our employees internally and for external folks, but it's just used internally and ServiceNow is being used as a practice for external customers. They are also using it at ProKarma. They have the means so that experts can set up whatever we need. The director made a decision to go over and start using ServiceNow internally instead of Zendesk. I think he was more interested in ServiceNow from a roadmap perspective.

In terms of scalability, that wasn't even something that we were considering, just that there were so many things that ServiceNow does that Zendesk doesn't from an IT infrastructure perspective. And we were looking at those features for future-state from the roadmap, security, asset management, and so forth.

We only have about 24 people interfacing with Zendesk. They are admin or developers. Then there's a few BA who are mostly either engineer support for the help desk IT or they  belong to one of those internal groups that we support, Salesforce developers, SharePoint developers, or Tableau developers and architects. These are the people who need to resolve the tickets when there's an issue.

Our IT director set it up. He said he has some basic things in there, a very simple workflow, an SLA, a change management, and I do a few reports. I have a couple of things where I set up the processes so that certain things get kicked back to IT to follow up on. But he said he set up something that was very simple and basic, and it's working for him. But he knew that there were more features that he should be using but he didn't know how to use them. And then we found out from the vendor that there were a lot of features that were grandfathered in and we're not even utilizing those features. At that point I think he made a decision that from an infrastructure perspective there are other features that he wanted that ServiceNow provides that Zendesk doesn't. I think it was more on the infrastructure and security sides.

We are still in a contract with Zendesk until the end of the year. And then they will make the decision whether to switch or extend the contract. So nothing has been done at this point. 

It took less than three months to set up, maybe about eight weeks.

I don't know about the deployment because they haven't made any significant changes. All I know is it took about eight weeks to create the processes and the flows that we currently have.

We did the implementation and maybe used some internal resources to set it up.

The licensing is yearly and it's less than 30 grand, I believe. We had a lot of things that were grandfathered in, so we were using a lot of things - Zendesk Guide Professional, Zendesk Explore Professional, Zendesk Gather Professional and Zendesk Sunshine Lite. All of these things are not being leveraged today. So it looks like we were just using Zendesk Support Enterprise, and the vendor was sharing with us basically what we had and what we were using.

You really need to know how you are trying to service your customers to make a decision on whether or not to go with it. We were looking at three products, ServiceNow, Zendesk and Service Cloud. And you wanted the infrastructure component, the Cadillac version, right? All three different, too. That was another thing you really need to know - what are your requirements? What are your needs? And also look at your future roadmap. To me, those should have been the driving factors for making a decision. Just to clarify, those three solutions are the possible replacements if we decide to phase out the Zendesk Guide. We were looking at Service Cloud and I don't know if we made a decision on it because we are already using Salesforce.

They have a help desk for it, but it came with a cost where you had to pay for every user who actually wanted to use it. We have 3000 or 4000 employees. They also had some type of restricted user license and that can be very expensive if the company is growing. But that would be good. It would be something just to follow up on to find out with ServiceNow. 

The total cost of ownership was a significant differentiator for Zendesk. I thought they were very reasonable. ServiceNow is very expensive, and adding each component every time you want to add a module and you're taking a lot of money. And they still decided to go with it.

One of the things that they showed me in ServiceNow is that they have an asset management component. That was pretty cool. So when you assign a computer to someone, they actually had a picture and they basically had a little card. Anyway, it was easy to click on and set up. I thought that would have been nice if they had some type of asset management component. I think we were using Salesforce to do asset management. Anything that's related to the HelpDesk, where they're tracking your device, your phone, that kind of stuff. So, it would be nice if that was included.

To be honest with you, I thought Zendesk was a very good product. I didn't understand why we were moving to something else when we weren't using all of the features. Usually you use everything and then you outgrow that solution and look for a new solution. But to me that wasn't the case. So the biggest lesson for me was all three products. This is not an apple to apple comparison. You have to know what your requirements are and the roadmap, which is what I mentioned, but I didn't feel that Zendesk fell short at all. I felt management was making a decision without knowing what the future roadmap looked like. Meaning, when I say, "What do you want for the future?", "I don't know, but we are thinking about the infrastructure component" and then they decided to go off and do ServiceNow.

So I guess my lesson learned is to make sure your requirements and your future-state roadmap are all in alignment with your strategy. And I didn't feel that that was the case because I felt that they were making the decision without any ROI analysis to back it up. I'm being honest. That's how I felt. But I felt Zendesk didn't fall short. So what's the issue? And they just said, "We don't know how to do all of this stuff, and we already have an internal group that uses ServiceNow with the infrastructure components. So we're going to go with that product." I said, "it is going to cost a lot of money. They said they were okay with that. They thought that they could still bring down the cost based on their usage. And they went with it.

On a scale of one to ten, I would give Zendesk Guide a seven.

To make it a ten, they should offer some more teachers to compete with the other folks for Help Desk, and other components like asset management. That was another thing that Service Cloud does. It's totally different. I had a feature matrix that showed me those comparisons. There was something that Service Cloud does that makes them more integrated. There was an issue with integration between Salesforce and Zendesk, but the vendor said they fixed that issue and now the integration should work. So that was another concern about just integrating with the internal tool, making sure it's an easier API connector, making it easier to integrate with other tools.

We are in support. Zendesk is being used by the IT group help desk and also by our team. We are an internal team that supports SharePoint, Salesforce, and Tableau. We use it for tickets for customer issues. We also use it for a help desk for everyone else internally.

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

There is multi-channel support and a self-service portal.

The product integrates well with Salesforce. 

The product features as we were currently using them are fantastic.

The solution offers a very good SLA. 

We concerned with and want to understand more about the change management features of the solution.

The solution itself wasn't easy to set up. 

We're only using a third of all of the features, and we wanted something that was more simple to configure and set up. We don't have anyone who has the skill set to do the configuration. On top of that, the way the service model is, we have a team that are practicing within our organization. We would like to have the expertise internally instead of relying on a vendor for support.

Anything that's related to the HelpDesk, where they're tracking, your device, your phone, that kind of stuff, would be nice if it was included.

The solution should offer API connections to make it easier to integrate between other solutions.

We've been dealing with the product for about three years at this point.

The solution has been very stable. IT's why I was curious as to why we were considering switching. However, apparently, there are other features that we want that ServiceNow offers and Zendesk doesn't offer. 

We didn't really talk about scalability previously. That wasn't even something that was considered as there were so many things that ServiceNow does that Zendesk doesn't from an IT infrastructure perspective. We're looking at those features for the future in terms of our roadmap, security, asset management, and so forth.

Currently, we have about 24 people on the solution. They are admins or developers, for the most part.

At this point, we don't intend to increase usage.

I've never been in touch with Zendesk technical support. I met with the vendor and they were very, very helpful. We were going to use one of them to expand on some of the features, however, we now have plans looking at something else.

We are a service IT company. We have Zendesk for our employees internally and ServiceNow being used as a practice for external customers. They also have a practice at ProKarma and they are using it. Now we are experts and can set up whatever we need. We're trying to decide between Zendesk and ServiceNow.

Our IT director set it up. He set up something that was very simple, and basic, and it's working for him. However, he knew that there were more features that he should be using, however, he didn't know how to use those features. Then we found out from the vendor, that there were a lot of features that were grandfathered in, and we're not even utilizing those either. At that point he made a decision that from an infrastructure standpoint, there are other features that he wanted that ServiceNow provides however, it was more on the infrastructure and security side. Therefore, we may be moving away from the product.

We are still in a contract with Zendesk until the end of the year. And then they will make the decision whether to switch or extend the contract. Nothing has been decided at this point.

The solution originally took less than three months to set up. If I recall correctly, deployment took about eight weeks. We don't have anyone assigned to regular maintenance.

We had the solution set up in house using our own resources. We didn't require any outside assistance.

I'm not sure if we can really point to an exact ROI, however, it would be a good item to watch in the future.

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. There are no other fees. Many items were actually grandfathered in. We have Zendesk Guide Professional, Zendesk Explore Professional, Zendesk Gather Professional and Zendesk Sunshine Lite. All of these things are not being leveraged as of today. It looks like we were using just Zendesk Support Enterprise, and the vendor was sharing that with us.

We looked at Service Cloud. They have a help desk on it, however, it came with a cost. You had to pay for every user who actually wanted to use it. We have 3000 or 4000 employees. We would have to have some type of restricted user license. That can be very expensive if the company is growing. 

We're using the Core Optimization package. We also have Zendesk Explore Professional, even though we're not really using it as well as the Zendesk Sunshine Lite. I'm not sure of the exact versions of the solution we're using.

You really need to know how you are trying to service your customers to make a decision of whether or not to go with a particular solution. We were looking at three products. We were looking at ServiceNow, Zendesk, and also Service Cloud. You really need to know what are your requirements? What are your needs? And what your future roadmap? Those should have been the driving factors for making a decision.

Zendesk is a very good product. I didn't understand why we were moving to something else when we weren't using all of the features. Usually, you use everything and then you outgrow that solution and you're looking for a new solution. To me, that wasn't the case. 

Overall, I would rate the solution seven out of ten. I would give it higher marks if they were offering some more features like asset management or if they were more integrated like Service Cloud. 

Its agility and simplicity are the most valuable features. This tool is very user-friendly.

It saves the costs, time and energy. It improves the relationship with my customers.

It needs to improve in terms of its flexibility, price, and installation.

I have used this solution for three months.

There were no stability issues.

At the very beginning, we had some scalability issues.

I would give the technical support a 9/10 rating.

Previously, we were using another solution and I switched over for the price.

The setup was complex because of the different parameters involved.

I advertise mostly about the price.

We did not look at any other solutions, this product was the only one that I tried.

You need to be helped by an expert, side-by-side.

Some of the valuable features are its agility, simplicity, and that it is a user-friendly product.

It helps us save costs, time, and energy. It improves the relationship with my customers.

There are various aspects of this product that need improvement such as its flexibility, price, and installation.

I have used this solution for around three months.

We did encounter some deployment issues due to the complexity of the parameters.

There were no stability issues.

At the very beginning, we had some scalability issues.

I would give the customer service a rating of 10/10.

I would give the technical support a rating of 9/10.

Initially, we were using another solution and we switched due to the price factor.

The setup was complex. This was because of the different parameters that were involved.

I used the expertise of the vendor, who had excellent knowledge of the product.

It is under assessment. I think the ROI is fairly good!

I advise primarily about the price.

You need side-by-side help from an expert.

In Views there are lists of all unsolved tickets, recently updated tickets, pending tickets, etc. It makes it very easy for me to keep track of all the tickets.

I am already a very organized person but the product really does everything for you. The way it’s set up makes it very easy for agents, end-users, and administrators to use.

It would be good to be able to edit. Unfortunately, Zendesk believes that the integrity of a ticket and its comments are important. That when either party reads comments on tickets, they should be able to trust the content is unaltered form its original context. As per Zendesk, they feel it does not fit in with the direction and vision they have for Zendesk which to many people such as myself feel it’s ludicrous and not very sympathetic to the needs of its agents and administrators. Creating triggers is complicated and confusing. They should make it easier for agents.

I have been using Zendesk for more than a year now in my current company. I am the Zendesk Administrator and in charge of all customer service within the company. I was introduced to the software at an accounting software company I worked for. It was used for customer support and to help their IT Department.

We had no issues deploying it.

There have been no issues with the stability.

I only receive a certain amount of tickets throughout my working day.

The level of technical support is very good and they are very helpful.

The product had been set up right before I started working at AP&G. I found out after I was hired I would be using Zendesk which of course I was happy about since I already was familiar with the software but I certainly have learned the software much more in depth in the recent months.

I have to admit when I started working here at AP&G, I actually got more involved into learning how to use the software better since I was the only person basically using it. I made sure to ask as many questions as I could to Zendesk support and read as many articles the Zendesk Community had to offer.

We did it in-house.

ROI I would say it has been good.

The pricing is pretty fair. Of course it all depends on what kind of business you’re running and how much traffic you have and of course how many agents would be using it.

The ease of use and great flexibility is awesome. Also, as an agent it's the macros and the tight integration with the Help Center. As an administrator, it's more how easy it is to configure the workflows and the apps framework.

It has lifted our customer service! Not only can we reply faster, we are more accurate on multiple channels and we get a lot of data from the system that we can use to become even better!

There is always room for improvement - The trick is to find an improvement that benefits a broad part of Zendesk’s user base. The product base is solid and i can’t think of anything major that needs fixing.

I have been using it for about six years in two different companies.

There are always different requirements for each company on implementation, but we always manage to find a solution

We have had no issues with the stability.

We have had no issues with scaling it for our customers needs.

Zendesk support has always been stellar. Most are spot on, some go above and beyond.

We had a homemade web based solution before, and we needed something new. The question started with: do we keep developing on our own system or do we get an out of the box solution and work from there. When we stumbled upon Zendesk there was no question. The level of functionality would take us too many man hours to create ourselves and would not be as great as Zendesk.

Basic setup is fairly easy and after that its really up to you how complex you make your setup.

We did it in in-house implementation. At the time we had the opportunity to do so and we opted to try it ourselves. If you are doing a very basic setup you can easily do it yourself, but if the complexity rises you are well off on spending some money on an implementation partner.

Zendesk might seem a bit pricey at first, but once you get down to what value Zendesk can provide your company - both in terms of saved working hours, happier customers and CX data from multiple channels, it's well worth it!

Start a trial or contact a Zendesk partner - you won’t be disappointed!

As I am a big fan of assigning tasks to people who are most skilled at doing them in a timely fashion, I found the auto-tagging function to be most valuable. This way we were able to divide the incoming tickets into several different categories which were then assigned to team members who had the best expertise and skills to resolve them as quickly as possible.

During the downtime of one of our business partners we were experiencing several payment related issues and as such there was a huge amount of tickets relating to this problem which were being automatically assigned to the relevant team.

Ticket forwarding and the ability to add subscribers to tickets as some back and forth correspondence needs to be brought to attention of several team members, sometimes across different departments. While the first one would be beneficial in cases when issue was resolved and needs only to be brought to attention the latter would be good when a specific issue would be dependent on several team members.

I've using the post-2012 version for about 20 months.

There were no issues with the deployment.

We had no issues with the performance.

It's been able to scale for our needs.

10/10 as they are prompt, courteous, and is available 24/7 via a wide array of channels. Zendesk's team was really great and when there were any issues or questions they were more than willing to assist. When there were issues with the stability and connectivity these were promptly resolved and we were updated on any of these.

We didn't have a ticketing solution in place before, and it was done mainly via emails.

It's straightforward to implement, and the documentation is extensive. Zendesk is willing to assist if you have issues.

We used an in-house team with assistance from the vendor. Should you have any questions you should ask Zendesk, they are there to help.