Slate Spotlight : CampusESP Integration

Uh-huh. Good morning, good afternoon. Wherever you're tuning in from, thank you for joining us today. If you want to participate in a little icebreaker or one that's a little bit less corny than ones that you might be used to, go ahead and let us know where you're tuning in from in the chat. It could be city and state. It could be university or institution. Anything you want to share with us, let us know where you're tuning in from and I'm going to go ahead with.

Starting by introducing myself, my name is Sarah Brown. I am the Assistant Director of Strategic Partnerships here at Technolutions.

Home for me is New Haven, CT, and I'm super excited today to be joined by my friends and colleagues, Fernando and Brooke from Campus ESP and Robin from our very own Technologies team. And today we're going to be talking a little bit about the Campus ESP integration. All of your questions should be answered. If there's any questions that you have throughout our time together, please go ahead and put them in the chat. It will be monitored and we'll have some time for question and answer at the end.

And as a brief housekeeping note.

I want to mention a few things to keep in mind so for those of you who may be tuning into our share platform for the very first time, you'll see a number of different icons located at the top right hand side of your browser. The one that I think I want to point out first is all the way to the right. It's 4 arrows. That is how you would make this full screen for viewing it's definitely way bigger, so I recommend it if you have the real estate on your desktop. The next icon to the left is the little chat bubbles that will toggle the chat on or off if you find it to be distracting we.

I hope you don't. We hope you'll engage in our session today. Leave the chat box on and participate to the left of that chat box. The double CS will turn closed captioning on or off for you. If you have any issue with your audio at any time during our presentation and webinar today, go ahead and refresh the screen. That should take care of any echoing that you might hear or any latency for the audio. And finally, last but not least, this webinar will be recorded and made available to you at the completion of our session today.

So without further ado, I'm going to go ahead and turn it over to Robin. Thank you all for being here with us today. And again, don't be shy. Drop your questions in the chat.

Thank you. Sarah and I, I figure we might actually as a group introduce ourselves and I'll give you a little bit of the order of operations of our presentation today. So my name is Robin Lancaster. I'm a technical engineer at Technolutions. I work primarily on integrations, deliver, the deliver module and the other components of slate that are involved with connecting slate to other systems, which is why I'm here today. I'm joined by two of our colleagues from Campus ESP, who all asked to introduce themselves. They're going to talk a little bit about the Campus ESP platform.

After I give a brief overview of the slate side of the integration that we're here to discuss today. So I'm going to hand off to Fernando 1st and then to Brooke to introduce themselves.

It's nice to meet everybody. My name is Fran Aquaya. I work at campus, ESP as a senior IT implementation specialist. What that really means is I work with our customers to integrate with their CRM systems, SIS, SSO, e-commerce, et cetera. I was very lucky to have worked with Robin on our slate integration. It was a pleasure and I'll pass it over to Brooke. Very excited for today's talk.

Thanks, Fernando. Nice to meet everyone. My name is Brick Sternick. I'm our VP of Product and Product Marketing at Campus ESP, so my team handles all product enhancements and sharing product success stories and results. I've been at Campus ESP for nearly eight years and I'm happy to answer any questions about Campus ESP for those of you who may not be familiar.

To you, Robin.

Thank you very much, both of you and I will go ahead and take it away. And Brooke and Fernando, you're welcome to stay on or drop off video as you choose while we do this presentation. So I'm going to take about 5 minutes now to go over the.

Components of this integration from the slate side and the 1st place to start, as with every integration is with the knowledge based documentation. I've just put a link to that documentation in the chat. I'm gonna go ahead and share my screen.

Everyone let me know if you can see my screen now. So you should see the documentation from for the campus ESP integration. Fantastic. If not, just go ahead and shout in the chat or or go ahead and refresh the page. So this is the documentation for the integration. It will walk you through step by step how to add the components of this integration. And that's exactly what I'm going to do today is walk through the steps of this documentation and show you how you would add each.

Component of this integration. So step one is adding the service account. This is an SFTP integration which means that you have to have a service account. The service account is loaded with.

Pre agreed upon credentials. So you shouldn't need to make any adjustments to the authentication step. So we're going to go ahead and jump into a database to add that service account now. So as as the step one indicates, we're going to use the Slate template library in order to add this tool so.

The Slate Template Library allows you to add resources that have been designed by technolutions.

