VoiceBot RASA Setup

In this documentation you find information on how to configure your RASA agent, including step-by-step instructions for setting up the required settings.

Settings on RASA platform

Start intent

In the VoiceBot block, a start intent must be defined which is called “tenios_start”. Example:

rules.yml:

rules: - rule: Tenios start rule steps: - intent: tenios_start - action: utter_start

domain.yml:

responses: utter_start: - text: "Hello, how can I help you?"

For your bot to function correctly, you should most likely define a fallback mechanism in RASA. There are multiple ways to achieve this, but one of the simplest ones might be to define an intent that is called “nlu_fallback” (see Fallback and Human Handoff )

rules.yml:

rules: - rule: Ask the user to rephrase whenever they send a message with low NLU confidence steps: - intent: nlu_fallback - action: utter_please_rephrase

responses: utter_please_rephrase: - text: I'm sorry, I didn't quite understand that. Could you rephrase?

In order to end a conversation and exit the VoiceBot block, it is necessary to define an endpoint. Therefor you can either make RASA return an empty response text or you can use a custom output payload:   domain.yml:

responses: utter_goodbye: - text: "Have a nice day" custom: end_of_conversation: true

The advantage of using a custom payload is, that in this case, the output text “Have a nice day” will be played before exiting the VoiceBot block.

Action mappings (optional)

If you want our Number Routing to perform certain actions (e.g. forwarding to a number, playing an announcement, …), depending on your RASA bot, you can achieve this with output mappings. Example:

domain.yml:

responses: utter_support_rep: - text: "One moment please, we will forward you to our support staff" custom: output_action: "fwd_support"