使用 sys any 的回退意图
Fallback intent with sys any
根据下面的 Google 通信，从 1 月 15 日开始，如果您有启用 Web 钩子来处理用户输入的后备意图，则它可能无法正常工作，因为现在用户输入可能会被 Assistant 拦截交错说话。对于我的应用程序来说，即使是后备处理也很重要。我可以只使用带有 @sys.any 的意图，但这很难，因为我有多个意图。具有 sys.any 的意图的优先级是否低于其他意图？在这种情况下会发生什么？什么是最好的方法？
Dear Actions on Google Developer, We are reaching out to provide more
details regarding the Google Assistant Actions fallback intent
behavior change that we announced on October 15, including more
details on the decision and recommended steps to take with your
Actions development projects. In order to provide a better experience,
we now allow users to ask for some Assistant features, such as the
weather or time, from within your Action. To perform this function,
the Assistant detects if your Action matched a user's query with a
fallback intent or NO_MATCH intent. If that is the case, and an
appropriate response is available, Assistant responds to the user's
request. If no response is available, or Assistant doesn't understand
the query, the conversation continues within your Action. As of
October 15, 2020, this new behavior applies only if the fallback does
not use a webhook. Starting January 15th 2021, we'll start enabling
this feature for any Dialogflow fallback intent or Actions Builder
NO_MATCH intent whether or not they use a webhook. This change should
not impact the operation of your Actions, unless you are using
fallbacks as a way to collect input from your users. Going forward,
you should only use fallback intents or NO_MATCH intents as a way to
reprompt the user in the context of your Action. If you want your
Actions to attempt to capture data from a wider range of user
responses, create an intent that uses a Free form text type if you use
Actions Builder. If you use Dialogflow, add an intent with a @sys.any
type as the training phrase. We realize that this guidance for the use
of fallback intents goes against some of our prior recommendations. As
we continue to improve our understanding of how users interact with
the platform, our approach to conversational interfaces also needs to
evolve. Thanks for your continued support of the Assistant developer
platform, and for your understanding as we continue to improve the
Google Assistant user experience. Sincerely, The Actions on Google
Team
具有@sys.any 的意图并不一定意味着它们具有低优先级。每个 Intent 都有一个 Priority setting you can set. You can read more about factors that affect Intent matching in this document.
根据我的测试，使用带有 @sys.any 的顶级 Intent 来替代 Default Fallback Intent 会很困难，因为它们的工作方式不同。带有@sys.any 的 Intent 将匹配任何用户查询，而默认回退 Intent 将捕获与 Intent 不匹配的用户查询。
相反，您可以将 Intent 与 @sys.any 一起使用，但作为 Follow-up Intent 来隔离不会影响其他顶级 Intent 的对话流。
根据下面的 Google 通信，从 1 月 15 日开始，如果您有启用 Web 钩子来处理用户输入的后备意图，则它可能无法正常工作，因为现在用户输入可能会被 Assistant 拦截交错说话。对于我的应用程序来说，即使是后备处理也很重要。我可以只使用带有 @sys.any 的意图，但这很难，因为我有多个意图。具有 sys.any 的意图的优先级是否低于其他意图？在这种情况下会发生什么？什么是最好的方法？
Dear Actions on Google Developer, We are reaching out to provide more details regarding the Google Assistant Actions fallback intent behavior change that we announced on October 15, including more details on the decision and recommended steps to take with your Actions development projects. In order to provide a better experience, we now allow users to ask for some Assistant features, such as the weather or time, from within your Action. To perform this function, the Assistant detects if your Action matched a user's query with a fallback intent or NO_MATCH intent. If that is the case, and an appropriate response is available, Assistant responds to the user's request. If no response is available, or Assistant doesn't understand the query, the conversation continues within your Action. As of October 15, 2020, this new behavior applies only if the fallback does not use a webhook. Starting January 15th 2021, we'll start enabling this feature for any Dialogflow fallback intent or Actions Builder NO_MATCH intent whether or not they use a webhook. This change should not impact the operation of your Actions, unless you are using fallbacks as a way to collect input from your users. Going forward, you should only use fallback intents or NO_MATCH intents as a way to reprompt the user in the context of your Action. If you want your Actions to attempt to capture data from a wider range of user responses, create an intent that uses a Free form text type if you use Actions Builder. If you use Dialogflow, add an intent with a @sys.any type as the training phrase. We realize that this guidance for the use of fallback intents goes against some of our prior recommendations. As we continue to improve our understanding of how users interact with the platform, our approach to conversational interfaces also needs to evolve. Thanks for your continued support of the Assistant developer platform, and for your understanding as we continue to improve the Google Assistant user experience. Sincerely, The Actions on Google Team
具有@sys.any 的意图并不一定意味着它们具有低优先级。每个 Intent 都有一个 Priority setting you can set. You can read more about factors that affect Intent matching in this document.
根据我的测试，使用带有 @sys.any 的顶级 Intent 来替代 Default Fallback Intent 会很困难，因为它们的工作方式不同。带有@sys.any 的 Intent 将匹配任何用户查询，而默认回退 Intent 将捕获与 Intent 不匹配的用户查询。
相反，您可以将 Intent 与 @sys.any 一起使用，但作为 Follow-up Intent 来隔离不会影响其他顶级 Intent 的对话流。