Contents:

• Overview
• Customization
• Variable to Merge
• Advanced Settings

 

Overview

The Cloudingo Integration deduplicates Leads and Contacts as they’re routed through your graph, reducing any need for manual triage. 

Leverage the Cloudingo node to select the duplicate record (i.e. Matched Lead) that will be used to merge with your routed Lead. The two records will then be sent to Cloudingo and merged based on Cloudingo’s Merge Settings which can be configured to preserve values on a field-by-field level. 

Use Cases:

• Enhance Data Quality: Instantly identify duplicate Leads and Contacts and specify fields that should be prioritized, kept, or combined during merging. Examples include:
  • Preserve Original Lead Source Fields: Merge duplicate Leads and keep the Lead Source and Lead Source Detail fields on the oldest record to know exactly where the Lead originally came from.  
  • Prioritize Working Status Field: As new Leads enter Salesforce, check for duplicate Leads. If one exists, merge it with the new Lead record. If the existing Lead’s Status happens to be “Working,” ensure this status is kept during merging to prevent any disruption to an existing sales cycle. 
  • Preserve Do Not Call Field: Merge duplicate Contacts as they are identified; If one of the Contacts has a “Do Not Call” field checked, ensure it is never overwritten when the duplicates are merged. 
  • Sum Lead Scores: When merging duplicate Lead records, sum the Lead Scores to help sales and marketing teams prioritize efforts effectively. 
  • Append Notes: Carry over Notes on any duplicate Lead or Contact to provide teams with all the context they need to make the right engagement. 
• Accelerate Speed-to-Lead: Eliminate duplicates as records are routed through your graph, eliminating any need to wait for deduplication to happen at a specified time. With real-time deduplication in LeanData, confidently route records to the right rep for appropriate follow-up. 
• Maximize Rep Efficiency: Eliminate time wasted on manual duplicate triage and record assignments. Clean duplicate Leads and Contacts as they’re routed, and assign them to the right owner to ensure your reps are always acting on reliable record data. 
• Improve Marketing, Sales, and CS Alignment: Eliminate dirty data that creates orchestration breakdowns across functions and inconsistencies in Salesforce reporting. Clean duplicate records as they’re identified, improve account insights in sales cycles, and create reports that all revenue teams can trust.

 

Customization

You have a number of options to configure the node to fit in your Lead / Contact Router Graph.

• Node Name
• Description
• Variable to Merge
• Advanced Settings

 

Node Name

By default, the Node Name is set to Cloudingo Merge. You can change this label to anything you need. We strongly recommend giving this node a meaningful name such as the subject of the assignment. 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. By default, the field is hidden under the word Description. Click the arrow to the side of the word Description to expand the field.

 

Variable to Merge

Which variable would you like to merge in Cloudingo?

This section displays the default variable selected to be merged with the Routed Lead in Cloudingo. This variable is the existing Lead that the Routed Lead matched to in a Duplicate Match Node. If you have another variable to replace the default variable, you can use this field to select it. The object type is locked to Lead.

 

Advanced Settings

The Advanced Settings section gives you fallback options for the routed records. 

• Configuration Error -  If the integration cannot connect to Cloundingo, the routed record will follow this edge.
• Variable Not Found - If the selected variable is not available at time of routing, the Routed Lead will follow this edge.
• Invalid/Inactive User - If the user associated with the Routed Lead is invalid or inactive at time of routing, the Routed Lead will follow this edge.

Working with Edges

You can Connect nodes in one of several ways:

1. 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.

 

2. 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.