Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
N/A
Khoros Communities
Score 8.3 out of 10
Enterprise companies (1,001+ employees)
Khoros Communities is a fully-featured community platform, built for self-service support, education and collaboration. Organizations can host a vibrant space where customers can find answers, develop expertise, share experiences, and connect with their brand.
N/A
Pricing
Adobe Experience Manager
Khoros Communities
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Experience Manager
Khoros Communities
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Pricing is variable based on the needs of the customer.
AEM provides a sustainable quality of work that goes long-lasting, and we don't need to worry about future updates as AEM gives time-to-time security, patch, and platform updates. Not only updates, AEM introduces new features every now and then, which not only encourage its …
Adobe Experience Manager allows web content managers to share the work of site maintenance while being able to set access/publishing. Editors don’t need to have advanced HTML experience to make edits or even build new pages. Having workflows to allow authors/editors to request publish gives content managers the ability to review content before it is made public. Being able to set on and off times for pages helps control when content is released and retired. AEM is not ideal for highly specialized and customized designs with lots of interaction/automation
Khoros Communities is my go-to when I'm part of a big company with lots of customers who want to help each other. It's awesome for talking about products, giving ideas to make them better, and getting help when I need it. If my team is spread out or we're working from home, Khoros Communities is handy for sharing updates and working together. It's also a good tool for events, helping with planning and discussing what happened. But if my group is small or not very active, or if I just need a simple place to chat without too many extras, Khoros Communities might be more than I need. Plus, I've got to be ready to keep an eye on things to keep the community positive, and it works best when I have a plan to grow and keep the community lively.
It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.
It's still, at the end of the day, a very traditional platform in by that we mean it's a bulk air platform. There are too many components, which means a lot more operating costs in terms of manageability and things like that. We have tried to streamline that as much as we can, but the multiple components still exist. If anything, Adobe could kind of think about that a little bit to maybe decouple some of those and make them a more slimmer platform. I think that would help. I think that a lot of customers are still in the traditional environment and as we ourselves are looking to move to the cloud, I think some of that will get taken care of, but I think that's one area where it would help if Adobe can put some thoughts into that.
Self Service, Low and No Code. The Community Managers should be able to some UI Tasks by self with doing any code updates.
Salesforce Integration: The basic Integration should also include the basic level of business requirement. (Contacts and Accounts Mapping)
Slack Connector Update: There is no update on this connector till the time its launch. The other team has lot of options to push the notification in multiple slack channels. And unfortunately Khoros does not. This creates a lot work for Community team to bring internal teams to the community to respond or acknowledge an post.
More Integrations: Since now the Khoros communities does not comes up with the integrations with basic support tools like JIRA, Confluence, Github etc.
Search Improvisation: Apart from last search update there is no updates we see in this feature. The team should think of Putting Some AI based Search into the community which helps the Community managers to manage the content accordingly
Some update on AI and Gen AI: Khoros communities did not shared any thoughts about their plans for putting these technology in community
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
On a scale of 1 to 10, I'd give Khoros Communities a solid 8. The system is extremely easy to use, enabling our team and community members to navigate and interact with the platform with ease. The wide range of features offered by Khoros Communities has greatly enriched our online interactions and improved the efficiency of our customer service. The technical support team has also been extremely helpful, could be quicker sometimes for answering our questions but they efficiently resolving any problems we have encountered. The platform is perfectly scalable, capable of handling our growing user base without any performance problems. What's more, Khoros Communities offers excellent integration capabilities with our other software tools, making our operations smoother and more efficient
Adobe launched the Touch UI experience a few years back, I think it's been four to five years now. I didn't see much improvements in terms of usability. So there's definitely there's room for improvement there, especially around our authoring team. They really struggle when it comes to finding things in them or navigating easily to pages. It's always a struggle for them. I think the overall authoring user experience, the way authoring UI, the way it is set up, can be optimized. I think in its current state, I don't think it's that well set up. It can definitely be redesigned for sure.
Like every backend, it can always be improved upon. The excellent thing is that Khoros have a hugely active customer support community as well as a fantastic case management system to triage support issues and requests. So regardless of your level of knowledge or familiarity, you're well supported out of the box.
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
I've hardly ever seen downtime in any of their production communities. There's the occasional reboot needed for config reasons or if patches are applied, but these take place after customer approval and typically last only a few minutes.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
They are responsive and proactive. They are really on top of things. They send personal emails to check in on you. It feels like they really know you. You only get emails from 3-4 people at Khoros – they must be customer assigned.
It was out of the box training - pre-recorded/ not live. There was nothing for more advanced topics like APIs. They do have a good knowledge base and community that you can access and folks in there are responsive. I would however like more advanced training options.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
We were up against a hard stop with Jive’s contract ending and Khoros connected us with a deployment partner to do accelerated deployment using a template approach. It could have happened in 2 weeks. We did not end up going that way since we wanted more customization. Lithium handled technical stuff like migration, but a lot of the process is self-deployment. It’s one of the ways they teach use of the system is having the user self-implement.
Overall, the implementation was super easy to do. Doing single sign-on (SSO) was the only hard part. The implementation ended up taking nine weeks total, but in hindsight, we could have done in it six. Most of the implementation time was spent in course work, which consisted of on-demand training - approximately 7-8 hours that you are required for you to do, before they turn on the system. During this nine week period, about 50% of my time was spent on implementation.
We had a deployment manager who we were able to email 1-1. I leaned on him heavily. He was great at all hours, for example, they would call back at 7pm PST. They were very responsive.
Content migration strategy is important to consider. Moving from an existing community you need to strategically choose how your layout will be. Two different systems will have two different ways to format communities. For example, Jive has communities with sub-communities, whereas Khoros has community, category, and boards.
Contact migration is also an important consideration. You need to think through how you are going to move contacts from your old community to a new one. For example, are you going to create new logins and passwords? We were hoping to use the integration with Salesforce.com to be a portal, but ended up using an in-house solution that works well to maintain same the same logins. The next related question is are you going to be able to keep them connected to all the posts in your old community? We migrated old posts. If you have a tech-savvy team, you can do a self-migration. Khoros has a migration services team that we utilized. It cost us $10k to move content and posts were kept tied to the user.
The next consideration is your launch/promotion plan. Khoros helped us out and gave us a lot of examples. They shared pre-launch email dates, follow-up emails, FAQ pages (e.g. to explain why switching, why better).
At Canadian Tire Financial, in the time I've been there, we've always used AEM, but in past places I've used WordPress, I've used Squarespace. Things that are more general user-friendly where you're like building your own blog or you're creating a small business website where it's basically just text, you're not intaking information or something like that. I think the customization options in AEM are huge. My experiences with WordPress were pretty straightforward. Again, it was like, I don't know, like college newspaper website or something like that where you're just like putting content up for people to look at. You're not necessarily taking in any other information. Maybe you might allow people to log in or something and save articles or something pretty straightforward, but then even then I remember that stuff taking me forever to do, to figure out and scroll through tons and tons and tons of documentation. It's just not fun. No one enjoys doing that and then even then you might not have the answer available to you. And that's so frustrating. Hey, it's super user-friendly, figuring out the content editor is pretty straightforward. You're not clicking around and being, "what the heck am I looking at?" Or you're not looking at a bazillion menus to be like, "maybe the thing I want is in here." I can't stand that. I want to be able to look at a page, see what I'm going to be getting in production, and then publish it. I don't want to look around in menus to figure out how to add something to a page.
Large companies and organizations with complex community needs are well served by Khoros communities. The platform's advanced analytics and reporting features helps organizations seeking deeper insights. The gamification is the best way to boost user engagement, Khoros Communities has a rich feature set. Also with customization options offered by Khoros Communities, companies can develop a unique and customized community experience.
Instead of being directly involved in the tool purchase, I am involved in analysis or what we can use to maximize the tool. Small organizations may find it expensive. However, if the team or organization focuses more on your ROI or the features you will get, then it will definitely be worth it. Pricing is based on a number of factors, including team size or the use of the tool. The user can select the pricing option that best fits their needs based on the number of form submissions they make or the number of pages they wish to publish on their global/multisite sites.
I think I would give Khoros an overall 7, while there were things we really liked about it. I also saw things that just did not work well for us. We like using iG but it was not the friendliest in using it on that platform. Sometimes the software would glitch or lag which is not helpful during high critical moments
The professional services team within adobe is one of the best in terms of technical and solutioning knowledge. However, considering the billing charges of adobe professional services team, it is always recommended to involve them during platform initial setup or when a complex solution is to be built with platform customizations.
Well I can't speak monetarily but I can say it's allowed us to get some sites out and messages out very quickly. We've been able to stand up some sites incredibly under very tight timeframes. Messaging, especially during the pandemic, we were able to not only get information out about COVID, we were able to get messages out to the general population about information about their insurance, about issues that were happening, how to find test sites, how to find test kits, how to find information about your insurance, how to get information about storms or anything happening. So we found it was able to get up messaging very quickly and turnaround sites pretty fast. Once we got rolling on it, we were able to do it and we found that it was just able to get that messaging and sites out very fast.
We are able to see what our different cohorts of customers are doing within the community, and we are able to create content and programs based on the engagement we get from these different groups.
We have been able to start an Idea Exchange space where our customers can share, vote, and comment on features they would like to see in our products. It quickly became a very popular place within the Community.
With the discussion forums, we are able to use the Accepted Solutions functions to help deflect tickets and Support interactions working on a 1-to-many scale.
