Dive Deeper with Scoir : Don’t Leave Interest on the Table: Understanding and Converting Scoir Inquiries

Hi, everyone. Good morning, good afternoon. Thank you so much for joining us. My name is Sarah Brown, I'm the assistant Director of Strategic Partnerships here at Technolutions, and I'm super excited that you've chosen to join us for our dive deeper today with SCORE. I am joined by my friend and colleague, Ashley Murphy. I'll turn it over to her in just a minute, but I'll get us started and kick us off with a quick icebreaker. Let us know in the chat where you're logging in from. So let us know your institution or city and state and give us a heads up of what the weather looks like.

Where you are today in New Haven, it's beautiful and sunny. We're warming up and I am very grateful finally. So as you continue to do that, I'm going to move through a few housekeeping notes just to make sure you know what's going on today. So first and foremost, this webinar is going to be recorded. After the completion of this webinar, you'll be able to access the recording through your home slate. If you want to rewatch or if you want to share with a colleague, you can toggle on or off the closed captioning with that icon at the very top right that says.

And that closed captioning is going to appear in the chat box. If you find the chat box to be distracting, you're not alone. You can toggle it on or off with that little icon to the right that looks like some chat bubbles. And then all the way to the right, you'll see the icon that has four arrows pointing outward. And that is how you will full screen this image so that you can view us larger and read any of the text. If you're having trouble. Next one thing to note is that if you should experience any sort of audio.

During our segment today, just refresh your browser. That should take care of anything that you might be experiencing That isn't quite right. I will also share that Ashley is joined by a few colleagues in the chat, as I will also be in the chat. So if you have any questions, go ahead and pop them into the chat throughout the duration of our session and I'll make sure that Ashley gets them for a question and answer afterward. OK, I think that's it for me. I'll go ahead and turn it over to Ashley, and thank you so much for being here.

Great, thanks so much Sarah. Hi, I see so many familiar names in the chat and I'm really excited that you all are joining us today. Umm, I really appreciate that warm welcome. I'm excited to present. I know it is most likely a pretty busy time of year. I mean, it never really slows down in admissions, but this week in particular I know is one that is typically full of excitement, but also can be a pretty stressful time too.

Certainly admit some of the surrounding uncertainty that we're dealing with. You know, it makes me even more grateful that you are reserving this piece of your day to learn more about SCORE and score inquiries and that you're looking to really set yourselves up for an even stronger year ahead next cycle. As Sarah mentioned, my name is Ashley Murphy. I am a product manager at SCORE. I've been with SCORE for about two years.

And prior to my position here.

I was, I spent many years on your side of the desk in admissions. Umm, I've had responsibilities overseeing recruitment, umm, strategies, operations and related strategies. So, umm, I'm excited to hopefully be presenting some things that will help streamline your jobs, make your work easier, umm, give you some new ideas to attract some new intentional interest. Umm, and I've been working in slate for the past eight years.

And was really brought on board to score to ensure our integrations with Slate run smoothly and that those of you on the receiving end of our data.

Are well equipped to maximize it into your operations. So we have a couple of agenda items today and as Sarah mentioned, I do have my colleagues Brooke and Andrew with me. They're going to be helping out in the chat. Feel free to drop your questions for sure. We want to make sure we keep track of them throughout the session. They'll do their best to answer anything that they're able to and then certainly reserve some time for Q&A at the end to answer anything that would be app.

To hold off and wait until after I'm done presenting. But first, just to quickly go through the agenda, I'm going to take some time to unpack what it means, what we mean by a score stealth inquiry. You're probably all pretty familiar with the concept of a stealth applicant. You know your prospective students that you're not aware of until they submit their application. But this idea of a stealth inquiry might be new for you.

It very likely is, and it might even feel a bit like a contradiction. Like how can an inquiry be stealth?

But it is something new that Score has introduced due to the way that we allow colleges to import their lists of interested students from our site. But there are really valid reasons why we're handling our imports the way that we do, so we really want to take some time to break that down. Then I'll review some tips and best practices for managing the Stealth records in your instance of Slate.

I'll give an overview and some strategies.

For converting stealth inquiries with score outreach messaging. And finally, share some sample reports that could help you get started with evaluating score performance in Slate.

