Contents:

• Overview
• Customization
• Filter Duplicate Contacts
• Prioritize Matched Contacts
• Advanced Settings
• Summary

 

Overview

The Duplicate Contact (DupeC) Match Node is used to identify Contacts in your Salesforce account that are duplicates of the routed Prospect. Once the duplicate Contact has been identified, you can route the Prospect to a user on the Contact record for scheduling. The Duplicate Contact Match Node also includes filters and Tiebreakers to help you identify the best duplicate Contact record if there are multiple potential duplicate Contacts.

 

Example: David is the LeanData admin for Lighthouse Development. In his BookIt Router flow, he needs to match the routed Prospect to their duplicate Contacts. He configures the DupeC Node, with Filters and Tiebreakers to match to the duplicate Contact. Using the Filters, he ensures that the routed Prospects are not matched to any Partner Contacts. He then routes the Prospect to the Duplicate Contact for scheduling

Each Match node includes Tiebreakers to identify the best matched record if there is more than 1 possible match. Tiebreaker rules are included in the node configuration to pick the best match when LeanData finds multiple duplicate Contacts. These Tiebreakers function just like the Tiebreakers in Tagging. The Tiebreakers on the node are local only to the node. Any changes made to the node’s Tiebreakers do not affect the Tagging Tiebreakers or even the Tiebreakers on other match nodes.

 

Customization 

You have a number of options to configure the node.

• Node Name
• Description
• Filter Matched Contacts
• Prioritize Matched Contacts
• Advanced Settings

Node Name

By default, the Node Name is set to Match Node. You can change this label to anything you need. We strongly recommend giving this node a meaningful name such as the goal of the Match Node or simply Prospect to Contact Match. This will help others understand the purpose of the node. 

Description
This field is not required but we recommend adding a description to document any customizations made to the node. If someone else needs to take over the management of the flow, the description will help them to understand the goal of the customizations.

 

Filter Duplicate Contacts

Use Filters to include or exclude duplicate Contacts from matching to the routed Prospect. In our example, we are excluding Contacts that have a bouncing email address (Email Bounce Date Before Today). This ensures that we will not match the routed Prospect to a duplicate Contact record that has an email that is bouncing.. 

 

Value/Variable

The Value/Variable selector lets you choose between filtering for a value in a field on the duplicate Contact record and/or comparing a field on the duplicate Contact record with a variable on the routed Prospect.

 

When using Value, you are looking for a specific value in a field on the duplicate Contact record. For example, if you wanted to exclude any Duplicate Contact with a bouncing email from matching to the Prospect you could configure the Email Bounce Date with the Before operator and the relative date of Today.

When using Field, you are comparing the value of a field on the duplicate Contact record with a field on the routed Prospect. For example, if your goal is to compare the Mailing Country field on the duplicate Contact record to the Country variable on the routed Prospect, you could select the Mailing Country field from the duplicate Contact Field and Country for the Variable on the Prospect. Setting the Operator to Not Equals ensures that the Logic rule will exclude any Duplicate Contact with a different country from matching to the routed Prospect.

For each condition you add, you will see:

• Field: The Field selector will give you a list of all the fields on the duplicate Contact record that you are filtering.
• Operator: The Operator gives you a condition to apply to the field for the decision. (Example: Contains, does not contain, starts with, is null, etc). The values in the Operator selection change depending on the field selected.
• Value/Variable: The Value is the value you are evaluating against in your selected field. This is typically a pull-down menu of possible values. If you select Variable for Value/Variable, you will see a pull-down of Variables on the Prospect.

You can add as many conditions as needed to create the desired Filters.

Working with Multiple Conditions

When you edit or add rules, you can have multiple conditions.  When you have a rule with multiple conditions you are given the option to specify the relationship between the conditions. By default, you will see an AND relationship. You can change this to OR as needed. You can also use parentheses to group conditions together. Example: ((1 AND 2) OR 3).

 

In the example above we use an AND relationship because we are looking to exclude Contacts that have bounced emails AND have a Mailing Country different from the Prospect’s Country.

Exclude Matched Contacts with Inactive Owners

This option, when checked, will prevent LeanData from matching to duplicate Contacts with inactive owners.

 

Prioritize Matched Contacts

In the Prioritize Duplicate Contacts section you will see a list of rules called Tiebreakers. These rules are applied after filters if there are multiple duplicate Contacts that can match to the routed Prospect. Tiebreaker rules are processed from the top down and are used to narrow the pool of possible duplicate Contact matches down to the best match. The node will check each rule, one at a time, from top to bottom, until only one remaining potential duplicate Contact remains. This duplicate Contact will be matched to the routed Prospect. The Dupe node includes a set of default Tiebreaker rules. You have the following options to modify the Tiebreakers:

• Edit the existing rules
• Add/remove rules
• Change the order of the rules

Please Note: You will see error icons for any tiebreakers that use variables that were not mapped in your New Prospect Trigger. You will need to either delete the tiebreaker rules or map the Variables in your trigger node.

Editing a Rule

To edit a rule, simply click in the rule to open it for editing. You will see the same options as in the Filters.

 

Adding a Rule

If you choose to add a custom Tie-Breaker Prioritization Rule, click New Rule. There are three rule types; LOGIC, SOQL, MIN MAX.

 

• LOGIC - When configuring a new logic rule, you can use a Field or Field Value from the duplicate Contact level. This works the same as adding Filters.
• SOQL - You can use a SOQL (Salesforce Object Query Language) string here. More Info
• MIN MAX - The field you are choosing is the duplicate Contact level field. Set the Operator to either Min or Max. Min meaning the lowest possible value and max being the highest. For Date and Time fields, Min equals the oldest date and Max equals the newest date. When applied to time MIN is the oldest time and MAX is the most recent or further into the future.

For example, Mel the LeanData Admin wants to build a tiebreaker rule that will look for the duplicate Contact with the Min (oldest) created Date. She sets the duplicate Contact Created Date to MIN to ensure the tiebreaker looks for the oldest duplicate Contact that matches.

 

Advanced Settings

Under Advanced Settings there are options for setting the targets for the node edges.

Node Edges

There are 2 exit edges from a Match Node. Under the Advanced settings you can select a target node for each of the edges for what you would like LeanData to do in each of these scenarios.

 

• Match: LeanData has identified a best match based on the algorithm, after applying your Tiebreakers and Filters.
• No Match: LeanData has not identified a match, after considering your Filters.

 

Summary

Duplicate Contact (DupC) Match Node is used to match a routed Prospect with the best duplicate Contact record in your Salesforce account. The DupC node uses filters and Tiebreakers to identify the best duplicate Contact record to match to the routed Prospect. 

For more information on working with BookIt router flows please see our BookIt FlowBuilder Guide.