Contents:

• Overview
• Customization
• Node Edges
• Things to Know & Best Practices
• Summary

 

Overview

The 6sense Branch Decision Node allows you to make branching logic based on the criteria on a record or on a record you previously matched using a Match Node. Use a Branch node to determine if a certain condition is met and then determine which path the Lead record should take. This node allows for unlimited outcomes. If you have multiple rules that require more than 2 outcomes (such as geo, industry, company revenue size etc), you must use the Branch decision node.

Use Cases:

• Route Leads by Intent Level: Assign leads to Reps based upon the level of intent and buying stage found in 6sense, referencing the LeanData matched account.

You will find the 6sense Branch Decision Node on the Decision Node menu of the Node Selector.

 

Example

In the following example graph we are using a 6sense Branch Decision Node to route Leads based off of the 6sense Intent level. For low intent, we are routing the Lead to an email notification to the Rep. For high intent, we are routing to an Intent SLA using a Hold Until Node. If the time expires and the Rep has not acted we send the Lead to a Slack Node to remind the Rep to take action on this buying signal.

 

Customization

You have a number of options to configure the node to fit in your Account Router Flow..

• Node Name
• Description
• Compare Matched Account to Routed Lead
• 6sense Conditions

 

Node Name

By default, the Node Name is set to 6sense Branch. You can change this label to anything you need. We strongly recommend giving this node a meaningful name such as the subject of the decision. This will help others understand the purpose of the node. For our example, we would call this node, 6sense Intent Level Branch.

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.

Compare Matched Account to Routed Lead

Use this setting to select the variable which contains the Matched Account you want to compare the Routed Lead with.

Optional: Select a different Matched Account to compare. Most users leave as default.

 

6sense Conditions

Use the 6sense Conditions to create the rules to route based on the information from 6sense such as 6sense Intent level or other 6sense fields from the 6sense integration.

In our example we are routing based on the 6sense Date. You can use any 6sense, Lead, or Matched Account fields for your routing decisions.

 

Node Edges

When you first open the 6sense Branch Decision node you are presented with 2 rules/edges, a blank rule/edge and a Default rule/edge. Use the suggested 6sense Account fields to set up conditions to orchestrate Accounts based on 6sense intent. Accounts showing intent can be surfaced to the right revenue team member for action

The blank rule/edge is the first of your decision edges. Edit as needed to configure the node.

After clicking Edit condition:

 

Use the New Rule Button to create a new rule and exit edge for the node.

The Default Edge

The default edge is called a fallback edge. This edge is designed to catch all the records processed through the node that do not meet the other rules set on the node. The fallback edge can be set to send the records to another node or to just end the flow. If you set the fallback to end of flow, LeanData will take no further action on the record.

 

Working with Edges

You can Connect nodes in one of several ways:

Open a node and select the Target through the dropdown next to the condition or outcome you wish to assign. Use the search functionality to narrow the scope of the results. If you want Lead processing to stop at your selected node, simply select End of Flow. 

 

Alternatively you can click the Stop Sign icon to set a particular edge to End of Flow, or click the crosshairs icon to assign that edge visually on the main flowchart graph view by clicking the node to which you would like that edge to proceed.

 

 

If you are already in the main flowchart graph view, you can click on the yellow triangle and drag the edge you wish to direct to the next node to which you would like that edge to proceed.

 

Things to Know & Best Practices

• Use Logic rules rather than SOQL conditions as much as possible.
• Change the names of the Labels as needed to help identify certain paths in the flow.
• Change the names of your Nodes so you can easily decipher the condition or criteria going through that node.
• Add descriptions wherever you can.
• You can only use a 6sense Branch Decision node that references fields on a matched record if you had previously found a matched record in a corresponding match node.

 

Summary

The 6sense Branch Decision Node is a powerful tool to apply 6sense buying signal conditions against a record and to determine the record's route through your router flow. The 6sense Branch Decision Node gives as many edges as you need to route your records. The Branch node creates an edge for every rule you add. Using the customization settings, you can create a powerful test for your records. The Branch node also includes a fallback edge to catch any record that does not meet the rules and conditions of the node. This fallback edge can be routed to another node or set to end of flow.  

 

For more information on working with router flows please see our Lead Router Guide.