RStudio Connect vs Zendesk comparison

"RStudio Connect is very powerful statistically and can handle large datasets, even on a free version on a laptop."

"The most valuable feature is the trackability of incoming requests. The system keeps a comprehensive history of work requests, making it a useful tool for our internal processes."

"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 has good management, the ability to sign tickets based on content, the multi-channel support, the self service portal, the integration with Salesforce, the setup process, and the product features as we are currently using them."

"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."

"Zendesk has been invaluable in automating communications such as email and phone calls."

"It's very convenient to use."

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

"I rate my experience with RStudio Connect as average because I am not yet comfortable enough to provide a definitive assessment."

"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."

"Zendesk's stability on inbound calls could be improved as compared to Talkdesk."

"Zendesk Guide could be improved by allowing us to put our assets in one location. What happens now for each article, for example, is we have to upload the images for that article to that location, so the image reuse is still not something that they have perfected. If they could allow us to update all the images in one location, and then pull the image from there, it would be easier when working on Multibrand projects. There are no Multibrand updates available—we have to update each brand manually. For my company, I have come up with an API tool which allows me to push the content to multiple brands together, but if you don't have something like that, you have to manually do it."

"The support team is time-consuming, and they don't find the answer to our problem."

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

"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."

"They have something called Zendesk Explore, which isn't as good as what they had in place previously."

"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."

"The price is very competitive."

"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."

"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."

"From what I hear, Zendesk's pricing is a little expensive."

"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."