Virtual Agent features supported in Slack conversations

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Virtual Agent features supported in Slack conversations

    The Virtual Agent features integrate seamlessly with Slack conversations, enabling functionalities like AI Search results, notifications, and conversation design tools. However, it's important to note that Conversational Integration for Slack is not available for on-premises instances.

    Show full answer Show less

    Key Features

    • AI Search Results: Virtual Agent generates search results displayed as Genius result cards and multi-link outputs, enhancing the user experience.
    • URL Navigation: Links to ServiceNow records open automatically in base system portals, with the option for admins to configure which portals are used.
    • Trusted Domains: In custom integrations, values from the Trusted media domains field take precedence over other settings, ensuring proper domain handling.
    • Chat Localization: Conversations are localized according to the user-specified language in the Slack UI, with fallback options available if the requested language plugin is absent.
    • Virtual Agent Designer Support: User input and bot response controls, including table responses and card controls, are fully supported in Slack.
    • Virtual Agent Notifications: Notifications can be sent and received during conversations on the Slack app.

    Key Outcomes

    By utilizing the Virtual Agent features in Slack, customers can enhance their conversational workflows, deliver localized experiences, and streamline interactions with integrated notifications and AI-driven search capabilities. Proper configuration ensures optimal use of these features to meet specific business needs.

    Virtual Agent features, such as AI Search results, Virtual Agent notifications, and Virtual Agent Designer controls for creating Virtual Agent conversations are supported in Slack bot conversations.

    Note:
    Conversational Integration for Slack is not supported for on-prem instances.

    This section highlights key Virtual Agent features that are supported in the Conversational Integration with Slack app.

    AI Search results

    Virtual Agent can generate AI Search results that are displayed as Genius result cards and multi-link outputs in conversations. For details on how Virtual Agent generates AI Search results, see Improving the user experience with AI Search. The default AI Search configuration for Virtual Agent enables search results for Q&A (knowledge base) and catalog items.

    URL navigation for chat links

    In Virtual Agent and Live Agent conversations on the Slack app, links to ServiceNow records open automatically in base system portals—including links displayed in output cards, Virtual Agent notifications, and AI Search results. If needed, admins can change the portals in which these links are opened. For configuration details, see Configure URL navigation for chat links.

    Trusted Domains

    In custom chat integrations, the values specified in the Trusted media domains field of the Provider Channel Identities table [sys_cs_provider_application] takes precedence over the Connections table [sys_cs_provider] and therefore overrides.

    Chat Localization into Conversation Language

    Starting from version 5.0.1, chat gets localized into the customer specified conversation language set in the Slack UI, though the session language is different.

    Translation of responses to the conversation language is done using the function gs::getMessageLang(str, lang), where the language retrieved from Slack is passed through this function as a parameter. The translation process works with the following three use cases, when:
    • The requested language plugin is available in the ServiceNow instance.

      When the requested language plugin is available in the ServiceNow instance then the Session language honors the Conversation language set by the user.

    • The requested language plugin is absent, but fallback is set and enabled​.

      When the requested language plugin is absent, then the fallback language specified in the [sys_language] table is used for the translation process. However, for the fallback mechanism to work, you must enable the glide_i18n.language_fallback_enabled system property. By default, the value of the property is false. Set it to true to enable the fallback mechanism. For more information, see Set a fallback language.

    • The requested language plugin is absent, but fallback is not set/enabled.

      When the requested language plugin is absent and fallback is also not set/enabled, the default translation language will be English.