Hiver vs. Oracle Service

One scenario where Hiver works really well is in a shared support or billing inbox or anywhere multiple team members need access to the same messages. For example, when a customer emails about a billing question, we used to reply and manually loop in the billing team or forward the message. That often caused confusion, especially when someone forgot to “reply all” or responded only to the teammate instead of the customer.Now with Hiver, we just assign the conversation to the billing inbox, and whoever is available can respond. Everyone on the team can see the thread, status, and notes, which avoids duplicated efforts and missed replies. We also used to rely on Google Groups, but it wasn’t clear if someone had already replied, and there was no easy way to collaborate behind the scenes. Hiver completely solved that for us.As for situations where Hiver might be less ideal, I’d say if your team isn’t using Gmail or Google Workspace, then it’s probably not a good fit. It’s really designed for teams that live in Gmail so the team doesn't have to learn a new system. I'm sure some businesses will require a more robust ticketing solution but for our use case, this was a perfect option to improve outcomes, client service, and satisfaction.

Incentivized

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

• automation through rules
• tagging emails, anaylics behind them
• support, chat always responds right away

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

• It could be considered expensive, but ultimately worth every penny for those who use shared inboxes/groups to run their business.

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.

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.

Easy to use

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

Support is there, can be slow at times.

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

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

True ticketing solutions are certainly more robust in that you can typically manage social media channels and phones, etc. But, in my opinion, when you don't have a team solely responsible for managing a ticketing system they can be complicated to implement. With HIVER, we're already all accustomed to managing our own G-Suite inbox, so it was simply a matter of teaching the team how to utilize the solution.

Incentivized

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

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

• The ROI on showing how many emails are being received and addressed in a timely manner are great for KPIs
• the ability to search and ensure emails are not being deleted as an automatic report is sent out the following day saying if any emails were deleted by whom
• the ability to automate who gets assigned what emails from specific vendors per entity

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