How to create dialogflow conversation to make a price estimation
up vote
0
down vote
favorite
My agent’s goal is to ask 6 questions to make a price estimation of 2 different products.
It asks the 1st question: ‘do you want to make a price estimation for product1 or product2 ?’
And then, it asks 5 questions about the product’s characteristics (i.e. the product’s age, size…) to finally display the price estimation.
All flow made on Dialogflow UI with an inline editor for the fulfillment to calculate and then save data on Firebase DB.
My question -> Is it better to create :
1/ Create only 2 intents : product1 and product2 ? Then in those intents, ask the others 5 questions in ‘action and parameters’ section by filling parameters, entities and values.
2/ Create 6 differents intents for the 6 questions, with parameter value for each ones.
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.
- 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. 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 ;)
node.js dialogflow
New contributor
add a comment |
up vote
0
down vote
favorite
My agent’s goal is to ask 6 questions to make a price estimation of 2 different products.
It asks the 1st question: ‘do you want to make a price estimation for product1 or product2 ?’
And then, it asks 5 questions about the product’s characteristics (i.e. the product’s age, size…) to finally display the price estimation.
All flow made on Dialogflow UI with an inline editor for the fulfillment to calculate and then save data on Firebase DB.
My question -> Is it better to create :
1/ Create only 2 intents : product1 and product2 ? Then in those intents, ask the others 5 questions in ‘action and parameters’ section by filling parameters, entities and values.
2/ Create 6 differents intents for the 6 questions, with parameter value for each ones.
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.
- 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. 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 ;)
node.js dialogflow
New contributor
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My agent’s goal is to ask 6 questions to make a price estimation of 2 different products.
It asks the 1st question: ‘do you want to make a price estimation for product1 or product2 ?’
And then, it asks 5 questions about the product’s characteristics (i.e. the product’s age, size…) to finally display the price estimation.
All flow made on Dialogflow UI with an inline editor for the fulfillment to calculate and then save data on Firebase DB.
My question -> Is it better to create :
1/ Create only 2 intents : product1 and product2 ? Then in those intents, ask the others 5 questions in ‘action and parameters’ section by filling parameters, entities and values.
2/ Create 6 differents intents for the 6 questions, with parameter value for each ones.
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.
- 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. 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 ;)
node.js dialogflow
New contributor
My agent’s goal is to ask 6 questions to make a price estimation of 2 different products.
It asks the 1st question: ‘do you want to make a price estimation for product1 or product2 ?’
And then, it asks 5 questions about the product’s characteristics (i.e. the product’s age, size…) to finally display the price estimation.
All flow made on Dialogflow UI with an inline editor for the fulfillment to calculate and then save data on Firebase DB.
My question -> Is it better to create :
1/ Create only 2 intents : product1 and product2 ? Then in those intents, ask the others 5 questions in ‘action and parameters’ section by filling parameters, entities and values.
2/ Create 6 differents intents for the 6 questions, with parameter value for each ones.
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.
- 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. 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 ;)
node.js dialogflow
node.js dialogflow
New contributor
New contributor
edited Nov 10 at 11:28
lgwilliams
129211
129211
New contributor
asked Nov 10 at 10:46
Fab_
11
11
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Remember that Intents are designed to capture what the user is saying - not necessarily the logic behind how you intend to handle that. While you can use things like Contexts to keep track of state, it is sometimes better to handle that with your logic. (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.
Thx, you have confirmed my believe. I made it with differents intents and retrieve all parameters to save them on Firebase RealTime Database.
– Fab_
5 hours ago
Storing it in the Real-time database also makes sense, as long as you're associating the information with the same user or session. If my answer has helped, upvoting and/or accepting it is always appreciated.
– Prisoner
16 mins ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Remember that Intents are designed to capture what the user is saying - not necessarily the logic behind how you intend to handle that. While you can use things like Contexts to keep track of state, it is sometimes better to handle that with your logic. (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.
Thx, you have confirmed my believe. I made it with differents intents and retrieve all parameters to save them on Firebase RealTime Database.
– Fab_
5 hours ago
Storing it in the Real-time database also makes sense, as long as you're associating the information with the same user or session. If my answer has helped, upvoting and/or accepting it is always appreciated.
– Prisoner
16 mins ago
add a comment |
up vote
0
down vote
Remember that Intents are designed to capture what the user is saying - not necessarily the logic behind how you intend to handle that. While you can use things like Contexts to keep track of state, it is sometimes better to handle that with your logic. (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.
Thx, you have confirmed my believe. I made it with differents intents and retrieve all parameters to save them on Firebase RealTime Database.
– Fab_
5 hours ago
Storing it in the Real-time database also makes sense, as long as you're associating the information with the same user or session. If my answer has helped, upvoting and/or accepting it is always appreciated.
– Prisoner
16 mins ago
add a comment |
up vote
0
down vote
up vote
0
down vote
Remember that Intents are designed to capture what the user is saying - not necessarily the logic behind how you intend to handle that. While you can use things like Contexts to keep track of state, it is sometimes better to handle that with your logic. (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.
Remember that Intents are designed to capture what the user is saying - not necessarily the logic behind how you intend to handle that. While you can use things like Contexts to keep track of state, it is sometimes better to handle that with your logic. (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.
answered Nov 10 at 15:04
Prisoner
29.3k12551
29.3k12551
Thx, you have confirmed my believe. I made it with differents intents and retrieve all parameters to save them on Firebase RealTime Database.
– Fab_
5 hours ago
Storing it in the Real-time database also makes sense, as long as you're associating the information with the same user or session. If my answer has helped, upvoting and/or accepting it is always appreciated.
– Prisoner
16 mins ago
add a comment |
Thx, you have confirmed my believe. I made it with differents intents and retrieve all parameters to save them on Firebase RealTime Database.
– Fab_
5 hours ago
Storing it in the Real-time database also makes sense, as long as you're associating the information with the same user or session. If my answer has helped, upvoting and/or accepting it is always appreciated.
– Prisoner
16 mins ago
Thx, you have confirmed my believe. I made it with differents intents and retrieve all parameters to save them on Firebase RealTime Database.
– Fab_
5 hours ago
Thx, you have confirmed my believe. I made it with differents intents and retrieve all parameters to save them on Firebase RealTime Database.
– Fab_
5 hours ago
Storing it in the Real-time database also makes sense, as long as you're associating the information with the same user or session. If my answer has helped, upvoting and/or accepting it is always appreciated.
– Prisoner
16 mins ago
Storing it in the Real-time database also makes sense, as long as you're associating the information with the same user or session. If my answer has helped, upvoting and/or accepting it is always appreciated.
– Prisoner
16 mins ago
add a comment |
Fab_ is a new contributor. Be nice, and check out our Code of Conduct.
Fab_ is a new contributor. Be nice, and check out our Code of Conduct.
Fab_ is a new contributor. Be nice, and check out our Code of Conduct.
Fab_ is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53238161%2fhow-to-create-dialogflow-conversation-to-make-a-price-estimation%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password