DialogFlow-改进字母数字参数的实体/参数识别 [英] DialogFlow - Improve entity/parameter recognition for alphanumeric parameters

查看:72
本文介绍了DialogFlow-改进字母数字参数的实体/参数识别的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试创建一个DialogFlow意图,该意图将要求用户提供帐户代码。帐户代码为字母数字,最多10个字符。我最初使用 @ sys.any 参数设置我的意图,该参数确实收集输入。但是,通过语音识别,它不是一个单词,因此很难解决。例如,如果我说帐户代码X36501被解释为 x3650一个。

I'm trying to create a DialogFlow intent that will ask the user for an account code. Account codes are alphanumeric and can be up to 10 characters. I originally setup my intent with a @sys.any parameter which does collect the input. However with voice recognition it struggles as it's not a word as such. For example if I say the account code X36501 it gets interpreted as 'x3650 one'.

我想我可以做的是创建一个名为accountCode的实体,其中包含条目列表(关闭同义词),例如:

What I thought I could do is create an entity called accountCode with a list of entries (synonyms turned off) for example :

X36501
ZZZZ01
ABC100

然后我将intent参数从 @ sys.any 更改为 @accountCode 。我希望它会根据识别结果选择最接近的值。但是,现在它根本无法填充参数值。

I then changed the intent parameter from @sys.any to @accountCode. I was hoping it would select the nearest value it could match based on the recognition. However it now fails to fill the parameter value at all.

还有其他方法可以实现吗?定义引导语音识别的模式/正则表达式的任何方式?

Is there any other way to achieve this? Any way of defining a pattern/regular expression for guiding the voice recognition?

推荐答案

在设计会话体验时,它被认为是最佳做法避免强迫用户输入不容易大声读出的代码,数字和其他类型的数据。识别错误的可能性很高,这会增加用户的沮丧感。

When designing conversational experiences, it's considered best practice to avoid forcing users to enter codes, numbers and other types of data that are not easy to read out loud. The chance of recognition error is high, which increases user frustration.

这更多地限制了我们的说话能力,因为即使与其他人交流时,这仍然是一个问题。回想上一次您必须通过电话读出一个长号的时间。

This is not a limitation of the technology; it's more of a limitation of our ability to speak, since it remains a problem even when communicating with other humans. Think back to the last time you had to read out a long number over the phone.

在继续之前,您应该考虑是否存在另一种识别帐户的方法。还有其他识别数据会让用户更容易说话吗?

Before moving forward, you should consider whether there is another way to identify an account. Is there any other identifying data that would be easier for a user to speak?

如果真的没有其他选择,您可以考虑一个一个地收集数字,意识到对于您的用户而言,这将是一个痛苦的体验。

If there is truly no alternative, you could consider collecting the digits one by one, conscious that this is going to be a painful experience for your users.

这篇关于DialogFlow-改进字母数字参数的实体/参数识别的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