Static Choice user input control
Use the Static Choice user input control in a Virtual Agent topic to list predefined choices available to the user. You can select only one item from a choice list.
Choice display
The choice list contains up to 10 items per page. The choice list prompt contains a search icon [Omitted image "icon-search.png"] Alt text: Search icon. that users can select to filter the results. When more than 10 items exist in an LLM chat conversation, a scroll bar appears. When more than 16 items exist in an LLM chat conversation, a search bar appears.
The Static Choice control provides the option to add a header card that displays above the choice list. Header cards are supported in web and mobile channels.
-
The header card can contain a large or small image or a YouTube video card, along with descriptive text. The choice list contains up to five items by default, but the search feature is suppressed. If there are more than five items, users can choose to show the additional items.
-
To control the number of items displayed below a header card, add the com.glide.cs.web_header_picker_page_limit system property. Use the Value to specify the number of items displayed in the choice list. For details about creating a system property, see Add a system property.
Static Choice user input control properties
|
Property |
Description |
|---|---|
|
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 [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. |
|
Choices | |
|
Display name |
For each choice, the text that appears to the user for that choice. Use short phrases in your choice lists.
|
|
Value |
For each choice, the string that is stored in the variable when the corresponding choice is selected. |
|
Advanced | |
|
Header Card |
Toggle to open a field to add cards which may include images or YouTube videos. For more information, see Insert a header card in a Static Choice or Dynamic Choice control |
|
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. If users enter a value such as |
Note: Asset library controls may display and function differently in other channels.
|
Input properties |
Static Choice list user prompt |
|---|---|
|
[Omitted image "va-static-choice-llm-3.png"] Alt text: All basic Static choice user input fields are openly available. Select any of the advanced options to toggle them open individually. |
[Omitted image "nass-static-choice-user-prompt.png"] Alt text: A choice list returns a list to select from. |
|
Channel |
Support |
Constraints |
|---|---|---|
|
Microsoft Teams |
Supported |
None |
|
Slack |
Not supported |
Header cards aren’t supported.When a choice list has three or fewer choices, Slack displays the list as buttons. |
|
SMS Twilio |
Supported |
Header cards aren’t supported. |
|
|
Not supported |
Header cards aren’t supported. The prompt or body text has a maximum limit of 1,024 characters. For list buttons:- Each button label can have a maximum of 24 characters.
|
|
Google Chat |
Supported |
None |
--- title: Static Choice user input control description: Use the Static Choice user input control in a Virtual Agent topic to list predefined choices available to the user. You can select only one item from a choice list. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/conversational-interfaces/virtual-agent/va-static-choicelist.html release: australia product: Virtual Agent classification: virtual-agent topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 4 keywords: [Virtual Agent, Static choice, User input, Designer] breadcrumb: [Assistant Designer user input controls, Assistant Designer interface reference, Reference, Virtual Agent, Conversational Interfaces] --- # Static Choice user input control Use the Static Choice user input control in a Virtual Agent topic to list predefined choices available to the user. You can select only one item from a choice list. ## Choice display The choice list contains up to 10 items per page. The choice list prompt contains a search icon \[Omitted image "icon-search.png"\] Alt text: Search icon. that users can select to filter the results. When more than 10 items exist in an LLM chat conversation, a scroll bar appears. When more than 16 items exist in an LLM chat conversation, a search bar appears. The Static Choice control provides the option to add a header card that displays above the choice list. Header cards are supported in web and mobile channels. - The header card can contain a large or small image or a YouTube video card, along with descriptive text. The choice list contains up to five items by default, but the search feature is suppressed. If there are more than five items, users can choose to show the additional items. - To control the number of items displayed below a header card, add the **com.glide.cs.web\_header\_picker\_page\_limit** system property. Use the **Value** to specify the number of items displayed in the choice list. For details about creating a system property, see [Add a system property](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_AddAPropertyUsingSysPropsList.md). ## Static Choice user input control properties <table id="table_zjt_pz3_h1c"><thead><tr><th> Property </th><th> Description </th></tr></thead><tbody><tr><td> 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"> Choices </td></tr><tr><td> Display name </td><td> For each choice, the text that appears to the user for that choice. Use short phrases in your choice lists. - Slack has a limit of 30 characters for choice list labels. - Workplace has a limit of 20 characters for choice list labels. </td></tr><tr><td> Value </td><td> For each choice, the string that is stored in the variable when the corresponding choice is selected. </td></tr><tr><td class="sub-head" colspan="2"> Advanced </td></tr><tr><td> Header Card </td><td> Toggle to open a field to add cards which may include images or YouTube videos. For more information, see [Insert a header card in a Static Choice or Dynamic Choice control](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/insert-header-card-user-input-control.md) </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 or skip this node </td></tr><tr><td> Conditionally use 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 Static Choice user input control **Note:** Asset library controls may display and function differently in other channels. <table id="table_rc5_cp5_zzb"><thead><tr><th> Input properties </th><th> Static Choice list user prompt </th></tr></thead><tbody><tr><td> \[Omitted image "va-static-choice-llm-3.png"\] Alt text: All basic Static choice user input fields are openly available. Select any of the advanced options to toggle them open individually. </td><td> \[Omitted image "nass-static-choice-user-prompt.png"\] Alt text: A choice list returns a list to select from. </td></tr></tbody> </table>## Channel support <table id="table_iw1_2j3_rsb"><thead><tr><th> Channel </th><th> Support </th><th> Constraints </th></tr></thead><tbody><tr><td> Microsoft Teams </td><td> Supported </td><td> None </td></tr><tr><td> Slack </td><td> Not supported </td><td> Header cards aren’t supported.When a choice list has three or fewer choices, Slack displays the list as buttons. </td></tr><tr><td> SMS Twilio </td><td> Supported </td><td> Header cards aren’t supported. </td></tr><tr><td> WhatsApp </td><td> Not supported </td><td> Header cards aren’t supported. The prompt or body text has a maximum limit of 1,024 characters. For list buttons:- Each button label can have a maximum of 24 characters. - Only 10 list buttons are visible at a time. - If there are more than 10 buttons, the system automatically uses pagination to show additional options. </td></tr><tr><td> Google Chat </td><td> Supported </td><td> None </td></tr></tbody> </table>**Parent Topic:**[Assistant Designer user input controls](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/va-user-inputs.md)
| title | Static Choice user input control |
| description | Use the Static Choice user input control in a Virtual Agent topic to list predefined choices available to the user. You can select only one item from a choice list. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/conversational-interfaces/virtual-agent/va-static-choicelist.html |
| release | australia |
| product | Virtual Agent |
| classification | virtual-agent |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 4 |
| keywords | Virtual AgentStatic choiceUser inputDesigner |
| breadcrumb | Assistant Designer user input controlsAssistant Designer interface referenceReferenceVirtual AgentConversational Interfaces |