Drupal vs. Zendesk Chat

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.

Incentivized

Zendesk Chat is suited for all the support teams that provide real-time assistance. Like if someone wants to block the debit/credit card, it is a high-priority case that needs real-time assistance. Whereas issues like close my account, and invoice request doesn't need real-time assistance, where Zendesk tickets support will be perfect.

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• Extremely fluid chat interface allows for easy communication.
• It can be used directly on a website page or as a widget.
• Allows the end user to translate the chat into their own native language.
• Notifies you with pending chats via on-screen notifications and sound effects.

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

Incentivized

• Linking with a telephone, so the agent is only working on 1 channel at a time
• More simplified way to create and use templates
• Link users who may have provided us a new/different email from what we have on file for 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.

Due to staffing issues, we have temporarily stopped offering chat as an available channel. We're also interested in the best ways to integrate chat with our FAQs and AI to provide quick responses, either during off-hours or prior to speaking with a live agent. I've also found that reporting is rather limited where some of the interesting and useful data made available and visible during the chat cannot be pulled post-chat; it would be great to pull a high-level report so we can analyze this data.

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.

Incentivized

As mentioned previously, it's a clunky product that lacks user-friendliness. It feels old and behind the times compared to other products we have used. The inability to have a wrap-up time before a new chat comes in is also a big issue for our team.

Incentivized

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.

Incentivized

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.

Incentivized

Getting assistance and/or troubleshooting anything with Zendesk can be quite frustrating. In my years of experience with Zednesk, I have almost never found the answer to my question without going through multiple articles, ultimately getting frustrated and reaching out to our contact for more assistance. So for a consumer, the support is not as relieving as Zendesk Chat is to our customers in getting the questions answered by us.

Incentivized

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.

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%

Incentivized

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.

Incentivized

Zendesk Chat is far more user friendly than some of the other competitors on the market. It has a very all the features that you require to ensure your customers are contacted in 'real time'. Its main tools include a live chat interface for quick communication, customisable chat widgets to fit your brand, mobile responsiveness for all devices, and canned responses for common questions. The platform can also start chats based on visitor actions, like time on a page or exit intent. A real must for any leading company

Incentivized

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.

Incentivized

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs

• Positive impact - Compared to our old system, this newly updated system provides features and functionality that has increased our agent productivity and provided customer insight like we've never had before. This has resulted in fewer hold times and higher customer satisfaction.
• Negative impact - Our reporting team still struggles with obtaining the right information from time to time with the chats. This leads to loss of productivity and more resources dedicated to reporting.
• Positive impact - Due to Zopim's embed, we are able to more successfully place them on the appropriate self-service portals and pages, reaching a larger audience, and being more readily available to answer our client's questions. This has resulted in an increase in our self-service portal usage, driving down the phone and email support channels, which in turn reduces support costs.

Incentivized