mirror of
https://github.com/hexastack/hexabot
synced 2025-06-26 18:27:28 +00:00
GITBOOK-101: update: block form screenshots
This commit is contained in:
Chedli Ben Yaghlane
committed by
gitbook-bot
gitbook-bot
parent
a4c8eda6da
commit
eff83c6c22
@@ -24,166 +24,166 @@ Pa**ssword :** adminadmin
|
||||
|
||||
#### 1. Go to Hexabot visual editor page. This is your main workspace where you can build your chatbot conversation flow. In this tutorial, we will design a chatbot that can answer question about a company return policy.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 2. Click 'Simple Text' to insert a new block in your workspace.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 3. Double-click on a block to begin making changes
|
||||
|
||||
|
||||
|
||||
|
||||
#### 4. Add a descriptive block title relevant to this step in the flow.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 5. Toggle the switch to set this block as a starting step in the conversation.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 6. You can trigger blocks based on custom conditions. Click 'Add Pattern' to create a new trigger.
|
||||
#### 6. You can trigger blocks based on custom conditions. Click 'NEW TRIGGER' to create a new one.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 7. Select 'NLU' from the dropdown to create a condition based on natural language understanding.
|
||||
#### 7. Select 'Intent Match' from the dropdown to create a condition based on natural language understanding.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 8. NLU triggers can detect the user's intent, even if the message is in different words or forms.
|
||||
#### 8. Intent Match triggers can detect the user's intent, even if the message is in different words or forms.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 9. Let's start by adding a greeting intent as a trigger, since this is the beginning of our conversation. You can also combine multiple triggers for more complex scenarios.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 10. Click to select the intent 'greetings\_hello' from the list.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 11. Go to the 'Message' tab to configure responses.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 12. Expand this section to view the replacement tokens.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 13. Select the first name replacement token
|
||||
|
||||
|
||||
|
||||
|
||||
#### 14. Copy the token
|
||||
|
||||
|
||||
|
||||
|
||||
#### 15. To customize the reply message, edit the response to 'Hi {context.user.first\_name} !'
|
||||
|
||||
|
||||
|
||||
|
||||
#### 16. Hit the submit button to save the block setup
|
||||
|
||||
|
||||
|
||||
|
||||
#### 17. To test your conversation flow, open the chat widget launcher.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 18. Type any form of greeting to trigger a reply from the chatbot.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 19. Return to the blocks library and add a Quick Reply block to your flow.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 20. Double-click on the block to customize it.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 21. Let's modify the trigger to use natural language understanding (NLU) instead of basic keyword matching.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### 23. We've previously created a new intent in our NLU provider, specifically designed to identify when a user inquires about our return policy. If you want to use this intent or define a new one in your own chatbot, you'll need to train Hexabot's NLU engine. Learn more about this feature in the [nlu-training.md](../user-guide/nlu-training.md "mention") guide:
|
||||
|
||||
|
||||
|
||||
|
||||
#### 24. Set this block as the starting point. Multiple blocks can serve as entry points in your flow.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 25. Go to the 'Message' tab to configure responses for this block.
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
#### 26. Customize the response message by replacing the default content.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 27. Add quick replies. Each reply will be an option the user can click instead of typing.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### 30. Save your changes, then link the blocks together
|
||||
|
||||
|
||||
|
||||
|
||||
#### 31. Try out the new block by asking a question about the return policy in the chat widget.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### 33. Depending on the user's response, we'll provide different answers. Let's add a new block to continue building our flow
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### 35. Let's name this block Return Eligibility
|
||||
|
||||
|
||||
|
||||
|
||||
#### 36. Go to triggers tab
|
||||
|
||||
|
||||
|
||||
|
||||
#### 37. Our keyword trigger should match the option we added in the quick replies block
|
||||
|
||||
|
||||
|
||||
|
||||
#### 38. Click on "Message".
|
||||
|
||||
|
||||
|
||||
|
||||
#### 39. And provide the appropriate message or messages
|
||||
|
||||
|
||||
|
||||
|
||||
#### 40. Save and connect the block to the Quick Replies block to continue the conversation flow.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 41. Go back to the chat widget
|
||||
|
||||
|
||||
|
||||
|
||||
#### 42. Click on "Return Eligibility".
|
||||
|
||||
|
||||
|
||||
|
||||
#### 43. 🎉 By following this flow, the user was able to receive accurate information about return eligibility from the chatbot.
|
||||
|
||||
|
||||
|
||||
|
||||
#### 44. You can add more blocks to cover the other options like "Refund Timeframe" and "Other" by creating connecting a new block and repeating the same steps
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user