---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/conversational-interfaces

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Enable Proactive Triggers

# Enable Proactive Triggers {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

Use Proactive Triggers to create and view context-specific messages and use relevant actions on the chat widget.

## Antes de Iniciar

Nota:  
The Proactive Triggers feature \[sn_pt\] is available as an app and must be installed from the ServiceNow Store. This feature is only available after you've installed and updated the Omni-Experience Standard Feature Set to the latest version through the ServiceNow Store. Subsequent updates are also available there. Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://docs.servicenow.com/bundle/store-release-notes/page/release-notes/store/sn-store-release-notes.html).

For conceptual information about Proactive Triggers, see [Exploring Proactive Triggers](https://servicenow-prod.fluidtopics.net/Appro3XA2KA4dl_AN~~FRw "Proactive Triggers is a ServiceNow Store application that is available to all Virtual Agent chat widget and Agent Chat customers by default. Proactive Triggers can increase adoption of Virtual Agent by proactively sending context-specific messages to end users.").

The Proactive Triggers feature can be used with Domain Separation. For more information about Domain Separation, see [Domain separation explained](https://www.servicenow.com/docs/access?context=bp-what-is-domain-separation&version=australia&pubname=australia-platform-security&ft:locale=en-US).

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

An admin first enables and then creates rules and actions as separate tasks.

## Procedimento

1. In the navigation filter, enter <kbd class="ph userinput">sys_properties.list</kbd>.  
   The entire list of properties in the System Properties \[sys_properties\] table appears.
2. Search for the <kbd class="ph userinput">com.glide.cs.advanced-chat-popover</kbd> system property, and then change the value from false (default) to true.  
   This system property enables the smart chat component on the Service Portal. This system property is only applicable to the requester persona.
3. Navigate to Conversational InterfacesSettings.  
   You must be in the Proactive Triggers scope to enable this feature.
4. Under Proactive triggers, select the more info icon (![More info icon.]()) next to the Enable proactive triggers field toggle switch to view the Proactive Triggers scope reminder.  

   <br />

   For more information about scopes and how to change them, see [Application scopes](https://servicenow-prod.fluidtopics.net/dfE1El20kdLG6P86Tcb4yQ "To upload and distribute custom applications on the ServiceNow Store, you need to create a private scope for your applications.").
5. Under Proactive triggers, select the Enable proactive triggers field toggle switch to enable the feature.  
   By default, the Proactive Triggers feature is inactive.
6. Next to Rules, select View all.  
   The default sample rules included with Proactive Triggers appear.
7. Navigate back to the Conversational InterfacesSettings page and next to Trigger types, select View all.  
   The default trigger types appear. All trigger types default to Active is true except the Search Event trigger type. To turn on the Search Event trigger type, proceed to the next step.
8. **Opcional:** Turn on the Search Event trigger.  
   The Search Event triggers a pop-up message on the Service Portal Default Search Profile whenever a search result yields no result. The Search Event trigger is an inactive default trigger type that uses the System API source rather than the web browsing
   source. Because this trigger type defaults to inactive, an admin must turn on the related business rule, trigger type, Proactive Triggers rule, and action prior to using this trigger.
   1. Navigate to System DefinitionBusiness rules.
   2. Search for <kbd class="ph userinput">Proactive Trigger on Search</kbd> in the Business Rules field, and then select the business rule.
   3. Select the Active option to turn on the business rule.
   4. **Opcional:** Adjust any settings, as needed.  
      Nota:  
      Your organization may want to update the Filter Conditions on the When to Run related tab. For example, if your organization doesn't use the Service Portal, update the default values in the Filter Conditions section to reflect your organization's preferred portal or site. Your organization may also want to adjust the Proactive Triggers API script in the Advanced related tab. For additional information on the Proactive Triggers API script, see [ProactiveTriggerAPI - Scoped](https://www.servicenow.com/docs/access?context=ProactiveTriggerScopedAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US).
   5. Select Update.
   6. Navigate to Conversational InterfacesSettings and under Proactive Triggers, select View All next to Trigger Types.
   7. Select Search Event.
   8. In the Proactive Trigger Type form for Search Event, select the Active option to turn on the trigger type and adjust any settings, as needed.
   9. Select Update.
   10. Select Search - No Search Result from the Proactive Rules related list.
   11. In the Proactive Rule form for Search - No Search Result, select the Active option to turn on the rule and adjust any settings, as needed.
   12. Select Update.
   13. Select No Search Result Message from the Proactive Actions related list.
   14. In the Proactive Action form for No Search Result Message, select the Active option to turn on the action and adjust any settings, as needed.
   15. Select Submit.

   {#enable-proactive-triggers__substeps_ixj_nz2_nxb}  
   The Search Event trigger type is turned on.
{#enable-proactive-triggers__steps_yvz_cb4_vvb}

## Resultado

The Proactive Triggers feature is enabled and you know where to create rules, actions, and custom trigger types.

## O que Fazer Depois

Create rules and actions for Proactive Triggers. For more information, see [Create rules and actions for Proactive Triggers](https://servicenow-prod.fluidtopics.net/XxJ9ItYEnXwQhu8uueKX7A "Create rules and related actions for Proactive Triggers. These rules and their related actions determine the messages that end users see on the ServiceNow portal.").

Create custom trigger types. For more information, see [Create custom trigger types](https://servicenow-prod.fluidtopics.net/o~QEsfBlCt3TEZWz4_hLwA "Create your own trigger type during the rule creation process that is specific to your organization for improved Proactive Triggers usage.").
**Tarefas relacionadas**   

* [Enable message preview on the chat widget](https://servicenow-prod.fluidtopics.net/mHV~~fY5MtFCzUt~XCYpwQ "Admins can allow their end users to see a preview of any new or unread messages waiting for them when the chat window is minimized.")