--- title: "Rules in Chili Piper" source_url: https://help.chilipiper.com/hc/en-us/articles/30080073275027-Rules-in-Chili-Piper article_id: 30080073275027 updated_at: 2026-07-03T17:08:57Z --- ## Who can use this feature? Available on All Products or Routing & Scheduling Available to Admins or Workspace Managers [Billing Center](https://fire.chilipiper.com/fire/admin/billing/overview) [Get a Demo](https://www.chilipiper.com/request-demo?utm_source=zendesk&utm_medium=help-center&utm_campaign=chili-hub) Routing rules are crucial to ensure your prospects are correctly routed among your Teams within your Chili Piper products and assets, such as [Chat Journeys](https://help.chilipiper.com/hc/en-us/articles/27532198601107-Creating-a-Journey-in-Chat), [Concierge Routers](https://help.chilipiper.com/hc/en-us/articles/28522554434323-Creating-a-Router-in-Demand-Conversion-Platform-s-Concierge), [Handoff Routers](https://help.chilipiper.com/hc/en-us/articles/29684412579987-Creating-a-Handoff-Router-in-Demand-Conversion-Platform), and [Distro Routers](https://help.chilipiper.com/hc/en-us/articles/23304655920403-Creating-a-Distro-Router). This article will teach us how to create routing rules for your products and all the possibilities you can work with while building them. * * * #### Table of Contents * How to Create Rules? * What Types of Rules Can I Create? * CRM Ownership * Without Ownership * Can I Disqualify Prospects Based on Rules? * Condition Types * Groups and Sub-Groups * Rule Operators * Route to Any Salesforce Object * Lookup Fields or Other Fields * Route to Any HubSpot Object * Lookup Fields or Other Fields * Lead to Account Matching * * * ## How to Create Rules? After accessing an existing or creating a new [Chat Journey](https://help.chilipiper.com/hc/en-us/articles/27532198601107-Creating-a-Journey-in-Chat), [Concierge Router](https://help.chilipiper.com/hc/en-us/articles/28522554434323-Creating-a-Router-in-Demand-Conversion-Platform-s-Concierge), [Handoff Router](https://help.chilipiper.com/hc/en-us/articles/29684412579987-Creating-a-Handoff-Router-in-Demand-Conversion-Platform), and/or [Distro Router](https://help.chilipiper.com/hc/en-us/articles/23304655920403-Creating-a-Distro-Router), you can create rules within their setup. While adding your Routing Rule node or path, click the "Select Rule" button and then the "Create New Rule" one. Existing rules will also be listed if you would like to use an existing one. Here's one example from a Concierge Router, where we added the Rule from a Routing Rule path: ![](https://help.chilipiper.com/hc/article_attachments/30080073164051) You can also access your Rules from the Assets menu on the left-hand side. Click the "Create Rule" button on the top-right to create a new one, or click Open next to the rule you want to update. ![](https://help.chilipiper.com/hc/article_attachments/30080073171987) Any Rule can be reused on multiple Journeys or Routers across your products ([Chat](https://help.chilipiper.com/hc/en-us/sections/27531015253395-Chat), [Concierge](https://help.chilipiper.com/hc/en-us/sections/28558396528531-Concierge), [Distro](https://help.chilipiper.com/hc/en-us/sections/8298371316883-Distro), and [Handoff](https://help.chilipiper.com/hc/en-us/sections/29684376670099-Handoff)), saving time when creating and maintaining your routing criteria. It means that, for example, if you are a Chat and Concierge user, you can use the same Rules in those two products. While creating a rule, you will notice that you can select [CRM Ownership](https://help.chilipiper.com/hc/en-us/articles/29365688876051#h_01HWQVZD412KQPZ2JZB17FH7SR) or [Without Ownership](https://help.chilipiper.com/hc/en-us/articles/29365688876051#01HWQW5DF19GMBJ5TVMTM1A81Y). Click the option's name to be redirected to the next section, which covers those in more detail. * * * ## What Types of Rules Can I Create? Once you start a new rule, you can choose whether to route the prospect to an object record owner or not. Select "**CRM Ownership"** to route to the owner or “**Without Ownership** ” to route unowned records. In summary, if you want to dynamically evaluate a condition such as Lead Owner, Contact Owner, or similar, you would choose the "**CRM Ownership"** type. ![](https://help.chilipiper.com/hc/article_attachments/30080036145043) ### CRM Ownership If you choose "**CRM Ownership"** , you must select which CRM records you want to check for the owner and create or select an existing **Team** of your reps, such as Sales or CSMs. CRM Ownership rules work with **Salesforce** and**HubSpot** values conditions. The example rule below checks if the prospect is a Lead, Contact, **or** part of an Account that exists in Salesforce and is owned by one of the reps on the AE team. ![](https://help.chilipiper.com/hc/article_attachments/30080073175187) Coming to HubSpot, here's one example where we check if the prospect is a Contact **or** part of a Company that exists in HubSpot and is owned by one of the reps on the AE Team: ![](https://help.chilipiper.com/hc/article_attachments/35816163899283) Reinforcing always to double-check to select the correct rule operator: **AND / OR**. ### Without Ownership If you choose "**Without Ownership,"** you can route using one of the standard Salesforce values and Data Field values to route on form fields. This Salesforce-related example rule checks whether the prospect Lead **or** Contact's company size on the **Salesforce** record is 1-10 or 11-50. ![](https://help.chilipiper.com/hc/article_attachments/30080036150547) Coming to HubSpot, we have a similar example where we check if the Contact's company size on the **HubSpot** record is 1-10 or 11-50: ![](https://help.chilipiper.com/hc/article_attachments/33378774749075) If you have mapped your form fields to Chili Piper [Data Fields](https://help.chilipiper.com/hc/en-us/articles/27607845025555-Setting-up-Data-Fields%20), you can route prospects based on form values they submit by setting up a Data Field rule. If you are working with **Concierge** , ensure the rule uses [Data Fields](https://help.chilipiper.com/hc/en-us/articles/27607845025555-Setting-up-Data-Fields%20) mapped to the Trigger, like the example below where the Email and Company Size fields were mapped there: ![](https://help.chilipiper.com/hc/article_attachments/30080073186707) Then, we can see one example of the Company Size Data Field applied to a Rule condition, evaluating if the form choice was 1-10 or 11-50: ![](https://help.chilipiper.com/hc/article_attachments/30080073187731) Feel free to mix and match Data Field conditions with CRM conditions in your Rules and, as usual, check if the operator (AND/OR) is correctly used! ![](https://help.chilipiper.com/hc/article_attachments/30080036155539) If you are an Admin, [click here](https://help.chilipiper.com/hc/en-us/articles/27607845025555-Setting-up-Data-Fields%20) to check more details on how to configure Data Fields for your org. ### Can I Disqualify Prospects Based on My Rules? Yes! You can set up a rule to disqualify prospects; a common scenario is disqualifying those with a public-domain email. Add a **Routing Rule** node and associate it with your disqualification condition. In the example below, we will disqualify prospects with gmail.com and yahoo.com domains: ![](https://help.chilipiper.com/hc/article_attachments/30080073196691) You can follow it up with a **Redirect To** node to navigate the customer to a thank you page or back to the form. ![](https://help.chilipiper.com/hc/article_attachments/30080073200147) **Don't forget to Publish at the top-right once you are done!** * * * ## Condition Types A Rule comprises one or more conditions, which are composed of Objects, Fields, Values, and the Operator selection. Once you are building a new Rule or updating an existing one while adding a new condition, you will notice two options: * **CRM values:** your CRM fields in Salesforce or HubSpot will be synced and available for your rule. For this type of rule, you need to connect your Salesforce or HubSpot account. * **Data Field:** The form data will be used for the rule evaluation based on the Data Fields configured by your org to build the rule. [Click here](https://help.chilipiper.com/hc/en-us/articles/28918570010131#01HWQW5DF19GMBJ5TVMTM1A81Y) for more details about mapping to Data Fields. After selecting the field type, select the **Object**. For Data Fields, the objects available are Company or Person; for Salesforce, the available ones are Lead, Contact, Account, Opportunity, and Case; for Hubspot, the available ones are Contact, Company, Deal, and Ticket. Now that the Object has been selected, it's time to select the **Field** used in the rule. In the dropdown, you will see your CRM object-related fields or your Data Fields-related ones (Data Field). Last, select the **Operator** ([more details here](https://help.chilipiper.com/hc/en-us/articles/28918570010131#h_01HWQX6ZBA445H84J5BGC9E9Z6)) and the **Values**. You can use comma-separated values to include multiple in the same rule. Also, watch if you are correctly using the **AND** or **OR** operators. For example, if you are a Salesforce user and have a Lead-related rule and a Contact-related condition in the same rule, you should **not** use the AND operator. Click on it to switch them accordingly: ![](https://help.chilipiper.com/hc/article_attachments/30080073206419) You can also click on the three dots to Duplicate a condition to avoid manual effort while building similar conditions or remove a condition: ![](https://help.chilipiper.com/hc/article_attachments/30080036173715) Here's one rule example, where we set a Rule to evaluate if Leads **or** Contacts have their Country field as the United States or Canada: ![](https://help.chilipiper.com/hc/article_attachments/30080073215379) **Don't forget to Publish at the top-right once you are done!** * * * ## Groups and Sub-Groups Before exploring the Rule Builder in more detail, 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. Here's one example: We are evaluating whether the Lead's Country contains the United States or Canada first, **OR** the group condition evaluating the Account's Country contains the United States or Canada 500 **AND** Account's Customer field is equal to True. ![](https://help.chilipiper.com/hc/article_attachments/31399102399251) The logic for the above would be 1 OR (2 AND 3) to evaluate if a prospect qualifies. * * * ## Rule Operators `Operator`**field value** | **Example** | `Value`**field** ---|---|--- is any of | Company is any of: Sam's Club, Chili Piper, etc. Supports multiple values (comma-separated) | `comma-delimited text` is not any of | Company is not any of: Sam's Club, Chili Piper, etc. Supports multiple values (comma-separated) | `comma-delimited text` contains | Company contains Club | `Text` does not contain | Company does not contain Club | `Text` contains any of | Company contains any of: Air matches "Air Canada" **and** "Fairview Corp" (unintended) | `comma-delimited text` contains none of | Company does not contain any of: Club, Piper, etc. | `comma-delimited text` starts with | Company starts with C | `Text` starts with any of | Company starts with any of: **Air** matches "**Air** Canada", not "Fairview Corp" | `comma-delimited text` ends with any of | isolates what ends with any of: **ways** matches "Air**ways** ", not "Wayside Inc" | `comma-delimited text` ends with | isolate emails ending in .io | `comma-delimited text` is equal to | Company equals Sam's Club | `Text` is not equal to | Company does not equal Sam's Club | `Text` is less than | Revenue is less than 5 Available for certain Field Types like Number, Currency, Formula, Date, Time, Date & Time. | `Number` is greater than | Revenue is greater than 5 | `Number` is less than or equal to | Revenue is less than or equal to 5 | `Number` is greater than or equal to | Revenue is greater than or equal to 5 → only one numerical value | `Number` is null | Cannot enter any value | `TextField disabled` is not null | Cannot enter any value | `TextField disabled` If you are using a Date Field, below are the available operators and how they work. The value will be one of the following: Today, Yesterday, This week, 7 days ago, 30 days ago, custom, or specific date. `Operator`**field value** | **Example** ---|--- is before | Became a customer date is before today is after | Became a customer date is after 30 days ago is on or before | Birthdate is on or before Jan 1 is on or after | Birthdate is on or after Jan 1 is on | Became a subscriber is on this week is before or after | Is before or after 7 days ago is null | Became a lead date is null is not null | Became a lead date is not null * * * ## Route to Any Salesforce Object By working further within our integration with Salesforce to support any Salesforce Object (Standard or Custom), our Rule Builder supports more use cases. Let's cover these settings below: ### Use any Custom or Standard Object (Distro only) If you are a Distro user, you can activate any Salesforce field to be used in your Rules and Triggers. Check [**this article**](https://help.chilipiper.com/hc/en-us/articles/31924265515923-Route-to-Any-Salesforce-Objects-in-Distro) to learn how! ### Lookup Fields or Other Fields When you create a Rule, you can refer to a field on the object itself (first degree), but you can also refer to a related object field through a Lookup (second or more degree). Let’s say we want to search for the field Account on the Opportunity Object: * **Lookup Fields** (Relationship to another Object) * **Other Fields** (Opportunity Fields here) In this example, we want to route any new Opportunity to the Account Owner. To achieve this, we will select the “Account” lookup field and then select the Owner ID of the Account: ![](https://help.chilipiper.com/hc/article_attachments/30080073219603) Here is what the rule looks like: ![](https://help.chilipiper.com/hc/article_attachments/30080073223315) We can also add one layer of complexity by ONLY routing these Opportunities WHEN the Account Owner is Active with these additional criteria: ![](https://help.chilipiper.com/hc/article_attachments/30080036188563) From the Opportunity Object, we will select the Account Lookup, then the Owner Lookup of this Account (User Object), and retrieve the field: “Active”. Here is the final result: ![](https://help.chilipiper.com/hc/article_attachments/30080036189843) Exploring an additional use case, let’s say we want to route any new Contacts to the Parent Account. First, we will select the Contact Object, then the Account Lookup, then the Parent Lookup![](https://help.chilipiper.com/hc/article_attachments/30080036192147) It will look like this:![](https://help.chilipiper.com/hc/article_attachments/30080073243155) To achieve a Lead to Account Matching, for example, this relationship does not exist as these two objects are not connected in Salesforce's architecture: ![](https://help.chilipiper.com/hc/article_attachments/30080073245331) The Rule will be configured this way: ![](https://help.chilipiper.com/hc/article_attachments/30080036197651) The lookup: "Matched Account" is a smart field as it’s an inexistent relationship in Salesforce. Chili Piper plays its magic to create this connection between these two objects. ![](https://help.chilipiper.com/hc/article_attachments/30080036200211) The Matched Account is found through our [L2A Matching process](https://help.chilipiper.com/hc/en-us/articles/14008379577491). * * * ## Route to Any HubSpot Property Our HubSpot integration also supports routing to any HubSpot Property. Let's cover how to use them below: ### Lookup Fields or Other Fields When you create a Rule, you can refer to a field on the object itself (first degree), but you can also refer to a related object field through a Lookup (second or more degree). Let’s say we want to search for the Matched Deal on the Contact Object: * **Lookup Fields** (Relationship to another Property) * **Other Fields** (Contact Properties here) In this example, we want to route any new Contact to the Company Owner. To achieve this, we will select the “Matched Company” lookup field and then select the Owner name of the Matched Company: ![](https://help.chilipiper.com/hc/article_attachments/33378774759059) Here is what the rule looks like: ![](https://help.chilipiper.com/hc/article_attachments/33378760616979) We can also add one layer of complexity by ONLY routing these Contacts WHEN the Matched Company's Primary Owner's Email is Enabled with these additional criteria: ![](https://help.chilipiper.com/hc/article_attachments/33378760624787) From the Contact Property, we will select the Matched Company Lookup, then the Email Property. The lookup: "Matched Company" is a smart field as it’s an inexistent relationship in HubSpot. Chili Piper plays its magic to create this connection between these two objects. The Matched Account is found through our [Matching process](https://help.chilipiper.com/hc/en-us/articles/14008379577491). * * * ## Lead-to-Account (L2A) Matching in Salesforce Your workspace Matching settings are where you can refine how Chili Piper performs Lead-to-Account matching for Salesforce. We advise checking[ this article](https://help.chilipiper.com/hc/en-us/articles/14008379577491) for more details about this feature. ![](https://help.chilipiper.com/hc/article_attachments/30080036201875)