---
title: "Enhanced SLA Tracking in LeanData"
id: "45899"
type: "resources"
slug: "enhanced-sla-tracking-in-leandata"
published_at: "2026-06-17T23:49:17+00:00"
modified_at: "2026-06-17T23:50:14+00:00"
url: "https://www.leandata.com/resources/enhanced-sla-tracking-in-leandata/"
markdown_url: "https://www.leandata.com/resources/enhanced-sla-tracking-in-leandata.md"
excerpt: "Measure precise time to action with LeanData's Track SLA Node, ensuring that your most valuable leads are being followed up with promptly."
taxonomy_topic:
  - "Intelligent Go-to-Market Orchestration"
taxonomy_role:
  - "Operations"
taxonomy_content_type:
  - "Video"
---

Video

# Enhanced SLA Tracking in LeanData

Intelligent Go-to-Market OrchestrationOperationsVideo

LeanData’s [Track SLA Node](https://support.leandata.com/s/article/Track-SLA-Node-and-Time-to-Action-Tracker)
 extends the capabilities of FlowBuilder, allowing you to evaluate SLA criteria during a specified time frame and measure time-to-action. Records are held in the node until the conditions are met or the SLA Timer expires, with the option to continue tracking time beyond that window. The Track SLA node also supports tracking multiple concurrent SLAs on a single record and sending reminder notifications before the SLA expires.

As records enter and exit the Track SLA node, a corresponding **Time-To-Action Record** is created for reporting purposes, capturing information about when the record entered, exited, and whether the SLA was met or expired.

Want the full conversation? [Watch it here.](https://www.leandata.com/resources/whats-new-leandata-june-2026/)

## Video Transcript

Click to Open

So we are updating our hold until node , to be called the track SLA node to better match , you know , that use case you will obviously wanna use , for SLA tracking . And we also added a series of big , updates to the node itself , so that it does have more , SLA tracking and governance capabilities . So even one use case we hear often is , like , today , if you actually wanted to track multiple SLA actions , like , there’s actually multiple steps and things that a rep needs to do , you would have to chain multiple pulled into a note in order to do it , just because it exits after , like , one rule is met . The other thing that we also often hear from customers is , like , sending SLA reminder alerts also needs to be changed because , you know , let’s say there’s , like , thirty minutes left before SLA expires . You actually need to configure that send notification node . Essentially , exit that first hold until node , configure that send notification node , and then go back into another hold until node . So , yeah , we made some updates . We’re trying to make that a lot easier . So within the track SLA node , it can now handle multiple SLA rules so that you don’t actually exit that node until all the rules are met . And then we allow for tracking the specific amount of time it took for each of those rules to complete as well as in total how long did it take , for SLA to be met as a whole . Within that note itself , now we built in those reminder notifications so you no longer need to exit those notes . It supports email , Slack , and Teams so that you can just automatically send out those up those , those notifications , without exiting note itself . Overall , this should make time to action tracking a lot simpler because , you are still tracking that under one time to action tracker object . The last thing we did here is we do have this new optional , set optional feature here where you can actually extend how long that that record is being hold held in that node , even after SLA is met . So , you know , you might actually want to see how long your rep ultimately did it , didn’t take the action , and you have some leeway in terms of , like , hey . Like , they didn’t do it in the four hours , but if they do it in the next hour , we’ll keep it to that rep . We now allow you to do that just within that SLA note itself . Yeah . That that’s great . Personally , that’s one that I’ve been waiting for for a while , as far as extending that , tracking . You know , obviously , this is a lot of additional functionality , stuff that you couldn’t do before or you kind of had to do some workarounds to kinda get at that , approximate that . For folks who’ve been already using our old hold until node and building time to action tracker reports , does this because we’re tracking different things here . So does it change how they would need to structure the reports ? Do they have to change their existing reports ? How does that kind of affect the reporting aspect of things ? Yeah . So we built it to kind of , make the changes pretty minimal in terms of your time to reporting . If anything , this actually gives more detail , that you can add in your reports for time to action tracking . You can track those individual rules , for example . But there are some updates that are made . It’s gonna be in the new package . So you’d have to update your package to get those new reports Okay . If you are using another box reports