Name: Spring Cleaning Essentials: Blackbaud Altru® Data Management Best Practices
Uploaded: 2025-03-26T19:30:37.367Z
Duration: 43 min 40 s
Description: Spring Cleaning Essentials: Blackbaud Altru® Data Management Best Practices

Transcript for "Spring Cleaning Essentials: Blackbaud Altru® Data Management Best Practices": Alright. Hello, everyone. If you can hear me, can you please drop, an emoji in the chat? Just wanna make sure we're ready to get going here. Awesome. Looks like we are live. Okay. Well, thank you all for joining us today for the next installment in our arts and cultural webinar series, Spring Cleaning, Essentials for Maintaining a Healthy Altru Database. Please feel free to go ahead and introduce yourselves in the chat, and we will go ahead and just jump right in. My name is Alexandria Trempe, and I'm a senior customer success manager here at Blackbaud. Prior to joining Blackbaud, I worked in development and marketing at a children's museum, shout out to my friends at Collideum, and a foundation with house museums focused on historic preservation. At both organizations, one of my primary responsibilities was managing our organization's appeals, incoming donations, and reporting. I was a daily Altru user at both organizations and also managed an RE seven to Altru conversion. I live in Charleston, South Carolina with my husband, our two kiddos, our dog, and two cats. We got a full house over here. A little housekeeping to get started. The webinar audio will be broadcast through your computer speakers. If you encounter any audio or technical issues such as slides freezing, usually a quick refresh of your browser is the best way to get it working again. Worst case scenario, leave and log in again. Chat and q and a are located on the right hand side of the screen. It looks like most of you have found that. If we don't get to your question during the sessions, we will follow-up by email. And then next to chat, you should see documents. Go ahead and click on this link and you'll be able to see several links and resources you may want during our presentation or to save for future reference. You can adjust any settings by using the cog wheel at the bottom of the event space and sometimes slides look a little bit squished and gold cast. If you're having that issue, hover over the right hand corner of the display and click on the box to expand your slides. Also, one other note, sometimes it's helpful to follow along in your own database while we're going through these webinars. So feel free to open that up, and take a look as we're running through. Alright. So I'm a gardener. And each spring, once I'm pretty sure that the last frost has passed, I will spend time in my garden pruning, removing old growth, pulling out dead plants, and just generally tidying up. While there's nothing more rewarding than pulling a nice big tomato off of the vine, I know that I have to start with the not so fun dirty work months ahead of time to see the best growth and yield from my plants. Once I've made my first big sweep through the garden, regular maintenance helps me keep up with all of the weeds and pests that are competing with the plants that I've actually sown. Much like a garden, a database will produce the best results and the best data with regular care and attention. As you all know, Ultra is a very comprehensive system and is intended to cover most major functionalities for arts and cultural institutions. It's inevitable with many data entry points, users, constant additions, deletions, new new initiatives, etcetera, that your system will pick up errors along the way. When you go to use or extract your data for a mailing campaign donor research etcetera, those errors and issues can stand between you and the information that you need. By setting aside time to address some common issues and creating an organizational schedule for database maintenance, you can prevent compounding errors that make using your system seem difficult. Maintaining your data throughout the year will help you stay ahead of data problems, notice issues early on, and be prepared for your appeals and those last minute report requests that we've all received. Excuse me. Let's take a look at our best practice order of operations. Number one, identify issues that are common to your database. In your daily work, make note of errors that you're seeing frequently. Maybe you're pulling a list of new members to send your monthly newsletter and you notice some are missing email addresses or you're working on invitations for your gala and see backward salutations. Whatever it is, take time to record problems you're seeing so that you have a to do list to tackle once it's time to begin your cleanup. In addition, every organization should also have their own data entry policy guide. What works for a children's museum may not match the needs of an art institute. Different constituents and audiences require different treatment models. Setting down best practices that are specific to your organization, your practices, and incorporating those best practices into both your training and onboarding will help ensure that you have data entered consistently and correctly. Next, once you've identified your areas of top concern, create a plan of action. By looking at commonalities between your issues, you can create a plan to address them. In many cases, once you've decided to take charge of database health, you may initially have a significant number of impacted records, a little bit of a backlog. Tackling that first big batch of data problems, that first pass through the garden, will take time, but it will also make things easier down the road. Once the initial problems have been dealt with, you can set up automated processes to tackle frequent problem areas like duplicates. This will lighten the overall maintenance load and help keep things tidy going forward. And our last step is prevention, keeping those errors from happening in the first place. This is where automation and that policy guide are essential to helping you create some best practices for yourselves. Ultra has a number of cleanup tools built in, including Address Finder and Deceased Record Finder, which you'll find under Data tune up, duplicate management processes, and global changes. For many maintenance projects, query, export, and import are essential tools. Excel is also your friend for data hygiene work. As a reminder, your Altru subscription now includes Address Finder and deceased record finder features under data tune up to help you manage constituent updates. Address finder utilizes United States Post Office or USPS National Change of Address or NCUA database to look for updated address information. The USPS updates the NCUA database four times a year. You can also run AddressFinder four times per year. Deceased Record Finder is a service that screens existing constituents submitted from a database through the social security death index and other sources. These two easy to use features help ensure that you have clean and up to date information and avoid some embarrassing solicitation errors. Now, let's talk about the major data cleanup task, duplicates. We could probably do an entire webinar just on duplicate management, but we will just hit some of the highlights today. You may notice duplicates throughout the database as you pull a query, prepare for a mailing, or research donors or members. Duplicates can come from many different sources including data entry errors, web forms, etc. Identifying the root cause of your duplicates can help prevent those errors from being made in the future. Once you are ready to address existing duplicates you will need to run a duplicate search followed by a duplicate merge process. There are two different options for a duplicate constituent search either full or incremental. A full duplicate search will search the entire database. If you have never run duplicates before or if it's been a while this search process can take some time. An incremental duplicate search finds duplicates added or updated since the last full duplicate search. Your initial duplicate process should follow the steps outlined on this side. Number one, run the full duplicate search process. Then you're going to want to run the duplicate constituent report. Confirm that the constituents returned in the report should actually be merged. You definitely want to take a take a look through and make sure that those are true true duplicates and not just folks with similar sounding names. Then run the merge process. You can repeat steps one through four until your duplicates are resolved and your data is clean. Then you'll be ready to set up some automated processes. Addressing duplicates is a great way to familiarize yourself with your overall system while addressing a common roadblock for many organizations. Now let's talk about the different ways you can merge constituents. If there are just a couple duplicates or your results include some constituents you would prefer to address individually, you can manually merge those records using the merge to constituents tool found under duplicates. The tool will allow you to select your source and target records, merge configuration, and determine how you handle the extra record, either by deleting it or marking it inactive. You can also configure how a merge process handles conflicting data. For example, if names are different on match constituents, you can choose whether to keep the target's name, the source's name, or whichever name is most complete. If you have many duplicates, sometimes manually addressing each of those records is not possible due to time constraints. You can use the constituent merge process to mass merge records. An essential piece of the merge process is the percentage match threshold, which determines how much information on each record must be the same in order to consider the records a match. There are three separate sets of match confidence thresholds. One for records added by batch or import, one for records added through web forms, and one for records added manually on the add an individual or add an organization screens. If necessary, you can edit default thresholds for your organization. However, we recommend that you retain the defaults because the matching algorithm is designed to provide optimal results with those percentages and may return unexpected results if you change them. For example, if two records have matching email addresses but no other matching data, Altru flags them as possible matches because their match confidence score of 70 is within the possible matches threshold threshold default range. But if you change the threshold by just one point, Altru is no longer going to flag those records. The Altru constituent matching algorithm goes through several steps to identify matches. First, it standardizes data on the incoming record, Then it selects a pool of records that are potential matches and standardizes the data on those records to compare. Then it compares field values on incoming records with field values on the existing record and calculates their match scores, which are weighted based on field type. Field type is gonna be something like phone number, email address, etcetera. The algorithm then deducts match scores from a perfect score of 100 to calculate that total match confidence score. Last, Altru will compare match confidence scores to the match confidence threshold to determine whether the incoming record is a match, a possible match, or not a match. It is very very important to note that there is no undo for the constituent merge process. Be certain that your match threshold is sensitive enough to avoid merging records that are not truly duplicates. Once you've dealt with your initial bulk duplicates, you can use these best practice guidelines to set up a process to address duplicates automatically to prevent build up and free up staff time. We recommend that you run a full duplicate search at least once a quarter. If you have the time, you can even do it monthly or weekly if you'd like. Create a merge process that's going to search for 100% matches based on the full duplicate search. Then you can use the duplicate constituent report to view the full search and research records that have less than a % match. Run an incremental duplicate search and create a search create a job schedule that runs the search daily. You can create a merge process that's searching for a % matches based on your incremental duplicate search and then a job schedule that runs the merge process daily. Make sure your merge process job runs after your search job to be sure that you're collecting all the correct records and duplicates. Now we'll get into some common issues and how you can fix them using query, import, and export. For all of these topics, you will find resources included on the documents section of the webinar screen. First, let's talk about query browse which can be used to correct records in each of these scenarios. You can access query browse on the right hand side of your complete query. Once you click browse, Altru will ask you to select a record type to open based on your source view. A source view is going to be something like constituent page, marriage options, membership page, etc. You can then click through the records that it's returning to edit information. Alright, scenario one. To begin fixing constituent records without an address, first you will need to use a query to identify those records. On the screen you can see a screenshot of a sample query. The resources guide also includes step by step instructions for setting your own query up. You're going to want to select a source view of constituents and then you're going to highlight the applicable fields. You can also specify which information you would like to extract in the query under the display field. If you're going to be exporting or importing records, you always want to remember to include a lookup ID. Once you've identified your impacted impacted records, you have two options to fix them. Option one, you can use query browse, which we just just got just discussed, to open the record and update the address. Option two, you can use import to either update the status of the address to be do not mail or use import to update the address that's on file for the constituent. Much like our first scenario with addresses, there's two steps to fixing spousal records with two last names. First, you'll need to identify impacted records using a query, and your source view for that query should be constituent, and then you'll need to set your input and results fields. For specific fields, I've got a KB included that's titled I need to find spouses with different last names. Once you've identified impacted records, you can begin to fix them using query browse. This scenario is a good example of a situation where knowing your constituents and their preferences is essential. It's much more common now for spouses to have different last names and less formal salutation preferences. You need to know how folks like to be addressed before you can, before you can address them properly in your outreach options. This brings us to our next topic, missus and mister salutations. You might notice when you're processing mailings in Altru that your constituent's addressee or salutation fields appear as missus and mister instead of mister and missus. Typically, you'll see addresses or salutations coming through like this when a couple of combination a couple of conditions is met. First, you may have a name format that begins with title and spouse title, then the female constituent is listed as the primary member on the household record, or your constituent records have an unknown gender. You can also have name format options that are configured to build joint name formats with the primary household member or female constituent first. It's important to note that many organizations now are choosing to forego formal name formatting and moving towards a more informal style. For example, John and Jane Smith rather than mister and missus John Smith or just mister and missus Smith. If you choose to continue using formal salutations, here's some options to configure to prevent this from happening and to check. Option one, when you're processing mailings, ensure that your name format options are configured to list the male constituent first. Option two, you can edit female name formats to a different format such as spouse title and title. This would then create a record option of mister and missus. You can also query on primary addressee primary salutations that begin with missus and mister to clean them up manually. Option three, you can make mail constituents the primary household member. Another option to fix this issue is to ensure that the mail constituent is the primary household member. When Altru pulls name formats for mailing purposes, if no genders are listed or specified in the name format options area, the system will list the primary household member first. Your organization can make the male constituent the primary household member as an internal best practice. Our next topic is global changes. In order to use global change, you'll need the global change system role added to your profile. Global change in Altru is a feature that allows users to make bulk updates or modifications to constituent data in the database. This feature enables users to perform actions such as adding or deleting attributes, mail preferences, solicit codes, relationship managers, and more for a selection of constituents or all constituents at once. Because this role is very impactful, it's very important that it's limited and that the folks who are going to use it know how to use it well. Additionally, global change instances can be created, edited, assigned permissions, and processed to apply changes efficiently across multiple records. Let's talk about three types of global change you can use to clean up your database. We've got batch reports, business processes, and constituent changes. Over time, sometimes your database will accumulate numerous batch control and exception reports that you don't need anymore. To remove these from the database, you can create a batch control and exception report global change definition. After you create the definition, you can execute the global change process to remove those batch reports. As a best practice, we'd recommend deleting reports that are three years or older. You're probably not going to need those anymore. Much like excess batch reports, your database can also accumulate business process output files that you no longer need. Most common business processes are going to include the export process, acknowledgments, marketing efforts, appeal mailings, membership renewals, membership card printing, etcetera. Similar to the the batch reports, we're gonna recommend deleting processes that are three years or older. While old output files have been deleted, your export process remains unchanged, so you don't want to worry about impacting that. You can also use global changes to add or delete segments on a constituent record. This can help update specific information on a constituent record and make it easier to query them, update the relationship manager, change their solicit codes, etcetera. Using global change, you can target a specific group of records in your system. For example, trustees for your organization are rotated annually, one every three years, etcetera. So every year, you're going to have to remove the trustee constituency from all previous year trustees and then add it to your new folks. Using a selection of your previous year trustees, you can use the Delete user defined constituency definition included in global changes and remove the trustee constituency from all expired trustee records. If you've recently completed a capital campaign or other major campaign with pledges, you may be left with some pledges that are overdue, unlikely to be filled fulfilled, etcetera. Those pledges can make can continue to appear in the system and make it more difficult to accurately understand your data. You can write off an entire group of pledges so the balance for each no longer appears as expected income in your general ledger. In one action, you can write off multiple pledges that meet the set of criteria you've defined. The first step to globally writing off pledges is to collect the pledges you would like to address using a query and a selection from the revenue source view. When you select to create a static selection, the program is going to write off only those pledges that meet the criteria for that selection at the exact time you create the selection. You can write off pledges in a static selection only once. To create a global write off process you can use multiple times, select to create a dynamic selection. Dynamic selections are going to include any new pledges that meet the original criteria each time you run the write off process. You can also use pledge write off batch to write off multiple pledges at one time, write off the full pledge balance or selected installments, and take advantage of the approval workflow and validation functionality within batch. Next, I wanna take a moment to discuss security. This is a vital but often overlooked piece in the data maintenance puzzle. First, take a look at your org admins. As a rule of thumb, we recommend limiting the number of org admins to maintain security for your database. Two or three is a bit of a sweet spot. Do not limit org admin access to just one user at the organization. If something happens and your one org admin is unexpectedly gone, we'll call this the won the lottery theory, you don't wanna be scrambling to get access to essential pieces of Altru. Three is a nice number in case you have two org admins out or inaccessible simultaneously. You should also take a look to see who your system role administrators are. This is another role that should be limited to just a few users at the organization as it has extensive access system wide. It is a best practice to audit your users on a regular basis and confirm that those who no longer need access to the system, whether they have left the organization or moved into a new role, have been removed. You should also take a look at the security roles you've assigned to your users. We recommend limiting access to different roles until a need for some of those features and functions has been demonstrated. In other words, don't give every user access to capabilities that they're not going to need in their day to day work. And finally, here are just a few areas where we commonly see some data errors build up. If you need recommendations on database health and maintenance, reach out to your customer success manager. We're here to help and have resources to help you tackle your data goals. And with that, I think Rosita has been hitting most everything in the chat, but let me take a quick glance through some of these questions here to see if there's anything we need to jump on now. Yeah. I'm typing fast. So, I'm But I can go ahead and actually, let me ask a couple of the ones because we got a lot of repeats. Yep. So we've got a lot in the chatter about, you know, mister and missus, missus and mister, what's right, what's what's etiquette, what's not etiquette. Just know you can make these whatever you want. So if your organization doesn't mind the missus and mister and that's how you guys want to refer to people, you can't. As for not wanting to, ask for identify people by gender, it might be the best practice to not use titles. Just use their names. So you could just use their first names and last names as part of the addressee and salutation instead of using the titles. So you can absolutely, do that. Altru does not, look at gender as a determining factor when it's building the name formats. So all it's considering is the record that you're on and the spouse, individual record that's tied to it. So it looks at as constituent one and constituent two, and constituent one is whatever record you're on. So if I have my record with Idris Elba, who's my husband, on my record, the system's gonna create my name format as missus and mister because I'm constituent one. I'm on that record. If I go to Idris's record, he's now constituent one. I'm constituent two. So the name format looks at that, you know, mister or missus based on the record that I'm on. This is something that we have been told and asked to kinda look at and review that is gonna be with our product development department to determine, you know, any updates and changes that we make to that. Yeah. Also, another quick question people are asking about, you know, how can you determine or what's the best practice for defaulting, to a male head of household. The best way to do that is if you look at your name format options, there is a setting. There's a tab for joint name format. So you don't have to worry about touching every single record. If you look at that specific option, there is an option that says no matter what, if I am pulling a record where both individuals are, pulling as results of that query that I have for my mailing, it has a setting that says always pick the mail name format first. That's on that joint name format, name format option where you can set that. So at that point, if you're keeping up with the genders, the system will see, okay, if I see Rosita and Idris pop up in my query to send this mailing out, it's gonna make sure I use the name format of Idris. That's how you can default to that male head of household no matter what the system is adding for adding to that female record. And I think I think that's all of the questions here. I'll keep scanning the chat here to see what else we have. So give me just a second. Let me just kinda go through that. Thanks for your patience as I'm reading through these fast. Okay. I got a lot of questions also about, how do we, deal with, like, duplicate records where they have, like, maybe a nickname, Chris versus Christopher. All again, the system will, will be able to see that it's a valid and matching record if you add that information. So, also, on the constituent record in that personal info tab, there you can add in some information about their nickname. So first and foremost, I would pick if there's a certain way that you want the to address this donor or constituent and they prefer to be Chris instead of Christopher, then I would just update their record to to Chris. But if they prefer to be, you know, Christopher, but they also wanna be you wanna be formal about it, then add Chris as the nickname. So even if they try to, you know, create or do a transaction online, it should identify Chris as a valid entry for Christopher for that same record. Now that's if you're not using Extrulink. So, Extrulink's a little bit different the way they do their deduping process, you you may not see that action. But for those of you who don't have Extruling, even online, if someone if you have Chris as the nickname, it'll pick up and say, oh, that's the same Christopher and Chris are the same record. And that's if the name and the email address if the email address is exactly the same, it will know it's the same record. Okay. Any tips on help when you have two separate records when they accidentally get merged? Oh, that's that's from Dawn. Hey, Dawn. Okay. So for that, unfortunately, you're going to have to create the record and split the information up, auto you know, but manually by hand. There is no undo button in when we do our mass, mass merges. Okay? So no undo. So you're gonna have to go back and actually do that by hand. Does Ultra ever recognize street and street are the same? Yes. So Lauren, for that, when we're looking again at all mine transactions coming in, if that's where the duplicates are happen, yes. There should be a setting that should be checked if you go to, all true. And then in your all true, go to the, let me find it real quick for you off the top of my head. So to make sure you have that setting, if you go to Altru and then go to administration, in administration, you'll see the constituent match settings. If you have access to to that, if you're or database if you went matching settings in that section, in that edit, then at the very, very bottom, there's a checkbox that says, hey. If you know, ignore any matching if the first name, last name, and the email match exactly. That should take care of any addresses, you know, any address, with street spelled out versus abbreviated. It takes the address out of the equation if you do it, if this if you have that box checked because, again, it's just looking at the name and the email address to make sure it matches. Then it finds the link. Let's see. Yes. Yes. Untangling those records. Yes. I yes. We yeah. That's it. It's a tough one when you accidentally merge two two records together. Yeah. We're always looking at ways that we can, really update and fine tune our, fine tune our duplicate settings. But, again, we're running into some, we're running into some issues with, like, making sure we're in line with our with our, our partners to make sure what their duplicate settings aren't, you know, in conflict with ours. So we're still working that out. When a constituent buys a ticket online, it does not apply to their record but makes a new constituent record. It will now allow us to merge to constituent. For Dina, Thurmond, you may wanna go ahead and create a support for that because it could be we needed to figure out why it won't let you merge. It might be because it could be trying to merge to records that have a a membership or something like that. But, with all of these, there should be some really good knowledge based tips on how to handle those types of merge situations where both records have a membership or, both records are trying to attend the same special event. You'll get that error message sometimes when you try to merge them together. Contact support if you can't find that in the knowledge based solution, but we should have some articles on that. We did get a a lot of comments about wanting to do a deeper dive on duplicates. I think that's a great idea. I'll see about us getting that in, play so you guys can, see that. And so we'll be looking we'll see if we can get that, session together for you because we do have a lot of questions around how to handle, duplicates. Let's see. How do we check, if constituent should be merged in the merge process? Okay. So when you set up the automatic merge processes, I hope you were very clear in saying please only schedule that process for 100% matches. I would not have a schedule for anything quite less than that unless you know for sure that you don't have a lot of, suffixes where you have juniors and seniors with the same exact name because that can, fall into, that matching criteria of, you know, just slightly less than a hundred, and they also live in the same house. So be careful around that. We you can look at the preview before you merge through a mass merge in the mass merge, section. If you do it for, like, a lower, let's say, 95%, you can just have the system say, okay. Show me that 95%. But in the table, there's gonna be a table that's gonna give you a preview. It'll show you all the records it's gonna try to merge. So in that, you can select, hey. Yes. This is actually a duplicate. I want you to merge it. Or no. I'm not sure if this is a duplicate, so skip it. Or no. This is definitely not a duplicate. Don't ever show me again. And you would say delete match. That doesn't delete any records. That just deletes them for being ever being, connected again, as a duplicate record. So you do have those options so I wanna jump in there and urge caution in that area because I've I've from experience, I can say be very careful with that merge process. Yes. There's no undo. There's no undo. Let's see. Oh, this is another great one. So the merge process looks at all the pieces of data. If a record does not have an address, Address Finder is not gonna give you an address. It does that's not how Address Finder works. You have to have a starting address so it has that to compare to the national database. So, you know, submitting blank addresses won't give you an error message. It's not going to allow you to, create that new address. It's not gonna give you the new address. So, just be mindful of that. Yeah. It's not like credit card updater for addresses. Correct. Correct. I got another question here about what to do when you have a, individual or organization record that's the wrong type. This can happen sometimes where, organizations are put in as individuals and vice versa. The only way to do that is to create a brand new record in the new record type and then transfer over that information. You should be able, in those cases, is in any revenue transaction, you should be able to edit the transaction, which will allow you to edit the constituent names so you can put it on the new constituent name that you create. So there is a way to, do that, but it is manual. The system won't do it automatically for you. Alright. Oh, sorry. I got one more one more clarifying one, then we can let I'll let you guys go. Sorry. So, we got one more question asking, you know, about the the the blank addresses. Can I take a blank address and merge it with an, address that has or a record that has an address? Yes. You should you will be able to do that. Amazing. Thank you, Rosita. Okay. I think that hit the majority of our questions. So I'm just gonna run through a couple closing slides here. And if anything comes else comes up in the meantime, we can hit those at the end. But next, just a quick plug for our next webinar in the Ultra webinar series. It's going to be April 23, and we will be covering, Ask Ladders and Smartfields. That's definitely a great one. I recommend attending that. Then we also have just launched registration for BB Dev Days twenty twenty five. That's going to be coming up in early June. If you haven't attended before, BBDEV Days is great. It's a virtual conference for, developers of all skill levels. So that's maybe somebody who's never developed all the way up to professionals. And so it's a three day long conference where you can go through innovative ways to automate and extend your Blackbaud solutions. It's not limited to Altru. It covers RE NXT, FE NXT, you name it. And we'll have other Blackbaud pros, partners, peers, and then they have topics all over the board. Major ones for Altru would be something like Power Automate. And then a couple resources to run through. Just a reminder that you have Blackbaud University. Blackbaud University includes free basic courses for folks who do not have a learn subscription. And then, of course, if you have a learn subscription, you can access the full Altru catalog. We also have customer support and knowledge base on hand to help with your troubleshooting, or how to article questions. And then last is Blackbaud Community. I highly recommend for folks to take a look at Blackbaud Community if they're not familiar with it. It's a great way to engage with your all true peers and maybe ask some more specific questions for other daily users or other organizations for how they're using the system for specific items. Those are my wrap up slides. Any questions come up since our last round? Rosita, are you good on your end? I have a I wanna do a couple more shout outs if I could. I do. About the about the BB Dev Days. We have, we actually have Altru content, so please join us. There's a small group of Altru customers that have been looking at using Power BI, and other reporting tools. So please, if you're interested, definitely join us for BBDEV days. We've got some cool stuff to show you guys and, get you guys learning. We're starting to build some, starting to build some user groups around that too. If you're interested, just select your CSM now and they can get you the information on BB Dev Days. Amazing. I've seen a couple of questions about accessing resources after the webinar. I think that it sends them out to you, but if not, please contact your CSM and I'll make sure everybody has a copy of the resource list so that they can provide them to you if you need them. Alright. And and we will get back to anybody who has, like, specific questions. We'll go back and I'll make sure I'll get answers to all of them. So thank you guys so much for attending today. Amazing. Thank you all so much. We appreciate it and have a great rest of your day. Bye bye.