So to really look at and understand SCORE Stealth Inquiries, I'm going to break this piece into two parts. 1st, to really understand why SCORE is introducing the concept of a self inquiry, I think it's important to first understand.

A bit about SCORE, I promise we really, we did not introduce this self inquiry concept to make your lives more difficult or to create chaos or confusion with your data. There's real purpose to what we're doing and understanding more about the SCORE network will help us make better sense of that. And then after we take a look at SCORE, I'll breakdown what the stealth inquiry looks like in Slate.

So SCORE is many things. In a nutshell, we are an admissions network that brings all stakeholders to the same table. One of the most important aspects of SCORE is that we are a college and career readiness platform for high schools. We are also available for free to community based organizations and their advisors. So in turn we are then the college search in preparation solution for the students.

And the parents and guardians that these schools and Cbo's serve. And even if a student's school does not use score, the student, a student's parent or guardian can create an account and use score at no cost. So there's never a cost for a student or a parent to use score, regardless of whether or not the high school is a customer. And then we offer a number of solutions for colleges and universities to increase their presence on the.

Platform and to connect directly with the students, families, school counselors and CBO advisors who are using it. A little bit about who we reach. There are over 1,000,000 students and parents and nearly 10,000 school counselors on score that represents a bit more than 2200 high schools and that number is growing about 40% year over year. What we're showing here is a little bit of the.

Breakdown of high schools between public and private and where our schools land across the country. We've recently been focusing our some energies to better support public school districts. We have some of the largest school districts across the nation using Score and we recently announced a new partnership integration with Common App for the upcoming cycle. So we anticipate even further growth in high schools choosing Score for.

Counseling solution as integration with the Common App was one of the most requested features and it will allow students to sync their college lists between the Common App and score and will also help streamline some things with application document delivery.

So just kind of taking a quick peek into SCORE, it really is our aim to make the admissions process easier for students and more sustainable for colleges and universities. This is an example of a student's My Colleges view. So when they're logged into SCORE, this is the space with that they come to to build and organize their college lists. For the purposes of this session, just with the time that we have together today, I've skipped over.

The search and discovery pieces of SCORE, where students can look for colleges that match their interests and preferences, but once they've identified colleges of interest, they'll land those schools here to keep themselves organized. And it also keeps their school counselors informed if their school is a score school and they can sync with a parent and guardian account.

So parents can stay informed too.

And both parents and school counselors can make suggestions to students of colleges that might be of interest, and those colleges will land in that suggested column. It says 0 in the screenshot. But if a parent or school counselor makes a suggestion to a student, it lands there over in their suggested list. But basically, once a student moves your college to any of these swim lanes from the following column over to the right, so following and beyond.

That is when we consider that student to be an inquiry to your school. And I'm going to come back to this, but keep this in your frame of reference for when we talk a little bit later about targeting and converting students who are expressing interest in your college on score. I just wanted to show this here. So you have, if you're brand new to score, you have somewhat of something to to reference when you're thinking about how do students express interest? How do they build their list when?

Using our site, so much of what I've covered so far and taking a peek at Score might seem pretty straightforward in some cases. It's possibly somewhat standard with other platforms. So you might be thinking, where does this idea of a stealth inquiry come into play? Well, that's because of Core to Score's mission is to put the student first, and one of the ways we do that.

Is our promise to never share or sell their personally identifiable information or PII and really valuable? A really valuable outcome of that is the trust that students have in our site, the freedom that they feel to explore and search without the risk of being inundated by college marketing. We know, many of you probably know as well, the presence of stealth applicants.

Continues to be on the rise, and probably the biggest reason applicants remain stealth is because they don't want to be inundated with information.

But SCORE really is introducing reintroducing the option for students to more freely explore, mark their interests. And because of the size of our network, that's resulting in anywhere between 50 to 90% of our college partners SCORE inquiries being stealth.

So in other words, those are students who have expressed interest in the college on score, but are otherwise unknown to the college, umm, in their system in Slate. Umm, So they're not being sourced anywhere else. Umm and that number or that percentage increases significantly as we move down the lower class manures. I'm going to take a look at a sample report in a little bit that kind of digs into those stats a bit.

Umm, so that's a bit why self inquiries exist, and it's mostly due to our.

