IBM® watsonx™ Orchestrate® leverages AI to automate complex workflows. The solution helps build, deploy, and manage AI assistants and agents. It offers a catalogue of pre-built agents and tools, low-code agent builder, multi-agent collaboration capabilities, and integrations with enterprise apps.
$500
per month per subscription
Rasa
Score 6.0 out of 10
Enterprise companies (1,001+ employees)
Rasa is a conversational AI platform from the company of the same name headquartered in San Francisco, enabling enterprises to build customer experiences. Rasa’s platform was built to create enterprise-grade virtual assistants, allowing personalized conversations with customers - at scale. Rasa’s conversational AI platform allows companies to build better customer experiences by lowering costs through automation, improving customer satisfaction, and providing a scalable way to gather customer…
$0
Pricing
IBM watsonx Orchestrate
Rasa
Editions & Modules
Essential
$500
per month per subscription
Essentials
$500
per month Per subscription
Standard
Enterprise
Standard
Enterprise
per month Per subscription
Developer Edition
$0
Growth
starting at $35k
Enterprise
Contact Sales
Offerings
Pricing Offerings
IBM watsonx Orchestrate
Rasa
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
IBM watsonx Orchestrate can be deployed and run on IBM Cloud, AWS, or on-premises. Prices shown are indicative, may vary by country, exclude any applicable taxes and duties, and are subject to product offering availability in a locale.
—
More Pricing Information
Community Pulse
IBM watsonx Orchestrate
Rasa
Considered Both Products
IBM watsonx Orchestrate
Verified User
Anonymous
Chose IBM watsonx Orchestrate
I think this product's got a lot more use cases from a business standpoint. I find the other products are very based in end users and also the orchestrator has a lot more agnostic connections to a lot of products, whereas Microsoft is very Microsoft dominated and the other …
The other solution provides far more capabilities but at a much higher price and far more complexity. The IBM watsonx Orchestrate tool is less expensive (about 25% of the other solution) while being good enough for what we needed and being easy to use.
Strong ITSM and HR workflow automation with governance, ServiceNow excels in IT/HR but lacks flexibility for cross-departmental use cases such as demand planning, finance close, or procurement analytics. Orchestrate supports a broader set of enterprise functions beyond IT …
Google Cloud Dialogflow, Amazon Lex, and Azure AI Bot Service were assessed before selecting IBM watsonx Assistant. The primary reason we used IBM watsonx Assistant is the ability to remember diverse contexts during the multiphase bookings and to support multiple languages that …
The code generation feature of IBM watsonx Assistant was slightly better than in ChatGPT and Vertex AI. However that might change in the future since AI engines are evolving very quickly.
Similar positions for similar purposes include Google Cloud DialogFlow and Azure AI Bot Service that I have considered. As opposed to Dialogflow, IBM watsonx Assistant is more tightly linked to comprehensive analytical units that provide clearer and more comprehensive data …
My experience working with Microsoft Bot Framework and Dialogflow has shown that Watson Assistant features an intuitive interface combined with powerful analytics. We selected Watson Assistant because it strikes an excellent balance between providing powerful capabilities while …
Make has more community of workflows to follow that have been redeveloped and are available for download. Selecting WxO is based on our trust level with IBM and the propositions of the Granite model being less biased, more business trained, and the ecosystem allowing for …
I selected IBM watsonx Assistant so I could maintain the NLP/NLU processing from our last supplier (which was not Twilio). Since we switched, I have not liked IBM watsonx Assistant so much. We are sincerely thinking about changing it to a new one, the Kore.AI which seems easier …
The NLU algorithms are more efficient in Rasa. Creating conversations is much easier. In IBM, the more use cases we created, the more complicated it was to up date the entire model. It was quite common to mess up what had already been done.Rasa has greater scope for use with …
Glean - proprietary semantic search algorithms, no backend actions integration IBM Watsonx - complicated dialogue builder, poor separation of no-code and pro-code interfaces ELMOS (agent based) - all logic in code, no dialogue logic in no-code interface possible
In our case, it is well-suited for workday integration, which allows us to automate the entire workflow. However, we are still working on the O9 platform integration, which we feel is less appropriate, and integrating the workflow into the platform.
I have been using the platform for over 3 years and I have noticed a very good evolution, in an attempt to reinvent themselves. The support team is amazing, always available to work out with us in achieving the best results. About the technology, the algorithms available in the platform suits most of the cases. Being language agnostic is a very positive point for us, because some big tech platforms have little support for PT-PT language.
Rasa CALM flows and Rasa domain could be made fully independent of the Rasa training process and dynamically retrievable from e.g. a graph DB. This would make the chatbot more flexible.
Prompt templates, or at least paths could be referenced in Rasa config. Different policies in the Rasa config could then be configured without code change to use different prompt templates
LLM configuration should rather be part of the endpoints, than model configuration.
Rasa Studio could support all the functionality of Rasa Pro.
IBM Watson simply works well for my organisation. We were able to design, build, and deploy a fully integrated chatbot in a matter of months. The basic building blocks (intents, skills, dialogue nodes, integration) are relatively straightforward for a technical developer to work with. The bot now supports retail customers in 3 different countries on both web and app based channels. We plan to further develop the bot to expand the way it interacts with customers through voice to text, and optical character recognition, as well as an improved UI.
With the growing use of AI and chatbots, it's very easy to use, and the conversational language makes it easier than keyword searches in a document. The contextual language processing is impressive. It's easy to integrate into our internal portal. The use of this tool would depend on each company's security and data sensitivity.
With the help of dedicated team - documentation and video resources it is relatively easier to build. We prioritized pro-code usage to begin with launch.
To develop chatbots based on client provided flow what kind chatbot required for client either button or free text chatbots. we will decided accordingly flow and develop chatbot using IBM Watson. We will integrated custom components if required which is not present in library. IBM Watson library anyone can easily learn and develop chatbots.
We've rarely had to engage support, but they've always been prompt in responding and very attentive. Support experiences have been extremely positive (but we're mostly happy that we just don't have any cause to routinely need support in the first place!).
Rasa support has been very responsive, trying to fix any reported issues ASAP. They've also listened to many requests for improvement. The Rasa features and changelog are well documented
I think this product's got a lot more use cases from a business standpoint. I find the other products are very based in end users and also the orchestrator has a lot more agnostic connections to a lot of products, whereas Microsoft is very Microsoft dominated and the other products are very technical and not business focused.
Glean - proprietary semantic search algorithms, no backend actions integration IBM Watsonx - complicated dialogue builder, poor separation of no-code and pro-code interfaces ELMOS (agent based) - all logic in code, no dialogue logic in no-code interface possible Rasa - transparent and simple sharing of objects between no-code and pro-code interfaces. Transparent LLM usage and restrictions. Simple backend integration via Rasa SDK
From past 3+ years I am using IBM Watson in our current project easily can implement and manage and monitor user how their using. Is there and update also just update dialog is just enough to change no need to touch any other templates. Multiple language will support, and action and dialog speak recognize chatbot we can create as per client requirement. Overall, as of now good experience with IBM Watson.
The clients have received additional, rather enhanced, individual conversion rates of users who interact with the virtual assistant.
Due to the introduction of automated methods of handling a majority of the calls that are made, many call center agents are thus left to handle only complicated cases.
According to a more advanced understanding of patterns, the assistant has been critical in suggesting solutions and thus drove optional revenue management.