To integrate with our partners, the template library, although it says legacy in some places, is still a valuable tool for adding user accounts and a few other resources that are not yet presently accessible via Suitcase. So the Slate Template Library has a lot going on. And one thing that I'd like to remind you before we start here is that if you don't see an object you expect to appear in the Slate Template Library, make sure you hit this refresh button because often you'll go, Oh no, the account that I'm looking for is not there.

And what's actually happened is your local cache of what the template library contains is just not up to date and you need to refresh the library. So in this case, following our directions from the knowledge base article, we can search for campus ESP. We can click add. This will bring up the service account. We click add. Hey presto, we now have a working service account in our database.

Similarly, the next step is to import the data export query. This is the main, this is the meat of the integration campus, ESP as a platform you'll hear more about from Brooke and from Fernando later on. But its strength is communicating with users, parent users, relationship users. And so the main power of this integration is taking data which you already have in your Slate instance on your students and their parents and their relations whom you want to integrate into the Camp CSP platform. And you'll do that using a configurable.

Query. This configurable joins query is a template, so it contains the starting place.

For.

Whoops, yeah, that one. It contains the starting place for a this integration, but you can build on it and customize it. And that's something that broken and and Fernando will be able to speak to in more detail later. So I've navigated to the suitcase interface. This is a mechanism for bringing in, if you're not familiar, it's a mechanism for bringing in resources from other databases either designed by us at technologians or designed by other people in the community or by preferred partners.

So from the Knowledge Base article, we'll go ahead and copy the suitcase ID.

And now that we have the suitcase ID in our clipboard, we'll click import, we'll paste in the suitcase ID, we'll click import again. This will bring up the components of this integration. So in this case, the data export. If we're so inclined, we can rename the query or modify the query, but in this case, we just want to bring it in and it's complete format.

And as you can see, this already tells us we're missing some component that we need to to interact with. So this query brought into your database now reflects the outgoing fields that are required for this integration. But this is where it gets turned over to you. Your job will then be to adapt this query to your data structure as to how you are using the Slate and Campus ESP platforms, both of which are highly customizable and.

Whose strength relies on your process and so this query will pull data that standard in Slate.

That is standard in campus ESP, but also will require some configurations such as updating these stage and cohort values to match what should be appearing in your database, and these will reflect. There's documentation in the Knowledge base article. The data dictionary will help explain what each of these fields should represent so that you can work through this this process on your own. You can also add columns to this export as as suits your process.

Finally, there's an optional step which is adding the source format. The source format by default does not create new records.

So what you will do is navigate to 1/3 tool and if you're unfamiliar, this is the quick launch menu. So if you see me bringing up this menu to go find tools, this is you can access this with command K or control K depending on which platform you're on. That will bring up the quick launch menu and then I want to search for source format library.

And I want to find the campus ESP data import, click add, click add.

And now to a large extent, the integration is configured. I have all the pieces that I need. And then at this point, you will have to take the steps that you normally take with a source format to go in and map any incoming fields. There's no data in here right now, so we're not seeing any columns, but this would be where you would map to any custom fields, bring in any data that you'd like to update, such as the.

Model score from campus ESP that you can use to make decisions, take action in your slate environment. So these are the slate components. I'm going to leave the the link to that integration documentation in the chat, but at this point it's just slate. You are now working with tools that you're familiar with. You should now be be using your knowledge of queries, source formats and.

User accounts and the SFTP process to fine tune this integration to your own ends and to set it up so that it suits your process and so that you can drive the kinds of engagement that you're using these two platforms for. So with that, I'm going to turn it over to Brooke and Fernando to start talking about the campus ESP side of this integration.

Thanks, Robin. All right, let me get set up. Yeah, so in case anyone is not familiar with Campus ESP, I'm gonna just spend a few minutes talking about IO product and the practical applications of the Sleet suitcase integration and really how how this can benefit you all. So Campus ESP is your complete parent engagement strategy. It includes a parent communication platform.

That means a parent portal, emails, text messages, event management, system analytics, and so on. We also have a team of export, a team of experts here to help you. Our team actually does the whole implementation for you, so it really only takes three weeks of your time. You also get a dedicated account manager at campus ESP, which means you have unlimited customer support.

And then lastly you get access to the campus ESP content network.

Our team curates on average 90% of the content that goes into your parent portal. Part of that comes from scanning your website, part of that comes from content partners we have. And then we also have an AI content personalizer that helps you edit content, translate content, or really generate net new content. And I see Sue in the chat calling out her account manager at campus, CSP, Elizabeth Harris. I'll let Elizabeth know she got a shout out.

We work with over 450 colleges and universities.

Most of whom are also Slate users and have supported over 15,000,000 parent, parent and family users.

