Assigned
Status Update
Comments
va...@google.com <va...@google.com>
nr...@google.com <nr...@google.com> #2
nr...@google.com <nr...@google.com> #3
I also have the same problem:
Project id: restaurant-phone-reservat-b9tt
Location: us-east1
Please have a look, this is a blocker for us.
Thank you!
Project id: restaurant-phone-reservat-b9tt
Location: us-east1
Please have a look, this is a blocker for us.
Thank you!
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Hello everyone,
We've notice an issue happening with the fallback intents.
The fallbacks intents are not being triggered.
Below is explained in more detail the problem.
Do you know why is this happening and how can we correct this? The problem also happens with other regular expressions.
I've attached some images to help the understanding of the problem.
The images 1 and 2 refer to the structure of the chatbot.
1- The main menu has its own fallback intent.
Main menu intent: 2.UserInformEmail
Main menu fallback intent: 2.UserInformEmail – fallback
* This fallback will be activated if the user says something that is not listed in the options.
2- Password reset flow:
Intent that collects the user ID: Reset de senha
Fallback intent for collecting the ID: Reset de senha – fallback
In this fallback intent, it should be triggered whenever a user writes something that is not matching the regex: ([bB][pP]){0,1}\d{5,8}
However, what is happening is that if we write the ID "BP123" or "BP123456789", with more or fewer characters than accepted in the regex, it is not going to the ID collection fallback. It is going directly to the main menu fallback.
So the problem is: The fallback for collecting the ID is not being activated.
We would appreciate your response as soon as possible.
Thanks in advance.