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
Verint Community
Score 9.9 out of 10
N/A
Verint Community (Telligent) is a community and collaboration software platform developed by Telligent Systems and was first released in 2004. Telligent's focus was on offering a platform that can be integrated and extended, but this requires technical expertise. Verint acquired Telligent in 2015.
N/A
Pricing
Khoros Communities
Verint Community
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Khoros Communities
Verint Community
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
Pricing is variable based on the needs of the customer.
The given FAQs, tutorials, and resources for self-service reduced support tools, Loop for Product Feedback gives insightful consumer feedback to help with products to meet growing needs. Businesses could succeed by utilizing the Khoros community as a strategic tool, which educates consumers and facilitates meaningful discussions.
If you need a community platform that's very versatile and has a relatively low entry-cost to get started, Verint is a good pick. If you need a solution that is guaranteed to work seamlessly and have no hiccups or issues overall, it is not well suited. Although it is a SAAS solution, some of the aspects of the platform do not make it seem so.
Forums - organizing forum questions and identifying answered
Various layouts of blogs, divided by groups to enable different or similar layouts throughout the site. Ability to enable all to view the same or have particular groups of blogs to stand out and have it's own look and feel
ability to customize widgets to the needs of your use case
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
Verint Community can work on improving the language part of their business which would help in interacting with customers in non English countries more easily
User interface is very dated, it required very high customizations from our side in order to be using it as functional. Hoping for UI part to be more focused on their upcoming updates.
Features such as chatting and group chatting could be introduced in a similar way to other big social media companies
They could build a mobile application as well other than the website for much better collaboration and ease of use.
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
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.
If you are an experienced online community professional, Verint offers the flexibility you need. You do need to have a lot of expertise if you want to build a solid user experience because there isn't a template out-of-the-box that is just ready to go for various use cases. It will take awhile to fully understand the capabilities of Verint Community.
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.
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.
While the support portal (cases) is helpful, I've been even more impressed by their own support community. I always get quick, thoughtful, and interesting answers to my questions from support personnel, in-house developers, other users, and even the VP/GM himself! They have a really wonderful thing going there.
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.
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).
Khoros Communities is like a tool for companies to create and manage online groups where customers can talk, share, and get help. It's all about building a community. On the other hand, SAP Business Technology Platform (BTP) is like a big toolbox for businesses. It helps them do many things like building apps, managing data, and connecting different parts of their business. So, Khoros is more about talking and engaging with customers online, while SAP BTP is a toolkit for handling various tech needs in a business. They serve different purposes based on what a company needs.
I believe Verint Community stacks up very against previous solutions I have worked with. For an externally facing community, I think Jive-X was the best in class for many years, and Verint matches up very well from a features and configuration perspective. The other key point for me, is that Verint Community is also similar to Jive in that it has an extremely strong customer community of experienced community professionals. Verint does a great job of engaging with us about future plans, roadmaps, events, etc. I think this is a very under-rated benefit of a community platform, and Verint's is exceptional.
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
At times, troubleshooting in the software tickets takes too long. However, we have worked with that team to share our specific examples and have seen some improvement in this area, yet there is not always good response with documentation to reference later should an issue arise again. The ticket team could do better to point us to resources that will help.
