The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
My previous company used Zendesk for ITSM (IT Service Management) products and Jira for internal development, such as HR, finance, and other departments.
It was mostly used for internal purposes and integrations because it was mobile apps related to ride-dealing, like Uber. So, it was mainly for receiving requests from the customers and scanning the stuff.
It's a very stable tool, very powerful.
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.
I have experience with this solution. I worked with it for five years.
It is a stable product. I worked on it for five or five students. It's very stable.
Scalability is normal. Not very high. At that time, there were around 1100 end users using this solution.
The support team is time-consuming, and they don't find the answer to our problem.
Because if you are doing your job by yourself, it will be a lot of aim to seek their support. But if you have, like, a support contract with them or something like that, there's the support when you go for a good position or if they can push it. You have to pay extra for better support.
Neutral
We decided to switch from Zendesk because of limitations for integrations. We were a tech company, and we needed more features, more add-ons, more conditions with a lot of tools that weren't accessible with Zendesk, so that's why we had to change it.
The initial setup is very difficult, and we had to use support help for the account setup.
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. The pricing is expensive.
Back then, we were paying $51 per license for agents and $89-90 per license for tech users.
We were paying around $2.25 million per year.
I would suggest using a trial version first and reading the logs before using it.
Overall, I would the solution a six out of ten because of the complexity of the tool and the high license price.
monday.com acts like a very user-friendly CRM tool that helps us keep our users in check. What we do is run the systems for student accounts and student onboarding, which is the data that gets stored onto monday.com. We use monday.com for its better user experience so that we can extend the access to our tutors, which will have access to all the students in their particular classes, and they can take some actions based on what they want.
For example, we can provide a monday.com admin action to mark attendance, and the tutor can use that board to mark the attendance for a particular student, and there could be back-end automations running to do the same for the user. There are a couple of automations that run in monday.com, which is probably Google Sheets on steroids with enhanced features, multiple processes, and even automations baked into it.
As those automations are not fulfilling our purpose, we can have certain values of a column updated or certain parameters of any particular item updated using monday.com automations directly. For example, we can set up automation in monday.com that will mark something that runs every Monday and marks something based on having recurring classes every Monday.
If we have an absent flow, when the tutor marks absent, we can trigger a particular value in a certain board using monday.com automations. For more complex scenarios, we use the webhooks feature for monday.com so that we can better handle our use cases by calling a webhook in Make.com, Zapier.com, or N8N and call them to do complex workflows directly on monday.com.
The main use case for monday.com is that, and apart from that, the other day-to-day workflows would be the seamless integrations between multiple different boards and the mirror column facility, which facilitates data to be on one single board but displaying across multiple different regions. With monday.com, we are able to handle thousands and thousands of students that we intake based on our different education brands, like test prep, med prep, or even school-level mathematics.
Having monday.com makes it more centralized where we can handle student accounts only in one board and then for different classes, we can extend access to different boards and use mirror columns to showcase the students while we still have one central source of truth.
Probably the best feature of monday.com would be the intuitive user interface and user experience, which any user who has used Google Sheets or Microsoft Excel would find themselves familiar with, along with built-in automations, the ability to call webhooks, and the various number of column types.
The better user interface and user experience definitely stand out to me because this is a tool that can be used for both the development team as well as extended access to the consumer or the customer side of the system, or in our case, the tutors and other relevant stakeholders who need not understand the deep technicals of things but can take actions directly from the board.
We run into technical issues a lot with monday.com, where certain errors just pop up randomly, and we would want to have a little bit more developer-friendly part from monday.com. There could be better communication with mirror columns or have a better experience in terms of the technical side of it and not the front-end side of it, which can be improved.
I started using monday.com probably two years ago, and with this particular company, I have been using it extensively, so I have around one and a half to two years of experience working with monday.com.
Because of the technical issues that we run into on a monthly basis, if those can be improved, the score can definitely be improved.
Tutor satisfaction is definitely one of the points that I would like to share about monday.com. Before monday.com, we were using HubSpot, which, even though it is a very good technical tool, does not provide a very good user interface for people who are not working in sales or people who do not really want to know the technical side of things. Having a simpler UI with technical functionalities of a backend and a good user-initiative front-end, where we can change labels based on certain parameters, is definitely something that the tutors were eager to try out, and they really liked the systems from the time we set it up.
My advice for those looking into using monday.com is to probably start using it, especially if they are dealing with stakeholders who would want to review things directly on the database side and take actions directly on their own, as monday.com would definitely provide a good user interface and experience for that. I also advise the technical team to probably use a side automation platform such as Make.com or a script running on some cloud to talk between platforms using the automation functionality of monday.com.
We have very good GraphQLs for monday.com that help us do most of the work, with the monday.com community also being good enough to push updates on a regular basis. A one-word description for monday.com is "Google Sheets on steroids", and I think I would stick to that. I would rate this product an 8 out of 10.
