Drupal vs. Kustomer vs. Magnolia

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

I would say the greatest strength of Kustomer is its flexibility. In the hands of a skilled admin, it can be adapted to tons and tons of different use cases. I've been able to make custom displays for different groups of agents, produce complex cross sections of users, draw interesting data relationships combining marketing contacts and customer-initiated contacts. For example, there's really no other data source in our company which could tell you which users received a specific promo code and checked out with it, received their delivery within 14 days and then can related that to the number of times they contacted us about using our product. At the intersection of communication, marketing, data, and relationship-management, Kustomer shines at the center. I would say it falls short when you are trying to coordinate multiple "side conversations" with multiple sources to resolve an issue. This is a tough task for any type of platform, but if you're maintaining 3 different email chains with a 3PL partner, the customer, and a separate internal conversation, it would be confusing anyway!

Incentivized

Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities. One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels. Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.

• 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

• All customer data (past orders, communication with customer service, rewards account data) is in one place. This helps agents avoid confusion and reduces the number of tabs they need to open.
• The Knowledge Base (or K Base) is very helpful. Any time we roll out a new policy or have a limited-time promotion, we can add all the relevant information and worksheets there for the convenience of the agents. That way they can stay in a chat while looking up the answer to a question.
• We can seamlessly move from chat into email if the customer leaves or the queue times are too long. All the interactions will stay on the customer profile page, so they are kept up to date.

Incentivized

• Speed of development - time to delivery from zero to MVP was excellent
• Ease of use - the authoring experience is very easy to build and train
• PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on.

• 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

• For our team, the feature that defaults all notes to begin in "done" status is difficult. Throughout each day we need to have notes open and assigned back and forth to different teams, and we have to remember to manually "open" each note. There is too much room for human error with this setting, and it is easy for important notes to be missed if a user forgets to open the note.
• Similarly, it can be hard to remember to assign emails/notes to a particular team in addition to a user. We almost exclusively work out of team inboxes, and if someone on Care writes an email to a customer, the email will automatically be "done" when it is created, and it will be assigned to the user who wrote it, but not also to the user's team. There are instances where an email needs to be snoozed for several days/hours with further action needed, and unless the user remembers to assign the email to their team it may "awake" from the snooze and not be visible to anyone except the user who created it. Similarly to my first comment, this leaves a lot of room for human error and is not very intuitive.
• Personally, I do not love that all tickets/emails/notes are jumbled together in the same inbox. While this gives visibility to everything on the "to do" list at the same time, it can be visually overwhelming. We have created unique folders for certain types of projects or categories of work, but have experienced tech glitches or just the awkwardness of another step to manually read the note, determine what type of category it is, and then manually assign it to another folder. Would love to have things auto-sort and take out this manual lift.
• I love the idea of the autopilot setting, but we have not been able to use this for our work because it sorts items based on time, and not based on priority. In our line of work, we may have an urgent situation arise that needs attention before an email that was sent in 60 minutes ago. The autopilot feature would push the email to my associates sooner than it would the urgent situation from 5 minutes ago. Due to this, we manually monitor inboxes and assign work to ourselves and others.

Incentivized

• The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces.
• The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this.
• Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes.
• Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them.

Incentivized

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.

Because there's no other tool like Kustomer

Incentivized

We have invested a lot of time and energy into tailoring a solution that works for the company.

We think the new features in v6.2 will help us get to the next level

We also don't have the resources to rebuild a website platform from scratch even if we wanted to

Incentivized

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

There is a learning curve, but it is more than worth it, especially to have a dedicated resource pointed at Kustomer and any other software it interacts with. The basic implementation is useful, and powerful - certainly a MASSIVE upgrade over taking care of your customers in an email inbox or shuffling between multiple windows and applications! It is also set up really well to grow and reconfigure with your business. I'm a big fan.

Incentivized

We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.

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

Because Kustomer is available when you need it

Incentivized

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

Because ages load quickly, reports complete in a reasonable time frame, given their complexity

Incentivized

I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.

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

I did not reach out to Kustomer support when we had an issue. Still, whenever we provide feedback to our manager regarding what can improve based on our experience using Kustomer, our manager always comments that Kustomer support always replies with some positive feedback based on our suggestions.

Incentivized

You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases

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.

Because they are very hands-on in training us and very approachable

Incentivized

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.

It was very easy to understand.

Incentivized

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

Nothing really because it is easy to use. After an hour of using it, we're already getting the hang of it.

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

Apps like Intercom, Zendesk, and Gorgios all treat customer inquiries as tickets, just tracking that one issue or interaction with a customer. Kustomer treats each customer as an individual, which allows us to provide top-notch customer service. Customers love that we're able to be more conversational and informal, while still solving their issues quickly. It also helps us build relationships with customers and increases repeat orders.

Incentivized

I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.

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

Because customer is flexible and scalable

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

• We’re getting so much positive feedback — which is not something you traditionally associate with a customer care team — because we’re making it effortless for customers to deliver both positive and negative feedback, and we can now resolve the bad feedback really really quickly.
• Primarily from our increased efficiency with Kustomer, we’ve seen a significant reduction of $3 to $4 for every cost per contact.

Incentivized

• Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse
• The software is affordable with no compromises on capabilities and therefore it is gives us value for money.
• The templates makes the whole process easy

Incentivized