--- title: "Lead-to-Account (L2A) Matching in Workspace Matching Hub" source_url: https://help.chilipiper.com/hc/en-us/articles/14008379577491-Lead-to-Account-L2A-Matching-in-Workspace-Matching-Hub article_id: 14008379577491 updated_at: 2026-07-24T18:56:01Z content_hash: fa13107d --- ## 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) When the triggered record is a Lead in **Salesforce**, but the evaluation of how to assign or make changes to this record is based on Account data, Chili Piper will need to use Lead-to-Account (L2A) matching logic to decide which Account to match to. The Matching settings will be relevant to [Distro](https://help.chilipiper.com/hc/en-us/sections/8298371316883-Distro), [Concierge](https://help.chilipiper.com/hc/en-us/sections/28558396528531-Concierge), [Handoff](https://help.chilipiper.com/hc/en-us/sections/29684376670099-Handoff), [Chat](https://help.chilipiper.com/hc/en-us/sections/27531015253395-Chat), and [ChiliCal Scheduling Links](https://help.chilipiper.com/hc/en-us/articles/29763780952467-Scheduling-Links-in-ChiliCal) and their respective [User Controls](https://help.chilipiper.com/hc/en-us/articles/29685472294803-User-Controls-in-ChiliCal) and [CRM Actions](https://help.chilipiper.com/hc/en-us/articles/29767375437203-CRM-Actions-in-ChiliCal). This process involves initially following our default matching algorithm and subsequently configuring the settings that can be configured through the Matching settings page, which will be explained next. #### Table of Contents: - [How to Enable or Disable the Lead-to-Account (L2A) matching in a Workspace?](#h_01H69PDXEF8ATTF7MPYPFHSD9K) - [Filtering Matches](#h_01H69PE1MXG09CE9P7M35HDRQ2) - [Tiebreakers](#h_01H69PE5Y7ESF6JNYYGC4GW0MX) - [Lead-to-Account Rules](#h_01H69PEAG3T5WY1WVPRA5SVBMH) ## How do I Access the Lead-to-Account (L2A) matching in a Workspace It's important to mention that this setting is global, so it will be applied to all your [Distro CRM Flow Builders](https://help.chilipiper.com/hc/en-us/articles/23304655920403-Distro-CRM-Flow-Builder), [Concierge Routers](https://help.chilipiper.com/hc/en-us/articles/28918570010131), [Handoff Router](https://help.chilipiper.com/hc/en-us/articles/29684412579987-Creating-a-Handoff-Router-in-Demand-Conversion-Platform),  and/or [Chat Journeys](https://help.chilipiper.com/hc/en-us/articles/27532198601107/). - In your workspace left-side menu, under **Settings**, click on the "Matching" option:![](https://help.chilipiper.com/hc/article_attachments/31245784070931) - There, you will initially see the "CRM Lead/Person to Account" tab, where you will notice the [Default Chili Piper](#h_01J2HAD5CK69D05SEYB0C0XRWV), [Salesforce](#h_01J2HAD06Y0KRMHGSVHVXF912P), [Filtering](#h_01H69PE1MXG09CE9P7M35HDRQ2), and [Tiebreaker](#h_01H69PE5Y7ESF6JNYYGC4GW0MX) sections that will help you configure your Lead-to-Account (L2A) logic for the workspace.Each one of these sections will be covered in more detail below. Before proceeding, notice the updates in this section are **auto-saved**, so there is no need to publish changes or confirm anywhere else.![](https://help.chilipiper.com/hc/article_attachments/31245784073363) ## Default Chili Piper and Salesforce You can combine Chili Piper's matching algorithm with Salesforce deduplication rules to build your Lead-to-Account (L2A) matching logic, use just one of them, or disable both if it makes more sense to your use case. In this section, we will explain how the Default Chili Piper algorithm and the Salesforce one work. By default, the Lead-to-Account is enabled, but you can fully disable it (or enable it back) by toggling the following button on/off: ![](https://help.chilipiper.com/hc/article_attachments/31391406570259) Also, note that any updates done on this page are **auto-saved**.   ### Default Chili Piper You will notice two different logics within the Default Chili Piper Algorithm: Contacts and Accounts. Let's cover them separately below:   #### Contacts The algorithm will extract the record's (**Lead**) domain (acme) and extension (.com) to find **Accounts** that have**Contacts**with the same domain and extension in your CRM. If there's a match, then the related Account(s) will become a potential match: ![](https://help.chilipiper.com/hc/article_attachments/31245788953363)   #### #### Accounts As a fallback, you can match Accounts by their website domain. If enabled and no matching Contacts are found, Chili Piper will check if the Lead's email domain matches the Account's website domain field in your CRM. If there's a match, the Account will be considered a potential match. If enabled, for this example, we would follow this logic: - A [Distro CRM Router](https://help.chilipiper.com/hc/en-us/articles/23304655920403-Creating-a-Distro-Router), [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), [ChiliCal Scheduling Links](https://help.chilipiper.com/hc/en-us/articles/29763780952467-Scheduling-Links-in-ChiliCal) or [Chat Journey](https://help.chilipiper.com/hc/en-us/articles/27532198601107-Creating-a-Journey-in-Chat) evaluates johndoe@acme.com - Suppose no Contacts are using the @acme.com domain in Salesforce - However, there's one Account that has the website field populated with [www.acme.com](http://www.acme.com) - [Distro](https://help.chilipiper.com/hc/en-us/sections/8298371316883-Distro), [Concierge](https://help.chilipiper.com/hc/en-us/sections/28558396528531-Concierge), [Handoff](https://help.chilipiper.com/hc/en-us/sections/29684376670099-Handoff), [ChiliCal](https://help.chilipiper.com/hc/en-us/sections/22410530826003-ChiliCal) and/or [Chat](https://help.chilipiper.com/hc/en-us/sections/27531015253395-Chat) perform the necessary extractions and see that @acme.com from the email matches acme.com from the website field - The Account above will be considered a match because this setting is enabled. Otherwise, there would be no match. ![](https://help.chilipiper.com/hc/article_attachments/31245784083731) You can enable or disable each of the algorithms explained above separately by toggling the On/Off button next to it. If you disable both, Chili Piper's algorithm will be consequently off. ![](https://help.chilipiper.com/hc/article_attachments/31245784092051)     #### Optimize Results If you have a massive Salesforce database with 100 million or more accounts, finding the right account will take a lot of time because of the number of records. This optimize results toggle uses a different technology to perform the query. Instead of SOQL (Salesforce object query language), it uses SOSL (Salesforce object search language), which works better for large databases. This option is not activated by default, but it will help if you are experiencing a high delay.   ![](https://help.chilipiper.com/hc/article_attachments/39756866650643) ### Salesforce In addition to the default Chili Piper algorithm, Chili Piper can leverage Salesforce Duplicate Rules to find more potential candidates for Lead-to-Account Matching. You can enable or disable it using the button on the right: ![](https://help.chilipiper.com/hc/article_attachments/31245788971027) If enabled, clicking the "Add Salesforce Duplicate Rule" will display the active Deduplication Rules you have in Salesforce. Click the checkbox next to the ones you want to add for evaluation to add them.  You can also re-order the priority which these rules will be checked by dragging them: ![](https://help.chilipiper.com/hc/article_attachments/31245788973715) If you notice some rules are grayed out, like the ones below, they are inactive in Salesforce. If you plan to use them in Chili Piper, activate them in Salesforce first. ![](https://help.chilipiper.com/hc/article_attachments/31245784102035)   ### What If We Have Multiple Matches? If a prospect matches with multiple Accounts after checking your enabled algorithms, we will use [Filtering](#h_01H69PE1MXG09CE9P7M35HDRQ2) and [Tiebreakers](#h_01H69PE5Y7ESF6JNYYGC4GW0MX) to get the best result.  ## Filtering _****_**Data Field Mapping** Filters rely on CRM fields. Ensure your Data Field mapping is set up correctly to avoid record leaks. [**Check this article**](https://help.chilipiper.com/hc/en-us/articles/27607845025555-Setting-up-Data-Fields) for more details on how to set up Data Fields for your team. A filter can be used to tell [Distro](https://help.chilipiper.com/hc/en-us/sections/8298371316883-Distro), [Handoff](https://help.chilipiper.com/hc/en-us/sections/29684376670099-Handoff), [Concierge](https://help.chilipiper.com/hc/en-us/sections/28558396528531-Concierge), and/or [Chat](https://help.chilipiper.com/hc/en-us/sections/27531015253395-Chat) which Account should be considered only if there is more than one possible Account matching after checking the default matching algorithm. Two types of Filters can be created: - Account filters that include/exclude potential matches based on Account field values (**Value**). - Account/Lead comparison filters that allow you to include/exclude potential matches based on how field values compare to the Lead and potential Account matches (**Lead/Person**). For example, suppose that johndoe@acme.com matches multiple "ACME" accounts in your Salesforce instance. In this case, we can use Filters to narrow possible matches by setting. Let's see one example where we set two filters: - Account's Customer field should be the True **AND** - The Account Name does not contain the word "Test": ![](https://help.chilipiper.com/hc/article_attachments/31391406578067) Still using the same example, let's set one more Filter to check if the Account's Phone field is equal to the one as the Lead/Person's Phone field: ![](https://help.chilipiper.com/hc/article_attachments/31391392702227) **Always double-check if you are using the right operator (AND/OR). You can switch it by clicking on it:** ![](https://help.chilipiper.com/hc/article_attachments/31391392712723) **Note:** The fields used above are examples. In your workspace, you will see a complete list of standard and custom fields based on the configuration of your Salesforce instance. ## Tiebreakers _****_**Data Field Mapping** Tiebreakers rely on CRM fields. Ensure your Data Field mapping is set up correctly to avoid record leaks. [**Check this article**](https://help.chilipiper.com/hc/en-us/articles/27607845025555-Setting-up-Data-Fields) for more details on how to set up Data Fields for your team. If, after checking Filters, there is still more than one possible Account match, Tiebreakers can be used to prioritize further which Accounts should be selected. Tiebreakers include standard and Smart field options to help you prioritize the right Account. There is no limit as to how many Tiebreakers you can have. Additionally, you can create a list of Tiebreakers that can be ordered based on priority and help to match with the expected Account.    In the example below, we created a list of Tiebreakers that will be checked from 1 to 3 until we have a match: ![](https://help.chilipiper.com/hc/article_attachments/38004524403219) Note that the smart Tiebreaker fields below are not standard fields in your Salesforce instance but rather special fields created by Chili Piper that are available for the Account object: - Number of Children - Number of Matched Contacts - Number of Contacts - Number of Opportunities You can re-order the priority of conditions by dragging the Tiebreakers up and down the list: ![](https://help.chilipiper.com/hc/article_attachments/31391392729875) Also, it's important to note that the default Tiebreaker **can't** be deleted. It ensures that you have at least one unique match for evaluation. For example, you can re-order to be the last evaluated in the list, like in the above gif, where the _Account Created is maximum_ Tiebreaker was moved from #1 to #3, but not removed from the list. ## Lead-to-Account (L2A) Rules Let's see how we can apply the L2A Matching to a real use-case example:  ![](https://help.chilipiper.com/hc/article_attachments/32095267891859) These rules evaluate if the**existing Lead** matched **Account** (#1) **OR** if the **net-new record's** **Account** (#2) company size is 501-1000. L2A rules also have two operators: **null / is not null,**allowing you to match and Enable the Lead to Account, making it easier to exclude Account-related rules when combining them with other objects. **null** -> Maps to an empty field or a record that does not exist. **is not null**-> Maps to a non-empty field or existing record. These operators can be used to evaluate Account data if necessary. We can force object checks using this type of Rule (it works for any type of object).   ### 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:   #### 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/31892841122835) Here is what the rule looks like: ![](https://help.chilipiper.com/hc/article_attachments/31892849778067) 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/31892841133715) 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/31892849787667) 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/31892849789843) It will look like this:![](https://help.chilipiper.com/hc/article_attachments/31892841145875) 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/31892841151635) The Rule will be configured this way: ![](https://help.chilipiper.com/hc/article_attachments/31892841155859)   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/31892841158291) [**Click here**](https://help.chilipiper.com/hc/en-us/articles/30080073275027-Rules-in-Chili-Piper-s-Demand-Conversion-Platform)if you'd like to learn more about how to build Rules for your Chili Piper products.