Commitment to not sharing PII and the number, the large number of stealth inquiries being because of the size of the network and the trust and freedom that students have and being able to explore in our our platform. But it certainly does introduce some unique elements in the way we're able to engage colleges and understanding their audience of interested students, particularly via data import into Slate. So for a long time we didn't share data because we didn't have.

Way to do it without compromising our mission. But we worked closely with technolutions and about a year and a half ago we introduced the score audience source format to better align with how you're receiving inquiry information from other third parties, but in a way that still protects the student. So technically how this all works is the records that are sent from score to slate include some hashed values. So I'm showing that in the.

Piece on the right first, last date of birth and 1st last e-mail come over in the import file in a hashed format so any end user can't decipher the information behind it, but the system is able to read the hashes to determine if there's a match to a record already in your system.

Slate is going to look for a match in this order, so first it's going to look for a match on score ID, then first last e-mail.

And then first last birth date. If a match is found, the record is imported and the score information is just appended to the existing record that's already in your system. If no match is found, then a new record is created and the name on all of those Stealth Inquiry records is going to come over as unknown, which is shown in this screenshot here.

You'll only know a little bit of information about these unknown records.

We provide you their high school, we provide you their graduation year, their score engagement stage. So whether they've set on score that they're following, applying or have applied. And then we add a score account device, which I'm showing here, to their profile, which is a way that we can help identify these records that serve several purposes.

Maybe if you end up messaging students, which I'll talk about in a little bit. It serves similar to an e-mail address for an e-mail message.

But it's also a way that we can query on these records and better manage them and understand them in the system using this score account device.

But those hashed values values, even though we cannot see them, they are stored behind the scenes and used for matching on any future import or form submission. And this is really important because the whole point of giving you your stealth inquiries is so you can work to convert them.

Umm, the presence of stealth inquiries is exciting because you're getting access to prospective students that you're not reaching anywhere else. But obviously we don't want a stealth inquiry to stay stealth forever. They'll need to raise their hand in your system at some point to continue moving through the funnel. And this is just a quick query you might use to spot check or do some reporting on stealth inquiries who have converted.

Very simply, if the record has an origin source.

Of score and is now a known record. Then it's converted from stealth to known. So obviously you may set up your origin sources a little differently. We do provide some pre built filters which I'm gonna go over in a little bit, but this would be on the right. Just an example of using an origin source to be able to get at the records that have a score origin source.

Umm.

Also important to note it is any future import or form submission that finds a match to hashed values will convert the record. It doesn't have to be associated with score. So once that record then converts, you'll retain the source of score. You'll also retain any messaging or interactions that you've noted on the timeline as well.

So some questions we get are just some trepidation or hesitation around having these unknown records in your instance of Slate.

When we first introduced these imports, that was definitely the biggest concern was this idea of unknown records being brand new and how do I manage them and messing with the data in my system. You know, just having something in there that you're really unfamiliar with can be nerve wracking in terms of making sure you're getting things right. So I just wanted to chat through some tips and best practices for managing self data.

In truth, I think it's really rather straightforward.

And I hope to put those concerns at ease so you can really see how much the benefit of working with these inquiries really outweighs any perceived risk to your database.

The first tip I say is when you import these records, import them as inquiries. So the import comes through the score, audience, source format and I really recommend adding a static mapping that imports these records as inquiries to the person status. These students have expressed interest in your college. They are not prospects like purchased names. They are high intent interested students who would be.

By other vendors as inquiries, new inquiries to your system, just in those cases there's identifying information. The only difference in our process is that we don't share their PII. Otherwise the act of expressing interest is the same as other sites. So those records really should be treated the same way you would treat interest from other platforms. Another tip going back to the idea of an origin source is to create an origin source for the score.

Audience source format. Many colleges I speak with are maybe new to origin sources, or if they have origin sources it can be easy to forget to add new ones when you add new entry points into your processes. So not to forget to add 1 for the score. Audience source format. This is just a quick screenshot of how you might set that up down there at the bottom.

Naturally, all stealth inquiries will have a score first.

Source. Their date of following you on score. You know, we send that record over to you and the next nightly import and it becomes the date of record creation in Slate. So naturally they'll have a score first. Source.

But for inquiries that come over once you turn on the integration and they match to a known record.

You will not until the integration starts to catch up with itself, you will not be able to.

