Report generation is still slightly tricky and not very customizable as per my inquiries. It would be advantageous to have an AI layer that can analyze incoming requests and generate summaries, as well as a knowledge base similar to ServiceNow's.
Sometimes, the calls do not record, and your conversation is cut midway. When you want to do a call calibration, you realize that the call is incomplete. Zendesk's stability on inbound calls could be improved as compared to Talkdesk.
As per me, there arent much significant issues or areas for improvement with Zendesk, as my usage of it is limited. I appreciate its ability to organize tickets effectively based on tags, allowing me to easily gather and analyze customer feedback and requests.
It has a huge problem regarding the price. The price increases every year. Every year, they raise the price of the licenses, which makes a lot of limitations, and you have to pay more. So that's some conditions. Actually, most of the companies that use Zendesk need a customer experience or customer care department. However, Zendesk only works with chatbox or emailing services, but it can also use Genesys, VoIP, or voice sensors. Additionally, Zendesk needs the administration panels to be easier because it's a very complex panel. You need to search for a lot of things to do, like a small job. So you have to do a lot of setup regarding the integration, and it's a little bit challenging to integrate any software in the vendor.
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. You get a new ticket on Zendesk and are able to view it in your browser, but when our program queries it for new tickets, we won't get that ticket. That takes some time to sync, and if the solution could speed it up, it would improve our work very much. The solution’s stability could be improved.
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.
Senior Back Office Manager at a financial services firm with 51-200 employees
Real User
2022-05-16T13:42:01Z
May 16, 2022
When I first started, I was added as an employee, not as an administrator, and the access for an employee would allow you to see all of the tickets from all of the departments. You could assign tickets to different departments and you could actually remove tags if you needed to. After a while, we started having new hires and they were also added as employees. Their access was meant as employees. Then, Zendesk changed their terms and conditions, their licenses, and what those licenses actually have, including what type of access they offered and employees couldn't, for example, see all of the tickets from all of the departments. They couldn't really move, add tags, assign tickets to different departments, et cetera, however, even though they have the exact same access as I do. The features were limited, even though they had the same access as we did. Since those features were now added into administrator access and you couldn't give administrative access to new hires, you can also see a lot more information for reports and stuff like that. This is basically none of their business, so this is why we changed to Freshdesk.
Customer Success Manager at a computer software company with 51-200 employees
Real User
2021-04-22T17:24:29Z
Apr 22, 2021
An area of opportunity for Zendesk is probably just when there's a long email chain and everything gets forwarded to support, I know it can be time consuming for them to extract the important information from the email chain. Sometimes if there was a way to just flag the actual issue out of those email chains - that would be really helpful. It's just so time consuming, especially trying to find attachments too. I think it'd be good to have just one place, "Here's all the attachments and the 24 emails that's been sent in this chain." It's hard to say what needs improvement being someone who usually does the communication was Zendesk in Slack rather than the actual interface. However, on the customer success side, it would be really, really helpful if I can somehow categorize all these Zendesk tickets by customers, so that I can see all the outstanding support tickets. That way, the status is in one place for that customer. Right now I really have to check by ticket number. We use Pendo, which is another complete different software, however, they have something called NPS scores. I just do a quick search in Slack for the customer's name. Then I see all the NPS scores out of the search results. If I put in the customer name, it's just kind of not associate on the account level in this solution.
Senior Application Support Engineer at a tech services company with 51-200 employees
Real User
2021-04-08T12:59:26Z
Apr 8, 2021
Zendesk used to have a whole reporting tool, which they have actually terminated. That has been a small blow for us, however, it used to be a feature where they had that tool that allowed you to just have reports on the go, on the fly. They should bring this feature back. They have something called Zendesk Explore, which isn't as good as what they had in place previously. The reporting and analytics part should be improved even more. The effort taken from the user side to configure the reports is a bit more when it's compared to the solution that was there earlier.
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.
Zendesk Support is intuitive, and it's built with support agents in mind. Everything they need lives in a single, dynamic help desk interface so it's easy to be productive and manage customer interactions.
Report generation is still slightly tricky and not very customizable as per my inquiries. It would be advantageous to have an AI layer that can analyze incoming requests and generate summaries, as well as a knowledge base similar to ServiceNow's.
Sometimes, the calls do not record, and your conversation is cut midway. When you want to do a call calibration, you realize that the call is incomplete. Zendesk's stability on inbound calls could be improved as compared to Talkdesk.
As per me, there arent much significant issues or areas for improvement with Zendesk, as my usage of it is limited. I appreciate its ability to organize tickets effectively based on tags, allowing me to easily gather and analyze customer feedback and requests.
It has a huge problem regarding the price. The price increases every year. Every year, they raise the price of the licenses, which makes a lot of limitations, and you have to pay more. So that's some conditions. Actually, most of the companies that use Zendesk need a customer experience or customer care department. However, Zendesk only works with chatbox or emailing services, but it can also use Genesys, VoIP, or voice sensors. Additionally, Zendesk needs the administration panels to be easier because it's a very complex panel. You need to search for a lot of things to do, like a small job. So you have to do a lot of setup regarding the integration, and it's a little bit challenging to integrate any software in the vendor.
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. You get a new ticket on Zendesk and are able to view it in your browser, but when our program queries it for new tickets, we won't get that ticket. That takes some time to sync, and if the solution could speed it up, it would improve our work very much. The solution’s stability could be improved.
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.
The price of the solution should be reduced.
When I first started, I was added as an employee, not as an administrator, and the access for an employee would allow you to see all of the tickets from all of the departments. You could assign tickets to different departments and you could actually remove tags if you needed to. After a while, we started having new hires and they were also added as employees. Their access was meant as employees. Then, Zendesk changed their terms and conditions, their licenses, and what those licenses actually have, including what type of access they offered and employees couldn't, for example, see all of the tickets from all of the departments. They couldn't really move, add tags, assign tickets to different departments, et cetera, however, even though they have the exact same access as I do. The features were limited, even though they had the same access as we did. Since those features were now added into administrator access and you couldn't give administrative access to new hires, you can also see a lot more information for reports and stuff like that. This is basically none of their business, so this is why we changed to Freshdesk.
An area of opportunity for Zendesk is probably just when there's a long email chain and everything gets forwarded to support, I know it can be time consuming for them to extract the important information from the email chain. Sometimes if there was a way to just flag the actual issue out of those email chains - that would be really helpful. It's just so time consuming, especially trying to find attachments too. I think it'd be good to have just one place, "Here's all the attachments and the 24 emails that's been sent in this chain." It's hard to say what needs improvement being someone who usually does the communication was Zendesk in Slack rather than the actual interface. However, on the customer success side, it would be really, really helpful if I can somehow categorize all these Zendesk tickets by customers, so that I can see all the outstanding support tickets. That way, the status is in one place for that customer. Right now I really have to check by ticket number. We use Pendo, which is another complete different software, however, they have something called NPS scores. I just do a quick search in Slack for the customer's name. Then I see all the NPS scores out of the search results. If I put in the customer name, it's just kind of not associate on the account level in this solution.
Zendesk used to have a whole reporting tool, which they have actually terminated. That has been a small blow for us, however, it used to be a feature where they had that tool that allowed you to just have reports on the go, on the fly. They should bring this feature back. They have something called Zendesk Explore, which isn't as good as what they had in place previously. The reporting and analytics part should be improved even more. The effort taken from the user side to configure the reports is a bit more when it's compared to the solution that was there earlier.
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.