Today’s buying journey is decidedly digital-first. The result is an explosion of buyer signals — website visits, blog post reads, eBook downloads, trade show booth visits and MUCH MORE.
UserGems saves 10 to 20 hours a week that was formerly spent troubleshooting routing issues, writing custom Apex code or creating their own solution with standard Salesforce functionality.
With LeanData, speed to lead and accountability are now built into the lead management process for F5 allowing them to improve the customer experience.
Sometimes you are uploading a large list or making some bulk changes to records, and you want to skip or bypass LeanData routing for these records. Here is a way to exclude these records from LeanData Routing without affecting routing for other records.
If you use multi-select picklists, you might want to use something like the “contains” operator to look for one of several different values in a field. Even though there isn’t a contains operator , here are two ways you can set up your nodes to look for a one out of several options in a multi-select picklist.
Sometimes you want to trigger a record to route depending on the prior value on a field, such as triggering on an increase in Lead score, but not a decrease. This will explore a way you can compare a field's new value with its prior value in determining when to trigger routing.
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.