Calculate score first source or the origin source for those records, even though it's actually quite likely that the inquiries that match to a known record in your system have actually expressed interest in you on score well before they raise their hands to you. In Slate, we have an insights report that we can share back with you that analyzes the data first. Follow against the date of record creation for inquiries that match to a known record.

And we can do that just to kind of supplement the process.

Until the integration catches up and Slate can be the system of record for that info down the line.

In our help doc we provide a suitcase ID and we'll make sure we send a link to that as well where you can import a score query library that includes a number of pre built filters and exports. That's just really helps make working with score inquiries more efficient. You don't have to start from scratch if you're really not sure how to get it understanding and identifying these records.

This this score query library will help you do that.

Umm, these filters will help you identify all the inquiries just kind of going down the line here, umm, all the inquiries who are still actively following you because, umm, sometimes students change their mind. So they may have expressed interest and then said they're no longer interested. We do send that information to you as well. Umm, and then some filters that focus on identifying inquiries that are self versus those that are known.

And I am going to show you some examples of how you might use these filters in your work.

But just know you don't have to build them from scratch. Import the query library via the suitcase ID we provide and you can go from there.

And for the most part, I want to say that stealth inquiries really shouldn't get in the way. But conversely to that thought, you you really want to include them in your reports and queries where you're looking to understand your volume of interest and how that interest converts. But sometimes it may be in more actionable queries, like if you have.

E-mail recipient lists or call lists. You might want to consider filtering them out because the only means you have to interact with a stealth inquiry is through score. So if you're building an e-mail, for example, you certainly can include your score stealth inquiries. You could definitely include your matched or your known inquiries because you have an e-mail address for those records, but you wouldn't have an e-mail address for a stealth inquiry.

So in those cases it might make sense to filter out your stealth inquiries from that recipient list. Here I'm just showing a super simple example of including the pre built filter, not score stealth inquiry. And then on the right I'm showing what's behind that filter, which is just a super easy way to exclude stealth inquiries where it would make sense.

And so one of the reasons we provide you with your stealth inquiries is so you are able to evaluate score as a source point or even just a touch point.

For your prospective students, similar to the way you would evaluate engagement with other third party platforms, but also recognizing the opportunity that these stealth inquiries hold, you may wish to put effort into engaging them and strengthening the conversion of stealth to known and moving them through the funnel. We certainly would encourage you to do that and you do have several options depending on whether you are already partnering with.

Umm, or you would be trying score out for the first time.

So going back to this slide, remember we talked about how this is where students are curating their college lists when they're actively engaging in their list building. Colleges are when they're the students are putting these students here in this list and they're starting to follow them. Colleges are acknowledging the students interests and presenting the students with content to pique their interest and keep their interest.

And one of the ways that colleges do that is through SCORE outreach messaging. This slide shows a peek into the students view of their inbox on SCORE. Colleges who participate in outreach messaging will send messages to students that the students receive right on the platform. So that's really something that's special about SCORE Outreach messaging. It is.

Outside of the noise and clutter of the students e-mail.

Inbox or their text messages.

And messages can be delivered upon an action, so for example when a student first follows or first indicates their plans to apply.

Or messages can be sent one sort of more one off targeted content if that makes more sense for the the type of message. But the important thing here is that I wanted to emphasize is that if you're not.

Participating in outreach messaging and students are expressing their interest and you on SCORE and the student is stealth, then they're not hearing anything from you. They'll see messages from other colleges in their inbox that they followed or that they've expressed interest in, but your chance to get in front of them and acknowledge their interest is missed. An outreach messaging does not require a contract with SCORE.

Score messages can also be built and sent.

Right from Slate UMM. So partner colleges who do contract with SCORE have the option to build and send messages either through SCORE or via Slate UMM. But colleges who aren't yet partnering with SCORE UMM can build and send messages through Slate to try things out. Umm to the students, the important thing is that their inbox experience looks the same. So regardless of how the message is built, whether it's done via SCORE.

Or done via Slate. It looks the same to the student, and the important thing is, is that they're hearing from you regardless of how you get that message off the ground.

So just taking a look about messaging stealth students on SCORE, I wanted to note that presently SCORE does not have an option to filter or segment on stealth inquiries when you're building a message on SCORE. But that doesn't mean you can't make it happen if you are a SCORE partner and you're building.

