action_default_fallback" ^ This look to be the default code to make the action work…?
You don’t need to overwrite this to make the fallback work. This is the name of the action which is triggered when all user affirmations failed.
^ Unsure what this does…?
This distinguishes between a core fallback and nlu fallback (The TwoStageFallback-Policy can only ask for affirmation in case of NLU fallbacks, in case something went wrong in the flow, it directly triggers fallback_core_action_name. You can avoid the manual distinction by specifying different actions for fallback_core_action_name and fallback_nlu_action_name in your policy config (Policies) .
^ after passing the if conditions of the above code it will show a set of buttons? Unsure why the feedback value is set to negative though… and would it help improve the chatbot to have a feedback value.
In case the affirmations by the user didn’t help to resolve the ambiguous intent, it will show buttons to the user. We are asking if they want to restart the conversation and if they have feedback for the bot (thumbs up, thumps down buttons).
^ If none of the conditions in the if statement is passed, the bot will return a default error utterance…?
In case something went wrong in the dialog flow, we utter a message (check the domain for that) and revert everything including the latest user message (you could also do a Restarted here).
Does that make sense?