Input Collector user input control

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Input Collector user input control

    The Input Collector control is designed to gather user data for use by ServiceNow Otto during conversations that utilize large language model (LLM) topic discovery. It enables the collection and management of multiple user inputs within topic flows that employ LLM discovery capabilities.

    Show full answer Show less

    Input Collector Properties and Usage

    • The Input Collector is exclusively available for topics using LLM discovery.
    • It can hold up to 5 LLM user input nodes, excluding other Input Collectors. To collect more than 5 inputs, you can chain multiple Input Collector nodes or adjust the system property com.glide.cs.vainputcollectormaxnodes.
    • Users can reorder input nodes within the Input Collector both on the canvas and in table views by dragging or using up/down arrows.
    • Nodes can be added, removed, or moved between Input Collectors directly on the canvas for flexible conversation design.

    Configurable Flow Action Properties

    • Node name: Identifies the node within the topic flow.
    • Advanced Additional Instructions: Allows providing extra guidance to the LLM, including data formats, restrictions, or default responses. Instructions can be plain language, scripts, or conditional logic using data pills.
    • Confirmation message: When enabled (default), presents users with a summary of collected inputs at conversation end to confirm correctness. Users can respond to confirm or restart input collection.
    • Conditional display and skip: Nodes can be conditionally shown or skipped based on no-code conditions or low-code scripts, enabling dynamic conversation flows.

    Channel Support

    The Input Collector control supports LLM and/or NLU on select channels as follows:

    ChannelLLM SupportNLU/Keyword SupportConstraints
    Microsoft TeamsSupportedSupportedNone
    SMS TwilioSupportedNot supportedNone
    Web UI, Mobile UI, ServiceNow Otto panelNot supportedSupportedNone
    Slack, Workplace, Facebook Messenger, LINE, WhatsApp, Apple Messages for Business, Alexa (Voice)Not supportedNot supportedNot applicable

    Practical Benefits for ServiceNow Customers

    By using the Input Collector control within LLM-based conversations, ServiceNow customers can efficiently gather structured user inputs, confirm data accuracy with users, and create dynamic, condition-based dialogue flows. This improves the quality and reliability of conversational interactions powered by ServiceNow Otto, especially on supported channels like Microsoft Teams and Twilio SMS.

    Use the Input Collector control to gather data for use by ServiceNow Otto in conversations that use large language model (LLM) topic discovery.

    Input Collector Overview

    For an overview 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 on both the canvas and table views. To reorder nodes 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 from an Input Collector, or nodes between multiple Input Collectors, by selecting a node and dragging it into or out of an Input Collector node on the canvas. To reorder nodes in an Input Collector 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 when activated.

    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

    Basic properties include the node name. Advanced options include Additional instructions to LLM, Confirmation messages, and Hide this node.

    Input Collector canvas view

    Input collector canvas view, holding text and static choice input nodes. You can move nodes by selecting and dragging them inside, out of, or within the Input collector.

    Input Collector table view

    Input collector table view, showing text and static choice nodes, with up and down arrows to reorder nodes inside the collector.

    Channel support

    Table 1. Channel support for the Input Collector control
    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
    WhatsApp Not supported Not supported Not applicable
    Apple Messages for Business Not supported Not supported Not applicable
    Alexa (Voice) Not supported Not supported Not applicable