Your messaging on Score. You would just need to export a list of intended recipients from Slate and then paste the score IDs into score when you're building the message. So the screenshot on the left is an example query that would target stealth inquiries who are actively interested in you with a term of interest of Fall 2026, and then the screenshot on the right is showing where you would paste those IDs into Score when building a message.

To the self students and again those score specific filters are included in the score query library that we provide so you don't have to build them from scratch. Here I'm showing a similar approach. So this is sending a score message to stealth increase from Slate. Again using those pre built filters. Looking on the left you can narrow down your recipient list.

And then they export and that screenshot where it says person score recipient.

That is that score device account on the Stealth record profile that I showed when I looked, We looked at the screenshot of the unknown record and that's how we identify the student recipient for the message on Score. On the right, I'm showing the simple messaging editor in Slate that you're you're presented with when you select Score as the messaging method when you create a new message.

So if you're a score partner, it doesn't necessarily have to be a one or the other decision. There may be reasons why.

It makes better sense to send some messages through score versus Slate. Here I'm just highlighting some of the main differentiators in terms of cost. Messaging through score is included in your contract, whereas messaging through Slate uses Slate credits. There's a there is more advanced segmentation, which we'll take a look at next when you build and send a message through score and that includes messaging to parents, which is not available when building.

A message in slate to a stealth record and in slate your message will write to the records timeline and you do have the ability to create or to add to or adjust more robust drip campaigns which presently score does not support. So there could be different reasons and different use cases for where you decide to build your message.

I just wanted to take a look quickly at some of the more advanced segmentation options on score.

As I mentioned, you can target parents on score. We don't send parent information with your score audience import to Slate. So that's not a data that would be available to you, particularly for stealth.

And then on the right hand side of the screen, it's just a high level snapshot of some of the additional filters that are available to even further narrow down and target your messaging, which is pretty unique at a stealth inquiry level to have that type of.

Data available.

And in Slate, one way you might target, approach targeting yourself inquiries is to set up a drip campaign. So sometimes people have talked with me about setting the integration up and then not really knowing where to start. This is 1 idea that you could implement to help sort of low, low lift, set up a way to target and keep targeting your stealth inquiries.

Slate umm, so here I'm showing the creation on the left of a junior stealth population. Umm, so I've created the person population and then created this rule to put the appropriate records into that population. I'm calling it junior stealth. And then on the right, umm, I'm showing the campaign used to, to target that junior stealth population. So there's no mix of different messaging channels in this campaign.

SCORE messages because that's the only contact information you have for self inquiries, but it's timely to celebrate their interest in you. It personalizes the connection and it reaches them right in SCORE where they're already working to build their lists and make their plans.

You'll notice that this sample campaign is not really inundating the student with a ton of messages. Again, we really recommend usually sending no more than three messages per month.

Score messages are short. They're more like social media style and they are one way. So if you're not familiar with score messaging, it is one way. There's no inbox to monitor. Engagement comes with clear calls to action in each of the messages.

With both approaches, whether you wanted to build your messages on score or in Slate, another quick win recommendation is to focus on automated or triggered messaging.

Umm, so I'm showing score on the left and slate on the right. Umm on the left You can see triggered messages are set up in score by selecting an engagement stage, umm on the right. Similarly in slate umm, you could set up populations, uh, for each of the engagement stages. So what I'm showing here is umm, I created a population of umm, score following and I purposefully kept it broad. Umm, I didn't filter the population down.

To stealth following and known following.

My intention there would be to do the further filtering, the further targeting at the message level to keep the campaign opportunities a little more broad. But what this allows us to do is sort of mirror or match this triggered message that we can do in score as well. So by putting your, your score inquiries into the score following stage population if they're in that engagement stage.

And then creating a drip campaign that immediately sends them a message upon follow. That's something you can sort of set and forget. So anytime you get a new follow, they would fall into the campaign and get an automated message from you. In this example, I've separated it acknowledging that a new follow from a stealth inquiry would be brand new to us. So you may wish to have a special RFI form or a special call to action because you're not aware of those.

Students and you really want to convert them and get them to raise their hand versus a new follow from somebody who is already known to you. The new action or activity there is that the interest is they're they're active on score, but you're already aware of them. So you may want to position your message a little differently.

And then to just kind of wrap this session, this section, not the session, the section, we've talked about how a good chunk of a colleges inquiries on score can be stealth somewhere between like 50 and 90%.

