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
Salesforce Agentforce Service
Score 8.6 out of 10
N/A
Service Cloud is a customer service platform that helps businesses manage and resolve customer inquiries and issues. It provides tools for case management, knowledge base, omni-channel support, automation, and analytics, enabling companies to deliver exceptional customer service experiences.
Oracle Service is a powerful service where the customers or clients can be evaluated in-depth. It provides a unified way where the customers can also raise complaints that can further be evaluated or resolved by the monitoring team to enhance the product. Also, it offers a lot …
Oracle Service is slightly on the expensive side in terms of pricing but it offers powerful features as well. As compared to Intercom, Oracle Service is suitable for large companies, and the support in the case of Intercom is available only by phone and email while in the case …
Oracle Service seems to have the advantage of providing many opportunities to companies if they have the right knowledge base. It opened our eyes to what possibilities were afforded to us by exploring the different options that existed. None of the options seemed to be more …
Oracle Service is the best fit for companies already using other Oracle products. Though Salesforce Service Cloud is equally good in most aspects, Oracle is once again an ecosystem of products like Oracle EBS where seamless integration is possible. Most of our clients were …
Mainly because of the name Oracle, it's a world leading company backed by a large user community in a broad range of different products. We needed the certainty of good support team behind the product and Oracle could deliver on this much better.
Oracle Service Cloud offers a wide range of communication channels that optimize and innovate the company's communication process and management with our customers.
I was not a part of the company when it was selected. Newer software has come out since but OSC had become so integrated with our ecosystem of software that it would be difficult to get rid of now. It has become more of a necessity than a desire to have. If possible down the …
I was not part of the team to make the selection. I worked as a user of both products, and from that point of view can say that Oracle Service Cloud offers a better GUI.
Zendesk - I think it's not exactly user-friendly for the final user, but it's user-friendly for the configuration. So it's easier to manage when we have these amounts of data we're going through and it's more AI prepared. So by far Salesforce is more ready for what we want as …
We selected this product because we already had some competencies in Salesforce. We own a Salesforce partner with expertise in this area, and on top of that, Salesforce purchased it — it was originally called Velocity. When Salesforce decided to acquire it, that finalized the …
I evaluated ServiceNow also, but we didn’t see much customization kind of thing compared to Salesforce Service Cloud. And yeah, that’s it — I didn’t evaluate many other products because I’ve been working on this one for the last 14 years. I just evaluated a few things in that. …
I think Agentforce now got a lot of, I mean it will make our lives easier because there's a lot of automation going on at the same time. We're excited about Salesforce voice as well. That will help us in Service Cloud. So it's more of unified service for us that say a Service …
Evaluated ServiceNow. Evaluated Zendesk. We selected it primarily because we already had the Salesforce ecosystem and we didn't want to bring in another vendor. For us it was important to make sure that our data is only in so many different systems and so many different cloud …
Oh, now see, I forget the names of the other ones I've done. I mean I've used C4s, I've used some lower end ones too for local small business and I'd even recommend Salesforce for small business. Say pricing strategy for small businesses is harder for them to keep up with the …
Going back when this product was selected, they went through probably a two year evaluation process. We weren't personally a part of that obviously because we were on the implementation side, but they evaluated many products. Microsoft and Pega were the two main front runners …
I wasn't by the evaluation for years, so not that, but historically I've been here for 13 years, so not a lot, but previous company had a home built solutions for it, so they designed their own and built their own. But that was a big telco in the UK we had our own data centers …
I honestly prefer Zendesk to Salesforce Service Cloud. I find that Zendesk is easier to manage both on the support ticket side, as well as the knowledge center side. It looks and feels easier to use than Salesforce Service Cloud. Salesforce Service Cloud is fine, but it is …
Zoho is not very real-time, it has limited integration capabilities, and the UI is not very satisfactory for any incoming customer. The performance is slow and impacts the overall customer journey. The data stored in the backend is slightly scattered and needs to be cleaned …
Salesforce is a really great case management tool. Made things a lot easier for our team. Wanted something fairly simple that had a variety of capabilities we could customize.
We used Salesforce for years, Left for Hubspot, and then came back to Salesforce (SF). As they say, don't fix it if it's not broken. Salesforce and customizing were better for us.
Salesforce Service Cloud offers deep integration with our current and expanding CRM data, along with numerous pre-built features that didn't exist in Kayako when we used it. (We used to use an instance Kayako installed in a private cloud environment.) Salesforce Service Cloud …
Zendesk has it's own challenges in terms of Administrator difficulties and a completely different back-end than Salesforce Service Cloud. I would recommend Salesforce Service Cloud if you need a clean database of Companies and Contacts. Zendesk does not excel in overall CRM …
I'm not at the level where I would be part of the decision making process for choosing a vendor or product for the organization. Every position I've held, I've come into a company that has already implemented or is in the process of implementing Salesforce. Honestly I would not …
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.
Probably where you have a number of service teams that all contribute to a knowledge base is one area that's really useful. AI response, it looks like with AgentForce, that's going to be one of our next deployments. So they're AI based on the trust layer is, I like that it has the trust layer because it's already got some built in safeguards around privacy and security controls for AI, which is very important right now. Where it's probably less useful:gain, round robining a very email heavy conversation, so it's not the best email tool. A lot of our team still uses Gmail and logs to the case rather than actually emailing directly out of Salesforce. Email signatures are not great because you can only have plain text email signatures, you can't have HTML.
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.
I give this rating to RightNow because I believe that it's a strong CRM (I know RightNow doesn't like this term) product with virtually limitless possibilities. I like how flexible RightNow is, allowing businesses to fully customize it for their needs. I also like that it's cloud based and doesn't require additional local installation and management.
Professional edition works best for a small company with lower call volumes and is very useful but as you grow exponetially I think it has limited ability to do all the things we want to - SLA management, defect, release management to name a few. Reports and dashboards being available in real time.
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 love that the Salesforce Service cloud provides all of the functionality that I need when implementing business processes for our customer support representatives. It even has enough functions and features that allow us to customize and expand upon our current processes, giving us the ability to go above and beyond what we've thought we could ever do. Using cases coupled with Salesforce's automation tools help ease the workload and keeps our data integrity intact.
Salesforce's Trust Center clearly communicates occasional issues to anyone who subscribes, down to an organization's cloud instance. Bundled sandboxes ease updates, and seasonal upgrades are seamless, scheduled well in advance with plenty of information about what's coming. Support agents have noticed intermittent Omni-Channel disconnects due to internet connections, and these are clearly notified.
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.
Load times can be slow, but this is also based on how much customization you have done. We added a lot of custom fields which could cause additional slowness in loading. This was never anything that affected our overall efficiency. I did not notice that Service Cloud slowed down any of the systems we had it integrated with
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
Salesforce offers support, although it generally gets routed to overseas support teams first, and once they are unable to help, it gets escalated up the chain to higher tiers. Frequently, the answer back from support is that there is no native solution, and we either have to turn to the AppExchange for some solution provided by another developer, or custom build our own solution.
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.
Our in-person training was provided by our implementation partner and it was quite good. This was in part because we were already working with them and so it naturally leant itself to a good training relationship. And because they were building our customizations and configuring things, they could then provide training on those things naturally.
Trailheads are great but it was often unclear what actually applied to our organization. This made it difficult to get a whole lot out of it. Part of it is that because the basic Salesforce features didn't quite work for us, we had to add customizations, which then nullified a lot of the training.
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
I would go through an implementation very differently knowing what I know now. It was difficult coming from systems we liked in post-sales service and having to adapt to the clunky and underwhelming feature set in Salesforce. I would trim back our expectations
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.
Zendesk - I think it's not exactly user-friendly for the final user, but it's user-friendly for the configuration. So it's easier to manage when we have these amounts of data we're going through and it's more AI prepared. So by far Salesforce is more ready for what we want as the next level of hyper-personalization in sales and for sales.
Positive, absolutely the speed to market and being able to get the product out there. The continuous improvement that we've been able to deliver in terms of small incremental developments, moving from basically a more rigid homegrown solution that they had where the turnaround time was about six monthly releases. We've got it down to three monthly releases of hoping to go to one month releases very soon. So just that whole speed to market being government, I mean that is just a major improvement in terms of what they've been able to do.
I think the negative part was integrating it and the complexity we had in terms of integrating DevOps as a concept and being able to use the Salesforce DevOps tools to be able to get that all rolled out in their existing current, very structured and rigid environment. And that probably took us a solid year to get those processes up and running. But yeah, now that it's working, it's absolutely fabulous.
