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
ServiceMax
Score 5.1 out of 10
N/A
ServiceMax’s mission is to help customers with asset-centric field service management software. ServiceMax’s mobile apps and cloud-based software provide an overview of assets to field service teams. By optimizing field service operations, customers across all industries can better manage the complexities of service, support faster growth and run more profitable, outcome-centric businesses.
Business Development Director - TCS Oracle Practice, Americas
Chose Oracle Fusion Service
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 …
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.
Small deployments, where you have some specific need for ServiceMax and absolutely need offline capabilities, and are willing to deal with the problems. Otherwise, you may be better off looking at the built-in Work Orders and field service module that Salesforce is now providing. Their app is direct competition for ServiceMax and integrates much better with cases and knowledge articles.
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.
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.
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.
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.
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.
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.
ServiceMax has an offline capability, and also integrates with our Salesforce side of business. At the time, Salesforce did not have a field service application so we could not consider it, but if we could now, we would probably go with that instead. ServiceMax is also expensive. But at the time, ServiceMax was the only offering out there that integrated with Salesforce, had mobile offline capability, and could operate at the scale we needed.
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.
ROI for ServiceMax is mostly dependent on how in depth the organization wants the software. Our ROI is expected within the second year of operation due to the complexity of integration and the initial training requirements for in-house programmers.
Inventory control ROI is expected within year three or four due to the number of technicians and creating the foundation of information to import into ServiceMax. Expectations are the front end programming will be complete and our programmers will be better acquainted with the modules and architecture to make the inventory integration smoother than the initial integration.
Our organization has been working with ServiceMax for ten months and beginning to incorporate the financials to the work orders. This process has not been as seamless as once projected and the root causes are under investigation. It appears the original fields available to track time between employees were not in depth nor segregated sufficiently for granularity.
