简体   繁体   English

如何创建对话流程对话以进行价格估算

[英]How to create dialogflow conversation to make a price estimation

My agent's goal is to ask 6 questions to make a price estimation of 2 different products. 我的代理商的目标是要问6个问题,以便对2种不同的产品进行价格估算。 It asks the 1st question: 'do you want to make a price estimation for product1 or product2 ?' 它问第一个问题:“您要对product1或product2进行价格估算吗?” And then, it asks 5 questions about the product's characteristics (ie the product's age, size…) to finally display the price estimation. 然后,它询问有关产品特性的5个问题(即产品的年龄,尺寸...),以最终显示价格估算。 All flow made on Dialogflow UI with an inline editor for the fulfillment to calculate and then save data on Firebase DB. 使用内置编辑器在Dialogflow UI上进行的所有流程,以实现将其计算并保存到Firebase DB上的数据。

My question -> Is it better to create : 我的问题->创建更好吗:

1/ Create only 2 intents : product1 and product2 ? 1 / 仅创建2个意图 :product1和product2? Then in those intents, ask the others 5 questions in 'action and parameters' section by filling parameters, entities and values. 然后,根据这些意图,通过填充参数,实体和值,在“动作和参数”部分中向其他5个问题提问。

2/ Create 6 differents intents for the 6 questions, with parameter value for each ones. 2 /为6个问题创建6个不同的意图 ,并为每个问题设置参数值。

On my side : 在我这一边:

  • I have tested the 1/, I'm able to retrieve all data on my Firebase DB but my 2 products have similar entities and parameters values ('size' for example) and my agent make errors' flow to the wrong intent. 我已经测试过1 /,可以在Firebase DB上检索所有数据,但是我的2个产品具有相似的实体和参数值 (例如'size'),并且我的代理使错误流向了错误的意图。
  • I have tested the 2/ (I think it's the better way because all intents are more efficient) I'm able to make the good flow. 我已经测试了2 /(我认为这是更好的方法,因为所有意图都更有效),我能够使流程顺畅。 But at the last question, I don't know how to retrieve previous parameters values to make the price estimation. 但是,在最后一个问题上,我不知道如何检索先前的参数值以进行价格估算。

Thanks a lot for the help ;) 非常感谢您的帮助 ;)

Remember that Intents are designed to capture what the user is saying - not necessarily the logic behind how you intend to handle that. 请记住,Intent旨在捕获用户在说什么-不一定是您打算如何处理它的逻辑。 While you can use things like Contexts to keep track of state, it is sometimes better to handle that with your logic. 尽管可以使用诸如Context之类的东西来跟踪状态,但有时最好使用逻辑来处理。 (See Thinking for Voice: Design Conversations not Logic ) (请参阅思考语音:设计对话而非逻辑

You should be storing anything you wish to remember between Intents in the parameters of a long-lived Context . 您应该在长期Context的参数中的Intent之间存储要记住的所有内容。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM