---
title: Boolean user input control
description: Use the Boolean user input control in a Virtual Agent topic to present a Yes/No prompt to the user.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/conversational-interfaces/virtual-agent/va-boolean-user-input.html
release: brazil
product: Virtual Agent
classification: virtual-agent
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 3
keywords: [Virtual Agent, Designer, Boolean, User input, control, node, Yes, No, prompt]
breadcrumb: [Assistant Designer user input controls, Assistant Designer interface reference, Reference, Virtual Agent, Conversational Interfaces]
---

# Boolean user input control

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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/conversational-interfaces/virtual-agent/va-decision.md).

## Boolean user input control properties

<table id="table_cxj_5gj_h1c"><thead><tr><th>

Property

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Node name

</td><td>

Name that identifies this node in the topic flow.

</td></tr><tr><td>

Variable name

</td><td>

Name of the variable that stores the user response to this prompt. The variable name is automatically created from the **Node name** property.

</td></tr><tr><td>

Allow automatic slot-filling

</td><td>

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.

</td></tr><tr><td>

Detail description

</td><td>

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 \[Omitted image "variable-reference-picker.png"\] Alt text: to define conditions, or select the Open Editor icon \[Omitted image "icon-script.png"\] Alt text: to enter a script. If the **Allow automatic slot filling** toggle is activated, you can only enter a static description.

 \[Omitted image "LLM-input-discoverable-toggle.png"\] Alt text: When the Allow automatic slot-filling toggle is inactive, the detail description includes Data Pill Picker and script dynamic options. When the toggle is active, the Detail description field becomes static.

</td></tr><tr><td class="sub-head" colspan="2">

Advanced

</td></tr><tr><td>

Enforce user prompt

</td><td>

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.

</td></tr><tr><td>

Validation

</td><td>

Add a script to validate the user input. For example, check if the user entered a valid email address.

</td></tr><tr><td>

Additional instructions for LLM

</td><td>

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.

</td></tr><tr><td class="sub-head" colspan="2">

Hide this node

</td></tr><tr><td>

Conditionally show this node if

</td><td>

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.

</td></tr><tr><td>

Allow user to skip this node if

</td><td>

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 `skip this step` 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.

</td></tr></tbody>
</table>## Example Boolean user input control

**Note:** Asset library controls may display and function differently in other channels.

<table id="table_kml_drq_11c"><thead><tr><th>

Input properties

</th><th>

Input user prompt

</th></tr></thead><tbody><tr><td>

\[Omitted image "va-boolean-llm-3.png"\] Alt text: All basic Boolean user input fields are openly available. Select any of the advanced options to toggle them open individually.

</td><td>

\[Omitted image "nass-boolean-user-prompt.png"\] Alt text: An example prompt reads, "Have you performed the latest software update on your machine?" Answers are Yes and No.

</td></tr></tbody>
</table>## Channel support

|Channel|Support|Constraints|
|-------|-------|-----------|
|Microsoft Teams|Supported|None|
|Slack|Not Supported|None|
|SMS Twilio|Not Supported|None|
|WhatsApp|Supported|None|
|Google Chat|Supported|None|

**Parent Topic:**[Assistant Designer user input controls](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/conversational-interfaces/virtual-agent/va-user-inputs.md)