Lithium Community is a fully-featured community platform and is focused on the needs of marketers. Lithium most often competes with Jive Team Collaboration and Get Satisfaction.
N/A
PeopleOne
Score 8.5 out of 10
N/A
PeopleOne is a digital workspace software solution that aims to boost employee productivity. As a mobile centric intranet solution for O365 users, it integrates all an employee's digital tools into a single place. With it, the vendor says teams are empowered to do their best work through better communication, collaboration and social engagement on the PeopleOne platform.
N/A
Pricing
Khoros Communities
PeopleOne
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Khoros Communities
PeopleOne
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Pricing is variable based on the needs of the customer.
I describe Khoros as the salesforce of community software in that it's customizable and enterprise, however it can be a beast to use. There isn't any standout in the community field (in my opinion) so if you're looking for an enterprise community software, it'll serve you well. I do think it's important to realize you can't manage this without the proper buy in from your company when it comes to development of the site. You shouldn't be using Khoros if you only have a front end community manager. If you're going all in on community and need a solution that will scale as you grow, consider Khoros amongst your vendors and see how you like it. It's worth checking out.
We are using [PeopleONE] to collect and manage our field data for payroll, invoicing, and production management purposes. So far, it works quite well for those uses. Additionally, we are using the app to manage communications from our offices to our field management at upper and middle field management levels. We have successfully used the application to communicate important upcoming events, COVID protocols and reporting processes, and other initiatives. I am unfamiliar with the limitations of this technology or applications for which it would be unsuited.
The UI, both for desktop and mobile apps, is simple and virtually self-explanatory.
Compared to apps we have used in the past, PeopleONE is fast, in both data entry and retrieval.
The team responsible for creating our specific requirements for the app is exceptionally responsive. It is made up of creative problems solvers who have built a product that meets every need we have presented.
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 haven't actually experienced any issues of note to record here. Every concern, requirement, or change we have requested has been swiftly and satisfactorily resolved by the Impiger team.
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.
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.
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).
The company was already using this platform when I was hired, so it's what I had to work with. In a previous role, I did explore Khoros Communities as a platform and it was one I really wanted to use, but it's a very expensive platform so I wasn't able to move forward with it. Back to my current role, again, this is who we already had a contract with.
Khoros platform-based communities can very easily and rapidly grow in line with their community size. Better support could be given/provided to new customers to ensure their community development is in line with best practice. Communities can and do grow using methods within the Khoros platform that at later points can hinder growth rather than support it. e.g. Utilising custom content fields to update the production environment rather than building pages and quilts in studio and then pushing to prod and only adding 'posts' to the page in prod. Further training for community admins to look out for these pitfalls would be worthwhile.
