Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
$0
per month
Oracle Fusion Service
Score 6.9 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.
I think JIRA is best suited for IT tickets and service requests. Comparison is hard, but I use JIRA on a daily basis and I cannot think of a better alternative for the task we are using it for.
The biggest benefit that I see using Oracle Service Cloud is in terms of the technology stack that it uses. This translates to ease of access to resources regarding the skill sets that organizations need to maintain the product.
Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
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.
Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem).
No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability.
Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive.
Request forms are very basic and there is no native dynamic field ability available.
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.
I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.
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.
I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.
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
When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and JIRA was the better option since it was less expensive and geared towards being a ticketing system.
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.
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.
