Assistant Designer user input controls

  • Release version: Zurich
  • Updated March 12, 2026
  • 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 Assistant Designer user input controls

    Assistant Designer provides a variety of user input controls that allow you to prompt and capture information from users during Virtual Agent conversations. These input controls are essential for designing interactive and dynamic chatbots that can gather user responses efficiently and accurately.

    Show full answer Show less

    Common Properties

    • Input Variable: Each input control stores the user response in a variable named based on the control’s assigned name, formatted in lowercase with underscores. This variable is accessible within the same topic using getValue and getDisplayValue methods.

    Large Language Model (LLM) User Input Controls

    For topics leveraging LLM Virtual Agent capabilities, the following user input controls are supported:

    • Input Collector
    • Text Input
    • Static Choice List
    • Dynamic Choice List
    • Boolean Input
    • Date Time Input
    • Carousel Input

    Best Practice: Avoid using more than five user input controls per LLM topic or Input Collector to prevent overwhelming the model and causing inaccurate responses.

    Natural Language Understanding (NLU) Properties

    If NLU is enabled, input controls like Text, Static Choice, Dynamic Choice, Boolean, Date Time, and Carousel expose additional properties:

    • NLU Entity: Links an input variable to an NLU entity from the topic’s intent model, enabling slot filling where Virtual Agent extracts and stores recognized entity values from user utterances.
    • Enable NLU to Switch Topics: Allows users to change topics mid-conversation by matching their input to other intents, even if the input control type does not typically accept free text.

    Additional Features

    • Default Value: Input prompts can have preset values defined as strings or scripts, facilitating smoother user interactions.
    • Confirmation Messages: Customizable bot responses that confirm the end of an input interaction, helping users verify their responses.

    Input Control Types and Uses

    • Input Collector: Gathers multiple data points for use with ServiceNow Otto within LLM topics.
    • Text Input: Prompts users to provide free text responses.
    • Static Choice: Presents a predefined list of options, allowing a single selection.
    • Grouped Choice: Displays multiple groups of predefined choices in one message.
    • Dynamic Choice: Generates a choice list dynamically by querying tables or running scripts.
    • Boolean Input: Offers a simple Yes/No prompt.
    • Date Time Input: Enables selection of calendar dates and/or times.
    • File Picker: Allows users to upload files or images, which display immediately in the Virtual Agent client.
    • Carousel: Shows a horizontal series of labeled images from which users select one.
    • Secure Text: Encrypts sensitive textual information, especially useful in LLM discovery topics.

    Practical Implications for ServiceNow Customers

    By effectively using these input controls, ServiceNow customers can design more engaging, accurate, and context-aware Virtual Agent conversations. Leveraging NLU integration and LLM-specific controls enhances the bot’s understanding and flexibility, enabling better user experience and efficient data collection. Properly configuring these controls with attention to input limits and confirmation prompts ensures reliability and clarity in user interactions.

    Use the collection of input controls provided by Assistant 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 and getDisplayValue 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 is first_prompt. The variable name is lowercase, with an underscore character instead of a space. For more information on these methods, see Virtual Agent scripts.
    Figure 1. The Variable name field is populated automatically
    The Variable name field is populated automatically under Text input.

    Large Language Model (LLM) user input controls

    The following user input controls are supported in LLM topics when you create an LLM Virtual Agent topic. LLM user inputs include the following.
    Note:
    Avoid placing more than five user input controls in a single LLM topic, or more than five in a single Input Collector. Excessive user input controls can overwhelm the LLM and may lead to inaccurate or unexpected responses.

    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.
    • 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 Advanced options > Topic switching.
    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.