Jive-x (Discontinued) vs. Verint Community

Our version has some limits which have been overcome in newer releases of Jive with better workflow processes and plugins. It is clear that you need to be on the public cloud version as this will lower future costs however this limits you in terms of customization. So to make the case for a cloud version, you get the automatic upgrades with the upgrade costs attached to hosted versions

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.

Incentivized

• Simple. Intuitive for non-techies like myself.
• Real-time and easy to access.
• Optimized across multiple platforms, mobile devices, etc.
• Excellent reporting and visibility on usage and effectiveness.

Incentivized

• 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

• Jive could do a better job of providing parity with its on-prem product in terms of features and in terms of making tiles on par with widgets. They basically quit developing for widgets and then stopped at a basic set of tiles.
• Jive has some good health metrics built in, but the reporting tools need to be way more robust. It shouldn't require an API call to get information on which pages have the most likes or which customers have the most followers, or that sort of data. And they need to make the views/pageviews match the way Google Analytics reports them so it's honest data.
• They need to improve the Data Export Service, which is opaque, klunky and hard to use. If CMs are required to use it to get important metrics, it needs to be MUCH easier, less time consuming.

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

Incentivized

For a large company the cost can quickly escalate so this must taken into account when renewing. For me, the decision to review will be taken with upgrading to the cloud version in mind as well. My power users love Jive for it versatility but it is important to note that you must be prepared to constantly train and coach the non-power users

I am not part of this decision making process, but I did provide positive feedback to the decision making board.

Incentivized

The positives for general usage more than make up for the difficulties faced by the community manager. There are some glitches which will ease as future releases are made. No developer resources are required to help with set up and once users get used to the sometimes clunky way of creating content then the experience is quite good

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.

It works wonders. My only gripe would be that there are some customizations you can't make without hiring a vendor with coding experience to implement them.

Incentivized

The support has been fantastic when we have been trying to code our own apps. Jive have went above and beyond what was required to help us out. Bugs fixes are generally very good and they are upfront when they are unable to help or a 'problem' is actually in need of Professional Services

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.

all customizations should be under warranty so that you get the right level of support from the 3rd party

For the money, it just happens to fit best with our original use case. Now that it's been sold to Aurea, which essentially halted any support or dev for the product before selling it off to Lithium, we will have to eventually move off of it (this assumes Lithium won't hire devs for code they didn't build, and that's not a bad assumption). So, while I recommend it, it's with the caveat that it's been sold and will be evolving in the near future.

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.

Incentivized

Highly scalable system with the ability to expand to an increasing number of users and communities

• It reduced calls.
• NPS increased.
• Increased engagement in the program.

Incentivized

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