Oracle Service 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
Parature (Discontinued)
Score 5.0 out of 10
N/A
Parature was a self-service customer support platform providing a self-service knowledge base to connect with customers across multiple channels. The company was acquired by Microsoft in January 2014 and reached EOL in 2017.
N/A
Pricing
Oracle Service
Parature (Discontinued)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Oracle Service
Parature (Discontinued)
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Oracle Service
Parature (Discontinued)
Features
Oracle Service
Parature (Discontinued)
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Oracle Service
7.7
78 Ratings
6% below category average
Parature (Discontinued)
-
Ratings
Organize and prioritize service tickets
8.073 Ratings
00 Ratings
Expert directory
7.053 Ratings
00 Ratings
Subscription-based notifications
7.057 Ratings
00 Ratings
ITSM collaboration and documentation
8.050 Ratings
00 Ratings
Ticket creation and submission
8.074 Ratings
00 Ratings
Ticket response
8.074 Ratings
00 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
Oracle Service
7.0
74 Ratings
13% below category average
Parature (Discontinued)
-
Ratings
External knowledge base
6.065 Ratings
00 Ratings
Internal knowledge base
8.074 Ratings
00 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Product A and Product B
Oracle Right (Oracle Service Cloud) was an important evolution in the group's ombudsman channel management processes. We brought the Oracle Service Cloud to digitize the processes for capturing and managing the group's ombudsman channel, no longer operating manually (MS Excel).
Oracle Service Cloud (Right Now) brought about an important evolution in the management processes of the group's ombudsman channel, where activities that were performed manually, repetitively and with risk of errors, are now operated by the Right Now platform itself, whether by API, or by automation of the tool.
The single element of Parature I've not seen in any other system of this kind is the Download Module. You can post files in the open, or protect them by any number of entitlement methods. The solution is also appealing to those who don't want to manage the back-end/IT needs as it is a hosted solution and has proven to be very reliable.
Clean/Friendly UI. It was extremely easy to navigate around Parature's menus at a high level, and you could take advantage of the more robust features as you became more comfortable and familiar with how Parature operates!
Strong Knowledge Base. Writing KB articles or ticket summaries and making use of the search function within Parature allows for expedient recovery of past ticket information. Being able to search for a fix action, or at least a troubleshooting article that can guide you towards a resolution is extremely valuable.
Enhanced Notation Capability. Being able to send/post internal or external updates to a ticket is great! You can leave the wordy technical details for other employees while making sure to communicate the high-points and fix action to the end-user.
Oracle Service Cloud needs a better built in integration with Oracle Social Cloud or it needs to build in more Social network capabilities.
SMS is handle via a third party application but could be built in as part of the product.
The knowledge foundation product needs a better way to handle multiple languages. Currently you have to purchase an additional interface for each language. You can purchase the more expensive Knowledge Advance which does have a better language feature.
Reporting is barebones at best. If you need special reports, we had to go through Parature to have them built.
The use of frames on a website is very 1990s. It actually impacts usability of the product, especially when combined with how Parature handled sessions. An engineer could only work one ticket at a time which, honestly, isn't very realistic for a busy support team that is working on several issues at a time.
Support was often unresponsive when contacted for unplanned problems.
The knowledge base was not very friendly for clients and it provided no real encouragement for it to be used.
It took several clicks to do something as simple as edit and assign a ticket or to close a ticket.
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.
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.
It was bulky, cumbersome, and didn't allow us to handle the volume of cases we received on a daily basis. Many of our issues were highly technical in nature and we would often need to work on 2 or 3 at once. The poor design choices prevented this, which was unfortunate.
They recently had one very extended outage. It was a data center issue - but they were not diversified enough so in the end the system was down for almost 8 hours. There are also periods of time where for no reason the system simply doesn't respond. This small outages are usually short (just a few minutes), and have in fact been occurring less often, so it appears some corrective actions have been taken.
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.
Technicians seem to be assessed based solely on how quickly they close the issues. I've had to reopen requests multiple times because they didn't actually solve my problem. Also, when the issue has even a moderate amount of complexity, the technicians often instruct me to "open another SR" to handle the other issue. I'm the customer, I shouldn't have to follow their processes, they should handle that for me. But even when I create the new SR, it seems like their right hand isn't talking to their left - they aren't reading back to the previous issue for context. So I get bounced around a lot, and I have to tell them how to do their job
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.
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
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.