Transcript for "Simplifying Communication Preferences with Consent in Blackbaud Raiser's Edge NXT®": Hi, everyone. Welcome. Welcome so much welcome, and thank you so much for being here. Today, we're gonna be looking at how communication preferences are evolving in the Raiser edge NXT. So we're moving beyond solicit codes into a dedicated consent model. My sessions are part education, part practical guidance with some polls along the way, so I hope you'll participate. At the end of our time together, I hope you'll understand how consent can power your organization and your communications and consider how it can fit in to your work. What we'll be covering days. So we're gonna do a quick welcome CRM a poll. We'll talk about why consent matters, what it even is, how it's being used out in the real world, how you can adopt it and get Arts, and then I'll share some resources at the end, and we'll hopefully have some time for some questions. So first, let me introduce myself. I'm System Mattia. I'm a senior principal business consultant here at Blackbaud. I've been here about seven years now. And prior to that, I was a fundraiser and a database admin in the world of food banking. So I worked at a regional food bank here in in my area and really loved the experience. At Blackbaud, I specialize in razors at Gen NXT consulting, implementations, migrations, and mergers, as well as our new development agent onboarding. When I'm not doing those things, I'm a big fan of a good book, some good wine, and a good place to do both of those things. So I love traveling with my family. I'd like to know a little bit about you all. So if you can participate in my poll, my first of three polls, I'm gonna open the poll now, and let me know a little bit about you and your organization by telling me how are you currently managing communication preferences. So you should see on the right hand side of your screen a polls tab that just opened. Feel free to submit your votes. Are you using solicit codes for tried and true OG codes? Are you using consent? Are you using something else Online constituent Customer fields? Are you not sure? We'll share the results here. These are live. Alright. Thanks for participating. This is allowing me to kinda see where everyone's at. Give you a couple more seconds to to respond. Allows me to get to know y'all. K. Not surprising. I'm seeing solicit Cover in the in the, little Learn here. Okay. Great. I'm gonna close the poll now Aid appreciate you participating. Again, it's one of three, so, I love hearing from you all in this way. So why does consent matter? Obviously, based on the poll, we're we're seeing that Net surprising, solicit codes are our tried and true method of communication preferences today days. But why does it matter to think about how consent can fit in your organization? First, our donors expect so much of us. Right? And that's coming from every facet, every area of what we do. They're expecting more transparency, more control. They wanna be able to give their preferences and for you to honor them even when they're nuanced. They want to make sure that we are adhering to data governance laws, and they wanna be able to change their preferences when they can, when they want to. And we know today that solicit codes, while still really valuable and really helpful, there's there's limitations to that. Right? Sometimes our own staff Aid our team don't understand what those codes mean when they see it on the constituent record. It's often hard to explain to donors, and they don't even get to see them. There's no transparency there. It also is limiting when it comes to granularity, and it's often that all or Net nothing approach. So we're really seeing that consent is the evolution of a more modern communication preference management system. We can track both communication type Express preferences as well as Community contact method preferences. When that donor calls us and says, I really want your event emails, but I don't want your solicitation emails. We're actually able to manage those preferences, in the consent feature. I talk to organizations all the time and ask them how how that exact scenario. If a donor calls or Insitute calls and says, hey. I really want your event emails, but I don't I don't want your solicitation emails. I like the mailed version better, etcetera. How can you manage that? More often than not, I hear we don't really have a way to manage that for it's not easy. Consent allows us to track those decisions as well as also get a history, which is so valuable. Right? And we don't have those things with solicit codes days. And consent can really fill that void. What even is consent? So if you are here and you're unfamiliar with consent for you haven't had the time to even look at that feature in the Raiser Edge NXT, I'm here for you. So let's first talk about how consent is different than solicit Cover, but then how they work together. They're friends. I promise. They they depend on each other. So consent represents the permission a constituent gives your organization to communicate with them and use their data. It's the official record of their opt in or opt out decisions plus the history behind Team. Really valuable piece, that history. Solicit codes define the rules of contact Online that do not email or do not email event invitations. In short, consent is the record of the Donation. Solicit codes are the practical filters that act on those decisions. And like I said, solicit codes aren't going away anytime soon. They are tried and true OG codes. They are being triggered or fed by Center. So they really do depend on each other. In the consent feature, there are some key terms and concepts I just wanted to share with you today. Channel. We'll talk about channel a lot. Channel is the communication method. Email, mail, SMS, or phone are our typical top four channels. We have a couple other channels in there as well. Categories are the specific communications underneath that variety of channel. For example, a newsletter. Your organization might send in U newsletter via mail. It also might send it via email. Those are two type of consent configurations to get a donor's preferences on. Same with events. You might send event Inc. invitations via mail, email, or even text message. Those are three different types of consent configurations and options that you can provide your donors and get their preferences on. The consent statement is language shown to constituents at the time of them giving their preferences, so typically in an online for, so you can record what exactly they saw and what they agreed to and how you framed it. Privacy policy is the org's donor data management policy that's shown and provided Institute, typically, again, in an online form, but also it's public and available for any donor to or constituent to access. Source is where or how the preference was collected. Did you collect this in an online form or did that donor call in? Did you get it sent in with a remit and a donation? I, in my fundraising days, saw lots of ways that donors were able to indicate their preferences. We get some really cool things sent back to us handwritten in the in the mail. Status is the Response Response Team that constituent gave U that specific communication preference. Did they opt in for did they opt out? So, again, these are some key Connected Net terms that you'll see in the System in the configuration section Aid all the help files that I wanted you to be familiar with. With. A quick overview of how consent actually works within the Raiser Edge NXT ecosphere. Steps one and two are about configuration. So you define your channels and your categories, which are a user defined table. They're your categories, what you send and provide to your constituents, how you communicate to them, and sources. Again, another user defined table of how you expect your sources, to to be. Those map to those related solicit codes for every response. Once configured, steps three through six are then using consent. So adding the consent to online forms, the constituent responds. They also can respond offline. Right? They can call you. They could email you separately. They could also tell you in person that they no longer want to receive that event email. The consent is recorded either individually on a record just like you would add a solicit code today, you would add the consent, or it can be added Inc. bulk via import. Then the magic is where due to the configuration, the solicit codes are updated automatically. So if the constituent opts in, U might your configuration might dictate that a code is added. If they opt out, it might dictate that a code is removed, vice versa. This automation in step six is really key to reducing manual effort, and it reduces errors. Some guidelines around consent. So consent can definitely capture your communication preferences, track those Champions and opt outs, maintain that history, but it can't replace every business rule. It doesn't Luminate the need for thoughtful segmentation or Learn up undefined or poorly AgeFinder or, design solicit code strategies. So it can do a lot. It gives us a lot more features with that history and the response management, but it doesn't solve the whole thing. It's not totally Critical, around some overall organization governance issues. But it's definitely a step in the right direction. Let's talk about using consent out in the real world. So the next few slides are actually product screenshots showing consent in Raiser Edge NXT. If you're unfamiliar, I think this is sometimes helpful to see. I think of Center. I'm presenting this in Aid of three U, the end user, the database user view, the database admin view, and then the donor view. So first, the database end user view. If you're a user or that's able to enter consent at the constituent record level, U able to track overall channel responses as well as then those subcategories or categories within that channel Online we see here. Once consent is added for the first time, we now have a consent history starting to build. I really love this area because I can see so much more. I can now see when the consent was added, what the response is, opt in or opt out, and even the user that added it, which is really valuable for me as any data database user. I could talk to that person, see what context that that consent was given. I can also see the Search, so I can tell days it provided by the constituent in Purchase, over the phone, or via a form. That just builds a lot more, information for us. It's also exportable if you need records for compliance, which is really helpful. The donor view is mainly talking about forms. So the consent feature is integrated within all of the Raiser Edge NXT Forms, online giving forms, event registration forms, Net Institute forms, and someday soon, our membership forms, which we're really excited about. So this consistent consent integration allows you to meet your donors where you're where they're at. It also allows them to show that you're giving them options Aid that you're going to honor those options. It's important to note here that I always like to tell customers that this area just because you have maybe, say, 20 consent Information, in this form, you don't have to offer all 20. You can select exactly which consent preferences communication preferences you want your constituents to respond to. So you can manage them based on who the audience is for that form or the type of constituent or the type of communication that you're interested in getting those opt in responses for. On the admin side of things, in control panel and settings, we have the consent management configuration. This is where we're able to see all of the various channels and then those categories within each channel. Within each channel configuration, you can totally dictate how you want the razor's edge to behave when it comes to triggering those solicit codes. You can set up what codes are added or removed based on a constituent opting in or opting out. And for those of us that are used to using those OG solicit codes of a lot of times those more quote, unquote negative codes of the do not email, the do not email, event invitation styles, This really unlocks things for you because now you can actually get opt ins. You can see what donors want to receive from your organization, how they wanna be communicated to you. How cool is that? Because now we can actually meet them and provide meet them where they're at, provide them what they want. And that should increase trust and transparency with your donors Aid your organization, make them happier that you're honoring their request, and hopefully Fundraising your response rates because, again, you're not annoying them with thousands of emails that they've asked for you to no longer send. They're gonna just be Giving the things they want Aid, hopefully, again, reading and responding to those things. Out in the real world, there Card some great use cases that we're already seeing from clients using the consent feature. So scenario one is like an annual giving scenario. A donor says, I'm happy to support during Giving Day, but I don't want any other fundraising emails any other time. Great. We can set that up Aid consent. We can set up an email category for Giving Day emails and an email category for all other fundraising emails Aid opt that constituent into Giving Day and out of all other fundraising emails. Another scenario is still that more broad channel Performance, and so that doesn't go away by when we use consent. I talked about being able to be granular, but if your organization is not ready for that or isn't there yet or doesn't even have those needs, you can still just manage constituent communication preferences at that overall channel level. I'm sure everybody here at one point in their careers have heard a donor days, save money on postage. Just send me emails or text messages. Great. We can do that. You can set up and add to that constituent record do not mail. They have opted out of the mail channel, but you can opt them into emails or SMS at a channel level. Consent can also be used for internal use only or some what some of my colleagues like to use the term here at Blackbaud is the back office use only. This is where you can add those Cover, again, only within the consent configuration. You wouldn't put them on a form, for a constituent respond to, but an example that I often see is, like, the president or the executive director's holiday card list. You can opt your constituents in Team will trigger that solicit code, putting them on that mailing list. And then if they do opt out or request to be added to that list because they heard their friend got the card, you can then continue to opting opt constituents in. Again, this isn't something though that you would add to a form because you probably don't want the general public saying that they want to be added to the president's holiday card list. It's still able to be used though in the consent feature. I don't know what happened to scenario four. So we have I'm gonna skip to scenario five. Apparently, I couldn't count to Team when I made this slide, but there is a blog post in the Blackbaud community, gonna be published this week after this Website, and scenario four will be in there. So it's a little Easter egg for you. Scenario five, though, is talking again about those segmented lists. If a donor says to you, I want emails about reunion and athletic events only. Today, right now, could you honor that request? Could you make sure that somebody pulling those lists knows how to capture just those constituents? You might Net. And but you can using consent. That's a very easy channel Inc. different categories, reunion emails for athletic event emails that you can set up. I hope it's helpful. Some of our other clients have used consent already. Now your real probably question is, is this worth it? How do we start? Change is hard, and it's really hard to overall workflows and processes in our day to day. I totally get it. So let's talk about making the move. Why now? Why are we talking about this now? Why why consider making that switch now? Once you start adopting consent Center your organization, you're gonna see immediate benefits like what I've already spoken about. Easier for users, easier for donors, more transparency and visibility, and that more modern preference management style of communication management. There's long term benefits as well. You're gonna get and build that history of preferences over time, and you'll be ready to adopt other existing features within the Raiser Gen NXT already, like our development agent who does U consent. There's also future benefits. So starting consent today and utilizing it will put you in a great position to stay ahead of future legislation and Aid laws that might come to your state or country. Also, it'll make sure that you're ready for future product integrations and dependencies. Reminder. Center not replacing your strategy. It's just becoming the foundation for future communication capabilities. You might be saying out loud, and I just can't hear you or thinking, but we already U solicit codes. We don't know where to start. Our data and solicit codes are messy. Ah, this is this feels hard. I wanna hear from you all. This is my second poll. I love me a good poll. So as I open this up, again, you're gonna see it in the right hand side. You'll see a little polls tab. What is the biggest obstacle preventing your organization from adopting consent today? So you're already using solicit codes. You just really love them and you don't wanna let go of them. You don't have to. Hard to get others on Award. Unclear business value. Let's share some some results here. Okay. Higher. So some of the winners here is we don't know where to Arts. Data cleanup concerns, limited staff Team, and resources. Amen to that. K. Awesome. Well, thank you so much for that feedback. Great. I'm gonna close the poll now. This is really helpful for me to understand kinda where you all are at, in today's today's world and all the other things you have going on with your your organization and specifically your Raiser with Genex Team. So like I said, I get it. It is hard to make CRM big change. It's hard because you have limited staff and resources, and you wouldn't even know where to start. So here's a little bit of what, I like to share with customers that I work with one on one on how to get started because well, if this does feel hard. So first and foremost, just start School. Take one step at a time. That's overall my my my best guidance probably. The first step is I recommend that customers review their existing solicit codes. Dust them off. Look at those the latest definitions. Pull around your organization and see if users even know what they mean anymore. And are they still a fit for your current business needs? Oftentimes, we're just using them because we always have done it. Right? We've always done it this way. That's what I hear a lot. So taking a refreshed look at what those solicit codes are kinda help you start framing up and imagining how consent preferences will drive those codes. Again, solicit codes aren't going away. You can still use Team, but it's really good before we start configuring the new consent feature to make sure that the solicit codes we have are appropriate for our today's needs. Net, step two is configuring consent. So I showed you quickly with some screenshots from the product, going into setting Cultural Manager settings and control panel. Identify what your categories are. So what are all of the things that we send Team? Mail, email, text, as well as internal codes that we need. What are what are they? Set them up in the categories table. What are our sources? How are we expecting to receive Center? In person, phone, online form, etcetera. Set up your statements Aid then map the consent responses to those existing solicit codes. Next is preparing your users for the adoption. So you haven't even added consent on anyone's record. Maybe you did on your own record because you're testing it out, but you really haven't started using it for your population. But you wanna prepare your users for that adoption. So update your your workflows and your standard operating procedures. Share the definitions of your solicit codes. Again, if you've dusted them off and revisited them, more likely, than not, you need to share those definitions with your U users. Even veteran users might need a good reminder as to what they mean. So when they're looking at constituent records, they they know when and how to read them and use them. Also, train your database admins Aid plan on some communication for the rest of your database end users. Hey. You're gonna start seeing a consent tile populated. This is how you view the consent history. And don't worry. Our Solutions codes are not going away. But now you're gonna get a history and context as to what your our donor's preferences are. That's fantastic. Another step is then now to provide consent to constituents. Add consent into your donation forms, your registration forms, your constituent forms, and any other constituent touch point you might have. Maybe you have it in surveys or printed on Direct mail remits. You're able to integrate the constituent or communication preference gathering in all areas of your communications going forward. Last but not least, migrate gradually. Like, this does not have to be a big overhaul. It doesn't have a bit to be some big bang kind of conversion. No one has to be down for hours or anything like that. Just start maybe with new donors and new event registrations. How about that? Does that seem easier? Maybe you start with one communication category. Maybe it's just, hey. We have an Marketing, Center. So we wanna start getting communication preferences around event invitations. That will allow you to kinda dip your toes into utilizing consent that you can then build off of as you can start seeing the benefits. So, again, while some of these steps have to be done in order, they don't have to be all done at the same time. Like I talked about, it's great to reevaluate your solicit codes. And so with consent in mind during this exercise, we recommend Aid of setting your solicit code strategy. And there's a link at the end of this presentation that we have published in our help files of how to structure your solicit code strategy with consent in mind. So here's some examples. You'll see that first column are solicit codes without channel categories, but yet a mix of negative and positive codes. So you might have do not email, send all email. Do not mail, send all mail. That allows you to Management at the at the channel level if they want have opted in or have opted out of all emails, for example. The second column is a demonstration of solicit codes with channel categories, but still on the kind of all negative, the do not solicit code style. So we still, of course, have our overall channels of do not email, do not phone, do not mail, but then we have those categories under email. So do not email newsletter, do not email invitations, do not email appeals. Likewise, under the the mail category, we would or excuse me, mail channel, we would have categories such as do not mail the Direct, appeals, or invitations as well because those are the different ways you send communications out to your donors today. Another example is solicit codes with channel categories with that mix of negative and positive preferences. So you might see do not email newsletter and then send email newsletter because, again, you've got the opt in. You wanna be able to see that a constituent days said, heck yeah. I can't wait to to read your next newsletter. You might have options Online do not mail appeals and mail appeals. Do not solicit for Giving Day, but, yes, send Giving Day solicitations. So, again, at the time of this exercise that you are reevaluating your solicit codes, think about how there might be an opportunity for some additions. A little bit more about the privacy policy and consent statement. I often see when working with customers directly that they have a policy for privacy policy for their students or alumni. They have a privacy policy for the population that they serve, but they don't necessarily have a privacy policy for their donor data collection management and use. This is something that during our your consent adoption, you should evaluate and make sure that you have something. And if you have something, is it published and made available to the public? The privacy policy is provided in the razors at NXT forms, in our email, the donor portal, and also on demand. It's via a a link, a URL. It's typically your website. I've provided some links to some of our Blackbaud clients who have some great donor data privacy policies. Take a look at them. Maybe they can be inspirations for your organization. The consent statement is also configured in the consent module for excuse Inc.. Connected feature. Aid, again, this is the statement provided on forms that the user saw when responding to their preferences. So they don't have to be long or arduous. It can just be something similar Impact, like Team us what communications you'd like to receive from us. You can change your mind at any time by calling or emailing. Here's a link to our privacy policy. It can just be a couple Center. Again, typically, we see this in the Raiser did NXT t forms is what we're talking about and why we'd need a consent statement. So, again, just providing some examples here for you if you don't really know where to get started. Use some inspirations from what other people are using out in the real world. Alright. So what's next? My last poll in closing poll, what would help you most adopt consent? So I provided all the steps on how to do it, gave you some recommendations and some examples. So last poll in that upper right corner tile, what would help you most to adopt consent? Training, configuration guidance, data assistance, or strategy consulting. Alright. We'll see what the the polls say. K. Alright. Training Information guidance. Great. Some folks are saying data cleanup assistance and strategy consulting. Yes. How do I just do approach the bigger picture of of our communication preferences? Great. Thank you guys so much for participating in my polls. It's always great to hear you all and your your insight and your feedback. Okay. This is really helpful, for us as well internally as we can make sure that we're providing these types of resources for you. So we do take this this feedback into consideration as we're building out more of our readiness resources and our help files and everything else that you can find Internet your for Raiser's Genex Team resource center and also the Blackbaud community. Great. So the the the winning here is configuration Guided. So that's exciting. So I'm gonna close the poll now and get back to my we have resources for you in all of those categories. So we have number of knowledge based articles and help file blog posts, which you will see one from me Inc. the Blackbaud community this week as a follow-up, best practice guides and configuration documentation. Our wonderful trainers at Blackbaud University have built a number of consent related trainings, and then we are here to help. So someone like me in my role, we have a slew of advisory plus consultants, razors, Net consultants, Manager services consultants that can help you actually get this going, not only at the strategy strategic level, but then applying it within your database. Because like you said earlier Inc. my my second poll, limited staff, limited time, limited resources. So I provided some links here for you. So a copy of this presentation is available in the docs tile. There's a tab in the tile on the right hand side next to q and a. You should see the second one in the list is the beyond solicit codes webinar. Feel free to click on that to download. That is a link to this presentation so you can get all of these these links. There is a brand Net, hot off the presses, consent management Learn that Grantmaking folks in the Blackbaud University team have built for for us. So if anything, I recommend you click on that link to that new e Learn, share it with others in your organization Net go a little further than what I did today, Learn more about how consent Management and solicit codes work together Aid then, have discussions internally about how you can apply it to your organization. There's Online, list item here that does not have a link, and that's because it's available in the docs tab. So I have kind of provided what I work with clients on to get started, which is a consent configuration workbook. It's not glamorous, guys. It's just an Excel spreadsheet. It's probably the simplest low, tech way to just getting the thoughts down on paper. So we start with the first column in there, which is let's document what are all our solicit codes, and the second column is definitions of those codes. Feel free to, again, access that in the docs tab, and let that be your guide to just get some things down on paper, so to speak. And you can, like I said, start with evaluating what you're currently using. So I hope that's helpful for you. I really appreciate you joining me today and thinking about how consent has a place at your organization. Insight. Net me see. Get to my last thank you Online, which has my email address. There you go. If anyone needs any Wealth, if you need access to that blog post or anything, feel free to reach out to me. I Campus you in the right direction. I always love hearing from customers and how we can help U. And, I hope that you have a great journey into the consent feature in the razors edge NXT. And remember, starting small is perfectly valid for your first step. Thank you all. K. So I think we have some time for some Tuition. I'm gonna be inviting my colleague, Card, on stage here. Hey, Kara. Hey, Krista. Hello. I've got some questions for you. Okay. What does what do our. audience. member common one yeah. Lots of questions. Thank you to everybody that submitted. One of the common ones that I've been seeing is how consent Internet, if at all, with Raiser Edge NXT email unsubscribes. Can you speak a little bit to that? Absolutely. Yeah. Currently, we don't have that, integrated within the email. As you know, it's still an an opt out or an overall unsubscribe, but we have definitely talked about it. I know, Karen, you and I even just Inc. all the upcoming product meetings that we were in every week with our fabulous product management team. This is a continuous discussion about how we can further integrate the consent into something as key as our email tool. So, just know we've talked about it. It's it's a common feature. We see the Guided Inc. ideas about that, and we are hoping to see some improvements in the future on that. Awesome. Thanks, Krista. Another one we've been seeing, how can we mass update or add consent to records? Great question. This is why we have to be a little careful. Currently, today, right now, with Impact still being in database view, we do have the ability to import consent, the channel category Response statement, etcetera. But we cannot Aid a global or mass in a global or mass way Edge consent. So that's why I always tell people, be careful before importing. Do some testing, before you just throw a slew of consent in there because you'll just wanna, be strategic about it in in a mass way. I'm sure Team import tools out there can probably help you do more, but that's where we're at right now within product. Thanks, Response. Right now, this is a specific example. I touched on it in one of your slides, and it might be helpful for some of our users to revisit it. So if right now I have a solicit Cover at my organization that are exclusion specific, do I need to change them to be inclusion and exclusion in order for consent to work for me? Not at all. You can set up a configuration to just utilize the exclude codes only. And so while we have four fields for how available for you in the configuration Net tell Raiser's Edge what to do when there is an opt in, both add a code or remove a code or codes, we also have just the opt out. So while my example of my screenshot showed all four fields and options or actions, being filled in, you really can just set up the configuration to say when they opt out, add the exclude Cover, Exclude solicit code to the records. Great. That's the stuff. Let's see. Another one we have here. Could you speak a little bit to, how using consent would work in tandem with the do not contact flags on a particular email or phone number? Yeah. That's a great question as well. It a little bit depends, which I I kinda hate when I get these types of Search, so I'm gonna ask for forgiveness first. It depends how your organization has defined or used those do not contact or do not, email for, yeah, the do not contact or inactive flags on the phone and email level. Right? So it Aid depends a little bit about the for on the org. I've had some organizations really revisit that because just maybe over the the history of staff and internal use and what tools what other tools they're U, they don't know anymore why they use that. And so they actually make a concerted effort to go out and communicate and ask for a refreshed communication preference from those donors and then remove the flag, when when a constituent days, you know, responded. Yeah. I I I would love to still hear from you via email, but I maybe they have specific preferences of yeah. Don't don't bombard my inbox with all the emails, but I'd love to hear this read your newsletter. So, again, I hate that answer, but it is it is part of the discussion, which is it's depends on how the org has used it. They another kind of point to the question is they don't talk to each other and that Raiser's edge isn't gonna go look and see that that specific email address is Marketing not content and add contact and add any consent related to that. So, that's where kind of figuring out how you wanna use either or both. And especially as we're seeing, like, currently days Insight now, the razors edge NXT email unsubscribe action Arts those emails do not contact. So I have some organizations that look at a query of those that data every week, and they look at the email history. And they actually proactively add consent based on what type of email they sent Aid, remove the do not contact flag because they really know that in their organization with their constituents, it's really more of a preference. Lots of exploration to do there for some of our organizations. Yeah. I think I've got two or three more questions. So, how would you recommend utilizing Center, and solicit codes in tandem when I'm creating a mailing or email list? So should I be querying for consent or solicit codes? Obviously, only solicit codes are in lists in NXT right now. For to a little bit of that best practice. sure. Yeah. Well, Inc. query, you can query on both consent or solicit codes. The best practice would still be to lean on Solutions codes because, again, consent triggers or manages manages those solicit codes for you. So solicit codes are what our list poolers, list gatherers, should use when when doing their work. Good question. Fabulous. What about, if you can speak at all to consent, integrating with Institute Connected? We got quite a few, comments about that one. Okay. I don't know all the ins and outs of how con the current Institute contact integration Network, So, forgive me on that. I highly recommend, obviously, looking at our help files for that type of Information, and care if if U know, feel free to answer. But I I believe that from what I last heard, it is not necessarily updating consent. Is that true from your knowledge? believe it does map to, consent, one second. but there Card some comments in the chat. We only can map certain, a Certified volume of channels. So I see. have, a help file, from Constant Contact with the integration information, that could definitely be shared after the webinar. And, CRM, so we can make sure that we add some of that info into your blog post follow-up. as Wealth. Some homework for me to find you the answer on Team. Thank you for that question. Stump the consultant. I great. Yeah. It's a great question. Oh, I did wanna address it since, quite a few. people asked. Another one I was asked was about, integration with Luminate online, which it also doesn't currently integrate. Center does not integrate to Raiser's Edge from Luminate Online. Something to definitely put in our idea For sure. bank. Chris, I have one more question for you then. Okay. Does consent integrate with the donor portal? Can we utilize that in donor portal at all? question. Today, right now, I actually in preparation for this webinar, reached out to our lovely product managers that are responsible for that area Aid the donor portal to ask. It's definitely, in on the wish list. They have said that they see the idea banks. They, love the the idea to leverage donor portal and make it even more valuable. But what we were able to share is that we have a number of customers that have actually because donor portal allows for API integrations, have actually set up their own workflow, for consent management or consent gathering within donor portal. And I actually shared let me pull the slide back up. I shared the link to the community post from our own Learn Hudson, about that, resource. Let me see if it's gonna work for me. Probably doesn't want to. Is it gonna share? Let's see here. Well, it's on slide 29 of my of my, there it is. Okay. Hopefully, you guys can see this. So on the bottom right hand corner of this slide is a link to the Blackbaud community post about donor portal Team Performance, adaptive card, and power automate Complete. So, our my one of our colleagues has actually provided this, here for you. So that is one way currently Team, a customer could add it to portal until we just get it in there natively. Super great resources. Thanks so much, Krista, for answering all of our big Solutions, and I believe any unanswered questions will be addressed in the blog post following the recording of. this call. I'll do my best to add everything I can in there, and we'll definitely speak more about the LO and the Center contact integrations. That was a great one to ask about, the the broader world out there with all of the suite of your technology. So thank you everyone again for attending. I hope that you, appreciated today's topic, and I appreciate your time in attending. And I hope U look out for more readiness web webinars as we continue marching to more features, functions, and use of our Search NXT system. Thanks. Oh, I'm supposed to give you a poll. Sorry. Hold on. There's a survey. Launch survey. I always forget the survey part. Sorry, friends. Here we go. I just launched the survey. I always forget the survey. Let me see if I can get that to launch. K. We'd love to hear your feedback. Sorry about this. My marketing friends are gonna be sad that I didn't launch the survey. Let's see. Is it lunch? Net sure if the server is launching. Alright. Stay tuned here for a survey, and, we'd love your feedback on that. Thank you so much.