Typically. But what's also worth noting, or maybe reemphasizing, is the power of outreach messaging.

We know that e-mail inboxes and text messages get cluttered and noisy. We talked about that. But because students actions and score are intentional, and because we strongly encourage colleges not to over message and score their score, inboxes tend to be less crowded and messages have a much stronger engagement than typical emails.

Or texting. Umm. So not only is it smart to ensure you're in the mix of messages a student is seeing when engaging with colleges on score, it's also a space where students are actually paying attention.

And so last, I wanted to talk about how you can report on score performance in Slate. Hopefully by following some of the recommendations that we've outlined earlier, you'll feel more informed and confident just in working with data.

You're probably very likely to already have some performance reports or funnel reports that you're using in your own instance, possibly to evaluate your spend with third party platforms or other budget decisions that you're making in your recruitment process. But I wanted to show example report that you might consider if you need a place to get started. So in my report.

I'm relying heavily on the use of.

Origin sources. So I talked about origin sources a couple of times in the session.

But you're simply setting that up based on the record having been created by the score audience source format. But we know it's not always the source that matters. Sometimes you just want to look at conversion or a funnel report just based on any touch point or the existence of the inquiry having come from a specific.

Platform, site or purchase that you've made or in this case maybe you you don't even have to have a spend to score to get your score inquiries imported and still evaluate their performance over the course of the funnel. So in that case, the second line where it says score inquiries, I'm just identifying those based on the existence of having been imported in the score audience source format. So the difference in origin.

Is that the record was created by an import from the score audience source format versus just looking at all score inquiries. They are included in a score audience source format, so a little bit more broadly.

I also show here a review at the bottom of stealth to known conversion. So interesting to have a better handle on looking at records with the score origin source who are no longer stealth and again just using.

Those pre built filters from the score query library to pull this together in a in a report format. You know, as I was preparing for this, I thought another interesting report to explore might be building off of that stealth to known conversion. What's the next point of entry? So when they become known, what is is there a specific form or action? What are the actions that the students are taking to raise their hand after they, you know, have entered your system as they'll visit the.

Is it a special form you've created that could also be worth looking into to further target your efforts around stealth conversion? But as we know, no two instances of Slate are built alike, so these are just some ideas to help you get started. We can certainly provide a suitcase ID to this report. They'll give you the framework to begin building a report in your own database.

I'd also be happy to connect to work together to incorporate score inquiries into reports.

Umm, that you have already built? Umm. And then just quickly, part of our integration includes the option to share data back with score and noting that nothing in that data share back reveals PII or any other otherwise sensitive information. It's really score ID, person ID, date of record creation and slate, and then an indicator as to whether or not the record is stealth in your system.

And this just allows score to return an insights report. This is a just a sample of an example report.

And really the interesting things here is the breakdown of stealth versus known, which you can report on your own, but also that further breakdown of first source for known students. So I touched upon earlier that.

The first source of known records isn't immediately available to you in Slate.

Because we're not sending you the date of first follow.

It's only going to capture new interest moving forward from the state that the integration is turned on. Otherwise you're getting acknowledgement of score interest, but the record is already in your system. But we could supplement that data with this report until the integration has had time to catch up. And also just worth noting, I mentioned it earlier, the presence of stealth inquiries the second, the bottom chunk there.

And the score first source, you can see how much more prevalent in this example those numbers become as you move through the lower class years. So again, lots of opportunities to reach high intent interested students you're otherwise unaware of and also, as you can see here, much earlier in the process.

And super quickly before we conclude, I felt I needed to just take a minute to give a super fast plug for a new solution we have coming in the works. We're calling it High School Explorer, and it's really a reimagined solution for colleges to be able to search and discover high schools that would fit into their recruitment strategies. It also aims to make the process of scheduling high school visits.

Less arduous and to open up new opportunities to reach students, their parents and guardians and school counselors around scheduled visits and beyond. So what I'm showing here is you can today log into score, head over to the high school Visits tab and click that purple try it out link and take it for a spin. You'll see we've got some updated filtering capabilities. So this is a peek into the new look.

A refreshed map.

And we're also working to really build out some much more robust data elements and that the filter panel on the left is going to expand with much more data opportunities to help you hone in and narrow down and finding high schools of geographic regions that would meet your strategic initiatives. And we also have plans to include an export feature.

