Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Zendesk Suite
Score 8.6 out of 10
N/A
Zendesk is a customer support solution with built-in ticketing, conversational messaging, and live chat, designed to help businesses of all sizes and industries deliver personalized service at scale. Zendesk's AI agents are trained in CX to help Service teams resolve customer issues faster and more accurately while still providing a human-centered experience. Zendesk ultimately aims to help businesses improve time to value, reduce effort per ticket, and keep costs low.
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
Being a customer support agent, I found it very good when it comes to send an email or call or chat- with the user. I can do all that from the one single platform which is so easy and time saving for you. It does not take much time to use this, We can chat- with the user and at the same time we can send an email to them as well.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
Is there a way for AEs and CSMs to be informed in a weekly summary of all their accounts and any tickets? Example: Disney submitted a ticket on XYZ. Google has an urgent issue on X still unresolved.
Is there a way for CSMs or AEs to have a Dashboard that's specific to their accounts instead of seeing all the tickets in the queue that are not relevant to them?
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
Zendesk is an amazing tool for communicating with your customers easily. The communication tickets from sellers to us or from us to sellers are stored, and there are statuses used to make communication easy. We have internal conversations between departments, linked with useful software such as Zingtree, Talkdesk, and Webs.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Pros: The agent interface is sleek, contemporary, and relatively easy to learn compared to many other enterprise tools. For common tasks, admins are given point-and-click options- adding fields, modifying workflows, constructing macros. The knowledge base (Guide) editor is easy to use for non-developers. Drawbacks: Once you move past the initial things - complex automations, reporting/analytics in Explore, and/or customizations integrating the API, it requires much more advanced training to use successfully. Navigating between the different modules (Support, Explore, Chat, Guide) can feel very disconnected; often you are reminded that it really is a "suite" of products brought together -not really one unified platform. If you're using multiple brands managing simultaneous support tickets, or heavily customizing workflows to meet your brand, you may run into a bit of struggle with usability. So: it's a lot more user friendly than the palaces (Salesforce Service Cloud, ServiceNow), but is not used as quickly or with as much streamlined flow as a product made for a small shop. So if you are looking for a great balance, this is a good option if you are a net new organization or an organization on their way to scaling from 15 - 50 employee. Expect some elbow grease from the admin team once learning, adapting, and working efficiently once you move past the basics with your support tickets and initial customizations.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
We rarely need to contact their support team, but when we do they are responsive. However there have been notable times when communication between myself and the support rep was challenging despite me providing clear explanation of the issue, screenshots, and a thorough explanation of the goal we hope to achieve. It took several back and forth attempt, on a few occasions, to get resolution on an otherwise simple request
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Zendesk has tons of available material for training - videos, webinars, articles, etc. The only reason this is not a 10 is because it can be hard to figure out how to navigate to these things and find what you are looking for.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
I was very satisfied. They have a free trial for 30 days and I recommend you do that and use it. It is very easy to get started with the basics and the build on over time.
The only thing technically complex was single sign-on and integration to Salesforce.com required some tweaks – otherwise setting up system was very easy
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
The customisable reporting every time. Our leadership reply on me to run my team and want to know what customers are telling us so they can elevate our products. We have extensive custom reports that tie up all aspects of our product and customer journeys. I've not found another product that allows me as much freedom as Zendesk Suite explore does, so far.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Integrating other AI solutions for an organization with high volumes can cost about USD5000 monthly. With Zendesk AI and by building onto the same with AI powered apps built for Zendesk Suite we save a projected USD4000 monthly.
Robust Zendesk APIs have enabled us to integrate our internal system with a customized app saving us hundreds of hours every quarter spent loading customer profiles that are not loaded instantly from the app.
Plug and play apps like Round robin save us weeks of sprint delay timelines as they do not require additional coding or developer support to install and start using.
