- Step 1: Getting to Know LeanData
- Step 2: LeanData Basics
- Step 3: LeanData Routing
- Step 4: Advanced LeanData Routing
- Step 5: Troubleshooting LeanData
In this step we are going to get to know LeanData Router. As with our other tools, it's vital to practice with the tool to gain proficiency. SFDC Dev (Sandbox) Environments are great for practicing your skills without affecting your production environment. Even if you are the only LeanData admin we strongly recommend using a Dev environment to work on until you are ready to make changes in your production SFDC organization.
For our first part we will be learning how to use Lead Router. For this we have an overview guide for the Lead Router. This guide walks you through basic router actions, working with our brand and node design tool, and provides an introduction to using some of the various nodes we have available.
Now that you have some basic information on how to build a Lead Router Graph we can start looking at some of the nodes that are most common. All nodes are divided into 1 of 4 types; Entry Nodes, Decision Nodes, Match Nodes, and Action Nodes.
Routing starts with getting Leads into your graph through several special Entry Nodes. Below we will cover 2 of them.
The New Entry Node is a persistent node that will be added to all Router Graphs. It is designed to take in new leads as they are entered into Salesforce, either by importing, from a marketing automation tool, or by a user. This node cannot be deleted but there is a way to turn it off if you do not want to route New Leads.
The Updated Entry Node is the other persistent node that will be added to all Router Graphs. It is designed to route leads that are updated to match your trigger conditions such as Lead Status = Marketing Qualified Lead. This node cannot be deleted but there is a way to turn it off if you do not want to route Updated Leads.
The decision nodes give you the ability to question the data and route the Lead object based on the answer to the question. Below we will cover 2 of the Decision nodes.
The True-False node allow you to ask Yes/No True/False questions and route based on the answer. This is useful for simple sorting like is the lead valid, is this lead hot, or is this a lead for a customer account.
The Branch Node is great for asking questions with multiple possible answers. The Branch Node is useful for routing when there are multiple answers and the Graph needs to pick one for routing. Use a branch node when you need to separate leads by region, company size, or revenue tiers.
Match nodes are used to match the routed lead record to other objects like Accounts, related Leads and Opportunities. Matching is based on our best in class, proprietary fuzzy matching logic. Once you match to another object you can route based off of the other object such as checking for Leads matched to Accounts that are partner accounts.
The Lead2Account match node is the primary match node for customers that want to match new leads to existing account. The L2A node is designed to filter the potential account matches and then if more than 1 match remains, the node will apply tie-breakers to choose the best match. You can route based on if the lead matches to an account or not.
The Lead2Lead node is typically used when there is no account match. The L2L match node is used to match the routed Lead to a related Lead. A related lead is just another Lead for the same company (not account) as the routed Lead.
The Lead2Opportunity node is used to match the routed Lead to an open opportunity on a matched account. This node is used after a Lead2Account node in your graph. This node gives you the ability to use filters and tie-breakers with your opportunities to identify the best one.
These are only a few of the Match Nodes we have available. When you are ready to explore the other Match Node options click here.
Action nodes are used to assign Lead ownership, make changes to the routed Lead, even convert Leads, and create new objects in your router Graph. Below we have a few examples of the most common Action Nodes but this list is not all of the Action Nodes available.
The Assign Owner Node one way to assign an owner to the routed Lead. This node has several options for choosing who the owner of the lead should be. The Assign Owner node can also be used to assign a user to an alternate field instead of the owner. For example, this node can assign a Partner Rep or a CSM to a Lead.
The Convert Lead Node is used to convert a routed Lead into a Contact under a matched account.
The Route to Matched Account Node is another node used to assign ownership of a routed Lead. A route to node like the Route to Matched Account node is used to assign the owner of a node based on the matched Account identified by a L2A or Lead2Account Match Node. This node has more options based on the matched account.
Time based routing is used to delay routing until a condition is met or the time runs out. We have the Hold Until Node to manage the time based routing. With this Hold Until node you can hold a routed Lead until a condition you specify has been met or a timer runs out. If the Lead meets the set condition it will route as soon as possible. If it doesn't meet the condition it will route when the timer ends.
Some Example Graphs
We've put together some sample routing graph templates that you can download and use for practice or ideas. Simply download them from the Help Center and import them into your LeanData instance
We've talked about Lead Router up until this point and that's because all of the routers have basically the same structure but different objectives. We recommend reviewing the Lead Router Guide and any of the following Object Type Router guides that you will be using.
In Step 4 Advanced LeanData Routing, we will go over using some of the advanced features of LeanData's Lead Routing.