Proactive Rule form
-
- UpdatedAug 3, 2023
- 4 minutes to read
- Vancouver
- Proactive Triggers
When creating a Proactive Triggers rule, the Proactive Rule form includes the following fields.
Field | Description |
---|---|
Name | Name of the new rule that you want to create. |
Type | Proactive Triggers conversation type for end users. Choices are:
|
Description | Rule description. |
Order | Order of when a Proactive Triggers rule is to be applied. If there’s more than one rule, the rules with lower numbers for a particular delay time are applied first. |
Active | Option to activate the rule. |
When to run the trigger | |
Frequency | How often the rule should be applied. Choices are:
|
Delay time | Time to wait before the rule is applied. Choices are:
|
What initiates the trigger | |
Trigger type | System API or web browsing URL for the type of trigger. Select the lookup list icon ( If enabled, your default system API choice is Search Event. This trigger type triggers an action when no search results are found on the Service Portal or Employee Service Center.
Tip: Ensure that your Proactive Trigger business rule (Proactive Trigger on Search), trigger type (Search Event), rule (Search - No Search Result),
and action (No Search Result Message) have the Active option turned on so that this rule runs effectively. These parameters default to inactive. Your default web browsing URL choices are:
If you don’t see the trigger type that you need using the lookup list icon ( |
Conditions | Conditions that must be met for the trigger type to run as defined by the admin. Conditions vary by trigger type. Specify the Proactive Triggers conditions that you want to use. For more information about using conditions, see Condition builder. Note: Rule conditions are case-sensitive and must match. For example, if you want to use the name of a catalog item, such as the iPhone condition, entering "iphone" doesn't give you the results that you want. ![]() Note: When specifying the conditions that must be met for a trigger type, be careful not to specify conflicting trigger types and conditions. Conflicting URL trigger types and conditions can cause errors. For more
information, see Manage Proactive Triggers. |
Advanced conditions | Option for using scripts to define the condition.![]() |
Find available agent | Option to check for any available live agents. |