Building a helpdesk chatbot with the Rasa ecosystem
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.
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
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 Support
| Pros | Cons |
|---|---|
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
| Pros | Cons |
|---|---|
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
Please log in to join the conversation