Amazon Lex vs. Rasa

If you wish to quickly deploy multilingual chatbots without having to worry about infrastructure and model training, go for Amazon Lex. It is one of the best general-purpose conversational AI solutions in the market. The cherry on the cake is that it also seamlessly integrates with other AWS services, so you would be good there. Performance monitoring is very easy with AWS. It has support for both text and integration. If you are not a pro-NLP expert, Amazon Lex will make your job really easy.

Incentivized

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.

Incentivized

• Rasa team has Top notch AI knowledge
• Greate customer support, by listening towards the clients needs.
• And building future proof solutions around client Business Requirements within dazzling timeframes

Incentivized

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

Incentivized

Easy to deploy and very easy to integrate with other AWS services. Automating simple tasks is also very easy with Amazon Lex. We never had NLP experts in our team, but we were still able to deploy chatbots for our support functions with minimal issues. Native integration with other AWS services like S3 and Lambda has been of paramount importance.

Incentivized

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.

Incentivized

Community support for Amazon Lex is good. Also, since it is an AWS service, the support has a similar standard as other AWS services. We have had a couple of instances of our bots weren't able to interact with our web apps. We reached out to the support team, and they were able to resolve our issue in no time. The documentation from the Amazon Lex team also makes creating chatbots a breeze.

Incentivized

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

Incentivized

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

Incentivized

• Support satisfaction has increased
• Time to resolve customer concerns has seen a major improvement
• Amazon Lex can quickly automate repetitive simple tasks for us
• Our organization has built NLP capability without having to hire language experts/linguists
• Since the integration with AWS services is natively supported, our existing DevOps team can manage our Amazon Lex deployment

Incentivized

• Reduced Human Connected Calls Per active User
• Improved Calls disposed by Voice Agent
• Reduced call wait times

Incentivized