---
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


---

# Boolean user input control

# Boolean 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  
Use the Boolean user input control in a Virtual Agent topic to present a Yes/No
prompt to the user.
Boolean user input controls prompt the user to answer a Yes/No question, and store the response as a string with a value of true or false. Use this value in topic utilities, such as the prompted Decision utility, to branch the topic flow based on the answer.

When you place this control on the canvas, a window appears with the header Add a decision node? The window message reads A decision node will be added following this node and has No and Yes options. If you select No, you must add a Decision utility to complete the Boolean. You can customize the names of
the output values on the Decision node. For more information, see [Decision utility](https://www.servicenow.com/docs/7sm6Q6lnxcdlrlL7scmolw "Use the Decision utility in a Virtual Agent topic to add two or more branches that represent different paths in a conversation.").

## Boolean user input control properties {#va-boolean-user-input__section_mq1_hrq_11c}

{#va-boolean-user-input__table_cxj_5gj_h1c__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. |
| 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 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 <kbd class="ph userinput">skip this step</kbd> 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. |
[ ]

{#va-boolean-user-input__table_cxj_5gj_h1c}

## Example Boolean user input control {#va-boolean-user-input__section_jml_drq_11c}

Note:  
Asset library controls may display and function differently in other channels.  
{#va-boolean-user-input__table_kml_drq_11c__entry__2}

| Input properties | Input user prompt |
|-|-|
|   | Figure 1. Boolean user input prompt example |
[ ]

{#va-boolean-user-input__table_kml_drq_11c}

## Channel support {#va-boolean-user-input__section_ud2_p5p_rsb}

{#va-boolean-user-input__table_a2z_q5p_rsb__entry__3}

| Channel | Support | Constraints |
|-|-|-|
| Microsoft Teams | Supported | None |
| Slack | Not Supported | None |
| SMS Twilio | Not Supported | None |
| WhatsApp | Supported | None |
| Google Chat | Supported | None |
[Table 1. Channel support for the Boolean user input control]

{#va-boolean-user-input__table_a2z_q5p_rsb}