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
Pylon
Score 8.0 out of 10
N/A
Pylon is a support platform built for B2B. Presented as an alternative to Zendesk, Pylon can be used to track customer issues across any channel, automate with AI, and design a support engine.
$70
per month per seat
Pricing
Oracle Service
Pylon
Editions & Modules
No answers on this topic
Starter
$70
per month per seat
Professional
$118
per month per seat
Enterprise
$167
per month per seat
Offerings
Pricing Offerings
Oracle Service
Pylon
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
—
Up to a 33% discount available for annual pricing.
More Pricing Information
Community Pulse
Oracle Service
Pylon
Features
Oracle Service
Pylon
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
Pylon
9.2
1 Ratings
11% above category average
Organize and prioritize service tickets
8.073 Ratings
8.01 Ratings
Expert directory
7.053 Ratings
8.01 Ratings
Subscription-based notifications
7.057 Ratings
10.01 Ratings
ITSM collaboration and documentation
8.050 Ratings
9.01 Ratings
Ticket creation and submission
8.074 Ratings
10.01 Ratings
Ticket response
8.074 Ratings
10.01 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
Oracle Service
7.0
74 Ratings
14% below category average
Pylon
10.0
1 Ratings
22% above category average
External knowledge base
6.065 Ratings
10.01 Ratings
Internal knowledge base
8.074 Ratings
10.01 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.
I think Pylon is great for startups who are figuring out where they want to interact and how they want to interact with their customers. Pylon is also great for beginner account management in terms of keeping track of comms, usage, tickets, and a bit more. Overall, I think Pylon will scale nicely it just takes a bit of time to configure all (lots) of settings.I don't think Pylon is well-suited for teams who don't know much about support operations. The tool has so many great features an they ship super fast, but the product itself isn't very opinionated and the amount of options sometimes can be overwhelming
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.
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.
Overall, the UI is awesome and super intuitive. The features makes sense and everything is customizable to your liking. You don't need to create copies of filters, because the changing of filters on one saved few is THAT easy, which is something we love. Additionally, whenever we go to look for a capability or day dream about something... Pylon usually has it or its in the works. Only reason its not a 10 is that it can be overwhelming that it has everything, but a food problem to have
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.
After evaluating both platforms, we chose Pylon for its superior user experience and deeper integration capabilities. Unlike Zendesk's frustrating UI and limited customization options, Pylon offered seamless integration with our existing tools like Salesforce, Linear, and PagerDuty, while allowing our team to stay within familiar Slack interfaces. The multi-channel notification system and AI-powered features like article generation provided the modern support infrastructure we needed, eliminating the complex rules and automations that made Zendesk cumbersome. Pylon's robust analytics and broadcast features also gave us valuable insights into customer engagement, making it the clear choice for streamlining our support workflows while enhancing both team efficiency and customer satisfaction.