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


---

# Use custom controls

# Customizing Virtual Agent with custom controls {#ariaid-title1}

Release version: Brazil  
Updated October 24, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Custom controls are components that ServiceNow® developers can create for use in Virtual Agent topics or topic blocks. Such controls include sliders or video players. Custom controls complement the controls provided in Assistant Designer.

Assistant Designer provides a default set of controls that represent [user inputs](https://www.servicenow.com/docs/kvFNptsDpMYs5QDoK1JJqg "Use the collection of input controls provided by Assistant Designer to prompt and capture information from the user in a conversation."), [bot responses](https://www.servicenow.com/docs/dTEaoofyLRlOPgwbBeKfpg "Assistant Designer offers various controls for displaying bot responses in a conversation. Because the bot responses occur in third-party platforms, the format for each output may vary."), and [utilities](https://www.servicenow.com/docs/NzIRUd9yynf0Gzbx0H9RxQ "You can control interactions within a topic by using utilities in Assistant Designer. These utilities perform various actions such as adding topic blocks (reusable components), running a script, or adding different conversation paths (branches) in a topic. Utilities are represented as nodes in a conversation flow but do not display anything to the user.") for building a Virtual Agent conversation. As a developer, you can use the Asset library in Assistant Designer to create additional controls (interface components) for specific inputs or output responses. For example, a slider is an example of a custom input control that enables end users to select a
quantity.  
Note:  
Custom controls don't work on Internet Explorer version 11. Custom controls are also not supported for Microsoft Teams.

## Before building a custom control {#custom-controls__section_igd_gfj_skb}

Custom controls are based on customizable Next Experience Components that you
can create by using the Next Experience Design System.  
Before building a custom component, you must have the following:

* Basic knowledge of the ServiceNow AI Platform® and application table structures.
* General knowledge of web component concepts, development, and design.
* JavaScript knowledge to define component behavior and that of the custom control.
* Knowledge of the design process for creating custom components for use in Assistant Designer.
{#custom-controls__ul_bjc_lfj_skb}

To learn more about developing custom components for Virtual Agent, see [Develop a component for Virtual Agent](https://www.servicenow.com/docs/access?context=va-components&version=brazil&pubname=brazil-application-development&ft:locale=en-US).

## How custom controls work {#custom-controls__section_mlf_kcf_bmb}

To add your custom control to Virtual Agent, follow these main steps:

1. [Create a custom control definition](https://www.servicenow.com/docs/VAyt2W3KSK_YBucp6vkOuw "Define a custom input or response control definition that maps to a custom component.").

   After building the
   custom component to be used for the control, create a custom control definition that
   maps an input or response control to the custom component.
2. [Create a custom control using Assistant Designer.](https://www.servicenow.com/docs/wmqiQ0SUEJDRX8ns_bPUGw "Build a custom input or response control that topic authors can use in topics or topic blocks. In Virtual Agent conversations, an input control gathers information from end users, while a response control displays information to end users.")  
   A custom control is an input or response control. Developers build a custom control in Assistant Designer by doing the following:
   * Selecting a custom control definition.
   * Defining the input parameters for using the control.
   * Specifying the output parameters returned by the control.
   {#custom-controls__ul_fdy_ndn_fpb}

   An input control has callbacks that use input from the end user. A response control typically presents information to the end user and doesn't have callbacks.
3. [Add a custom control to a topic or topic
   block](https://www.servicenow.com/docs/EC4wxhAUOo3PfBfUpbiYrQ "Add a custom control to a Virtual Agent topic or topic block. During the conversation, you can gather inputs from the user or display outputs to the user.").

   Topic authors, virtual agent admins, or admins can add a custom control
   utility to a topic or topic block.
{#custom-controls__ol_ppp_zcn_fpb}

## Secure inputs {#custom-controls__section_tbg_3fr_zqb}

Beginning with the San Diego release, you can create custom input controls
that can accept secure inputs, such as passwords, to pass through to Integration Hub actions or subflows. To enable this, slide the Make inputs secure toggle switch when you create your custom input control. For
more information, see [Create a Virtual Agent custom control](https://www.servicenow.com/docs/wmqiQ0SUEJDRX8ns_bPUGw "Build a custom input or response control that topic authors can use in topics or topic blocks. In Virtual Agent conversations, an input control gathers information from end users, while a response control displays information to end users.").