Oracle Service vs. osTicket

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.

Incentivized

For beginning smaller companies that are in need of partially automating their incoming requests this product is easy to set up and will assist in structuring these request[s]. These requests can come in via email/phone or web portal. For companies that are beginning to streamline their support procedures, this tool can be a first step into automating part of these processes. This is also how user[s] should see it. It is merely a tool that can assist in structuring the incoming request flow the rest still has to be fit into business processes.

Incentivized

• We can access the best-in-class features for cross-channel contact center management amd field service management.
• It provides a great way to mobilize agents and boost collaboration within the office which in turn improves the overall customer experience.
• Automation of back of the office repetitive tasks leading to a faster way of addressing customer concerns.

Incentivized

• osTicket is extremely user friendly for end users and support agents. It's very easy for new end users to put in a service request. This aspect of simplicity is important because we don't have to train new users on how to put in service requests.
• Feature wise osTicket has everything you need without being overly complicated or cluttered. This is important for us because it allows for faster support times and happier end users.
• Lightweight and very reliable, osTicket uses PHP and MySQL. Setup is easy and it can be hosted internally or externally web hosed. Also, since it relies on PHP it gives you flexibility to use Apache, Nginx , Lighttpd , IIS, etc.
• Thriving community: the community behind osTicket is feature-wise. Which is very helpful if you have any questions.
• Best of all, osTicket is completely free and open source. While they do offer pair tier cloud-hosting and enterprise support. The free version offers all the features of the paid tiers (minus hosing and support).

Incentivized

• 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.

• Language package should permit also the translation of the templates
• It should not require the user to enter his details when creating a new ticket. This should be filled automatically
• Improve the layout of the ticket messages to facilitate reading and interpretation.

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.

It does well what I was looking for on a ticketing tool

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 am familiar with osTicket and this allow me to teach all the staff and support them whenever they have any concern regarding the usability and following processes.

We have never had issues with downtime or it not being available. Upgrades and maintenance also happens in weekends or at night.

Incentivized

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.

Incentivized

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

Incentivized

Being open-source it is community supported. There is a hosted version that provides better support. Honestly, I have not really needed support

Incentivized

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.

Incentivized

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

Grant all prerequisites are met, before installing to avoid any issue during the installation

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.

Incentivized

osTicket has proven to be a very useful tool for the team to help support the business. Open-source was the right price point and self-hosting as mentioned was quite important (however I believe that osTicket does have a hosting solution available if needed). Jitbit was a close contender but didn't like how it doesn't separate people submitting tickets from users acting as agents. So all in quite happy with the choice.

Incentivized

We have never had any down time, slowness or anything. Any error or instability that has occurrred has so far has been caused by user errors.

Incentivized

• Since its, it has significantly reduced our training time of new agents. What used to take 6 weeks in the class room, went to 4 weeks.
• Service Cloud allows us to easily gather data to report to the other departments quickly.

Incentivized

• When we had a hosted version of osTicket, we were saving some time by having them work on our setup, but we were spending a lot. Switching to our own osTicket build from their open sourcing not only saved us money upfront but we actually spent LESS time developing because we knew our ideas and didn't have to explain them to another (unrelated) party.
• Creating our own ticketing infrastructure for institutional data requests has been a game changer for us. We have been able to interface with our enterprise email client and create a level of customization that meets our existing informational technology culture.

Incentivized