For those who would prefer to work with the data right in Slate.

This is just an example of importing some high school level data, how you might see it on a record, how you might use Voyager to interact with it alongside your own data. And we will be introducing an early access program. So our goal is to really build this solution in partnership with you all using real time feedback and input. So head over to the Visits tab, take it for a spin. And there's an opportunity there to leave us feedback as well.

All right, that's my quick plug for High School Explorer. So that's all I have prepared for this session today. Umm, let's see if there were any questions in the chat that I can answer.

I think there were a few, but luckily I think your team handled most of them.

That's excellent.

Any other questions, please keep them coming in the chat.

Or if you don't have a question, share your biggest pain point when scheduling high school visits so we can be sure to address it in our RE envisioned high school Explorer. This is a good platform for that.

Lunch visits. I've heard that Lunch. I know I've lived that. The stinky cafeteria lunch visit.

So when do we think the high school Explorer data will be ready to share to slate? So our timeline for high School Explorer is to open an Open Access program or early access program, sorry in June, which would allow any interested participating college to have the ability to really work with the premium side of things. So we have a high school visits and score is one of our basic solutions meaning.

It's open at no cost to any college to come in. You score find high school schedule visits.

The early access program would be something that colleges could participate in, have access to much broader data, the export feature.

Premium functionalities with an increased opportunities for communication as well. And that would continue on for the course of this cycle, this academic year with the idea that it's a partnership where we're getting your feedback, we're incorporating your feedback and we're really building a robust solution.

To launch more broadly for the fall 2026. So the timeline that we're working from is to be able to open it up so folks who want to can use it and help build their scheduling and strategies in time for actually scheduling fall recruitment.

Awesome.

It sounds umm, my colleague Brooke mentioned that there was a question about umm, the self inquiries landing and consolidate records. So I wanted to touch upon that piece just a tad bit more. As designed, you should not receive a large volume of stealth inquiries in consolidate records. There have been a few colleges who have received some and consolidate record records.

And it's mostly been some technical.

Umm, things that we were able to work with them on to, uh, clean up and improve moving forward. So a couple examples of that, umm, the remap active status in the score audience source format needs to be active, as well as the overall status of the source format. Umm, and if you start importing the, the file without the remap active status on, then the score ID doesn't get mapped. And so you're bringing in stealth records.

And then when the remap active comes on, it catches up and it finds a match and so it lands and consolidate records. So as long as you have the remap active status on, we can avoid that issue. Another thing that can land records and consolidate records is if you have the default matching logic of first last date of birth turned off, that can result in more records landing and consolidate records. Otherwise it's typically a handful.

And it's timed around that initial import.

Of your first file, which is can be somewhere you know, between a couple 100 to several thousand interested records depending on your volume.

But after that, and that's typically because sometimes we have duplicates and they've stayed in the system until we've been able to clean them up. So it's usually, you know a handful at that point when they do land and consolidate records, which somebody noted it is going to be blank. So what we've mentioned to colleges and working with technolutions is if it lands in a bucket that's like first, last e-mail, whatever that bucket of consolidate records is that you're looking in.

To trust the data that Slate is saying is possibly a match, make your evaluation of the data that isn't unavailable to you, and then make your decision as to whether you want to merge or exclude them.

Stephanie asked if we need to contact to sign up if we use the non partner option. Umm, yes, I'll send a follow up just to make sure. Umm, that you, that there's the step by step, umm, and we can include our help doc. Actually, I could probably include that right now, which is a great way to get started.

But in the follow up, I will contact you. You are and you you have my contact information here. You are very welcome to contact me if you run into any snags. But the help doc should walk you step by step how to get started to set up the integration which is your first step of bringing in those inquiries and being able to work with them.

Any other questions?

OK.

If you haven't seen it yet, Ashley's contact information is uh on the screen now, so you can reach out to her directly if you have any questions. Just as a reminder, this session has been recorded. If you want to re watch anything or share it with a colleague to share some knowledge, you'll be able to access it within your home sleep portal. Umm, just give it a couple minutes to render and I'll get it in there for you. Otherwise, thank you so much for joining us today.

Feel free to follow up with any additional questions. And uh, I'd like to take a minute to also thank the Score team for being here and providing such a wealth of knowledge.

Thank you everyone.

Thank you.

Have a great day, goodbye.