Tips & Tricks is series of short videos highlighting common use cases for LeanData and how to accommodate these Use Cases in LeanData.
Interested in something you see below? Follow the link to the Tips & Tricks Video to learn how to do it.
Sometimes you want to merge records, and also continue with more routing decisions and action on the merged record. Use this tip to initiate routing on merged records to continue your routing.
Always answering questions about why records were routed the way they were? Give your Users a direct link to the audit logs to investigate on their own.
Ever want to give your reps the ability to send a record through a router graph without needing admin privileges? This video will show you how.
Have Duplicate Accounts in your system? Learn how to use LeanData Duplicate Account matching to identify and flag duplicates.
As you deactivate Users in Salesforce, you will start to have records owned by these Inactive Users. Learn how to regularly re-assign records to active reps, without having to run manual batches.
There are many enrichment vendors out there. Learn how you can accommodate any enrichment software that works with Salesforce, even without a direct LeanData integration.
Learn how to associate Contacts to Opportunities in either Contact Router or Opportunity Router.
As reps come and go and contacts and Accounts get shuffled around, find out how you can keep your Contact Owners aligned with the Account Owner.
You might start to receive multiple Leads from a new company that do not match to any Account in your system. Here is a way to aggregate them together so that you can regularly review them to decide whether you would like to create an Account for them.
You want to "top off" your Account managers with fresh Accounts as they finish working their current Accounts, but you don't want any individual Account Owner to have more than a certain threshold. Here is how you would set that up with Conditional Capping and Routing Scheduler.
As a New lead continues to interact with assets on your website, it may get updated multiple times shortly after it is created, leading to routing the record twice. Here is one way to prevent double routing.
Some organizations use Salesloft cadences to manage sales engagement. Learn how you can incorporate LeanData's Salesloft Integration to automate follow up based on campaign activity.
When merging duplicate records, you might typically prefer values from the newer record. But sometimes there are specific fields and values you prefer from the older record. Here is one way you can ensure those values are preserved on the master record.
Sometimes you need to reference an alternate set of working hours different from the hours assigned to a user, or you need an entire round robin pool to have a set of working hours, even if the individuals in it have different hours. Here's how you can use SFDC queues to incorporate alternate working hours into your routing graph.
If you would like to test out different processes and measure the effectiveness of each, here is a creative way you can use Round Robins to distribute records down different paths in an unbiased and equitable manner.
For those who use both 6sense and LeanData, combining the intent data you get from 6sense with the automation you can configure with LeanData will allow you to create processes for assigning and reassigning Accounts according to intent signals.
Do you ever need to update a different record than the one you are routing, such as a Matched Account, or a Related Activity? We walk through how you can do so using LeanData's Update Record Node.
Sometimes you need to use different matches for different purposes. LeanData's Object Variables will allow you to store different matches in different Variables and reference them whenever you need them in your routing graph.
As a native Salesforce solution, LeanData is subject to any validation or duplicate prevention rules you have in Salesforce. Here is a way that you can exclude specific Users like the LeanData Integration User from your validation rules.
Keeping Round Robin pools up to date with the latest members does not have to rely on someone remembering which Users to add. If there are specific criteria that will dictate which Users should be added to a pool, you can add them easily using Conditional Membership.
You may know that LeanData can update fields, but sometimes you may need to append additional text to a field instead of replacing it entirely. Here is how to do that in LeanData Router.
Tracking the history of certain fields is incredibly useful for troubleshooting, but there are limits to how many fields you can track in Salesforce. Here is how to set up Routing Metrics Mapping to track fields in your LeanData Logs.
Do you want a way to continue routing after Lead Router converts a Lead into a Contact? Here is a way to trigger Contact Routing when LeanData specifically converts a Lead.
If you ever wanted to add a Round Robin Pool within a Round Robin Pool, here is one way you can approximate that in LeanData.
Sometimes you want to trigger a record to route depending on the prior value on a field. This will explore a way you can compare a field's new value with its prior value in order to trigger routing.