So where does Slate play into all of this?

You pull student data from Slate into campus, ESP in order to create tailored enrollment, not just for parents. And we like to say that we we nudge the nudgers, that's what we call it. So you'll see that as the student moves through the enrollment funnel, the parent will see you personalized content.

About how they can help their student progress and what the next steps are in the enrollment process and as they move from inquiry to applicant to admin and so on. The whole parent experience will be personalized to match the student experience.

We also released a new feature last year called the admissions dashboard. This also pulls student data out of Slate to create a parent focused checklist in campus ESP. So our partners are using this to create admitted student checklists, new student checklists to share scholarship data to, to share housing data. And really it's it's very flexible integration. So anything you have in Slate you can present to the parent and campus ESP.

And then anytime the data changes, we will alert the parent and campus ESP so they know when it may be time for them to step in, get involved and nudge their students.

Lastly, you can also pull parent data out of campus ESP and into Slate and use that to inform your enrollment strategy.

So having a bit of trouble getting the next slide to load, There we go. So at campus ESP, we have a feature called Parent Promoter Score. It really takes any action the parent can take in campus ESP and summarizes that into a score. So it's looking at whether the parents are opening emails, clicking on content, logging into the portal, and then they get a score based off their activity level.

So we also, once the parent promoter score exists, we summarize the parent promoter score into quartiles.

Which means that you can see that at, you know, each stage of the funnel who are your most engaged families and who are your least engaged families. You can see who your least engaged families of applicants are, who your most engaged families of admitted students are, and so on. And our research shows that if the family is in the top quartile of engagement, the student is three times more likely to enroll. And that generally there's a really strong correlation between.

Parent engagement and student interest levels. So many of our customers are pulling this parent promoter score data back into Slate and using it to generally inform their enrollment strategy. So one really common use case is that, you know you can give your admissions counselors a list of those families who are in the top four child engagement, especially families of admitted students who haven't deposited yet.

May 1st deadlines coming up.

You could give those counselors a list of families and just make that their their call list. And oftentimes we hear that these counselors are having really good conversations with these families and you know, the student just forgot about the deposit deadline and it wasn't on the family's radar. And once you know the school speaks with the family, it helps kind of push the student over the line. So to summarize, you can pull student data into campus, ESP use it to engage the family.

To nudge the nudger and then you can pull the parent data back into Slate to help inform you know your enrollment decisions.

That is the quick overview of some applications of this data. I did not want to spend too much time talking about campus CSP.

But from here on out, I think we're going to spend the rest of the time going into Q&A and answering any any questions you all may have.

All right.

So pulling up the questions, there are a couple of questions that were submitted. Robin, I can't hear you.

Great, great minds. This is what I get for for turning on my microphone all at once. I was just going to say, Brooke, we do have some pre submitted questions, but I just wanted to encourage folks that if you have a question about this integration or you have a broader question about parent data, this is a great forum to ask it. And feel free to throw your question in the chat. And we'll be happy to to take it on from a couple of different perspectives from the campus ESP perspective and from the slate side.

So let's go ahead and start with one of our pre submitted questions.

The the first question is is a bit of a statement, but let me let me formulate it first and then reformulate it into a into a question. So one of our pre submitted statements was any information on integrating parent data from Slate relationships widget will be informative. So let's reformulate that as.

How might you go about integrating parent data from the slate relationships data structure to campus ESP.

And I'll, I'll talk to the slight side of of that piece to start, and then Fernando and Brooke can weigh in on the other side. The relationships widget is designed to store data in at on the person record as relationships. And those relationships are exactly the base rows of this integration. If you look at the query that we looked at briefly during the integration component section, that query is on the relationships configurable joins base. And so any data that a student enters on an application with a relationship widget or any data that you bring.

From a third party that is mapped to the relationships table will be included in that query. And so the data that appear in the relationships structure will be sent as a matter of course to campus ESPN. Fernando can talk exactly about how that.

Is integrated into into the approach that Brooke was just discussing where, where what happens with relationship information when it lands on the campus ESP side is maybe the way to phrase that question.

I got this, Fernanda. Yeah, go ahead.

Yeah, yeah, I was just kind of like, OK, who's gonna go first? Umm, yeah. Once we get that relationship information within campus ESP, it's very easy for, umm, anybody who does have campus ESP already to go within their own system, search up that user and have that information available for them. And then additionally, and then this ties into the integration as well. Parents and families are able to.

Self select and like input different information that maybe wasn't part of this integration already.

And then as part of the integration, also included in the suitcase, we can optionally send that information back to Slate, which is a big tool that a lot of our other partners like to use because it's very nice to have that information, additional information that maybe families or students like hadn't put on that initial application. Then having those family members input that into campus, ESP sending it to Slade, is a huge benefit. So you can get that information into your Slate instance and learn a little bit more about those family members that maybe you didn't know previously.

Awesome. So I, I see we'll, we'll keep taking through the, the pre submitted questions too, But there's a question here from, from Zachary in the chat and Zachary asks, this is more about general data than integrations, which is one of my favorite topics. Love general data. We've recognized that parent browsing activity is reflected by ping on their students record in Slate. And that makes sense, right, Because the way that ping works is it.

Attaches to the record by IP address, so when a student opens an e-mail or takes some other identifying action, like filling out a form for Fernando and Brooklyn. You may or may not be familiar with Ping. It's our mechanism for attaching web activity to a person record.

So when someone visits a page or opens an e-mail, that sort of thing, it is stored in a structure in Slate called Ping. And the notion that it's connected to the parent record makes sense because if they're using the same computer or they're using, they've opened an e-mail that was sent to both the student and the parent, their IP address can be used as a matching criterion to to connect to the student and that web activity.

So the question is if Slate eventually assigns these sessions to that respective parent.

Would we be able to factor that into the ESP parent engagement score? I will say from the Slate side.

That if is quite an is quite a big one. Because remember, the only information we have about these web sessions is that they're associated with an IP address that we know belongs to this student or someone who opened an e-mail sent to this student, you know, identified by by this record. So sorting out what is parent activity and what is student activity is a little difficult.

But I think the the more general thrust of the question would be a really interesting one to put to Brooke and Fernando, which is how might you use data sent over from Slate to inform the parent engagement score that you were talking about? How, how do you use data and how do you think about advising partners who use Slate on the data they should send and how creative ways they might use those data to to get a more informed parent engagement score?

Uh, yeah. That's, that's a great question, Zachary. So the short answer is at the moment this is not possible. The parent promoter score comes from activity that happens within the campus ESP instance. But I don't know, Robin, maybe now that we're done with this integration, we can explore future integration opportunities together. Yeah, I think this is, I think this is an awesome idea and we can.

We can certainly consider looking into it.

Some, some of the schools we do work with though, you know, of course there, there are so many different systems used to get at student likelihood to enroll and understand like student signals and student intent. So in the meantime, you know, I'm sure in addition to parent promoter score, you have some kind of student probability score, you have ping data. I would kind of just look at all of these different signals in conjunction together, but.

I think this is a great idea worth exploring more between campus ESPN slate.

Awesome. Zachary, feel free to to weigh in in the chat too if we missed some component of your question. But I I agree with Brooke, that's a that is really interesting thought experiment.

I'm back on here to pose one of the questions that we got in the 1st place and it's I. I came back selfishly because it's one of my favorite topics to talk about in sleep because so many people are doing it in so many different ways. And as a practitioner, as an implementer of Slate, I feel like I duped it out with this topic enough climes that I want to have the conversation. I'll ask Robin to answer it because again, selfishly, I haven't heard his take on it. But how do parents relate to students as people in sleep? Is it easy to relate to parent slash guardian?

And councillor to a single student contact using slate and can we relate one parent to multiple protective students any of those and any talk about the relationship table and or custom fields that are holding parent data. Robin, if you wouldn't mind touching on some of your opinions on thoughts ways people that ways that clients or schools are currently collecting this information how they're currently using them and pros and cons.

Opinion, because of course you can do any of these.

Yeah, I mean, this is this is one of the delights and one of the challenges of talking about slate is that slate is designed, you know, as the name says, to be a blank slate to a greater or lesser extent. It is accessible to you and your process to to make whatever changes to the data structure, to the way that your fields are organized into what information you collect. You know, within within reason, there are some things which are are fundamental to the way that slate thinks about the relationships between person records and what we call relations.

So let's start at that fundamental level.

Each relation belongs to a person. Person records are the fundamental record in Slate. They represent what they say. They represent persons. Whether those persons become applicants, whether they become donors, regardless of their mode of engagement or what constituency they belong to at your institution, they are represented by person records. Each person has the ability to have a connection to theoretically infinite number of relation records. I hope to have that many friends and family members in my life.

That my relation record could really reach start pushing the limits of slate in storing all my relationships. But I'm I'm a little antisocial, so I may not get that far. I probably have to have 10 or 12 people that would appear on my person record. But you can think of relations that way. They are the direct one hop people who are connected to a Slate person record, whether by parental relationships, so the default types of relationships that slate supports.

The box are parental, grand, parental, and sibling relationships. So you'll see that the relationship types include prompts for things like father, mother, legal, guardian, grandparent, brother, or sister. But you also have the ability to customize what those those relationship types are and add prompts to that list. So you might theoretically be able to store any number of potential relationships.

It just the, the fundamental idea of that data structure is these are the people who are related to this person record in one way or another, have some relationship to them with whom we might want to communicate. In almost every case, and in the integration we're talking about here, the most important relationships are going to be familial and immediate family, parents, grandparents, and.

The siblings of of a of an applicant or another constituent who you're working with, those data are connected in a many to one relationship, which we talk about a lot when we talk about configurable joins. There can be many records per one person record and.

The what information you have about your relations depends very much on your process. So as with everything in sleep, you can build almost everything in sleep. You can build custom fields which store your own data in your own format that describe information about a person record. You might, for example, want to have a field on the relation record that indicates whether that person is an alumnus or not.

Or whether that person is a donor. Those are the kinds of things that you can customize the relationship record to to track. Similarly, you could add a relationship scoped custom field to store.

The kind of parent engagement score that Brooke just talked about this powerful tool for figuring out how engaged this, this particular parent is in their students application process. So I, I, I know I'm covering a lot of of broad thoughts here. That is my, my tendency. So I'll say Sarah just posted the documentation in the chat. But the most important thing to know about relationship records is the use cases are nearly infinite, but the most powerful thing you can do is capture.

Diagram the relationships that affect a student's decision making process when they think about where they're going to go, where they're going to deposit and what they're going to do with the rest of their lives. And so this this data structure allows you to capture that in all its complexity as well. As I'll say the last thought is you have the ability to assign relationship records to existing person records in Slate, which is most often used in the case of siblings. If you have a sibling who's applied to the college, you know.

University before you can assign that relationship record to a person record, which allows you to then see all the information about these connected records through their sibling relationship.

Thank you Sarah for posting that article there.

Cool. I'm going to address the last question that we got beforehand and then if you have any, you being the folks in the chat and in the attendance, please feel free to let them continue to flow. But I will post one both and perhaps this is either for Fernando or Robin. How customizable is the integration? Can we tailor it to fit our institutions, institution specific needs? How often is the integration updated and will new features or improvements be rolled out over time?

Yeah. We'll see if I'm not seeing Fernando here. So let me take the the the first half of that question and then Fernando can sort of weigh in. So the integration is highly customizable. Both Slate and campus ESP are extremely flexible platforms. They're designed to to fit your process. And so the integration on the Slate side is essentially a configurable joins query. So the the integration is roughly as customizable as a configuration configurable joins query is.

Anything you can dream. Any subqueries you can build can be sent to campus ESP. Obviously, the data have to have some purpose on the other side, right? Like you can craft anything you want, send anything you want, but you have to work with your campus ESP Rep to make sure that those data are actionable. But practically speaking, yes, it's highly cut. It will always be customizable. It will always be able to mold itself to your process within the limits of what the two platforms can do, and it's continuing to evolve.

Overtime, Fernando and I have talked about several, several things that that he's thinking about adding or improving campus, ESP as a preferred partner.

Has been developing resources for slate and and can share and I don't want to take the Thunder if Brooker or Fernando wants to talk about some of the resources that they're working on in their in their slate environment to share, but improvements are are consistently under development.

And perhaps, oh, go ahead, I'm sorry.

Yeah, these mud, Robin. No, no worries, Sarah. Yeah, thank you so much, Robin, for starting us off. Yeah, just like you said earlier, like once that configurable join has been customized or, umm, configured just a little bit, umm, in your Slate instance, you're in Slate. So you're able to, you're free to do whatever you would like with that query. As you mentioned, any subqueries you would like to add? And then just for specifics within campus, ESP within campus ESP, we support up to 30 custom fields. So there's a lot of different data that you're thinking about that you would like to send.

Make available within campus ESP. You're happy to create that info umm, for for us to umm, process into our system and umm, yeah, those 30 custom fields really, umm, up to you, but you would like to do with them and we're happy to talk with you umm, about them. And we work with a lot of different customers who, umm, use them for a lot of different use cases. So we're happy to discuss that with you and make sure it fits your institutional needs.

