--- title: "What’s New with LeanData: Product Edition | June 2026" id: "45668" type: "resources" slug: "whats-new-leandata-june-2026" published_at: "2026-06-11T19:24:54+00:00" modified_at: "2026-06-11T19:24:55+00:00" url: "https://www.leandata.com/resources/whats-new-leandata-june-2026/" markdown_url: "https://www.leandata.com/resources/whats-new-leandata-june-2026.md" excerpt: "See what's new in LeanData 8.x — AI assistant, BookIt MCP, best fit assignment, unified audit logs, and more." taxonomy_topic: - "Revenue Orchestration" taxonomy_role: - "Operations" taxonomy_content_type: - "Webinar" --- Webinar # What’s New with LeanData: Product Edition | June 2026 Revenue OrchestrationOperationsWebinar LeanData’s 8.x release is built around three themes: AI capabilities that preserve observability, scheduling improvements that remove friction, and tools that give admins more control with less effort. This session walks through each major update with LeanData’s CPO and product managers, covering what’s available now and what’s coming next. It’s required viewing for Salesforce admins, RevOps practitioners, and operations leaders responsible for routing and scheduling accuracy. ### What You Will Learn - Use the new LeanData AI Assistant to answer rep routing questions directly from audit logs — without manual log tracing - Connect any AI client to BookIt via MCP to read and write scheduling data programmatically - Configure Best Fit Assignment in the Round Robin node using rep attributes pulled from the Salesforce user object - Manage meeting reassignments, cancellations, and host changes from the meeting log with full audit history - Build and reference multiple independent account hierarchies within the same routing graph ## Why This Matters Routing and scheduling decisions happen at the intersection of speed and accuracy — and both break down when admins are buried in manual troubleshooting or working around tool limitations. This release directly addresses that. The AI Assistant reduces the time admins spend answering “why did this route to me?” questions from reps. The BookIt MCP opens scheduling data to agentic workflows without requiring custom code. Best Fit Assignment adds rep-attribute matching to round robin without sacrificing fairness. And unified audit logs with cross-object search cut the time it takes to diagnose errors or trace a record’s path across products. Each feature is designed to reduce friction at a specific point in the GTM execution chain. ## Use Cases - An admin uses the LeanData AI Assistant to answer a rep’s routing question in seconds, bypassing manual audit log review - An AI agent or custom AI SDR connects to BookIt via MCP to book, cancel, or retrieve meeting data without a UI interaction - A RevOps team configures Best Fit Assignment to route Spanish-speaking leads to bilingual reps as a tiebreaker within equal-count round robin pools - An operations admin reassigns a booked meeting from a sick rep directly from the meeting log, with Salesforce events and round robin credits updated automatically - A Salesforce admin builds separate sales and legal account hierarchies and references both within the same routing graph to identify coverage gaps ## Session Transcript Click to Open All right. Well, let’s go ahead and get started. Welcome everyone to the June 2026 edition of our What’s New with LeanData webinar. And if this is your first time attending, we… This is where we get to showcase everything that our product and development teams have been working on, and to highlight for you the features in our re- latest release that are going to have the greatest impact for your organization. Now, before we jump into it, I do have a few housekeeping items to cover first. Firstly, we do invite questions, so if you have a question, please utilize the Q&A box that you see in your interface to ask that question, and we’ll do our best to address them naturally as they come up. But in case we don’t get to your questions, we’ll make sure that we follow up and get you the answers that you need. And secondly, folks will always ask if there’s going to be a recording of this. Uh, there will be. So, we will be recording the session so that, uh, we can make that available to you following our time today. And, uh, lastly, just a quick disclaimer. Uh, we may be mentioning a few things that are still on our roadmap, and with, um, as with all things that are still in the development phase, they are subject to change. So any future roadmap items that we mention represent our current plans, but they aren’t a guarantee of delivery by any specific timeframe. So, today we get the pleasure of hearing from our different product managers, Isabelle and Daniel, on different specific features of our latest 8.x release. But first, I do want to invite Amar, our chief product officer, who just joined LeanData last year. So Amar, can I invite you onto the stage, and you can introduce yourself and maybe f- pull back the camera a little bit for us to give us more color on the direction and the trajectory of LeanData products, where we’ve come and, and where we’re going. No, fantastic. Thank you for having me, Kevin. Excited to be, you know, on my first, uh, I guess product webinar here for the company, and excited to talk to everybody who’s on. Um, I, I came from, uh, 6sense prior to this. I spent more than a decade in GTM tech. Really excited to, like, take on this opportunity and, uh, really dig in with customers into, like, all the great things that we can do and build here as a part of the platform and the horizontal orchestration layer. Um, obviously been a fan for many years of LeanData even prior to joining. And, um, you know, just to build it out, um, over the last, you know, it’s been six months. Time flies. But in six months I’ve been able to have, you know, two customer advisory boards, had, you know, 50, maybe 70 customer interviews where I’ve been talking to many of you. Uh, went through a lot of the G2 crowd reviews and, like, understanding what people’s perspectives are. Um, talking to a lot of our CSMs who are representing, you know, all the feedback coming from you. And we’ve culled through tons, hundreds of feature requests, uh, that were pending just to understand, like, what are the big themes and big things that we can go ahead and do on the product. Um, and as we looked through, we put it all together, you know, that’s kind of what brought about our 2026 roadmap plans and we’re, you know, halfway through that. Uh, in fact, you know, this week most of our customers are now experiencing all the benefits of this May release. And so, um, the three big themes that aligned for us were, one is, hey, LeanData, invest in more AI capabilities, but it came with this subte- subtext of invest in AI capabilities that really help make things simple, make things more efficient, but don’t lose the ability to still maintain that trust, still maintain that observability. And so, that’s kind of where we’ve been focusing our roadmap. Of course, the whole, like, make our admins’ lives easier. You know, all of you are our primary kind of users for the product, and what we’ve found is every little thing that we can do that saves you time, whether it’s answering questions, making configurations, making graph updates, um, you know, thinking about how round robin pools are managed, like these were the places where admins were giving us a lot of feedback. And so, that’s a key theme for us. And then the third thing that we heard was, “Hey, we know we can operate and use LeanData, you know, within, within this great UI, but can you give us more APIs? Can you, you know, give us a MCP server that can do more things?” And this is for scheduling and for orchestration for all our products. And so, we, we kind of took that to heart and, as you’ll see, reflected in a lot of the work that we’ve done and where we’re going. These are the key themes that we’re keeping in mind. And so, what are we building for here at LeanData? It’s, it’s really we want to be the orchestration layer for what we believe is kind of the agentic era, right? Where everybody is investing in this. And there is a lot of foundational things that have to happen in order to power your agentic and AI experiences that you as our customers, as companies who are going through an AI transformation, needs from a vendor like us. And so, um, what did we do in the beginning? Well, you know, Q3 of last year, this is right prior to me joining the company, um, we kind of launched our AI graph summary and graph comparison feature that was really designed to explain the artifact of these flow builder graphs that, you know, many of you have been with us for five-plus years, and you have built some really amazing graphs. The logic starts simple, but over time, there’s so many amazing things that you want to do for your business, and the graphs kind of move with it. We support all these use cases, but over time it gets a little difficult to explain what’s happened on a graph, especially for somebody new who’s joining the company. And so, that feature was very critical, very important. We released that. I know many of you are using it. But soon after, in Q, Q, uh, four, Q1, we started working on this AI inference node, and the idea was, can we bring some element of reasoning into the actual graph logic and help you do more interesting things by having this inference node in addition to all the decision nodes? Uh, a lot of requests for, “Well, can we, like, get APIs and things out of a scheduling product and connect it to our AISDRs?”Whether it’s a qualified experience or a one-mind experience or something else. Uh, we have customers who have built in-house AI SDRs. And so we kind of invested in these APIs to power those agentic experiences. Where we are today, you’ll hear a lot from the team, is just kinda doubling down on that. We, we really leaned into how do we create an AI assistant that can really help answer all these questions that come on a daily basis. Um, reps asking questions about why something, you know, routed a certain way, or a manager asking for why is something not working, or you see errors and you’re trying to get an explanation for why something happened. Uh, so that was kind of, you know, step number one, is let’s go solve this. And to do that, we also had to unify the audit logs. And in, in turn, we solved, I think, hundreds of feature requests that were around, can we see these things unified? Can we see audit logs which combines things across different objects, which combines things across different products, scheduling in BookIt? And so we kinda delivered on that value with, with this release, and I’m excited for you to see and hear, uh, what the team’s gonna present. Uh, and also, we delivered, uh, this BookIt MCP. Uh, it’s currently in beta, but we’re encouraging a lot of customers to try it and tell us what you think. But how could we connect to your agentic experiences by offering an MCP server and offering you the ability to get more out of the system, you know, answer questions around operations and reports and data that can help you drive your business in a better way. Um, and where are we going, right? So if you see the theme, the connected theme here, we wanna keep adding more skills to our AI assistant. And so where we wanna go next is, how can we have the AI assistant actually do more with the flow builder graph, be able to understand what’s going on in the graph, explain different parts of the graph- Mm-hmm… even beyond what the AI summary can do. You know, help you configure a node, optimize it, uh, help you understand, you know, diagnostics of the graph and take advantage of, you know, all the different things that you can use in a conversational experience. So that’s kinda where we’re gonna go, big part of, uh, the second half of this year’s roadmap. Uh, and you’ll see the theme of unification. For scheduling, we wanna unify all the meeting logs because once we can do that, we can offer far more sophisticated capabilities and layer on AI and do a lot more for you from a reporting standpoint, from an orchestration standpoint. Uh, and round robin pools, you know, many customers have complained about, “Well, why are these all kinda separate? Why am I managing so many duplicated pools? Can this be easier to manage, easier to maintain?” And so we’re, we’re kind of doubling down on this theme of simplicity. How do we make it really easy and simple, whether it’s through agentic experiences, whether it’s through an MCP server, whether it’s through redesigning our UI. You know, we went through a major upgrade of our meeting type creation UI, UX in our last release. So we’re doing all these investments to just make it extremely simple for admins to get the task and the job done. And, you know, I brought this slide up just to say that, you know, these are not just features which are features we’re putting out there that are meant to check the box. Like, real customers are already using these features. You know, Uber is using this to power their self-serve experience, where they have the ability for users to come on board for Uber For Business, try to self-serve. If they hit a point in the configuration that it’s too complex, they use a BookIt experience to automatically get on a call with a rep to solve the problem and get them onboarded, right? That’s, that’s real business, real dollars, real time savings to get to the promised land of a converted customer. Or Tealium, right, who is connecting their AI chat solution with our lean data BookIt logic using these APIs, using our experiences, and then automatically routing visitors when they’re known visitors to the exact rep that the person should be speaking with. And Trilliant, you know, I, I love this use case because what they’ve done is they’ve taken the advantage of not just our scheduling product, but also the AI inference node, which sits within our orchestration product. And they’re looking at all these leads that are coming in, and where the leads don’t have the right company name, they’re using the AI inference node to do more research or extract the company name from the domain name of the email address. And if that particular domain name or the email address is a Gmail or a Yahoo Mail or something else, they’re actually, like, creating a task for their auto BDR to go out and do an email to validate which is the company and who’s the person, basically get more data. And so if you look at the benefit of that, this is all about automation and increasing the quality of the meetings that are getting booked. And so when you see these kinds of use cases that are built on all these features we’ve talked about, to me, this feels like we’re hitting on the right kinda use cases that are gonna help you extract more value. So if any of these things are interesting, highly encourage you to talk to your customer success manager and learn more about all these great use cases that customers are, are doing on these capabilities. So without further ado, you know, I’m not gonna spend, uh, too much time here, but the 8.x release is power packed with a ton of amazing features, and these are the themes with which we thought about it, right? It’s how do we make things simple, but at the same time, how do we give our customers a winning edge by using AI? How do we make scheduling really effortless? And we’re constantly removing, you know, any kinds of steps that are taking place from the point of configuration to the point of meeting booking. Uh, we’re adding more and more intelligence by adding hierarchies and giving you, you know, best fit assignment features and other things that we feel are gonna make it far more possible for you to do really interesting things on your graphs. And then finally, you know, going back to just saving time, we want to provide you the ability to have a lot more governance, especially as you’re entering into, you know, more AI driven and agentic experiences.This is gonna be very critical and crucial for any platform like LeanData to give to your, to you and to, you know, our customers, to our admins, so you have the control and the visibility that you need. But at the same time, it is about helping you save time and get to the promised land faster. So with that, without further ado, I’m excited to pass it on to the team and have them tell you more about these amazing capabilities we have. Yeah, no. Firstly, you know, th- thank you for walking us through that. You know, it really shows how much thought goes into the features that we work on and put our time and attention into. And also the fact that it, it comes from actual customer feedback. That’s huge, that’s important. It’s not just decisions that folks are making in a room together, but we’re actively listening to our customers before we do these things. You know, one thing that, um, did come up as you were walking through some of the different features that we will be highlighting here, didn’t hear too much around, um, buying groups. So are… Is there any effort and development around that, and sort of what can we expect regarding buying groups? Oh, that’s a, that’s a great question. So yeah, we’ve actually been investing pretty heavily into our buying groups edition product. Uh, so what’s been happening is, is two things in parallel. So we have been updating our current product and adding more features to it, and enhancing some of the UI usability. But in parallel, we are also working in a very iterative fashion with a bunch of customers who are part of our CAT, to basically try to iterate and understand some of the other pain points that they have, create features, give it to them in this kind of pilot environment. They test it, give us feedback, and we iterate. And so the results of all of these capabilities, we’re expecting that to be, uh, hitting GA in the second half of the year. Um, features like we have an AI assistant that we’ve designed, which is meant to answer interesting questions about journeys. Hmm. We’ve, uh, created capabilities that, uh, help you have a journey list and help you prioritize that list so co- teams know what to prioritize and how to work the list. Uh, we’re working on different capabilities to add more actions and more alerting. And so we’re just taking all this feedback and constantly just iterating on this pilot, eventually with the goal to make that a part of our, our GA product. So, uh, I’m really excited to tell you guys more about that, you know, as we get closer. All right. Looking forward to hearing about that. Thanks, Amar. Awesome. Thank you. Well, I know that many folks are excited about this release, the here and now, what’s available to you at this moment. So let’s first dive into this theme of gaining an AI-powered winning edge, and the first feature that supports that is our LeanData AI assistant. So I’ll invite Isabel, our senior product manager overseeing orchestration, and invite you to the stage to tell us about this AI assistant. Cool. Thanks, Kevin. Um, hey, everyone. I’m excited to talk about our new LeanData AI assistant. Um, so this is a new, um, jump forward in some of our AI capabilities, where we are gonna be bringing a new AI assistant into our audit logs. So with this assistant in this release, you’ll be able to kind of talk with this assistant, um, within audit logs to ask more about the s- details of specific logs and how routing, um, assignments were made. So before, you’d have to kind of go in if, for example, a rep would ask you a question like, “Hey, why did I actually get this lead? Why did this route to me?” Um, you as an admin would likely have to go into LeanData, open up audit logs for that specific object, um, that lead object, for example, and then trace back to find the specific log that that rep was asking about. After doing so, what you’d do is you’d probably read through that path, try to understand exactly what happened, what are the characteristics of the lead that made it route a certain way, and finally end up at that rep. From there, what you’d do is you’d probably try to translate that into something that the rep can understand, and then send that information back to the rep. Um, overall, a pretty long process, but we know it’s kind of a question that, um, a lot of you admins do get day to day from your reps. So the purpose of this assistant is really to help make that process easier. Um, so rather than going through that manual process, what you might do is actually just ask directly the assistant, “Hey, why did this lead named X person route to X user?” What it’s gonna do is now it’s gonna actually pull up that log for you on its own, no need to actually search that yourself, and then return the answer in natural language. That way, you can kind of read over it. Um, it’s already prepped for you to just send that back to your rep. Overall, really wanting to make that process a lot easier for you all. Um, but besides that, there are also other questions you might be able to ask, like, “Hey, why did this, why did this record ro- error?” for example, and that can hi- help you, um, kind of resolve any of the errors that might be coming out in your routing flows. We do have some additional just, like, AI assistant features that’ll help here. Um, we do have additional conversation-based threads so that you can actually have different conversations based off of, and pick u- up of, pick up on certain conversations based off of, like, what you’ve asked it before, and that’ll really help you organize your work efficiently there as well. Yeah. It sounds like a, you know, it, it’s definitely now a model that folks are used to interacting with a chat assistant in various capacities, so I think this will be a very easy thing to pick up for folks. But, um, you know, a- as for the time savings aspect, um, do you have any metrics around how much you would expect a typical admin to save on a, on a weekly basis by using something like this versus the old method that you described? Yeah, absolutely. Um, I mean, I just kind of went through that process itself on, like, how an admin, how you all might be doing this today. Yeah. Um, so I think, like, per time, like, a rep asks, like, I think that’d save you 10 minutes or so, depending on, you know, how quickly it actually takes you to look at that path. Um, so just think about that, how that expands into weekly. I think there is just a large number of time savings that can be done answering those questions so that you can actually better focus on, you know, your actual day job, which is not answering those questions. Yeah, yeah. Absolutely. Um, also another question about-So this will give you information about how something was routed, right? Um, but does it have the ability to then go a step further and then make recommendations for, let’s say, if it is a graph error or something that was set up in a certain way, to how would you want to set it up so that you get the result that you want? Yeah. So that’s actually gonna be answered with our next iteration of the AI system, which is gonna be bringing it into the flow builder itself. You’d be able to ask it questions like, “Hey, I see this error. How do I fix my graph so that, um, the error doesn’t happen again?” So that’s gonna be coming up next quarter, so kind of giving you a little preview about that. Um, so yeah, this first iteration’s gonna be mostly on logs, and then the- you’re gonna see this come up in other parts of our product, um, in the future as well. All right. Well, lots to play with now, but stuff to look forward to as well. All right. Uh, thanks, Isabelle. That was very exciting feature. Um, I think folks are really gonna enjoy it. Uh, but now we’re gonna switch gears a little bit, but we still want to remain on this theme of AI and how you can gain an edge with AI tools alongside LeanData. But we’re actually gonna jump over to the scheduling side of the house, and we’ll have a chance to talk about how AI interfaces with LeanData scheduling products. And for that, I’d like to invite Daniel, our scheduling product manager, onto the stage here to tell us a little bit more about BookIt MCP, which are two words I’m familiar with, but not together. So Daniel, can you tell us about BookIt MCP? Yeah, absolutely. Happy to. Thanks for having me, Kevin. So the BookIt MCP is one of the features we’re most excited about in ADOTX. And what the BookIt MCP allows you to do is connect, um, any AI client like Claude or ChatGPT or maybe your own AI agent, uh, allows you to connect those to BookIt and either read information from BookIt or write information to BookIt. Um, it essentially just gives you like a, a window into BookIt functionality. So I think we can kind of go through a use case here that’ll really cement this for the people, uh, listening. And so on the right, you see a Claude, uh, window open there, and there’s the question around availability for a particular pool and a particular meeting type. So an admin, admin might be asking at the start of the week, like, “What does availability look like for a particular meeting type for this pool?” And what is gonna happen is Claude is going to be able to use the BookIt MCP to pull availability for those reps, and then Claude is gonna present that information, um, however it will. In this case, it happened, uh, to present it in a report. So previously, to do something like this, you would have to, um, write custom code, or you would have to do a Salesforce report. But instead, you can just use something like Claude and the BookIt MCP to pull this information. But that’s really just, like, one small thing you could do with the BookIt MCP. We’re pretty much exposing all of BookIt, um, to be accessible through, like, AI agents or any of your AI clients. And so that’s, that’s extremely powerful because, um, an admin could begin administering BookIt through their AI clients, and reps could even begin using, um, the MCP for some of their functionality. For example, a rep might want to pull all of their booking links and be able to just grab one and drop it in an email. Or maybe they wanna be able to cancel a meeting, right? So they could say, “Tell me all my upcoming meetings. Okay, this one I already know should be canceled because I received an email, uh, that told me this prospect can’t make it anymore.” So they could just type right into Claude, uh, “Cancel my meeting with prospect X,” and then the BookIt MCP takes care of that. So it’s a really amazing, uh, interface into BookIt functionality, uh, that, that we’re, uh, bringing to you all. Yeah. That, that sounds amazing, and again, continuing on that theme of using a different interaction method that folks may be a lot more comfortable with. Um, Daniel, I know that we won’t have time to talk about, you know, the different configuration and setup for this, but something that does come up, uh, quite a bit when it comes to AI tools is just the level of access and visibility. So, you know, when we’re dealing with an admin working with the BookIt MCP versus a rep who is, uh, opening up their Claude and then chatting with it, is there a difference as far as the level of access and permission? What are some of the guardrails that we have around that? Yeah, absolutely. So, uh, with the BookIt MCP, there are actually two methods of authentication. Um, so one method is, like, a one-time code login, um, where you would just specify an email address and then the permission set, uh, that should be associated to that email address. Yeah. Um, either admin or user today. Um, admin would have, like, full permission. User has just permission scoped down to, um, you know, like, that, that kinda, like, user level, which is just what we call, like, dashboard access. Um, so you’re able to determine, um, with a one-time code login, like admin versus user. Um, and then whoever uses that one-time code and authenticates will just inherit the permission that, um, you know, was, was assigned to that email address. So that’s, like, the one-time code flow. That may be, uh, most useful if you’re hooking up, like, an AI agent, um, to the BookIt MCP, and there really isn’t, like, a Salesforce login. But most cases will actually use a Salesforce, Salesforce OAuth login, where the permission doesn’t have to be set ahead of time. We’ll just be able to detect that user’s permission set, uh, once they’ve gone through that Salesforce login. So for example, an admin, a BookIt admin, they would go into Claude, they would set up the connector, and then we would prompt them to log in through Salesforce, um, through a little window. And then once they’ve logged in, we know who they are, right? And we know their permission set, so everything is properly set. Same with, like, a rep. A rep who sets up Claude, um, connector to the BookIt MCP. When they go through the Salesforce OAuth login, we’ll know who they are, we’ll know their permission set, so they won’t be able to do things that an admin can do.Right? So anything that they could do in the end of the application will be consistent with what they could do through the MCP. Same with an admin. Um, so we’re being very careful making sure that, um, permissions are still properly scoped. Okay. Got it. So it’s just following the Salesforce permission set in the cases that we’re using that OAuth login, but otherwise, you get to preset the level before you send the one-time code if you’re choosing to use that method of authentication. Yeah, exactly. Okay. Excellent. All right. Well, let’s go ahead and continue on this theme of enhancements to scheduling. Now, scheduling is something that is invariably going to be a part of your go-to-market processes, but it’s not necessarily something that you th- should think or want to be an obstacle, uh, or a roadblock to your selling. Um, you should be selling off based off of the value of your product and the fit that it has with the particular customer. But scheduling friction should not be part of that equation, but unfortunately, it is for many folks. So our aim and our goal is to remove that friction and to make scheduling as effortless as possible. So Daniel, could you tell us about some of the ways that we can actually facilitate this effortless scheduling and, and make a better experience? So if you could tell us maybe about our first feature of, uh, our meeting type editor enhancements. Yeah, 100%. So meeting type editor enhancements is a complete rebuild of the meeting type editor. Um, so the meeting type editor really is w- one of the most important pieces of BookIt because it’s where all configuration for a meeting, uh, is, is done, or at least most of it. Um, so we’re talking about, like, duration of the meeting, if there are buffer times, um, how does the confirmation email look like, reminders, et cetera. There’s so much that’s contained within the meeting type editor. And so we wanted to revisit this piece of BookIt functionality to make it as easy as possible to set up, and also to give you really good defaults, um, that help you just set it up correctly. So that, those were kind of the first pieces. But then we took it even further, and we thought to ourselves, “Well, you know, how many times have you set up a piece of software and then wondered, um, ‘Did I actually do that correctly?’” Maybe that’s something that some people on this call can resonate with. Mm-hmm. And so we realized offering some sort of preview, um, per thing that you set up, when it has, like, a visual component, can be extremely valuable. So that’s what we went ahead and added in. So for example, if you change the styling, how does that look? You have a preview now. You can go see that. If you change the description or the meeting type name or the logo, right, how does that actually look? Or confirmation email, right? Um, or the calendar event, right? How does that all look? So now you can verify while you’re in the meeting type editor, instead of having to save and then go create a link and then use that meeting type and then load the page and then see if you did it correctly. You’ll just be able to do it right here. So that was really nice. Um, and then we’ve also, while we were at it, added in, kind of got in a couple more feature requests. Um, one thing that, um, some of you guys will really like is, uh, you’re now able to set the calendar event organizer setting at the meeting type level instead of at the global level, and that’s specifically for BookIt Handoff. And what that feature does, just real quick, is it allows the organizer of the calendar event to be the person who’s scheduling the meeting, the person who’s handing off the meeting, uh, instead of the person who’s receiving the handoff. And so this is really useful, um, with, for companies where their SDRs who are using Handoff need to own the calendar event, um, in case of, you know, if they need to move it around or change something, um, instead of the rep who’s gonna be the one, um, you know, scheduled with instead of them owning it. So when the SDR still owns that calendar event, you can now control that per meeting type, so it’s not global. Um, and then also another kind of small thing, but, um, is nice, the confirmation email, you can now con- customize it, uh, for host. Okay. Before, um, it was just, like, static. Now, if you wanna put some additional information in for the host to see, uh, you can, you can do that. And so that might be useful if there’s some just, you know, information you want the host to see that you don’t want, uh, guests to see. Yeah. That’s great. You know, I think for a, a lot of times when we roll out these new features, you know, they’re great for our users moving forward from this point on. Um, for those of folks who spend a lot of time setting up their meeting types and kind of getting them perfect and invested all that time into it, this doesn’t change that or undo or they wouldn’t have to go back and to update anything on their end. This is simply taking what they existing have and providing a new UI and a few new features around that, right? Yeah. That’s exactly right. So, um, they’re gonna see one-to-one between what they had before, what they have now. Uh, you will just notice it’s like a full screen experience, so- Right… things are a lot less crammed. You will notice that there are different tabs. Um, you know, we’ve simplified the tabs, and we’ve regrouped the features just to make them more aligned with, like, where they, where they should live, just making it more intuitive. Uh, you will notice that there’s some, uh, additional, like, helper copy, uh, for each of the settings and some more, like, icons that explain how things work. But as far as your actual settings, you don’t need to worry about it. Uh, it, they’re all one-to-one. Excellent. Love to hear about these quality o- of life improvements that’ll just make, uh, using LeanData BookIt that much better to use. Right. So let’s move on to our next topic. Um, so LeanData has facilitated your meetings, but what if then the details for that meeting change, and specifically, if the original rep can’t make it or they get deactivated or something along those lines? So, you know, how do we, um, handle that? What new features do we have in place to facilitate that specific scenario, Daniel? Yeah. So meeting reassignment is really meant to address that. It’s, it’s like, uh, meeting lifecycle management. Uh, it’s really, like, operational resilience-Um, to handle unexpected situations. So for example, let’s say like a rep is out sick, right? And you need to reassign that meeting to a different rep so that they are now on the calendar invite and they have, uh, all the information they need in order to then, like, go hop on that call. Um, also, you wanna be able to cancel the meeting from that old rep, you know, who was out sick. Uh, but there’s a lot of other stuff that needs updating. You need to update Salesforce events. You need to update remarks, all sorts of stuff. And before this feature, that all had to be done manually, right? It wasn’t a good experience for admins because there was so much work that they had to do. It wasn’t a great experience for prospects because they, um, likely would receive like a cancellation and then a new booking, you know, where they would have to, you know, get a new link and then enter information again and book it. And so it was, uh, there was just a lot of friction. And so with meeting reassignment, we actually handle all of that now. Mm-hmm. So what this looks like is, um, you go to the meeting log as an admin, you click reschedule meeting, and you’ll have the option to change both the hosts who are on the meeting- Right… and the date and time if you want. Or you could keep the date and time the same, as long as that works for the new host. And then when you click schedule, we’re gonna swap out the hosts. We’re gonna take care of giving the, giving the new host account, giving a credit back to the old host. We’re gonna update the Salesforce event. Uh, we’re gonna have a view meeting history, uh, table that’s gonna show you the entire history of the table so you know who reassigned it, when the new meeting was, all the information you need to audit. Um, and it’s gonna make just the whole kind of flow a, a lot more seamless, uh, for, for everyone involved. So yeah, really excited to bring this one, uh, out to our customers in 8x, ’cause we, we know that this use case comes up a lot. Uh, it’s really gonna save admins time. Yeah, absolutely. I think the benefit and the improvement for our admins and their use of this, uh, i- is clear. Um, and then you had mentioned that we take care of the fairness aspect of it in terms of crediting the right, uh, recipients for the meetings and, a- and handling all of that. Um, but for the end users, the, the folks external to your organization who are, are, uh, having these meetings scheduled with them, what do they see? ‘Cause there’s all this, this reassignment and, uh, things that we’re cleaning up on the back end. How much of that is visible to them? Is it, would it be confusing to them, uh, different messages that come their way, or is that all kind of handled within that as well? Yeah, it’ll all be handled. Um, there are times when we do want to send information to the prospect. For example, let’s say the date and time changes, but we want them to know. So in that case, they’re just gonna get a meeting that says like, “Hey, your meeting’s been rescheduled.” Right? So they’re not gonna get something that says, “Hey, it’s canceled with this old rep. It’s resche- you know, newly scheduled with this new rep.” It’s just gonna say it’s rescheduled. Um, but if there aren’t changes, uh, to the date and time, let’s say we’re just swapping hosts, everything on our end, BookIt then to, uh, like minimize the amount of communication that gets. So it’s just like we’re not gonna send them a new confirmation email, for example. Um, now the new host, they are gonna get a confirmation email- Right… um, ’cause they need to know. And then the old host, they’re gonna get a specific like reassignment email letting them know, “Hey, this meeting’s been reassigned away from you.” Um, but as far as our prospect, it should be, it should be very seamless, um, because we don’t wanna introduce any potential confusion- Absolutely… um, to Yeah. That, that’s the concern. You know, uh, it’s not you’re gonna get a cancel email then a, you know, a new meeting email, and you have to accept that. And so all of that’s sort of handled with the minimal communication as far as they get the things that they need and not a bunch of excess on top of that. That’s great. Absolutely. Yeah. Um, one other thing just to mention here, uh, while we were at it, on the meeting log, that’s where you’ll be able to reschedule meetings as an admin. We also threw in the cancellation email, I’m sorry, the cancellation link there. Okay. And so you’ll be able to cancel a meeting from the meeting log. Um, and because we know who’s logged in, we’ll be able to attribute that cancellation to you. So all that goes into that meeting history, uh, table that I was talking about, so there’s just much better auditing. And then also, as far as the fairness piece with the count that we give the new rep and then the credit that we give the old rep- That’s right… you’ll be able to see in the credit history that this was due to a reassignment. You’ll be able to see who reassigned it. Okay. So just like, and just, you know, uh, at LeanData, we really care about your auditability, you know, and like building that trust with our admins. So we’ve thought through that with this project as well, and, um, everything will, will, will be very clear as to what happened. Yeah. That transparency is a huge piece of things. Uh, even getting the credits right and having visibility into why the credits are the way that they are, are, you know, go hand in hand. So I appreciate you mentioning that, Daniel. Okay. So let’s move on to our next topic of calendar buffer events. So what is this? Why is this a necessary, uh, improvement for our, our admins? Yeah. So the last feature, meeting reassignment, right, it’s all admin driven. It’s, it’s something that, you know, helps them out, uh, kind of mostly. But the calendar buffer events, this is really around helping our hosts out. Okay. So we, um, have always had buffers in BookIt, but they were really only respected at the time of scheduling. So what that means is when a scheduling page loaded, if a meeting type had buffers on it, we would respect those buffers in the time slots that a prospect would see on that scheduling page. So we would only show time slots that took into account those buffers. Mm-hmm.Once those times were select– Once a time was selected and a meeting was booked, the actual calendar event didn’t have buffers on it or next to it. And so what that meant is that time that you expected to be blocked off, say like 15 minutes before and 15 minutes after, um, it didn’t persist post-booking. Right. So somebody might see that, look at your calendar, for example, like your manager sees you’ve got actually 15 minutes after that, you know, demo call you’re doing, and they might put something there. And so that time that you were expecting to have to, like, follow up, uh, with that prospect or maybe take some notes, update, you know, the record in Salesforce, actually gets booked over. So that buffer was only really respected during scheduling- Right… but it didn’t persist afterwards. And so what this feature does is it truly creates those buffer events on your calendar, on the rep’s calendar, uh, if they would like ’em. It’s optional. It’s just a checkbox. So if you want ’em, you can have ’em. If you want it to work like the old way, where it’s only respected at the time of scheduling, you can also do that. Um, and then on top of that, we added a couple more options for buffer events, ’cause we heard that 15 minutes was a little bit too long. That was our, that was our minimum. So we threw in five minutes and 10 minutes. Um, and then also, really importantly, these buffer events, they, um, are managed throughout reschedules and cancellation and reassignments. So if a meeting’s rescheduled, those buffer events are gonna move. If the meeting’s canceled, we’re gonna remove those. And then if the meeting’s reassigned to a different rep, we’re gonna remove them from the old rep, and we’ll give them to, uh, the new rep at the time of the meeting. Excellent. So, um, just to clarify, is this a global setting, or is this, uh, at, at the meeting type level for, for these buffer events? Yeah, great question. So it’s at the meeting type level. Right. So, um, that gives, you know, way more flexibility than putting at the global level. Um, and so, you know, if people have personal meeting types, they’re able to set those as they will. Um, and then yeah, it’s just, um, yeah, much, much more flexible, and it’s at the meeting type level. Okay. Yeah, so people have the option to have certain meetings have that buffer calendar event and others to, to not have that. So that’s gonna be helpful for a lot of folks. Thanks, Daniel. All right, so multi-meeting type landing page, uh, this looks familiar. Uh, if I’m not mistaken, this is something that we’ve had for a few versions now. So, uh, what’s new about this, and how does that support this idea of effortless scheduling for folks? Yeah. All right, so multi-meeting type landing page. Um, so what we had before was multi-meeting type landing pages for links. Right. And so what we’re doing here, or what we’ve done, is we’ve brought that functionality to Book of Reforms and Routing Links. And so the implementation is very different because with Book of Reforms and with Routing Links, you have a graph. You have your Book of Reforms graph, and it’s really the schedule node in that graph where the meeting type is defined. And so what we’ve done is we’ve given you the ability to select multiple meeting types. Right. And so what, why does that matter? Well, previously, when you can only select one meeting type in the schedule node, that means if you wanted to offer a different meeting type to prospects, um, there had to be some sort of logic upstream that directed you to a different schedule node. Because only sche- one schedule node can have one meeting type. And so that means you had to have some branch- Mm-hmm… right? So that means you have to have some decision logic above, and likely you’re making that decision based off of, um, something from the form. So that means another form field. Yeah. Mm-hmm. And so you have kind of all of these things, right? In order to offer a different meeting type, you had to do different things, right? Ask a prospect for more information. You had to change your graph. You had to add more nodes. So- It’s just more to maintain. But what we’ve done here is because now you can specify meeting types at the schedule node, and when you specify more than one, what we do is we show a landing page to the prospect. So the prospect can now choose the meeting type that’s most appropriate, um, for, you know, whatever meeting they wanna have. Let’s say you wanna offer a demo for scheduling or a demo for orchestration. Well, it’d be great, uh, for the host to know, you know, your rep, it’d be great for them to know which one the prospect has selected so that they can, like, prepare accordingly. And so now that choice is made by the prospect. So that saves you from having to set up multiple schedule nodes. It saves you from branching logic. It saves you from changes on your form, uh, because you’ve offloaded that to the, uh, prospect. And then it gives the prospect agency, actually, right? So it’s, uh, it… You know, do they want a 30-minute meeting, a 60-minute meeting, right? Different use cases, uh, different objectives. So, uh, all that, all those requests, we know that this has been working super well for links. And so when we released that, people were asking, “Hey, can we do this for Book of Reforms? Can we do this for Routing Links?” Um, so we can have parity there. And so, yeah, we, we’ve brought that in, so now we have, uh, alignment between all of the products. Yeah, that’s excellent. Yeah. I hadn’t thought, actually, of the benefit of not needing to have as many questions on your form fields to be able to direct someone to the right place, because if they’re self-selecting, those questions are inherently answered by the meeting that they select, and it’s done on their end without adding additional questions for them. Exactly. Exactly. And one of the, one of the other kinda things that doesn’t, is maybe not, like, as clear here is, remember we talked about meeting types. Like, a meeting type has all the configuration for that meeting. And so if they click LeanData Scheduling Demo-Because they’ve selected that meeting type, we’re able to show a totally different description. We’re able to show a different title. We’re able to ask different questions after, you know, in our, in our scheduling information page, different confirmation email, et cetera. And so it’s a way more customized experience that you can offer your prospects because they’re the ones choosing the meeting type. Yeah, absolutely. No, thanks for sharing that. That’s a very exciting feature, and I hope folks really get all the benefits that we described here from that. All right. Well, Daniel, thank you for sharing all of these exciting new scheduling features and enhancements. Um, we’ve really covered how LeanData is really pushing AI into everything that we do so that you can gain that winning edge, and we’ve also talked about this idea of effortless scheduling as a part of your GTM process. Um, it shouldn’t be the roadblock when it comes to selling. So let’s switch gears and transition a little bit into this concept of executing not just efficiently, but intelligently. And one of our newest features around that is Best Fit Assignment, so I’m gonna ask Isabelle to come back onto the stage and tell us about this newest Best Fit Assignment feature. All right. Thanks, Kevin. Um, yeah, so Best Fit Assignment is actually gonna be a new functionality that we support with our Round Robin node. Um, so what you’re gonna see is there’s this new mode, um, called Attribute Aware Mode, and what it is going to do is it’s gonna help route records to the best fit rep based off of those rep attributes, as well as some of context of the record being routed to the rep. So as you all may be familiar with, um, on the orchestration side, um, Round Robin pools were assigned, um, they, they send records, but they do it in a strict next in line order. So, you know, a lead A comes in, it’s gonna go to rep A. Lead B comes in, it’s gonna go to, uh, rep B, et cetera, et cetera. Um, so it’s in that order, but what it doesn’t do is take into account some of the characteristics of the leads, like maybe the language that the lead speaks, where is the lead from. And it also doesn’t take into account any of the characteristics of, you know, that rep. Like, you might have a rep who’s, like, a little bit more skilled, um, in a certain product. Maybe they speak a certain language. Um, and you can’t really optimize for those scenarios to give a better experience to your lead. Um, so with Best Fit Assignment, it’s a new mode here, um, where you, we’re actually able to take into account that record context. So like that example I mentioned, like, you’d be able to see, like, hey, the lead, you know, speaks a certain language, they’re interested in a certain product, um, and you assign it to the best fit rep, quote-unquote rep, based off of attributes of the rep themselves, like what language they speak, what expertise, product expertise they have, um, if they are actually good at a specific industry, um, have a good historical, um, kind of historical success with a specific industry, for example, as w- or their tenure. These are all examples of attributes you can take. Um, not meant to be, like, something you must do. Mm-hmm. Um, but it’s gonna help take that into account when we actually do the assignments. Now, kind of a question there is we’re also making sure we are balancing fairness to that. Um, so we’re not, you know, that can easily make it so that, you know, all the leads go to one specific rep. That’s not what we’re trying to do here. Um, this actually only takes into, it only comes into play in those specific tiebreaker scenarios. Like, if you have rep A and rep B, they both have the same number of counts. So given that, like, let’s assign this new incoming lead to the better fit rep in that scenario. That way you’re not gonna have those questions from your reps about, like, unequal assignment, for example. Um, yeah. So part of that, you’d be able to set those required, um, attributes or priority attributes, which is, like, attributes you might wanna prioritize. And we are also just, bonus here, bringing in count-based distribution, um, to our Round Robin pools on orchestration as well. Hmm. Got it. So, um, more, more about the attributes specifically. So you mentioned a few here, like language and product expertise, tenure. Are, are those things sort of preset, or can you have your own custom criteria internally that you can assign? And is that configured in LeanData, or is it configured at, like, the Salesforce, uh, level? Yeah. So there’s two steps to this. Um, the first step is actually kind of pulling in that attribute data for your users. Now, we’re gonna allow you to pull that in directly from Salesforce from the user object. Um, that way, you know, if there’s any updates that are done in the CRM, we automatically take in those updates. Now, so yeah, that could be anywhere there. Um, but actually setting which attributes you wanna prioritize, that will be done in LeanData. That’s gonna be done in the Round Robin node itself. Okay. Got it. Um, so kind of jumping, uh, a little over to what you talked about before with audit logs. Um, so this is sort of addit- another layer of how to route your records that’s sort of contained within a, a node itself. Is that captured on the audit logs? Can people see why LeanData chose this rep as the best fit versus this other rep? Yep, absolutely. So our audit logs are also updated now, so you kind of see those, um, very similar to the audit logs you might see in a Get Records, in a Match node. You see how, um, that logic cascades down and ultimately selects a rep. So it’s all gonna be there for you in audit logs as well. Okay. So full visibility as we like. Okay. All right. Our next feature here, we have, uh, multi-hierarchy support. So, you know, I kind of understand, uh, what the words mean here, but why would someone need support for multiple hierarchies? Could you tell us a little bit about this? Yeah. So this is gonna be another update to our account hierarchies functionality that we’ve been really adding to over the last few quarters. Um, and why a customer, or why you might wanna use multiple hierarchies is that you can actually now build and maintain different hierarchies for different use cases. So, you know, we’ve heard some of you mention that you have different hierarchies for different use cases. Like, you might have a specific legal hierarchies that’s really done for kind of billing purposes, but then you might have a sales hierarchy that’s more meant to, like, identify any open opportunities, uh, missing accounts that you want to reach out to.With this functionality, you can now build both. You can independently maintain them, and you can also bring them back into routing so that you can choose which specific hierarchy you might wanna actually use. I think another use case I did wanna bring up here is, like, I know a lot of you also have different enrichment providers that you use. So you’d be able to build a separate Zoom info, for example, hierarchy, and a D&B hierarchy, and then use that to try to, um, identify where the gaps are between each one. Hmm. I see. I see. Now, um, juggling multiple hierarchies, is this something that you can use multiple hierarchies within the same graph? Or is it, you know, only for, for visualization, or can you access both of them within the same path to your routing graph? Yeah. So I think what’s cool about this is you will be able to reference multiple within your routing graph. So once you build them, you select in that account hierarchy match node which hierarchy you’re actually trying to look into. Um, and then it will just traverse that specific hierarchy itself. Um, I did mention that use case a little bit earlier about, like, maybe you have two enrichment providers. So- Mm… one way you might want to take- use that to your advantage is when you go… when, like, an account maybe goes through your graph, you actually check for its existence in both of those hierarchies, for example. And, you know, if you see that one is missing, you can actually update that account itself so that it actually fits into the hierarchy of the other one. So that’s how you can kind of get that global hierarchy with multiple enrichment providers. Okay. Got it. Anything else to, to mention on this one before we move on to our next, uh, theme here? Um, yeah. I mean, I didn’t touch upon that too much, but it’s also gonna resolve in your, um, visualization as well. I mean, if you see that screen, you can now select which hierarchy you actually wanna look at. Um, so yeah, it’s just access to more information in general. Yeah. So they’ll all just be contained in the visualization. You can collapse or expand whichever one you wanna look at. Okay. Awesome. All right. Well, Amar mentioned earlier that we want to ensure that as you expand the capabilities in your tech stack, that you also have visibility and accountability, uh, that’s necessary. It’s also expected. Um, and we’ve made a few new enhancements that will support all of you admins i- in this regard. So our first improvement here is to audit logs. Um, so Isabelle, can you tell us what is new about LeanData’s audit logs, maybe other than the assistant that you already talked to us about? Yeah. We know audit logs is kind of one of the favorite features of our product, um, really with the visibility that it brings. So we did a big update and a refresh on our audit logs experience. So with this, um, with this new experience, you’ll be able to search across different objects and products in one search experience. Um, so before, you know, you’d have to go into… You’d have to click into lead audit logs or contact audit logs, or even, like, your scheduling audit logs, and you’d have to do that all separately. With this, um, we’re kind of bringing that all into one unified view. Um, that way you no longer have to kind of do that, make that extra decision where it’s like, “Well, I’m looking for a log, and it was this specific record.” You can just go there instantly there. You’ll also see that kind of new look and feel here. I’m trying to just kind of update that, make it a lot more easy to parse through. And, um, like I mentioned before, the new AI assistant is actually gonna sit upon, on top of this new experience as well. Nice. Nice. So I can definitely see the, the time savings, uh, as far as, okay, I don’t have to go to this page and then go to this other page to look at this other object. So every- having everything all in one is already a win, and then the auto log assistant, um, or the LeanData assistant on top of that’s gonna be helpful. Um, is there anything else that’s, uh, like net new functionality? ‘Cause this is a UI change, and that’s helpful in many ways, but is there anything that I can do now that I wasn’t able to do before with these auto logs? Yeah. I mean, one thing you can do here is we did add a new filter functionality, um, so that you can actually dynamically filter the records you see on your screen. Um, so a little different, different from the advanced search that we had before, where you kind of choose the specific, um, kind of logs you wanna see. Now you can actually zoom in on that even closer. You’ll see that left sidebar, there’s that new filter button where you can kind of drill in even more from there. Um, and then this is more on a benefit side, but, like, with all of the logs in one screen, you can now actually trace, um, chronologically trace how a record might have traversed different routing graphs. Um, you know, you know, have a lead, classic lead conversion to contact conversion use case. Now you can actually see, like, okay, how did it go through that lead graph, and then, then how it went through that contact graph in that one unified experience. No, that makes a lot of sense. That’s super helpful. All right. So that’s auto logs, already a beloved feature, but getting even better. Uh, also another beloved feature, um, being able to track SLAs using, um, what we used to call the hold until node. But we have some enhancements around that, so Isabelle, could you tell us about that? Yeah. And Kevin kind of gave you that little preview. So we are updating our hold until node, um, to be called the track SLA node to better match, you know, that use case you w- obviously wanna use, um, for SLA tracking. Um, and we also added a series of big, um, updates to the node itself, um, so that it does have more, um, SLA tracking and governance capabilities. So 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, um, you would have to chain multiple hold until nodes in order to do it, um, just because it exits a- 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 chained because, um, you know, let’s say there’s like 30 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, um, 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, um, for SLA to be met as a whole. Um, within that node itself, now we built in those reminder notifications, so you no longer need to exit those nodes. It supports email, Slack, and Teams so that you can just automatically send out those up- those, um, those notifications, uh, without exiting the node itself. Overall, this should make time to action tracking a lot simpler because, um, 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, um, sec- optional feature here where you can actually extend how long that that record is being hold, held in that node, um, even after SLA is met. So, you know, you might actually want to see how long your rep ultimately did it, did 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. Um, we now allow you to do that just within that SLA node itself. Yeah. That, that’s great. Uh, personally, that’s one that I’ve been w- waiting for for a while, um, as far as extending that, uh, uh, tracking. Um, 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 kind of get at that, approximate that. Um, for folks who’ve been already using our old hold until node and building time to action tracker reports, does this… ‘Cause 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, um, make the changes pretty minimal in terms of your time to action reporting. If anything, this actually gives more detail, um, that you can add in your reports for time to action tracking. You can track those individual rules, for example. Um, but there are some updates that are made. Um, it’s gonna be in the new package. Um, so you’d have to update your package to get those new reports- Okay… if you are using out-of-the-box reports. Okay. Excellent. Well, thanks Isabelle for taking us through all the features that you did. Um, and I just wanna give a thank you to, uh, Daniel and Amar earlier for sharing all the wonderful updates. Um, to close, I just wanted to highlight a few upcoming events that we have in the next few weeks. Uh, firstly, we have an expert hour coming up, and these are virtual user groups for those who are LeanData certified, and next one’s going to be on building a comprehensive revenue motion. Uh, for those of you who are not LeanData certified, we do have an upcoming live class. Um, so if you’d like to get that certification, please sign up for that next live class, uh, on the 24th. We also have an upcoming webinar on June 25th about agentic scheduling, um, as far as using LeanData alongside your agentic scheduling and, uh, building that within your routing as well. And then lastly, this is not within the next few weeks, but registration is open now. So, uh, we’re having our annual OpStars conference in San Francisco on October 5th. So if you have not yet signed up for that, please make sure that you do. All right. We will be closing it off now. Um, so I just wanna give a big thank you to everybody who joined us today, and, uh, we will be following up if there are any questions that we weren’t able to get to or f- those who- folks who wanna get a recording of this. But thanks again for joining, and have a great rest of your day.