User Says

In this tutorial you will learn about the User Says Node, what it does and how to use and its Settings

1. What it does

User Says node contains the conditions or rules or user utterances which are checked after a request is recieved from a particular Channel.
Based upon conditions or utterances provided inside the User Says, the incoming request from Channels like Alexa is passed internally to this User Says node via Router Node.

  • In Basic Conversation Mode:
    Settings provided in User Says node are used to create Interaction Model for Channels like Alexa

2. How to use

  • In Basic Conversation Mode

    • Input port of User Says node is open and can take input directly from the previously connected node.
    • You can also use the User Says node just after the Respond Node, to handle the incomming request.
  • In Advanced Conversation Mode

    • Input port of User Says node is close and can not take input directly from the previously connected node.
    • In this mode, User Says node can only be used as the Entry points for you dialog flow.

3. Node Setting

  • In Basic Conversation Mode
    • Name
      Name of node
    • User Says
      • Always use the Launch or Welcome as the entry point when user invokes your skill.
      • We have already defined some frequently used utterance used by user, like Yes, No. Use them, when you expects user might say/ask one of the above.
      • Use Utterances, when you expects user might say something different or unique.
        Note: Caution while using Utterances, do not use same types of utterances for any other User Say Node, this might cause NLU model to send request to unwanted User Say node.
        Note: Use Launch or Welcome, Help, Cancel, Stop, Exit, Unhandled only one time as entry points in your Flow, like below
    • User Utterances
      • When you select User Says as Utterance you need to provide the some user utterances (at least three and at most 20).
      • Utterances should only contains the alphabets and should not contain any special character except white spaces.
      • Utterances should be unique to a partiular User Says node.
      • When using Yes, No, Help, Cancel, Stop, ofcourse you can provide some user utterance, but for these it is not necessary.
  • In Advanced Conversation Mode

    • Name
      Name of node
    • Property
      • Defines type and property of the property on which conditions/rules will be checked. This property is just like left side of the comparison operators.
      • You can select a type msg., flow. and global. from the dropdown and on text field you need to put the property.
      • For most of the time you need to use type msg. and property NLU.intent.name to match the intent of incoming request from different Channels.
    • Rules/Conditions
      • Defined the value to be matched. These are like right side of comparison operator.
      • Here you must define atleast one rule/condition in order to match with property field.
      • You can also select different comparison operators from the select box.
      • Click on Add new rule button to add more rules/conditions.

        Note: In order to handle the incoming request Intent, Rules values must be same as the Intent Names used in the Intent Schema of Alexa-in Node, suppose if we have defined the FoodOrderIntent in the Intent Schema of Alexa-in Node, then only we can add the Rules value as FoodOrderIntent
        Note: Caution while using Rules, do not use same types of rules/condition for any other User Say Node, this might cause NLU model to send request to unwanted User Say node.
        Note: Use LAUNCH, AMAZON.Help, AMAZON.Cancel, AMAZON.Stop, EXIT, UNHANDLED only one time as entry points in your Flow, like below



    Always use the LAUNCH as the entry point when user invokes your skill.
    We have already defined some frequently used utterance used by user, like Yes, No. Use them, when you expects user might say/ask one of the above.
    Use Utterances, when you expects user might say something different or unique.
    Note: Caution while using Utterances, do not use same types of utterances for any other User Say Node, this might cause NLU model to send request to unwanted User Say node.
    Note: Use Launch or Welcome, Help, Cancel, Stop, Exit, Unhandled, only one time as entry points in your Flow, like below

    - User Utterances
    When you select User Says as Utterance you need to provide the some user utterances (at least three and at most 20). Utterances should only contains the alphabets and should not contain any special character except white spaces. Utterances should be unique to a partiular User Says node.
    When using Yes, No, Help, Cancel, Stop, ofcourse you can provide some utterance, but for these it is not necessary to provide user utterances

4. Input

  • In Advanced Conversation Mode
    This node can take input directly from other nodes

  • In Advanced Conversation Mode
    This node can’t take input directly from other nodes.

5. Output

Passes the msg object to next connected node