Prompt Response
Last updated
Last updated
You will be redirected to continue to stage 2 Prompt Response. A prompt response is a special type of dialog that asks for user input, confirmation for a response, and returns the response to the next step.
When conversation occurs, sometimes the user does not immediately deliver all entities and this is prompt response usability. The prompt response allows the bot to check required information from the customer has been fulfilled or not.
On the Prompt Response page, you can switch your prompt by drag and drop icon. And, to fill out the question response, click the 'Question' button ( ).
You will see a pop-up of the form question, on this form, there are several types to add a question to each entity, i.e.:
New Line is used to add questions in the different bubbles.
InLine is used to add the question entity in the same bubble.
Quick Reply can be used to add questions as a quick reply.
Media can be used to add questions using the digital library.
Here you will set the bot response to the possible questions from the users added in the previous step. For example, in the previous step, the user asks about the nearby station. In this form, you can set how the bot will respond to that question by adding the answer in the field question. Or, you may fill out with output from SDK or process flow by adding [$output$] in the field question. Then, press Enter and click on the type of question you want to use as described above.
This step is also used to confirm the suitability user's response to the bot feedback question. For example, the user asks about a nearby station. Then, the bot will continue the conversation by sending questions like 'where is your location currently?'. But, suddenly user's answer does not match the question. The bot still answers the customer's question and re-asks again the question earlier until getting a related answer.
Moreover, you may add logic to the entities by using Entity Rules. The function of entity rule is to set the entity rules using MVEL rules (java syntax). There is 3 main component of these rules there is clear, skip, and trigger (For further information, look at the explanation below). This component is optional. For example, entity==” fill in the entity”.
Component Explanation:
Clear All
To delete the contents of all entities.
Clear Current
To delete the contents of all entities the rule has been set.
Clear Variable
To delete the contents of all entities selected.
Skip Variable
To set the skip entity will not be asked by Bot.
Trigger Dialog
To call another dialog.
When you select this variable there will be another field to call another dialog. Put your objected dialog in here.
Note:
If you use this action, make sure on your objected dialog to skip the intention. To fulfill this, you must set 'entity intention to skip' by using process flow or SDK on the integration page.
Set up the entity values or you can skip it and click on the 'next' button to proceed to stage 3 Integration.
