Rules in Distro

A Rule is a group of conditions that are evaluated to determine assignment.

In this article, we'll cover:

• Groups and Sub-Groups
• What types of rules can you create?
  • CRM Ownership
  • Non-Ownership
• Rule Operators
  • Evaluating Dates (Date Picker)

Groups and Sub-Groups

Before explaining which kind of rules you can create in Distro you need to know that Chili Piper allows you to create a complex and robust group of rules based on your business needs. The purpose of grouping your rules is to relate conditions to one another using the same operator (either AND/OR).

While creating a rule, you can click on "+ Add Group" to create a group of rules that will be added to your conditions.

A Sub-group can only be created if you already have a Group. With this option, you can guarantee that multiple conditions will be checked in the same Rule, allowing you to create a complex scenario based on the fields you need to evaluate.

What types of Rules can you create?

You can create Ownership Rules (CRM Ownership) and general string-based Rules (Without Ownership) depending on your business needs. So for example, if you want to evaluate an Ownership field (E.G Account/Contact/Lead owner) you should select CRM Ownership type while creating your rule. The type of Rule can be selected within the "Rules" menu after clicking "Create a Rule" in the top-left:

Note: Ownership fields cannot be used in Non-ownership rules and vice versa. Also, once you create a new rule, the rule type cannot be modified. If you want to change a rule type from CRM Ownership to Non-Ownership you will have to create a new one from scratch. 

CRM Ownership

An Ownership Field is any field in Salesforce that is a lookup field related to the User Object, such as:

• Lead.OwnerID
• Contact.OwnerID
• AccountOwner.Name
• AccountOwner.Username
• OpportunityOwner.Email

Ownership Rules are configured to route an existing record to the owner in your salesforce system if one exists, given the Team pairing. The Team pairing can be selected while building the Rules and should be auto-populated in the Assignment Rulesets.

If you want to evaluate the owner of a record then use the "is in team" operator

You can add multiple ownership-related objects and build your Rules with the available operators (AND/OR) across the same Team. You can also build Groups and Sub-Groups to better accommodate your rules.

Ownership fields are not compatible with the following operators:

• is greater

• is less than

• is greater than or equal to

• is less than or equal to

The "is in team" operator in Distro Fire fundamentally behaves the same as is equal to where the user’s Id/email of the evaluated field is checked for an exact match against those of the users in the evaluated team.

This operator will be available when in Ownership rule types, and when an Ownership field is selected.

Also, the Ownership condition will be enabled based on the use of this operator. Otherwise, it is not considered an Ownership condition, even if an ownership field is used.

Once the "is in team" operator is enabled, your active Teams will be displayed in a dropdown:

Users who are on vacation will still get records distributed to them if they're the object owner and the prospect matched with an Ownership rule. Learn more about vacation and distribution settings here

Non-Ownership

Non-ownership rules will also let you build rules based on your CRM's fields and the available operators (AND/OR). The main difference is that we'll not perform the Team association, as noticed above, within the Ownership rules:

Like CRM Ownership, you can build Groups and Sub-Groups to better accommodate your rules here.
For both Ownership and Non-Ownership rules, you can switch the conditions and change their order based on your business needs:

Rule Operators

Evaluating Dates (Date Picker)

In Distro, if the added condition is associated with a Salesforce date field type, then the value field should become a Date picker:

• A single date can be selected.

• Scrolling takes users forward/backward for a month.

• Done closes the date-picker.

• If a user types the date, we should focus the calendar on that date once the configuration is completed.

For example, in the rule below Distro will evaluate if the Account created date is greater than 01/01/2023:

Please note that only the following operators can be used once a date field is selected: 

• is greater/less than

• is greater/less than or equal to

• is equal

• is not equal

• null

• is not null

The date picker format should follow: MM/DD/YY so:

• Month cannot exceed 12 or be less than 1

• Day cannot exceed 31 or be less than 1

• Year cannot exceed 4 digits

Distro Fire also enables L2A (Lead-to-Account) Rule matching. You can learn more about it in this article