Deploying Virtual Agent topics in other channels
Summarize
Summary of Deploying Virtual Agent topics in other channels
ServiceNow Virtual Agent allows you to create and deploy conversational topics across multiple chat channels, including both default and custom channels. Default channels include popular messaging platforms like Slack, Microsoft Teams, Workplace, Facebook Messenger, and web/mobile clients. Additionally, custom channels can be created using conversational custom chat integrations to extend Virtual Agent support to third-party chat providers such as Skype or SMS.
Show less
Specifying Channels for Topics
When creating or editing a topic or topic block in Virtual Agent Designer, you can specify which chat channels the topic will operate in via the Channels field under Advanced properties on the Topic Properties page. This enables targeted deployment of conversations to appropriate chat clients within your organization.
Virtual Agent Designer provides built-in guardrails that check conversation flow controls against the selected channels to ensure compatibility. If a control is not supported on a specified channel, warnings appear in the Properties tab and on the flow canvas, allowing you to adjust the conversation design accordingly. This ensures your topics function correctly across all chosen channels.
Managing and Viewing Available Channels
You can view and filter the list of available channels for your instance in the Assistant Designer Asset library under Conversational Interfaces. The Messaging Channels [syscschannel] table also enumerates all configured channels. This helps you identify default channels and any custom conversational chat integrations that have been added, such as SMS or Skype.
Practical Benefits for ServiceNow Customers
- Multi-channel deployment: Tailor and deploy Virtual Agent topics across multiple chat platforms to meet your users where they communicate.
- Channel-specific design validation: Use built-in designer guardrails to ensure conversations are optimized and compatible with each selected channel.
- Custom channel support: Extend Virtual Agent reach to virtually any third-party messaging provider by creating custom chat integrations.
- Centralized channel management: Easily view and manage all available chat channels in your instance for streamlined topic deployment.
When creating a topic or topic block, you can specify the chat channels in which the topic or topic block will run. During conversation design, Virtual Agent Designer provides built-in guardrails to help you tailor your conversations to those channels.
In Virtual Agent, a channel is a chat interface or application in which Virtual Agent interacts with end users. Default channels are the chat applications natively supported by Virtual Agent, such as the Slack, Microsoft Teams, Workplace, and Facebook Messenger applications, and the web and mobile clients. Virtual Agent also supports custom channels created through the conversational custom chat integrations feature, which enables third-party applications (other chat providers) to work in Virtual Agent.
For example, admins can build a custom conversational chat integration for a specific messaging provider, such as Skype. Admins also define the controls that can be used in topics that run in these channels. For details about creating channels for chat providers and specifying the controls used in a channel, see Creating conversational custom chat integrations in Virtual Agent.
Specifying channels in your topics or topic blocks
When you create or edit a topic or topic block, you can specify the applicable channels in the Channels field under Advanced properties in the Topic Properties page. Applicable channels are the custom channels created for your instance through the conversational custom chat integrations. Use this field to specify chat clients in which the topic or topic block will run.
During conversation design, Virtual Agent checks the various controls used to build the conversation flow to confirm that the control is valid for the channels in which the topic or block will run.
Design checks for specified channels during conversation design
- Properties tab (Topic Properties page)
In the following example, Skype and SMS are the additional channels in which the topic will run. The banner message identifies the controls that are not supported on the channels for the topic. As you develop the conversation flow, you can revise your conversation so that it does not use any of the specified controls for your selected channels.
Figure 2. Topic Properties tab with defined channels - Flow tab (Virtual Agent Designer canvas)
In the following example flow, the banner message identifies the controls that are not supported for the specified channels. The property sheet for the affected nodes also displays a message indicating that the control is not supported. For example, when you highlight a particular node (control) in the flow, the associated property sheet for the node indicates that the control is not supported in the Skype and SMS channels.
If you have controls that cannot be used, you can branch the flow so that you can continue building the flow with the controls that are supported.
Figure 3. Topic Flow tab with channel warnings
Finding the channels available in your instance
To see a list of the available channels in your instance, use the filter icon (
) in the Assistant Designer Asset library (). The Messaging Channels [sys_cs_channel] table also shows the available channels.
The default channels in Virtual Agent are the web chat and mobile clients and also the Virtual Agent messaging integrations for the Slack, Microsoft Teams, Workplace, and Facebook Messenger messaging applications. In the previous example, SMS is an available chat channel that was created for your instance through a conversational chat integration. When you choose a channel, the home page lists your topics (cards) by channel type. For more information, see Creating conversational custom chat integrations in Virtual Agent.