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
Oracle Service
Score 8.0 out of 10
N/A
Oracle Service Cloud is the help desk and customer experience management platform from Oracle. The technology was developed and supported by RightNow Technologies as RightNow CX for cloud-based call center automation, until that company's acquisition by Oracle in 2011 for about $1.5 billion.
N/A
Pricing
Khoros Communities
Oracle Service
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Khoros Communities
Oracle Service
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.
Oracle Service [(formerly Oracle Service Cloud)] is well suited for cross-channel contact center service which includes live chats, virtual assistants, email support and case management. It has a social tool that keeps tabs on your customer interactions within your social media platforms and your website. You can provide your customers with a knowledge base for self-service with information that they need by posting content and resources.
Oracle Service cloud handles incident management extremely well. It can accept requests from multiple channels. That includes email, website, phone, chat, SMS & some social.
Oracle Service cloud provides a knowledge base that can be used by customers or by agents. It can move consumers to self service for most issues. It also has good feedback from customers and agents so that the knowledge can continue to be updated to push people to more self service.
Oracle has a good consumer portal that can be used as a website or typically is used in conjunction with a main website as a contact center or help center site. This allows the contact center to manage both the knowledge and the request and the interactions with the customers.
Oracle Service cloud is built to provide a turn key solution for CRM/Contact center with some minor configuration. But it also has the ability to be highly customized to meet any companies needs. Much of that work can be done via the configuration options already in the system. It also have a full set of SOAP and Rest APIs for integrating to other systems.
I feel that the professional services engagements need to be better. There is a lot of miscommunication, and a lack of clear outcomes, goals, and timelines. It can take weeks to get meetings on the books and a team assembled to start getting work done.
Documentation on their website, at times, is outdated or incorrect. Sometimes the product doesn't even work as described in some of their documentation
The admin console could use a nice fresh UI overhaul. While it's functional, it would be nice to see a more modern UI for the area where most community managers are spending a decent amount of time
This is only an occasional, user problem; when searching for specific records, at times we receive an error that the maximum size has been exceeded and therefore does not yield any results. This is particularly frustrating when trying to search for a specific street address across several years.
Community has worked well for over the year. However, there have been a lot more technical and feature issues we have been seeing in last year or so. Also customer support has not been very quick to address issues. SO there are things that can definitely be improved on Khoros end
Although RightNow is extremely flexible, the flexibility comes with a price. It is often not intuitive which settings you need to change (and under which menus these setting are buried) to enable the system to do what you want. Also, sometimes the system can do things you need, but you don't initially realize it. When RightNow sells a system to a new customer, I think it should come with X hours of consulting time with a RightNow expert. The customer should be able to consult with this expert over the next year to get advice concerning how to configure the system to achieve desired needs. Often RightNow Support would just answer "no" when I asked if I could do something, but then I would find another way to achieve my goals after talking with other companies using RightNow.
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.
The learning curve is fairly steep; but for something that has this much capability, it's nearly impossible to make it "easy". The layout and organization are at least reasonably intuitive. The hardest part-- the "weakest link"-- is the portal development (where you can build help centers and other end-user pages.) The capabilities there are significant, but the learning curve for that part is especially steep and it takes a fair amount of expertise to be able to update it.
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.
We use a lot of tabs and fields on our incident workspace, which should slow the system down, but it's still quite fast, and we continue to optimize whatever is possible.
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.
The vendor offers customer support to users who maybe stuck in usage of the platform in a number of options and this ensures that one does not get frustrated at all in using the platform. This enhances the trust held by the clients concerning Oracle CX Service [(formerly Oracle Service Cloud)].
Most of our training was given while doing user acceptance testing, and getting the system approved by the market. When ever we were in doubt, our implementer helped us along. Later on we started exploring by our selves.
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).
Work with a RightNow expert during the implementation. Explain features that would you like to have. Often, somebody who really knows the system can show you what you need to do to achieve the desired results. Where a RightNow support engineer or a consultant might say "the system can't do that," a RightNow application engineer will listen to what you need, and often come up with an alternate path to achieve it
WordPress, Guild, tribe - all have pros and cons vs Khoros. The primary concern of Khoros vs other platforms is cost. For the price difference, Khoros *should* be a no-brainer choice. No one should ever consider using any platform other than Khoros... so why do people consider other platforms?
TCS' customers who also selected Oracle Service Cloud over Salesforce Service Cloud and GE's ServiceMax in the Mfg. vertical in which I work, did so because of the robust ability of Oracle Service Cloud and its APIs to integrate with other value-add solutions for manufacturers such as IoT applications, Big Data Analytics, and Field Service applications.
The platform is incredibly scalable and provides the flexibility to use it out-of-the-box or customize it to whatever extent is needed. It has very powerful APIs and is built in modular way that allows pages, components and other elements to be constructed easily.
We have an internal chargeback for servers and we anticipate that the cloud will save us some money or be cost neutral for us.
We plan to see a reduction in the need for data center staff and server provisioning as we move more environments to the cloud.
We are now responsible for our own destiny with the ability to ramp up and down our servers based on need. We can also monitor our costs more closely with the metered service and turn off the environments when we are not using them.
