---
sourceDocument: Brazil Conversational Interfaces
sourceDocumentLink: https://www.servicenow.com/docs/r/conversational-interfaces

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Text user input control

# Text user input control {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
The Text user input control in a Virtual Agent topic prompts the user for a text string.

## Text user input control properties {#va-text-input__section_xq2_jn5_g1c}

{#va-text-input__table_of1_vt5_g1c__entry__2}

| Property | Description |
|-|-|
| Node 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 ![]() to define conditions, or select the Open Editor icon ![]() to enter a script. If the Allow automatic slot filling toggle is activated, you can only enter a static description. |
| Input format | Text format that is validated when a user enters certain text items. If the user doesn't enter the expected format, an error message indicates that the format is not valid and asks the user to reenter the text. Choose the format of the text item to be validated: * Text: Any text string (no validation). * Email: Format that consists of an email prefix (user name), the @ symbol, and domain. * IP address (IPV4, IPV6): Data communication delivery format for Internet Protocol version 4 or version 6. * Phone number (E.164): Internationally recognized standard phone number format. * URL: Web address format. * Custom: A script that provides a validation rule for a custom text format. The script should include related error messages that are displayed when the expected format is not entered. {#va-text-input__ul_pf1_vt5_g1c}For phone and IP address format examples, see [E.164 phone formats](https://www.servicenow.com/docs/access?context=r_ConfigureE.164PhoneNumberFields&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) and [IP address field types](https://www.servicenow.com/docs/access?context=r-IPAddressFieldType&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). |
| 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 use 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. |
[ ]

{#va-text-input__table_of1_vt5_g1c}

## Example Text user input control {#va-text-input__section_zq2_jn5_g1c}

{#va-text-input__table_ar2_jn5_g1c__entry__2}

| Input properties | Input prompt |
|-|-|
|   | Figure 1. Text user input prompt |
[Table 1. LLM topic input control properties]

{#va-text-input__table_ar2_jn5_g1c}

## Channel support {#va-text-input__section_vr2_jn5_g1c}

Note:  
Asset library controls may display and function differently in other channels.  
{#va-text-input__table_wr2_jn5_g1c__entry__3}

| Channel | Support | Constraints |
|-|-|-|
| Microsoft Teams | Supported | None. |
| Slack | Not supported | Slack users can edit text previously entered in a conversation. However, Virtual Agent processes messages as they are first entered. If aSlack user edits text input, such as a comment to update a case, then Virtual Agent does not evaluate the edited update. |
| SMS Twilio | Not supported | None. |
| WhatsApp | Not supported | The maximum limit is 4,096 characters. |
| Google Chat | Supported | None |
[Table 2. Channel support for the Text user input control]

{#va-text-input__table_wr2_jn5_g1c}