Joule is an AI copilot that’s grounded in an organization's business data and infused with AI agents. It proactively assists employees in every cloud application they use while automating complex processes.
N/A
Oracle Digital Assistant
Score 7.9 out of 10
N/A
Oracle Digital Assistant delivers an AI platform to create conversational experiences for business applications through text, chat, and voice interfaces.
$1,160
per month 200 hrs/month
Pricing
Joule
Oracle Digital Assistant
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Joule
Oracle Digital Assistant
Free Trial
No
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Joule Base
Joule Base is a no-cost entitlement of SAP cloud products that enables teams to navigate SAP systems more easily, find the right information more quickly, and complete everyday tasks faster.
Joule Premium
Joule Premium extends Joule Base with more powerful AI, including advanced Joule skills, premium embedded AI scenarios, and Joule Agents. Joule Premium capabilities are accessed through the purchase of AI units. Visit the pricing page linked above to learn more about Joule Premium capabilities.
Joule in SuccessFactors is well suited in case you just want to have a quicker way to execute quick actions for a couple of users, or if you extend Joule with some Joule skills. Apart from this at this point in Time I don't see a lot of default scenarios that Joule brings to the table in SuccessFactors.
As mentioned in pros and cons, it depends on the use cases. Most of the normal chatbot use cases can be handled by ODA. If you want to build a chatbot with menu style or conversation style (it is not straight forward but it can be done), ODA can be perfect. If use cases are to also include AI with emotional intelligence to make conversational more interactive and also be able to detect through AI engine automatically what a person would like to do or perform or ask, then ODA may not fit for it. If you also are looking for virtual agents through tighter IVR integration then ODA may not be right. There are a few limitations around the number of words in the text to voice feature.
Instructing the right way of doing functionalities for e.g. creation of PR
pinpoints the exact PR and provide insightful information about it, which allows procurement processors to do the next step
provides thing to watch for in your tasks, for e.g. quickly address PO floating issues by navigating and showing the other partial items that are not GRed.
As we explore, we can learn more. As i believe, we can only learn to live and live to learn stuffs. So as well AI does the same and improve itself. By trying and prompting joule more, we can use it in better ways. I would definitely wait and use the new versions shared in SAP Teched on Joule with more LLM involved
I would rate Joule’s overall usability a 10 out of 10 because it makes interacting with SAP incredibly simple, intuitive, and fast. The conversational interface removes the complexity normally associated with navigating SAP modules, running transactions, or building reports. Even non-technical users can get meaningful insights within seconds just by asking natural language questions.
Usually support for Joule takes longer than normal, and the correct answer always takes a long time to get, or we just don't get it at all, and we fix ourselves.
Joule is better because it doesn't take only data available on the web, but combines that with data provided directly by the game publisher through API to us which includes every single match played = all data points from all of those matches. That means that for us Joule gives deeper insights than any online AI chat agent could do
I selected Oracle Digital Assistant against all other digital assistant platforms as this platform works like a charm with any Oracle application. It integrates well with Oracle Integration Cloud. The new beta version has an inbuilt conversation builder which can be used to build conversation without the YAML code.