Input Collector user input control
Summarize
Summary of Input Collector user input control
The Input Collector control is designed to gather user data for use by ServiceNow Otto in conversations leveraging large language model (LLM) topic discovery. It enables the collection and management of multiple user inputs during conversational flows, enhancing interaction quality and data accuracy.
Show less
Key Features
- LLM Integration: The Input Collector is exclusively available for topics that use LLM discovery, enabling advanced conversational data gathering.
- Input Capacity and Management: Supports up to 5 LLM user inputs per Input Collector node, excluding other Input Collector nodes. To collect more than 5 inputs, multiple Input Collector nodes can be chained, or the system property
com.glide.cs.vainputcollectormaxnodescan be adjusted. - Node Reordering and Organization: Users can reorder, add, remove, or move input nodes within or between Input Collectors using either canvas drag-and-drop or table view controls, providing flexibility in designing conversation flows.
- Flow Action Properties:
- Node Name: Identifies the node within the topic flow.
- Advanced Instructions for LLM: Allows customization of prompts with additional instructions, data formats, restrictions, default values, scripts, or conditions.
- Confirmation Message: Optionally displays a summary of collected inputs at the conversation's end, letting users confirm or restart input collection. This feature is enabled by default.
- Conditional Display and Skipping: Nodes can be conditionally shown or skipped based on no-code conditions or low-code scripts, configurable via a condition builder or scripting.
Channel Support
The Input Collector control’s availability varies across communication channels, particularly regarding LLM and NLU/keyword support:
| Channel | LLM Support | NLU/Keyword Support | Constraints |
|---|---|---|---|
| Web UI | Not supported | Supported | None |
| Mobile UI | Not supported | Supported | None |
| ServiceNow Otto panel | Not supported | Supported | None |
| Microsoft Teams | Supported | Supported | None |
| Slack | Not supported | Not supported | Not applicable |
| Workplace | Not supported | Not supported | Not applicable |
| Facebook Messenger | Not supported | Not supported | Not applicable |
| SMS Twilio | Supported | Not supported | Not applicable |
| LINE | Not supported | Not supported | Not applicable |
| WhatsApp (powered by Twilio) | Supported | Not supported | Not applicable |
| Not supported | Not supported | Not applicable | |
| Apple Messages for Business | Not supported | Not supported | Not applicable |
| Alexa (Voice) | Not supported | Not supported | Not applicable |
Practical Use
ServiceNow customers can utilize the Input Collector to create interactive, multi-input conversational flows powered by LLMs, primarily on supported channels such as Microsoft Teams, SMS Twilio, and WhatsApp (Twilio). Adjustable properties and conditional logic allow tailoring the user experience and input validation, while the confirmation feature ensures data accuracy by letting users verify their entries before proceeding.
Use the Input Collector control to gather data for use by ServiceNow Otto in conversations that use large language model (LLM) topic discovery.
Example
For a demonstration of the Input Collector from a user perspective, watch this video.
Input Collector properties
The Input Collector is only available for topics that use LLM discovery.
The Input Collector can hold up to 5 of any of the LLM user inputs aside from another Input Collector. To collect more than 5 user inputs, place multiple Input Collector nodes in sequence or adjust the Value of the com.glide.cs.va_input_collector_max_nodes property in the System Properties [sys_properties] table.
You can reorder nodes inside the Input Collector in both canvas and table views. On the canvas, select a given node inside the Input Collector and drag it up or down in the list. You can add or remove nodes, or move them between multiple Input Collectors. Select a node and drag it into or out of an Input Collector node on the canvas. In the table view, select a given node in the list, then select the up or down arrow next to the node.
Specify the flow action properties for the node that you want to create.
| Property | Description |
|---|---|
| Node name |
Name that identifies this node in the topic flow. |
| Advanced | |
| 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. |
| Confirmation message |
Toggle switch to display a summary of collected inputs to the user at the end of a conversation. If Summary message is activated, the Virtual Agent (when activated) presents the information that you have entered and asks if everything is correct. Select Yes to continue the chat or No
to restart collecting user input. You can also reply by typing a response in the chat window, to confirm or deny the summary or to change your answer. This option is active by default, and shows an enabled icon |
| 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. |
Example Input Collector capability
Input Collector canvas view
Input Collector table view
Channel support
| Channel | LLM support | NLU/keyword support | Constraints |
|---|---|---|---|
| Web UI | Not supported | Supported | None |
| Mobile UI | Not supported | Supported | None |
| ServiceNow Otto panel | Not supported | Supported | None |
| Microsoft Teams | Supported | Supported | None |
| Slack | Not supported | Not supported | Not applicable |
| Workplace | Not supported | Not supported | Not applicable |
| Facebook Messenger | Not supported | Not supported | Not applicable |
| SMS Twilio | Supported | Not supported | Not applicable |
| LINE | Not supported | Not supported | Not applicable |
| WhatsApp (powered by Twilio) | Supported | Not supported | Not applicable |
| Not supported | Not supported | Not applicable | |
| Apple Messages for Business | Not supported | Not supported | Not applicable |
| Alexa (Voice) | Not supported | Not supported | Not applicable |