Date Time user input control
Use the Date Time user input control in a Virtual Agent topic to enable the user to select a calendar date, time (hours and minutes), or both.
Date Time user input control properties for LLM topic discovery
The Date Time user input control accepts inputs from a calendar selection, or by entering plain language in the Virtual Agent chat window. If you type your answer, the Virtual Agent accepts different inputs depending on how your region handles dates. For example, if you're in the United States, the input control supports the MM-DD-YYYY format, while a user in Spain enters the date in DD-MM-YYYY format.
| Date Time property | Description | |
|---|---|---|
| Name | Name that identifies this node in the topic flow. | |
| Variable Name | Name of the variable that stores the user response to this prompt. The variable name is automatically created from the Node name property. | |
| Allow automatic slot-filling | Toggle to allow this node’s value to be automatically set by other nodes, as well as during topic discovery. When this toggle is activated, the Detail description field changes from dynamic Data Pill Picker and script options to a static text field. | |
| Detail description | Description of the information that you need from users. If the Allow automatic slot filling toggle is deactivated, you can create a dynamic detail description by selecting the Data Pill Picker icon Image omitted: variable-reference-picker.png to define conditions, or select the Open Editor icon [Omitted image "icon-script.png"] Alt text: to enter a script. If the <strong>Allow automatic slot filling</strong> toggle is activated, you can only enter a static description.</p> Image omitted: LLM-input-discoverable-toggle.png Input formatWhen the Allow automatic slot-filling toggle is inactive, the detail description includes Data Pill Picker and script dynamic options. When the toggle is active, the Detail description field becomes static.</p></td></tr><tr><td> | Type of Date Time control to be displayed. Select one of the following formats:
|
| Advanced | ||
| Enforce user prompt | Toggle to open a field for a custom message shown to the user instead of the message generated by the large language model \(LLM\). You can create custom messages in plain language, input a script, or define conditions with the data pill picker. | |
| Validation | Add a script to validate the user input. For example, check if the user entered a valid email address. | |
| Additional instructions for LLM | Further instructions to the LLM, such as adding data formats, restrictions, or default values for user responses. You can create additional instructions in plain language, input a script, or define conditions with the data pill picker. | |
| Hide or skip this node | ||
| Conditionally show this node if | No-code condition statement or low-code script that specifies a condition for presenting this node in the conversation. The condition must evaluate to true. | |
| Allow user to skip this node if | No-code condition statement or low-code script that specifies a condition for letting users skip this node in the conversation. The condition must evaluate to true. You can set this field using either the condition builder or a script. If users enter a value such as `skip this step` when the conditions do not allow skipping, they receive a message saying the node cannot be skipped and are re-prompted to provide an answer. | |
Example Date Time user input control for LLM topic discovery
Note: Virtual Agent Designer controls may display and function differently in other channels.
| Input properties | Date Time prompt |
|---|---|
Image omitted: va-date-time-llm-3.png All basic Date Time user input fields are openly available. Select any of the advanced options to toggle them open individually. | Image omitted: va-datetime-native.png In the Web client, a calendar pop-up lets the user choose a date and time. |
Date Time user input control properties for NLU topic discovery
| Date Time property | Description |
|---|---|
| Name | Name that identifies this node in the topic flow. |
| Variable Name | Name of the variable that stores the user response to this prompt. The variable name is automatically created from the Node name property. |
| Prompt | Prompt or question for the user. The prompt can be either a text string or a script that returns text. This value is used only when the default value is not specified. For example: `What's your name?` |
| NLU entity\[NLU topic discovery only\] | Option to associate an NLU entity with the node. If an NLU entity is associated with the input variable for this node, Virtual Agent can slot-fill the specified value based on the user's utterance. Select an entity from the list of entities associated with the topic intent. When you specify an entity for the node, the Do not ask users to confirm recognized entity toggle switch is displayed. When enabled, users are not prompted to confirm the extracted entity. |
| Input format | Type of Date Time control to be displayed. Select one of the following formats:
|
| Advanced | |
| Default value | |
| Predefine a value for user input | Predefined value for the user response to the question or prompt. The response defined in the Default value confirmation field asks the user to confirm the default value. If the user responds with no, the value becomes null. The default value can be either a text string or a script that returns text. For example, if you're using dot-walking, the default value might be: Script Variables > Last username. Or if you're using a script, the default value might be: {{vaScripts.lastUsername}}. |
| Confirmation messages | |
| Input completion confirmation | Bot response shown to the user when the node interaction is complete. The message can be either a text string or a script that returns text. For example, if you're using dot-walking: `Thanks, (Input Variables > Username)!` Or if you're using a script, the acknowledgement might be: `Thanks, {{vaInputs.username}}!` |
| Default value confirmation | Message that asks the user to verify that the value in the Default value field is correct. This message is used instead of a value in the Prompt field. It can contain either a text string or a script that returns text. For example, if you're using dot-walking: Are you (Input Variables > Username)? Or if you're using a script, the confirmation message might be: Are you {{vaScripts.lastUsername}}?. |
| Conversation switching | |
| This section is available only when NLU discovery is enabled on the instance. | |
| Turn on to let users change the subject | Option to enable NLU prediction for this 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. |
| Hide or skip this node | |
| Conditionally show this node if | No-code condition statement or low-code script that specifies a condition for presenting this node in the conversation. The condition must evaluate to true. |
| Allow user to skip this node if | No-code condition statement or low-code script that specifies a condition for letting users skip this node in the conversation. The condition must evaluate to true. You can set this field using either the condition builder or a script. |
| Skip reprompting if | No-code condition statement or low-code script that specifies a condition for letting users skip reprompting in the conversation. When a preceding node is revisited through a topic loopback or Dialog Act, the Virtual Agent bypasses this node and automatically retain its original value. |
Example Date Time user input control for NLU topic discovery
Note: Virtual Agent Designer controls may display and function differently in other channels.
| Input properties | Date Time prompt |
|---|---|
Image omitted: va-datetime-properties.png Basic properties include the node name, prompt, input format, and NLU entity. | Image omitted: va-datetime-native.png In the Web client, a calendar pop-up lets the user choose a date and time. |
Channel support
| Channel | LLM support | NLU/keyword support | Constraints |
|---|---|---|---|
| Web UI | Not Supported | Supported | None |
| Mobile UI | Not Supported | Supported | None |
| Now Assist panel | Not Supported | Supported | None |
| Microsoft Teams | Supported | Supported | None |
| Slack | Not Supported | Supported | None |
| Workplace | Not Supported | Supported | The Workplace interface does not natively support a date selection widget. Date and time selection is instead done with the buttons that are supported in these interfaces. The Date Time user input control prompts the user for a date, showing the current date and time. The user selects the month, day, year, or time button to modify that value. The time and day fields prompt the user to type in a new value. The month and year fields show a set of buttons with the current and upcoming months or years. Select one of these buttons or type in a value to set the time or year. |
| Facebook Messenger | Not Supported | Supported | If your administrator has set the option to request the time zone from the customer, the selected date and time reflect the customer's time zone. Otherwise, they appear in the UTC time zone. For more information about the time zone setting, see Set up Conversational Integration with Facebook Messenger. |
| SMS Twilio | Supported | Not supported | Not applicable |
| LINE | Not Supported | Supported | None |
| Supported | Supported | None | |
| Apple Messages for Business | Not Supported | Supported | None |
| Alexa \(Voice\) | Not Supported | Supported | For best results, enable NLU at the node. |
Parent Topic:Assistant Designer user input controls