Building a helpdesk chatbot with the Rasa ecosystem
Updated March 11, 2025

Building a helpdesk chatbot with the Rasa ecosystem

Martin Lukan | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Software Version

Rasa Enterprise

Overall Satisfaction with Rasa

Our use case involves an internal IT support helpdesk, which is served by the chatbot. We use Rasa Pro, Rasa SDK (action server) and Rasa Studio products. Our chatbot is supporting users with all hardware, software and access issues at their workplace. The hardware includes e.g. company mobile phones, laptops, printers and accessories. The software includes different applications from the internal software catalogue.

Pros

  • Provides transparent interface for dialogue management
  • Pipeline-based approach to processing messages allows easy extension and customization of message processing components.
  • Seamless integration of Rasa SDK for custom actions provides a powerful interface for integrating the chatbot with other systems for data retrieval and manipulation.
  • Rasa CALM does a very good job at restricting LLM hallucination.

Cons

  • 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.
  • 30% staff reduction on support hotline
  • >2 Mio Eur savings per year
  • Extended service hours, as chatbot is 24/7 online unlike human support.
Rasa Studio is very useful for no-code usage, but somewhat lagging behind Rasa Pro in features, which makes it hard to use it for development cycle of more complex chatbots (rating 7).

Rasa Pro and Rasa SDK provide quite transparent pro-code usage possibilities (rating 9), but there are some dependencies in the message processing, where we had to look for custom code/workarounds.
Rasa analytics could be more flexible, i.e. built without any dependency on Kafka event broker. That's why have built our own analytics, because we've had a custom SQL event broker. I'd give the Rasa ecosystem an overall rating of 8.
Yes, we have been able to customize it by using both NLU and LLM based approaches, implementing RAG using Rasa custom actions and building some custom pipeline components such as an entity extractor etc.
REST
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

Do you think Rasa delivers good value for the price?

Yes

Are you happy with Rasa's feature set?

Yes

Did Rasa live up to sales and marketing promises?

Yes

Did implementation of Rasa go as expected?

No

Would you buy Rasa again?

Yes

Rasa Pro is well suited for corporate use and for chatbots which require backend connections. Smaller chatbots with a few flows might be better served with a simple dialogue engine and custom AI agents, or Rasa Open Source. Rasa does not come with its own complex vector database, just in-memory FAISS and connectors to external vector DB's such as Milvus and Qdrant. It provides only a basic document parser and embedder for FAISS. If you need to build a RAG focused chatbot around a large knowledge base with complex documents, e.g. lots of MS Word or PDF files, you'll have to build a separate document parser and embedder, as well as your own semantic search engine.

Rasa Support

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.
ProsCons
Quick Resolution
Good followup
Knowledgeable team
Problems get solved
Kept well informed
No escalation required
Immediate help available
Support cares about my success
Quick Initial Response
None
We have chosen the licensed Rasa Pro and thus have received dedicated support. This was deemed necessary, as we rely on features not available with Rasa Open Source and we had a high stake use case.
Yes - We have reported several bugs, which were all resolved within reasonable time.
Rasa Technologies Inc provided several on-site workshops for our team, which was invaluable to get the development on track as fast as possible.

Using Rasa

ProsCons
Like to use
Relatively simple
Easy to use
Well integrated
Consistent
Quick to learn
Convenient
Feel confident using
Familiar
None
  • Build dialogue flows
  • Integrate 3rd party systems
  • RAG integration

Comments

More Reviews of Rasa