Types of Rules
Updated
Overview
The Sprinklr Rule Engine is a powerful tool that can be used to automate workflows, assignments, properties, and more. By configuring Rules, you can increase efficiency by transforming manual processes to automatic actions that execute according to the conditions that you set. Rules can be used to route and tag messages, profile audiences, send alerts, optimize paid media, and much more.
You can think of the Rule Engine as an If-Then statement. If an asset (like a message or a profile) meets a specific condition that you set, then an action will execute on that asset. Using "Yes" and "No" branches, you can customize different actions to apply depending on whether or not a condition is met.
Below, you can take a look at the ways to use Rules to increase operational efficiency, cut down on workload and effort, and streamline and enforce compliance across your environment.
Admin Set-up
To access the Rule Engine and to create or edit Rule configurations, you must first be assigned to a Role with the respective Rule Engine permissions. Learn more about Platform Permissions.
|
Types of Rules
Below, we'll explore the types of Rules supported in Sprinklr. Different Rule types may apply to a specific type of asset, like a message, Case, or profile. Or, Rule types may be based on the workflow stage that triggers the Rule - for example, Inbound Rules take action when content is pulled into the Sprinklr platform, while Queue Rules are executed when a message moves into a Queue.
Click on any of the below Rules to learn more about that Rule type. Note that some Rule types, like Listening Rules and Benchmarking Rules, apply to specific premium modules. Look for icons that indicate a specific module may be required in the below Rule Types.
|
|
| Used to apply properties to messages that are published natively, then automatically imported into Sprinklr. |
| ||
|
|
|
|
|
|
|
| Apply actions to messages and profiles when they enter a Queue (or according to the Rule's Trigger). |
| Autofill: Autofill rules are applied to outbound messages, but unlike Outbound Rules, which apply when a message is sent for publishing, Autofill Rules are applied when a message is being composed. |
|
| |
|
|
|
|
|
|
|
| Allow you to configure and measure the time it takes for an inbound message to travel through the various ‘stages’ of your workflow. |
|
|
| ||
|
|
|
|
|
|
|
|
| UGC: UGC Rules apply to user-generated content or their associated profiles when UGC is brought into the Sprinklr platform. |
| Listening Rules: Take action on content that is pulled into Sprinklr through Listening. ![]() Requires Listening |
| |
|
|
|
|
|
|
|
| Create notifications to users when a certain volume of messages hits an established queue. |
|
|
| ||
|
|
|
|
|
|
|
| Take action on content that is pulled into Sprinklr through Benchmarking. ![]() Requires Benchmarking |
|
|
| ||
|
|
|
|
|
|
|
| Apply actions when a Custom Field is added, changed, updated or removed from the |
| These rules are used to apply properties to messages that are published natively, then automatically imported into Sprinklr. |
| ||
DAM Update Rules are created to apply on existing Media Assets. | DAM Autofill Rules are created to pre-populate content whilst creating Assets based on set conditions. | Use this rule type to stop publishing any message(s) that meet the rule condition criteria when | ||||
Create post-publishing rules to tag messages that are published or to notify team members. | | Proactive prompts allow targeting website visitors with certain configurable messaging based on their behaviour. This rule allows you to reach on proactive prompt responses. | | Survey Response Rules allow you to automate queue assignments based on the responses your receive to surveys. | ||