And in terms of integration updates, we work together with our partners to make sure that all of these updates are are accurate and ready for you to use. So we will continue to work in close contact to make sure that you're getting the best integration as possible. I'll go ahead and read the other question and perhaps, Brooke, you might take this. What types of student data from Slate are most useful for engaging parents and how can we present that information effectively? What are some best practices for using this integration to increase parent participation in school events or meetings and how?

Measure the success of the integration in terms of both data accuracy and improved parent and gay plan.

With a few questions.

OK, a few questions. I'll, I'll address them one at a time. So first, what types of data, what types of student data from Slate are most useful for engaging parents? At the very least, a very bare minimum, we need student ID to be able to effectively link the parent and student records. We highly, highly recommend including the student funnel stage, whether they're an inquiry, an applicant and so on, so that the messages are really tailored to the exact stage they're in the funnel right now.

And what the next steps are and the ways parents can support them.

Same with entry term, of course. So we know you know which cohort we're talking about. So those those are the bare minimums where you could get really, really personalized in your content and parents can support even more or some extra indicators like whether or not the students submitted the FAFSA yet. And you could do highly tailored parent messaging about FAFSA completion counselor, you can include who the counselor is with the student and we see schools present to the student.

I'm sorry to the parrot. Like here's the student's counselor, here's who you can contact if you need anything and have increased counselor interactions that way.

Course of study is really interesting. You could share information related to specific colleges. I mean, you could really from there get as tailored as you'd like, but at the very least you know, student ID, student funnel stage, you know, application type, whether they're first year or transfers where the bare minimum of what you'd like to do. What are some best practices for using this integration to increase parent participation in school events or meetings?

It's interesting you mentioned events and meetings. I mean, just as a starting point, communicating with parents will increase student participation. We just hear this anecdotally all the time that you increase attendance at admitted student events, you increase attendance.

Even for enrolled students, like when you tell a parent there's a career fair, like suddenly students are going to the career fair because their parents nudging them to do that. So just communicating with parents in the beginning, you should see an increase in attendance.

But getting a bit more specific, you know, this is where parent promoter score can really come in. We have seen colleges just go like all in on the communication to parents that have a high promoter score. So say there's an admitted student day, you might want to send like one or two messages to all parents, but not overly overly address them with a ton of information. So maybe one or two to all parents, but then you could take the parents with a high parent promoter.

You can send them 4 notches, 5 nudges. They're opening all the stuff you're sending them, so you're not going to bother those folks.

And then the last thing I'll say about best practices, it's really like as with students and all audiences, you, you want to go multi channel. I mean campus, ESPN, Slate, both offer multi channels. You have emails, you have portals, you have text messages, different families, different students have different preferences. So you'd want to hit them with reminders across all those channels.

The last question, hopefully I'm touching on all of this is really how, how can you measure, how can we measure success of the integration in terms of both data accuracy and improved parent engagement? I mean, this is, I love this question. How do you, you know, how do you measure the success and make sure your efforts are working? I mean, really I would say you should see, you should see impact on your enrollment and we put out a case study every year. I could, I could drop a link in the chat.

In our case study this year from a handful of schools using campus ESP to engage, parents say that if the student has a parent using campus ESP or if the student just has a parent who's getting a lot of engagement, that yield rate for that student is 7% higher than average. And that's an average. So some schools see higher yield gain, some schools see lower yield gains. But I would say generally the way that that we measure success of parent engagement is that you should see.

You should see enrollment outcomes really across the funnel. That's why that's the reason you do this.

So hopefully that answered everything. That was a big question. Thank you.

Thank you. No, thank you. Uh, thank you all for your insight. I'll, I'll leave the door open for maybe one more full minute for any questions that might come in. Thank you all for joining us. Thank you for the participation in the chat. It sounds like we have some folks that are excited about this integration, excited about using the products, excited about seeing the results from engaging parents in this process. We know that they're involved and leveraging that involvement I think is key to a lot of processes.

So.

If you'd like to reach out and and have any sort of contact with us at all, I'll allow the team here to enter their contact information in the chat. If you'd like broker Fernando any other questions, you can always reach out to me again. This this webinar will be recorded and sent out to you after if you'd like to re watch or revisit or share with someone else. Otherwise, thank you all so much for being here today.

We've really enjoyed presenting to you and engaging with you.

And we hope to see you again soon. Thank you very much to Brooke and Fernando for being here as our guests to present this integration to.

Thank you all.

Thanks for having us, Sarah and Robin, and thanks for joining everyone.

Thanks everybody.

Of course. All right, everyone, have a great day.

Bye bye.

I wonder what's going on?