Virtual Agent Designer user input controls
-
- UpdatedAug 3, 2023
- 4 minutes to read
- Vancouver
- Virtual Agent
The Vancouver release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.
Virtual Agent Designer user input controls
Use the collection of input controls provided by Virtual Agent Designer to prompt and capture information from the user in a conversation.
Common input control properties
In addition to data pills and condition controls, each input control has the following common properties:
- Input variable for the user response
- Each control stores the user response in an input variable that is accessible from
other controls within the same topic using the
getValue
andgetDisplayValue
methods. The variable name is based on the name that you assign to the input control. For example, if you assign the name First prompt to an input control, the variable name isfirst_prompt
. The variable name is lowercase, with an underscore character instead of a space. For more information on these methods, see Virtual Agent scripts. - Natural Language Understanding (NLU) entity properties
- If NLU is enabled, the following properties are displayed in
the property sheet for the Text, Static
Choice, Dynamic Choice,
Boolean, Date Time, and
Carousel input controls. To view or enable these properties, go
to the Advanced options section.
- NLU entity: The entity that corresponds to the input variable for the control. You select the entity from the list of entities associated with the topic intent, as defined in the NLU model that you’re using for the topic. When Virtual Agent recognizes the entity value in user utterances and if the value meets the entity prediction confidence threshold, then Virtual Agent extracts the value. The value is stored in the input variable for the node. This storing action is called slot filling. Slot filling recognizes when multiple values for
the same NLU entity occur in a conversation. Users are prompted with a list to confirm which node value to select when multiple nodes are tied to the same NLU entity. This property is available only for NLU
topic discovery.
Figure 2. NLU entity property - Enable NLU to switch topics: Enables NLU prediction for the node. If enabled, users can enter
text to answer questions, regardless of the type of input control being used. Virtual Agent uses this utterance to match another existing intent,
letting the user switch topics. To enable this property on a node, navigate to .
Figure 3. Enable NLU to switch topics property
- NLU entity: The entity that corresponds to the input variable for the control. You select the entity from the list of entities associated with the topic intent, as defined in the NLU model that you’re using for the topic. When Virtual Agent recognizes the entity value in user utterances and if the value meets the entity prediction confidence threshold, then Virtual Agent extracts the value. The value is stored in the input variable for the node. This storing action is called slot filling. Slot filling recognizes when multiple values for
the same NLU entity occur in a conversation. Users are prompted with a list to confirm which node value to select when multiple nodes are tied to the same NLU entity. This property is available only for NLU
topic discovery.
- Default value
- An input prompt can have a preset value that you define. This value can be either a string or a script that returns a string. This property is in the Advanced options section.
- Confirmation messages
- These bot response messages signal the end of the node interaction and ask the users to confirm their response. This property is in the Advanced options section.