Zendesk Reviews

We use Zendesk Support to receive customers' requests. So, we basically emanate me a customer and get a submit a request from our Zendesk. We just pick it up from Zendesk and respond to their requests. You can also receive chats through Zendesk. 

Overall, Zendesk works well for me. The icons here are not overwhelming, and I only need to contact support once a day. Then, once you receive a request, you'll get an immediate notification, and you can respond to the client right away. Additionally, on Zendesk, you can create different items to categorize requests from clients in different regions, such as the US or other areas. We should definitely support that.

Additionally, Zendesk has a profile and knowledge base. You can connect Zendesk from Notion as well because we use Notion too. Any information you type on Notion, you can easily bring it in on Zendesk, which is super, super cool. Then if you want to get more information about the client you're working on, you can get them on Zendesk, which is super cool.

I have a concern regarding the side conversations. Instead of creating a separate transcript, you can simply click on the side conversation tab to communicate with clients. It should be within the same interface. 

So when you respond, you can easily switch back to them without opening another ticket or creating additional back-and-forth conversations. It's more streamlined that way. It keeps everything organized and avoids cluttering the interface with multiple tickets for one conversation.

I have been using Zendesk Support for two years now.

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. It could be from Zendesk, which I think they should work on.

I would rate the stability of Zendesk Support an eight out of ten.

It is a scalable solution. But for me, there is maybe some Slack thing, really for me. Slack becomes more than the same time. But all those decks, once you open Zendesk to attend to the customer’s request on the phone and all, and hence I would rate the scalability of Zendesk Support a nine out of ten.

Around 400 users who are using Zendesk Support in our organization. With Zendesk Support, you can also create the same Macro on Zendesk. The time you use to type in the calculator will take you more time. So it is better just to create a Macro instead of you wasting like five minutes typing.

Once you have already created the Macro, you can just send whatever response you want to decline if you are sure you know what the feedback really is. So I can resolve a customer request immediately.

The customer service and support experience were okay. When contacted, they respond really fast. I’ll give it to them on that angle. Once the network is down, within five or ten minutes, they will fix it.

Positive

For me, the initial setup for Zendesk was straightforward. It is not complex. 

I think the advice about Zendesk Support should be to use Zendesk essentially if you are in a customer support role. It is very important. Even if you are in pair with your customers onboarding, Zendesk is user-friendly. You can easily get the customer's request immediately to resolve and then create a Macro on Zendesk. We can import information from the Notion page to Zendesk, and you can even import and connect articles on Zendesk.

Overall, I would rate the solution a nine out of ten.

We've been satisfied with its general capabilities. 

The stability has been very good.

The licensing model needs to be more customer-friendly. At the moment you have to buy different pieces. ServiceNow, for example, provides just a part of their premium.

There needs to be better insights and analytics. Right now it's lacking.

The dashboard could be better.

We haven't bought service provisioning. We haven't bought the knowledge base, those were part of the main product. The chatbot is there, however, we tried it and it was lacking.

I've been using the solution for over seven years. It's been a while. 

We have found the stability to be quite good. It's reliable. There are no bugs or glitches. It doesn't crash or freeze.

We also are familiar with ServiceNow which has better licensing and better analytics. It also has a nicer dashboard.

I wasn't a part of the implementation process. I wouldn't be able to comment on how it went or what was involved. 

The licensing should be more extensive and not broken into individual pieces. It's hard to figure out what you need at the outset.

We are a customer and an end-user.

I'd rate the solution at a six out of ten. It's good, however, it lacks a few features across different areas. 

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.

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.