Fin vs. Oracle Service

Fin is fantastic at answering simpler inquiries, where the range and types of questions are easier to categorize. Thereby reducing the subset of possible answers. Where it has shown great improvement - but still needs more improvement - is by becoming a true Agentic AI support engineer that is capable of answering more technically nuanced questions. Our product has a lot of variables used for troubleshooting that cannot be adequately captured in documentation. Even though we provide thousands of pages of spec docs, each issue is unique. Training and empowering Fin to be as good as a Level 1 support engineer is still very challenging.

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

• It is very easy to train
• It does a great job of recommending answers when little context is given.
• I love the ability to create a snippet to address issues in the moment or in the long term, based on FAQs.

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 seems some users really struggle to figure out how to escalate to a human (especially through email).
• Not excited about how "soft" resolutions still count as resolutions and are paid for. Though some abandoned cases appear to be able to be concluded as "the user got the answer they needed", there are others where they clearly didn't, because they just open up another chat (or even more), trying to get more info. This pads the resolution stats and makes it seem more effective than it actually is.
• Cost -- Fin is quite expensive. It helps us with scaling coverage, but we're not really saving money.

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

We have been and will be continuing our journey with Intercom and nothing too concerning has happened that I have experienced or heard of that has us on the edge yet. If it ever happens it will be something along the lines of "Outgrowing" the use of need of the platform.

Incentivized

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 platform is overall clear and intuitive. As with any new platform, there's a learning curve, but that wasn't an issue for our team (and it shouldn't be an issue for others). Fin options are scattered across several submenus, and I'd like them grouped together, but I also like having all those training-related tabs open at all times, so it's not much of a real issue 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.

always there

Incentivized

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

Incentivized

works perfect

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

I can get help by asking Fin questions about itself. It answers accurately, citing its own Help Center resources with visuals. It can reason and dialogue well. But when it comes to getting human support for Fin, it is not as quick. It can sometimes take a few days. They are polite and well-meaning. Some things aren't their fault (product limitations), but there was one occasion where something took a long time to resolve with lots of back and forth but it was I who found out the error in the end that they missed, so they didn't really help resolve it.

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

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

Easy to know the learning path

Incentivized

The implementation was surprisingly easy but we are having to adapt from our old process to work well with Intercom.

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

There are so many AI platforms available, and you could theoretically build a system using the available AI API's from any of the big platforms. However, I dont think it's as easy as this. Intercom is deliberately built for customer service, the features they are releasing a based on providing the best customer experience. If we were to build this ourselves or to use another platform we would be taking on the upkeep, using Fin is just much simpler as it's also our chosen ticketing platform so anything that Fin is not able to answer yet and escalated directly to our team with no extra effort required from our side.

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

• New role opportunities — Using the “Fin-first” approach has reduced the workload for our Tier 1 team, giving them more time to focus on their own career growth. It’s also opened the door to a dedicated, AI-focused role, where a team member regularly reviews Fin’s answers and makes updates to help it perform even better.
• Enabling Fin has also reduced our response time and allowed us to meet SLA's.

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