The below transcript has been auto-generated for your convenience. Please reference the source video/audio for direct quotes or to clarify any errors.
Speaker 1: (00:01)
Welcome, welcome, uh, welcome to our webinar in the HubSpot Day Suite for, well, I say non-data friendly, uh, but we welcome all data people, uh, friendly or non. Uh, I'm gonna go through some, um, some high level pieces about data, uh, some different features of that HubSpot that you can leverage, uh, to own your data, keep it clean, keep it organized, uh, and just some process around thinking around it. Um, so I'm Ryan. Uh, I own our, our Revenue Solutions architecture function at, at apps. We're a HubSpot Elite partner. I'm with me, is Kara.
Speaker 2: (00:40)
Hey everyone. Uh, I'm Kara. I'm a product manager at HubSpot, and I work on our data quality tools. So excited to speak with you all today and dive into some more detail. Um, but I'll let Ryan kick it off. Cool.
Speaker 1: (00:56)
Awesome. So here's what we're gonna be talking about today. Um, a couple of a couple of things. Uh, so first, what we're gonna walk through data modeling within HubSpot, uh, including using custom objects, uh, as well as data model overview within HubSpot. Um, we're gonna go through some data cleanliness tools that HubSpot has, uh, way and keep data ongoing. Uh, the command center, um, using some automation recommendations as well. Going through making sure that you can not only build the data model that matches your business, uh, using all the, the tools that HubSpot provides, but also being able to keep it clean and helping you to scale, reduce the amount of, of effort. Uh, the people on this call are probably a mix of, uh, CRM managers, marketing folks, uh, executives, et cetera. Um, I think this, this will be helpful for everybody and going through just talking a little bit about why HubSpot for your data, why keep everything in here? Um, and I'll give it to Kara to talk a little bit about this.
Speaker 2: (01:58)
Yeah, so, like I said, very excited to, to connect with you all today. Um, but before we dive into some of the features, let's talk about the value of that data within HubSpot. And we all know data drives business decisions, and HubSpot can really support that throughout a customer journey from a prospect to, uh, a really, uh, great customer. So with all of that relevant info in one place and an easy to access, understandable format, you can be confident your teams really have the info they need to make informed decisions, communicate with your customers and grow your business. But really to, to leverage that data effectively within A C R M, you also need to think about the structure of that data, the quality, and the f foundational elements of setup, monitoring and cleaning. That data can help build trust in your organization that your data is an accurate picture of your customer, um, which hopefully will unlock a lot, uh, for you and your teams. Um, so
Speaker 1: (03:00)
We'll, yeah, I was gonna say one thing I think that, that I know that, that I see frequently, um, is that HubSpot is not just a marketing tool. It's not just a sales tool. Um, but the ability to flex and expand the system to house data that maybe isn't directly related to a sales process, um, or a service process, uh, as an example, um, but is adjacent or helpful. Uh, so I think of service, I think of like product usage data, right? Being able to structure HubSpot in a way that you can bring in information that's contextually important for marketing, sales, uh, service activities, uh, and doing it in a way that doesn't get in the way, uh, but is available for reporting. And, you know, linking into to deals and those types of things, um, is where I think HubSpot really shines. So it's, there's the basics of it.
Speaker 1: (03:53)
Um, I think what we're gonna focus on today is the sort of expanded use in ways you can, you can do all that, which I think probably transitions to my next slide, on data model. So, uh, as I just mentioned, the interesting, interesting thing about HubSpot is, is not just the, the hubs that it provides, but the ability to store information that's, that's contextually relevant for marketers, sales, uh, service folk. Um, and definitely important to understand what is going on in your database. So one of the, the common things that happens, especially as an organization expands, a lot of information gets put in there. Sometimes well thought out, sometimes not. Uh, and I know it can be, uh, a bit messy, um, but having a a very firm understanding of the makeup of your HubSpot instance and how your data is structured is absolutely critical to either fixing any sort of structural issues, but also layering an additional piece of information. So you have to know where you have to know how things are structured so you can figure out what the best place to put some additional, uh, piece of information.
Speaker 1: (05:07)
So, uh, HubSpot provides a, a visual data model overview, um, which we'll we'll see an image of it in a second. Um, but allows you to actually visualize and create kind of a narrative. Um, so one thing definitely is, uh, potential redundancies. So frequently something that happens with custom objects, uh, especially, but also just as far as using properties across, um, d other objects, is you have a lot of redundancy, uh, or gaps. Um, so if, if you need a clear understanding of where information should go, you don't have an object that's called contacts, uh, or context history, uh, or subscriptions, subscription history, any of those types of things. If you tell a story, uh, about your particular sales service marketing process, um, and you hit on each sort of major set of information, you should end up in a place that actually spells out which objects you should have.
Speaker 1: (06:02)
Data model overview allows you to, to visualize that and not have to memorize how information treks through your system across three to, you know, 15 or 20 different objects. Um, everything that the data model overview covers is really foundational to, to your crm. So I mentioned telling that sort of narrative. Uh, simple example is something like we as a company sell products object, uh, in a sale, uh, in a deal, right? Um, we sell to companies. We, those companies have contacts. Uh, at some point they're going to need a service appointment that's now an object, right? Um, we're also gonna need to track tickets, um, which could be a service appointment. Maybe we need history. So it's a way to kind of structure how someone goes through, uh, through your flywheel and at each major bucket of information, whether or not you have a clear, um, a clear place to put that information.
Speaker 1: (07:06)
Sometimes using custom objects or standard objects, um, well, we'll talk about that actually in a second. Um, but information can, can live in one of both of those, but the ability to actually visualize it helps. So you don't have to track across, uh, like I said, 10, 15, 20, you know, objects if you've got a lot of custom stuff in there and allows you to see the direct relationship. So if you're not understanding why you can't pull something in a report or a workflow, you can come right to the data model overview, take a look and say, oh, I don't have this kind of relationship between the subscription history object and my company's object. That's why I can't pull it. So I need to, you know, add that relationship in.
Speaker 1: (07:50)
So custom objects, uh, are a way to take you well beyond, uh, what HubSpot offers. So, like I said, the HubSpot CRM allows you to, um, allows you to store information that's contextual as well as direct. So in a situation where you sell products, have some special service process, like I mentioned, appointments or subscriptions, um, where HubSpot doesn't provide something standard and you wanna house that data, you can create custom objects, which is available, uh, with any enterprise, um, any enterprise hub. So in an instance, you've got, um, line items on a deal after somebody becomes a customer, you want to then reference what products they have. You may or may not, you know, make a lot of sense to constantly have to go reference a history of deals. You just want to store a library of currently active products that they have. Well, in that exact sense, uh, there's not necessarily a a the best way to store them in HubSpot on a standard object.
Speaker 1: (08:53)
So you might create a custom object called assets called, you know, something of that nature that you can reference against any of the existing objects. Um, a common use case also is like a history of upgrades or downgrades for a SA product. Uh, and you want to control and report on that as well. So the ability to have, uh, information that's not out of the box, um, put in a different place, it's not always the best solution. Uh, there are plenty of situations where using a custom object doesn't make sense, uh, specifically where HubSpot provides, uh, a standard object for it. Um, but frequently in a sense, uh, where we've got different types of hierarchies and relationships. Um, so in certain cases, things like, uh, parent child may not give you exactly what you need cause you've got 15 different levels, uh, of relationships and they're not all vertical.
Speaker 1: (09:44)
Um, being able to, to create sort of like a container object is another example. And I mentioned history before, is, is a common use case. Um, so the schools is a, as an area that we see, um, custom objects being used really well. And I think that the framework that we generally go through is if the information is contained inside of a contact. So, and it's not just a description about the contact or that particular object. So we've got contacts. Um, is it just a type of contact? Great, let's just use contacts and either, uh, an association label as it relates to another object or a property to define the different types of contacts. But if we need information about that contact that's completely different, like a contacts accreditations as an example, we're not necessarily gonna wanna create a property that we're gonna need to update, you know, a, a dropdown with 7,000 different, uh, different options that all also contain details. So we would probably want to create a custom object to reference that contacts accreditations as an example. Um, real estate is another example where custom objects are a really great use case. So you've got a, you know, a property it's listing, um, with hiring something that we actually use internally, right? We've got sort of candidate pipeline, we've got a job that's related, uh, offers, those types of things. All great use cases for custom objects.
Speaker 1: (11:21)
Anything that needs to be emailed, not a good use case. Uh, you're gonna be copying things over into the contact. Since HubSpot leverages the, the contact for all email, um, you could certainly have information in the custom object, you're just gonna be constantly copying it over, um, the, the example that I mentioned before, or you've got what is essentially just a different flavor of contact. So lead versus customer, uh, employee perspective, employee, uh, those types of things. You can use association labels, you can use, uh, dropdowns on the actual object to differentiate. You don't necessarily need something that's entirely custom. Uh, it's very easy to kind of get a little, uh, , get a go a little wild with custom objects. And every time you need something that appears to be different, uh, you create a new custom object. Um, but again, I think if you opt for always trying to use a standard object where possible, great situation, uh, great solution, keep it simple. But more often than not, you're gonna have some piece of information that is related to, but not a part of a HubSpot standard object. And that's where custom objects come in, save the day.
Speaker 1: (12:38)
So talk a little about data cleanliness, which I know is, uh, thorn in everybody's side all the time. Um, gonna turn it over to Kara to walk through some of this information.
Speaker 2: (12:51)
Awesome, thanks Ryan. Before I, I jump into that, do we have any questions? Just looking in the chat, feel free to drop those in and we can answer as we go, um, or at the end. But, um, would love to dive into, um, data cleanliness. Um, so, you know, with clean data, right, you can ensure your teams have accurate up to date relevant info, all good things to help you engage with customers and prospects. It helps you power your reports, your automation, key business functions. Um, but wanna take a closer look at some of the features we have, um, that can really help you, um, maintain that clean database over time. So a new one, uh, that we released this year's validation rules. So this is a tool that can help you keep bad data out. Um, we have this new feature in public data, which validates data as it's being entered.
Speaker 2: (13:54)
And, you know, that means better decision making, better customer experience, cuz you can ensure, um, your properties are formatted in a way that you'd expect. And some specific examples of this are you can, you know, set rules for custom texts and number properties to be certain length, and it really helps you remove the worry of human error of other people messing with your data. Um, and some examples of specific roles you could set are men and max character limits, restricting values to numeric characters only, or disallowing special characters. So depending on, you know, the data points that you're storing for, um, your business, you may wanna restrict to certain values to that. Um, when you're reporting on it, you can ensure all the values of or of a certain, uh, format. Um, another example is with currencies or setting a certain numeric range, uh, if you have, you know, a certain product or, um, customer value, you can actually limit to a certain range.
Speaker 2: (15:06)
And I wanna actually share this, uh, in the product. So you could get get a feel, you know, when you actually set this up, how does this work? So as an example, if you came in and wanted to set a specific range for currency, you could create a new property. Let's say it's a contact property. Um, and let's say it's a, you know, product currency, just a test property. Um, we want it to be number, um, it's actually currency. So set it up as that. And now we have these new validation in rules where you can limit, you know, minute max, uh, limit the number of decimal places we want two decimal places. If it's a currency, um, let's say we want it to be, uh, you know, the max, this can actually be as a, as a thousand. We don't want any more than that.
Speaker 2: (16:07)
If it is, it's not accurate, can create that property. And then within a record, you can see this actually, um, validate in real time. So let's see, my product currency, let's say I try to put in yeah, too high of a value, then like I will immediately get a warning actually needs to be a thousand or less. So you can have these checks in place now to actually prevent bad data from being saved in your records. Um, which is a great way to, um, you know, ensure when you're not the one inputting the data or, or other teammates are in there in the day-to-day. Um, you can standardize and make that consistent. So I wanna transition to a another feature. Um,
Speaker 1: (16:59)
Actually I wanna add one thing on, on validation. Yeah, sure. So data validation is a is somebody who spent a fair amount of time, uh, in, in ops and building, managing CRMs, um, or, you know, sales, marketing, any of those things. I, I think it's, it's a double-edged sword. Um, too much validation. So we wanna have some level of rigid data structure, really important for reporting, um, for everything to be accurate. I would say be mindful of allowing some level of flexibility in certain situations to enter certain information. If, if there are too many requirements, uh, for somebody to enter data, they will often just skip, uh, the things that aren't required. Um, so while you wanna make sure to have some level of, um, safeguards to prevent bad data, nothing, nothing is a complete replacement for training and purpose and all of those things. So it's a great validation's, a great compliment to do, you know, where, where things can be botched and make a huge difference, right? If somebody puts in a, a number that's too high, validation rules are an incredible use case for that, um, you can certainly overdo it. Uh, so I would say where simple training, low risk, you know, error, uh, a lot of times can be like a good, a good balance. So, so you have some validation rules, but not on everything.
Speaker 2: (18:27)
Yep. Yeah, it's a good call. Um, you also, you know, wanna be conscious of time and when you get that information, um, when it's input into the CR rm, you don't wanna block, uh, yeah, your reps or your users from being able to answer data either, right? Uh, in certain context. So yeah, really good, good call out.
Speaker 1: (18:45)
That's where just, uh, like property names also could matter a lot. Try and be descriptive
Speaker 2: (18:51)
Speaker 1: (18:52)
Speaker 2: (18:53)
Yeah, absolutely. Um, awesome. Let's, let's take a look at, uh, another new data focus feature that also doesn't require, um, specific data expertise to use. Um, it's called the data quality command center, and it helps you monitor your data on an ongoing basis. And the whole premise here is you can't fix what you can't find. And a lot of times bad data will, will bubble up in unexpected ways or when it's too late, like a customer communication has gone out or you notice it downstream. And in this new tool, you can get out of glance insights on the health of your HubSpot data in one place. So identifying sale properties, data sync bottlenecks, and more so you can get ahead of problems before they snowball and become much bigger. Um, as you add in new integrations, run imports or reps add more data to the C R m, it can be really difficult to keep tabs on that whole system and data quality over time.
Speaker 2: (19:56)
So for ops teams, this can mean that really reactive process when you notice that data, and that's where the, the data quality command center comes in. We're starting to monitor that more proactively, help teams give or help teams have a place really to, um, to go and, you know, monitor that over time and, and have actual steps to, uh, clean it up with their teams. So, um, you can think of this as a home base for operations to monitor and clean everything from your data set up. So properties to records, formatting issues and duplicates. And we have data sync on here as well. So with a view like this for the first time, we, we have a centralized place. These used to be in disparate locations throughout HubSpot, and now we're bringing this into one place where you can prioritize and take action. Um, but for a specific use case, right?
Speaker 2: (20:54)
If you went to a conference, you gathered a bunch of data, you have it in a C S V for the people that came to your booth, how those names and emails are, are, uh, recorded may be different from what you have in your c R m if you have any overlap, right? Um, and you know, there may be, uh, you know, consistencies, there may be inconsistencies in terms of names and emails, and we wanted to make it really easy to identify those records, um, and either merge them or reformat them to ensure that the data within HubSpot is quality. So let's take a look of at how that will actually, um, work within the command center. So this is the data quality command center. Uh, we have properties, record insights in this case we're really interested in seeing are there, you know, new duplicates records with formatting issues.
Speaker 2: (21:56)
We brought in the duplicates tool, uh, into this experience. You can come in right away, take a look at, you know, potential duplicates that we use AI to, uh, match based on name, email, phone number, and in this case, you know, Franz, we have Fran firstname.lastname@example.org, we also have email@example.com. Looks like a duplicate, you can take action here right away. We also added the ability to do this in bulk. So if you have multiple that you know are duplicates, you can take action and merge, um, right from here, really, hopefully, you know, making that process of finding potential duplicates easier, more proactive versus finding them later. Um, down the line. Anything you'd wanna add there, Ryan? In terms of,
Speaker 1: (22:47)
No, there, there were a couple questions around, um, dent around, you know, deals and also like tiers where some of these features are available.
Speaker 2: (22:57)
Yes. So yeah, so it's only available for contacts and companies right now. Um, would love to hear, uh, feedback around deals and how you would like that experience to work. Um, it's not something we have on our roadmap right now, but, uh, would be very curious to, to hear some of the attributes that you see duplicate deals come in on and, um, the actual duplicates tool. So what you saw here, this is available for all pro tiers. The ability to do this in bulk is an Operations hub, feature, operations Hub Pro, um, and the data quality command center, the centralized view is Operations Hub Pro, um, as well. Did I answer all the questions there?
Speaker 1: (23:44)
Validation, which is the field validation.
Speaker 2: (23:48)
Okay, that's available for everyone. Yeah, everybody, yeah. So it's, it's in beta still. Um, but yeah, any, any tier from free and above, so you could check it out, uh, in the free CRM as well.
Speaker 1: (24:02)
There's, there's a question actually here on validation. Camila data to be entered. Let's send a warning. So it can be manually evaluated
Speaker 2: (24:16)
Speaker 1: (24:17)
Technically the, yeah, I'd love to hear your your approach to that.
Speaker 2: (24:22)
Yeah, so right now it's, um, once you've set the rule, you can't save the value. So once it is a rule, you can't save the value, you know, is invalid based on the rule. Um, what is interesting though about that is, um, before you set a rule, you may have data that may not fit, fit that validation, right? So like, um, that you want to, to pull into that property. We haven't solved that use case yet. Um, so you can't set these on existing, um, existing properties only, you know, newly created ones, custom ones. So that's something we'll definitely be thinking about in the future is how do we handle, you know, if bad data does get in , how to review that and make sure that it, um,
Speaker 1: (25:11)
Yeah, you could also expectations depending on, depending on which hubs you have, um, you could actually run a workflow to check, um, check that field's value, and then depending on how intricate, uh, you want to get, if you have operations hub and you needed to cross reference that against something else, maybe you need a custom code action, maybe you can just do it within a workflow. And then if it hit, if it does or does not meet whatever criteria, and you know, you can send a notification to somebody. So somebody entered, um, a, you know, in a, in a dropdown, they entered this value at this stage and then, you know that's not supposed to be there. You can always run a workflow to, to check for it to make sure that the value's correct. If not, you know, it triggers like a notification to them, Hey, this is wrong. So probably better to, to get it before they even do it. Uh, but a certain situation, if you do want like a manual review, you could run it through a workflow as well.
Speaker 2: (26:14)
Yeah, that's good. Good idea, . Awesome. So I, I mentioned, um, formatting issues and duplicates. I'll show formatting issues in a little bit. Um, we also have the, uh, new property insights. This is diving into the actual structure of your data. Um, do your properties have any uses across HubSpot? Are there other apps that are referencing those properties? Um, do any records have a value for that property? So what's the fill rate? Um, and this could be really useful to make decisions around, you know, what properties do I need for a workflow, for a list, for a report, um, as well as understanding where the data is coming from. So another part of this in the command center is we actually surface, you know, for, um, for individual properties, you can see where the data is coming from over time. Is it coming from workflows? Is it coming from forms? To give you context on that, um, that data flow and understand, you know, are we seeing, uh, you know, inputs from workflows? Is it mostly from a particular integration? If something goes wrong, it, it gives you, um, more visibility into, uh, those data connections.
Speaker 2: (27:47)
And lastly, uh, we also have insights into data sync health. So the command center will show you total number of connected data sync apps, um, as well as daily report of sync issues. So you can actually dig into are there errors, um, is it actively syncing and take action on those. Uh, if there are any failures,
Speaker 1: (28:12)
One thing that happens with those, those especially, um, we see errors, a lot of times they go tic, um, and someone from an external system doesn't see that eventually goes back and looks and says, oh my God, we haven't gotten data on, on this in, in a week. Uh, and I didn't realize until I was building a list or, or pulling that information. So, so being proactive on that, um, especially seeing things that are recurring, um, if there's something blocking it, um, blocking it from happening and getting ahead of that, we'll save a ton of headache done on.
Speaker 2: (28:51)
Yeah, a hundred percent. Um, this is the, the hope here is that, you know, instead of going in and manually checking individual apps, you have one place to check, you know, all of data sync. And you can see, uh, if there aren't any recurring errors, um,
Speaker 1: (29:08)
I know in the past process has been like minimum once a week go and check like the Salesforce connector or something, like, is any anything broken? Um, so I think that any, any of those connectors be able to have one place quick check, don't have to do too much of a deep dive or tells you what's, what's going on there. Yeah.
Speaker 2: (29:27)
Yeah, I will say, so right now the current version, it's just data sync. We don't have some of our other integrations. So the Salesforce integration isn't on there at this point, but, um, our goal is to cover all, all integrations, um, so that it's the, the one stop shop, uh, to monitor. I'm gonna jump into automation. So all of this monitoring is great, but you know, can you automate some of those simple, more repetitive tasks away? Um, and we have a new feature called automation recommendations, um, which has AI based suggestions on reformatting data for standard properties. So contact, first name, last name, email. We will detect these for you and allow you to make quick fixes, no data expertise needed. Um, those suggestions alone are an operations hub starter, but we have the ability to actually automatically accept those suggestions for some of those simpler use cases like capitalization, um, right out of the box in Operations Hub Pro. Uh, so similar scenario, if you have a bunch of new data, um, or you just have data coming in on an ongoing basis and you want to ensure that it's formatted correctly, whether you're using it for personalization tokens or um, other outreach, we have the ability to check those formatting issues.
Speaker 2: (31:03)
So for example, um, in this case, you know, there might be a placeholder, so last name, name or the capitalization doesn't seem right. You can accept those manually, um, and will automatically change the record. The real power here is within automation, it's a few of, a few of the rules are two click automations. You can capitalize first name, last name, and ensure, you know, when a suggestion comes up, when we find one of these, we will automatically fix it for you. Um, you can save that
Speaker 1: (31:41)
Cause no one likes getting a, you know, an email and your name is merged in and it's, you know, all lowercase.
Speaker 2: (31:48)
Yeah, exactly. . So
Speaker 1: (31:50)
Looks like you're not trying very hard, right? wanna come off as as professional.
Speaker 2: (31:55)
Yeah. Um, and once this is turned on, you can also see, you know, where those changes are happening. Um, a quick audit, and this isn't, this is outside of workflows, this is just a simple cleanup based on the insights that we have. Um, so you don't n need to go build something separate to manage some of these over time. Um, hopefully this makes it a lot easier to take care of some of those, uh, simpler, uh, data fixes that that come up time and time again. And that's all I have for, uh, the data cleanliness portion. Um, happy dive into any of these features more and any questions you have, we'll open it up to more q and a.
Speaker 1: (32:47)
Sure. I'll, I'll take, there's actually a question that I think someone asked a little while ago. Um, selling software licenses of subscriptions and, and maintenance, um, and relation to, to custom objects. So yes, uh, the short answer is, is yes. So if you need a record, um, of things that were line items, uh, on deals, as an example, I need to reference them later for workflows, emails, visibility and portals. Uh, and that information contains a lot of detailed data that you may or may not, you know, wanna directly, uh, update. Storing those, the custom object is definitely the right place to, to put that. Um, so think of it as in a sense a reflection of of product, library, library, but you have specific data related to that particular customer. So tracking usage the last time, like what version they're on, um, is, is a good place. Uh, if, if you're selling on-prem software, um, definitely place and then all information you can copy, uh, over into a contact segment list based on on all of that. And yes, the short answer is yes, definitely Custom objects are a great use case for that. Um, Kara, there's a question on validations for email address. I'm not exactly sure what that means other than looking for, I'm guessing for parts of an email. I dunno if you have those s
Speaker 2: (34:25)
So yeah, so there's a few thing, uh, I'm guessing this is about like, is this a legit email? Like what will we be able to send to this email? Um, we have integrations with third parties that will will check that. Um, but the other thing I always recommend is, you know, if you try to send them, you can see send to them, you can see like bounce rates. So we have that data within HubSpots. You can clean up any records that have previous, previously bounced. Um, but I'd say either, um, take a look at your existing database. If you're trying to look at brand new records, that's gonna be a little trickier and um, we don't have, you know, immediate insights on contact bounce rates. Um, so
Speaker 1: (35:23)
How do you suggest people go about leveraging validation rules for currently existing properties?
Speaker 2: (35:35)
Yeah, it's tricky right now because we,
Speaker 1: (35:38)
That's working on the spot would be like a tough question I'm sure. Yeah,
Speaker 2: (35:41)
We're still working on this and you know, I'll definitely uh, pass this feedback along to the team, um, cuz we know, you know, new properties isn't going to cover a lot of your database, um, especially if you're established customer. Um, and so we're definitely thinking about how we can, we can do this, uh, in the future. Um, right now it's, it's, it's gonna be tough. I think the, the best option is if you have a critical property and you wanna make sure there's validation, creating a new property will be the easiest way to do that. Um,
Speaker 1: (36:15)
Just be mindful of any lists, workflows.
Speaker 2: (36:19)
Speaker 1: (36:20)
And all those types of things. It's, yeah, it's a migration. Yes. Don't, don't underestimate the list. If it's that's really important, especially the older instances, the, the more that's built out, more likely it is that, that that particular property exists and is used in a lot of different places. Hub, strattice and cool tools to be able to help help you identify where those places are. Um, but yeah,
Speaker 2: (36:45)
Speaker 1: (36:46)
Redoing them. Um, let's see, what else? Time picker property time. Ooh, product is a request. The time pickers property time,
Speaker 2: (37:03)
It's a really good question. Um, I'm happy to to pass that along to the team as well. Um, I'm curious like what, what you would use that for just so I have context on the use case.
Speaker 1: (37:20)
Yeah, I'm sure anyone new ones with us that uh, has questions, um, suggestions. I'm sure Kara would love to hear all of the different use cases. Uh,
Speaker 2: (37:30)
Here's my, here's my email. Feel free to reach out to me.
Speaker 1: (37:33)
Yeah, absolutely. And that's, um, let's see if any other questions at all those, um, thanks everyone for showing up today. Uh, I hope this was, this was helpful. Um, we will also be staying at a a follow up as well get the recording. Uh, and like we mentioned, if, if there are any specific questions, definitely email us any just specific use cases you wanna run through. I'm Kara, be happy to volunteer her time. Be happy to hear this and hope everyone has a, a great rest of your day.