Otto can help you find answers quickly!

Beginning with LeanData Version 1.557 (April 2021), LeanData will be expanding the time-based capabilities available in Router, allowing you to take speed-to-lead and SLA management to a whole new level.

 

Introducing the Hold Until Node

With this change, LeanData will be introducing the Hold Until node, which will hold records for a designated time frame or until the record meets one of its edge conditions. Upon meeting a condition, the record will be processed through the corresponding edge, without waiting for the remaining time frame to elapse.

The Hold Until node will replace the current Time-based node, which could only evaluate conditions at the end of the specified time frame. With the Hold Until node, records will no longer have to wait for the full time frame to elapse before proceeding down the appropriate edge.

Existing Time-based nodes will continue to operate normally, but new Time-based nodes will no longer be available from the Node Bar nor by copying an existing Time-based Node.

 

New Time-to-Action Tracker Object

In addition to the expanded routing capabilities, the Hold Until node will also introduce a new Time-to-Action Tracker object that will capture the date/time of record assignments through the Hold Until node and auto-calculate Time-to-Action metrics. User Schedules can also be taken into account when calculating metrics. This will allow you to expand your reporting capabilities.

 

Summary of Benefits

Here are the key benefits you can expect from the Hold Until Node:

• Optimize speed-to-lead
• Ensure timely follow-up
• Identify bottlenecks and deliver a better prospect/customer experience
• Report on follow-up times by rep and source
• Measure SLA metrics by source, score, campaign, etc.

For more information, please see our guide on the Hold Until Node & Time-to-Action Tracker.

We also have a guide that will help you build out Time-to-Action Reporting in Salesforce.

For help in migrating to the new functionality, please see this article on Migrating from Time-Based Nodes to Hold Until Nodes.

 

Frequently Asked Questions

When will these new features be released?

• This functionality will be available in Q2 2021, beginning with LeanData version 1.557.

 

What will happen to my current Time-Based nodes?

• Time-Based nodes that are already in your graphs will continue to function as they always have. Existing nodes will not stop working due to this transition. You can modify these existing nodes and re-deploy graphs containing them. 

 

Can I add more Time-Based nodes to my graphs after upgrading to a version using the Hold Until node?

• Once you are upgraded, your existing Time-based nodes will continue to operate normally, but you will no longer be able to add new Time-Based nodes to any graphs. You will also not be able to make a copy of any existing Time-Based nodes. You can utilize the new Hold Until node for any new time dependent actions you need to incorporate. 

 

Can I edit and deploy graphs that have existing Time-Based Nodes in them?

• Yes, as long as the existing Time-Based nodes are already in the graph, you can still deploy these graphs when they are ready to go live.

 

I need the full time frame to elapse before evaluating the conditions. Can I still use the new Hold Until node?

• If your use case requires that the full time frame elapses, you may still use the Hold Until node as a wait step and then direct records to a decision node with the corresponding conditions after that wait step.

 

Will the Hold Until node respect User schedules?

• Yes, the Hold Until node will retain the functionality to respect the current owner's schedule while elapsing the specified time frame. Time-to-Action metrics will also be calculated to account for Users' schedules in addition to capturing the raw time to action (without schedule calculations).

 

What if there is functionality that I am currently using that cannot be replicated with the Hold Until Node?

• Your existing Time-Based nodes will still operate normally, even after the transition. But as we want to ensure all of your use cases are covered with the Hold Until node, please contact our support team if you have a use case that cannot be supported with the new Hold Until node.