Hello RASA Community, I’m currently working on the design of our chatbot and a few questions regarding the handling of buttons came up, which I would like to discuss here. Maybe the thread will help one or the other. Namely, my consideration is to control most of the conversation/responses of the users via buttons, as this has the advantage that the intent is reliably recognized and the user talks about things the chatbot has been trained to do. Here are my questions: Can I implement it so that the payload of each button has the /intent_value as its payload? Accordingly, I assume that the NLU would then skip the evaluation and simply predict the intent, is that correct? If the answer format for a question is a button, is training still needed for the chatbot to know which intent is meant? Or can I also use this to reduce the training and thus the size of the model? If only buttons are allowed in the whole conversation “menu bot”, would RASA be a good choice at all or should I use a framework that doesn’t use training at all to keep it slim? Is it somehow possible to disable the free response format, i.e. the text field where responses are entered, so that the user is “forced” to respond with a button? I look really forward to hear your answers and appreciate every input! Thank you!

@LindaA Can I implement it so that the payload of each button has the /intent_value as its payload? Accordingly, I assume that the NLU would then skip the evaluation and simply predict the intent, is that correct? Yes, you can mention the intent, for example: responses: utter_greet: - text: "Hey! How are you?" buttons: - title: "great" payload: "/mood_great" - title: "super sad" payload: "/mood_sad" And you need to write the story for the same. If the answer format for a question is a button, is training still needed for the chatbot to know which intent is meant? Or can I also use this to reduce the training and thus the size of the model? Yes, you need to train the bot, as intent will be trigger based on story and conversation flow. If only buttons are allowed in the whole conversation “menu bot”, would RASA be a good choice at all or should I use a framework that doesn’t use training at all to keep it slim? Well, that depends on your requirement and use-case. Normally, we consider both Text and Button approach, other wise user is bound to answer based on buttons. Is it somehow possible to disable the free response format, i.e. the text field where responses are entered, so that the user is “forced” to respond with a button? Yes, you can do it but its much depends on your front end. I hope this will help you.

RASA and Conversational Flow with Buttons

Rasa Open Source

nik202 (NiK202) January 27, 2022, 2:51pm 7

@LindaA

I don’t think so, it much overload.

@LindaA Can you please see this blog post: How to Build Your First Rasa Form | The Rasa Blog | Rasa

Please see the concept of button, slots, from_intent using Form (Rasa 2.X).

Good Luck!

Topic		Replies	Views
Bot controlled by buttons only Rasa Open Source	2	195	October 30, 2023
Rasa buttons error Rasa Open Source	2	444	October 4, 2021
Rasa Button Payload and User Response Rasa Open Source	10	12096	January 4, 2021
Rasa buttons Rasa Open Source	2	659	December 13, 2019
Change intent during conversation [Deprecated] Rasa X Community Edition	7	1183	June 16, 2020

RASA and Conversational Flow with Buttons

Related topics