Slate Spotlight: Student Success

Dancing.

Tell.

Inside

Drama.

It's mine.

Winters.

Home.

Insecure.

Juju.

Aldi's

there isn't enough.

Gold

Good afternoon, good morning or good evening everybody. How's everybody doing? Welcome to everybody. Hope you're doing fine on this. Fine Tuesday in spring. Hopefully spring has found its way to you wherever you are. Thanks for all the.

Hellos and shout outs in the. In the chat there my name is Ken Higgins and I am the general manager of Student success here. As technicians slate happy to have you all. Thanks so much. Hopefully you enjoy those wonderful soothing sounds to start us off from. Yeah mid 80s. New wave Scottish band. Simple minds.

That played at the beginning. There is a musical portion of it that played at the beginning and then ended the wonderful, most wonderful movie by John Hughes. The Breakfast Club.

So yeah, that song is actually. It was written by the music producers that were on the film that were employed for the film. They wrote that they scored the music and then they tried to find a band to pick it up and actually perform it for them. Other bands that were in the running were Billy Idol and a couple other schools to a couple of schools, couple of bins too. So anyway and yeah, so breakfast club. Great movie. That song always makes me think of there's an image that's imprinted in my brain every single time I hear that song. It's John vendor.

Or Judd Nelson's character John Bender at the end of the movie, walking across the football field, raising his fist up into the Sky and it freeze frames there and the movie plays out.

Solid movie So anyway, actually you know what about the movie and there were there were two alternative titles to The Breakfast Club. In fact, one of them was going. It was going to be called either the lunch bunch or the library revolution.

So I'm happy that they picked The Breakfast Club. But I digress. You know, with those random trivia facts about about The Breakfast Club impress your friends at your next dinner party with those useless facts. Yeah, I'm tuning into you all from a sunny downtown, New Haven. It's it's mid 60s and like I said Hope Spring has arrived wherever you all are. We have an awful lot to cover today.

So I'm just going to dive right into it actually, and thanks so much for being here. So a couple of housekeeping items. This weapon is being recorded and will be made available for later viewing. It will be recorded and available on our website and we will follow up with all the attendees via link in an email. Closed captioning can be enabled by clicking the CC button at the top right corner of the share window.

And full screen viewing can be enabled by clicking the expand button at the top of the right corner in the share window. If you need to re sync audio and or video, just please refresh your share window. It should get you where you need to be and then any questions that you have throughout the chat. Excuse me throughout the web and R just post in the chat. I have the most wonderful Erin Gore colleague of mine who is the general manager of slate.org. In the chat. She's going to be keeping an eye on questions.

In comments that come up, I will do my best to save some time at the tail end of this so we can answer and address some of the questions that have come in. And well, I'm going to do my best to dedicate some time at the tail end for that. But if there's a question that's appropriate, and if I have an opportunity to answer it right then and there, we will go ahead and answer it. So post your post your questions there in the chat.

Right, so today's agenda. What are we going to talk about today? We are obviously going to be talking about student success. And what does that mean, right? We're going to define it. We're going to talk a little bit about kind of all the things that may be categorized under the student success umbrella. This kind of broad stroke of a paintbrush that is defined as student success. We're going to take a look back. I want to kind of kind of look backwards and see how student success is. Become a thing, an area of focus in higher education.

And then, particularly as it relates to technicians.

We're going to ask the question can slate question mark in Slate? Do this? Can Slate handle this? Can we do this inside of Slate? We're going to answer that or try to answer that. And then we're going to dive in and have a little bit of fun and see some stuff. I'm going to provide a little showcase of in inside of a showcase environment and see what some options are, what some of the capabilities are, what processes can exist inside of inside of slate as it relates to student success?

So let's talk a little bit about the life cycle, right this the student life cycle. That may, at this point exist inside of slate, right about a month ago. You all heard maybe a lot of you tuned in for with Erin Gore for Web and R in Slate spotlightaboutslate.org where high school students can engage. Obviously with admissions offices and their counselors can interact and engage with the admissions offices on campus and across through slate.org.

You have the admissions. Obviously the enrollment funnel their students are passed through the enrollment funnel V. Admitted via admissions. We're going to continue that thread today with student success. So how are you currently manage in your current students right? And how can slate help with those efforts? And then you've got the advancement piece after they've gone through the admissions to the enrollment funnel. After they've enrolled, they are graduated, they've become successful. They now become proud alumni and prospective donors. They're giving back.

And then we can obviously complete the full lifecycle. Here it starts all over with those alumni, children that then could become legacies and start the process all over. So really, what we're talking about is 1 section of this kind of student life cycle as it relates to slate, right? We're going to focus on student success to that.

Some of you guys have been using a lot of you have been using slate for your student success purposes for awhile now. This isn't brand new functionality or there isn't a brand new module that needs to be turned on or anything like that. It is a lot of the already existing slate functionality and capabilities that exist. You just need to take advantage of them. And some are just starting to maybe explore some. You might be here kind of listening in 'cause it's OK. Student success. I want to hear a little bit more about it.

And some of these words and terms and kind of phrases within the student success lexecon maybe new right? They may be older, they may be, you know what they are. But you say, well, how can we? How can we kind of adopted these efforts or these areas and processes inside of slate, right? So this concept of retention and advising and counseling right student persistence tutoring these early alerts? I kind of in the definition of student success. This big kind of umbrella.

Definition of student success. This is kind of what I'm talking better. At least these areas. Some of these may require, or you may may not be focusing on some of these areas at your institution, maybe focusing on all of them. Or you may be interested in focusing on all of them. But if we're talking about kind of expanding the lexecon here and getting familiar with some of those terms, this is kind of what the the details that we're talking about, right?

So let's take a look back, right? So a while back or I shouldn't say awhile back. At this point. 1015 years ago. At this point, we if we all remember there was a lot of big reporting that came out. There was a lot of literature. Be a look at big data that kind of looked out right? It looked out at some demographics to kind of get paint a picture of the next 15 or 20 years of high school graduation rate, which kind of then alluded to what?

College enrollment statistics may look like or at least freshman incoming right. So for the enrollment file, there was a lot of focus on how demographic shifts and demographic shifts were happening and how student needs were evolving, not only from the enrollment funnel, but also once they got to the institution. And a lot of focus started to come. And I would say this is hot. I mean, this has been amplified by orders of magnitude over the last year just because of the situation that the country's been in.

With the pandemic and schools really really trying to adjust that that they need this kind of focus or this refocus on retention and success efforts, right? It's not to take attention away from, let's say enrollment or advancement or or whatever. It is right? But there's this shift to kind of a high focus on retention and student success efforts.

The obvious this obviously you know if you're crunching big data, you can then use that data to make data informed decisions to assist with with retention efforts and persistence, and where human resources are going to ultimately kind of contribute to the success of a student, I'm going to say success over and over again, right? But it leads to where it can lead to these kind of enhanced support services to really assist the student throughout their their kind of journey.

And make sure that they have what they need, right?

So ultimately, you say OK.

Define cool. That sounds great, right? OK, so retention and all of this information. We it needs focus, but can slate right? The question is what can slate do? Can it be a data repository for all of our currently enrolled students can act as a communication tool. Can we use deliver for students? Can we manage our events inside of Slate? Can we you know process and manage and keep all of our forms inside of sleep? Can we kind of take this case management approach and move it into slacum? Can Slate help us review?

Cases that have that have kind of like a start and finish beginning Internet. Can we track engagement of currently enrolled students can require in report data? Can we calculate scoring? Can we manage alerts or early actions? Can we capture notes or user interactions and can we manage all of our users in Slate? Ultimately the answer is yes, obviously you know spoiled art. Yes you can. And this actually comes at no extra charge. The encouragement from my end is really to start exploring this. We're going to dive into it once we.

Once we get into Slate and I show you around a little bit but there is no extra cost that comes by expanding your user network. There's no per user cost. You don't pay an additional fee or cost to expand your efforts inside of slate for your currently enrolled students. If you have if your institution has 1000 enrolled students, or if it has 30,000 enrolled students, we encourage that you're using the tools.

That you're expanding your user network and that you're collaborating with other offices. Slate can enveloped these other offices across campus that can feed to that kind of cross departmental collaboration an effort and and really, really kind of ultimately end up really assisting in your in your success efforts. So I encourage you after and during this if you see you know stuff that you're interested in. I know that the attendees here it's mixed. I know a lot of you are in the admissions office, right? So your current users of Slate.

There are some that are at schools where the admissions office you sleep, but you might be here from another office. You might be coming. You know you're not a regular user of Slate or you're attending from another office and or you might not be using slate at all. So as I go through things just, you know, some of the things might be a little bit nuanced. Some of the examples you might say this makes a lot of sense to me, so just just bear with me, but we strongly encourage this is, you know, this is not something that were encouraging that you have.

To pay extra for, we want you to dive in and explore this and start expanding your user network.

A couple of things are going to be kind of running throughout, and I'm going to talk about these right when we get started in. In diving in, we're going to talk about record segmentation if we're operating in same slate database, how do we keep these records apart? Some of the admissions folks might say, you know, gosh, I've got my prospects and increase naps, but how are we keeping these these enrolled students kind of separated and segmented away from all the other records, right? We're going to talk about data integration. Kind of one of the fundamental strategic conversations that you have to have for slate.

However, you're using it, if you're using it for admissions or advancement, or student success, or all three, and then user management, sharing database and kind of using efforts within the same database but across Department store across offices or across a user network.

Is really going to require a close look at how you're managing your users and what the user experience by Department or by role or by permission. What that's going to look like and what what experience you want those those various users to have. So will be calling on these kind of recurring themes as we as we navigate throughout Alright cool. So let's have some fun. Let's dive in. We're going to dive into Slate again. Questions in the.

In the chat and Erinle will keep an eye on him, and if we have time at the end, we'll dive into them. So let's have a little bit of fun.

Alright, So what we're looking at here is a slate database. OK, this is the success showcase.technologies.net database. This is one of those environments where we want to kind of have one of everything kind of model for for student success specifically, and this is going to be. This is going to be available to you guys in short order for you to provision through your clean slate environment.

Alright, and just one quick call out. I'm sorry I got an eye on the I gotta chat Tasha Hendrickson from Baylor. Congrats to the Baylor Baylor's on the national championship that was unbelievable completely dominating performance last night. Anybody stayed up to watch? It was an amazing game anyway, so let's talk. 1st About records inside of slate, right? So one of the things that Slate is awfully good at. I'm I'm biased, a little bit 'cause it work here, but I used to be.

It's like user as well, is really, really good at kind of record management and we're going to look at first record here. We're going to look at late 10 Higgins. This is my daughter. She's not 20 years old. She's three years old but late and as a student record here in this slate database. And she looks pretty familiar to probably the structure in it's kind of setup of this record probably looks pretty familiar to a lot of the folks from the admissions office is on the in the web, and are so pretty straightforward. Pretty standard. You've got the profile tab. You've got her information here.

She actually applied. She is. We got really no information on late and she is kind of like a stealth app. Looks like she just started the undergrad app. We don't have much about her's off at all and and some of you in the admissions office is. You may have more custom tabs built out here, like details on and so forth, but Layton is stealth, the stealthiest of stealth apps. We don't really have any information on her, but I wanted to show her as an example because this is a really basic record, right? And she falls into the applicant.

A person status because she has applied, but we don't really know much else about this. This record is going to grow and become more rich with data as she continues her application as she starts engaging with emails that you send. So on and so forth, right? But basically is it. This is just to say, alright, we have a student in this database that exists as an applicant. OK, the real magic comes when we juxtapose this latent Higgins against Kendrick. Kendrick is the other record that we're going to be paying attention to today.

And Kendrick, as he compares to latent Kendrick, is an example of a currently enrolled student here.

So by way of some customization, some rules, some automation, some permissioning student records inside of Slate have a pen, have a wildly different look and feel and vibe and structure, kind of data structure as it relates to kind of where they are in time at the University, whether they are, you know, going through the admission process, OK, pretty basic, and I'm not saying that's that's a bad thing to be basic, right? But you know.

We don't have much information about Leighton, but for Kendrick he's been here for awhile. He already went through the admission process he enrolled, so we have a lot of information on Kendrick, and as we can see here, it's kind of loaded up one of the first things I want to call attention to is the concept of these custom dashboard queries and custom dashboard queries are really pulling and kind of front facing information right in front of the user to ensure that they get these various data points right when they log onto a student record. So if I have access to search Kendrick.

And I'm like he might be an advisor of mine or something like that. There needs to be. Maybe there's 10 or whatever five things that I need to know, right? Exactly when I get onto the student record, right when he's walking into the door for that advising appointment, or when he calls on the phone. OK, we're going to move from left to right here across his tab structure. We're going to bounce. We're going to skip over these for a second. Will come back there though. But let's take a look at his profile. Just like slate, you know. Again, there's nothing new here. There's nothing turned on. We've got his basic profile sub tabs. We've got his contact information. We've got his.

Our man is mailing address in permanent address. We might start adopting the.edu the institutional email address. Once they become an enrolled student right, we can start categorizing things like courses. Some folks in need throughout the admissions process will categorise an capture courses on the courses table on the standard standard course structure too.

Uh, what they took in high school? Or maybe like if they had a dual enrollment course or for transferring credit in which you might also say no. Actually we want to start categorizing the courses that they are currently taking at fill in the blank slate University because we want that to be a part of this person record. We want to see this. We want our advisors to be able to see this and access it and take a look at oh, I don't know. You know some of these various data points, right? The materials tab so think of materials as OK if.

If this were a an admission student, somebody going through the enrollment funnel an applicant, we'd see things like their transcript and their letters of recommendation and the resume, so on and so forth, right? Everything? That's kind of associated with their application. But this thing can take kind of a different spin where you say no, we're no longer really interested in collecting that type of information, but we really do have other examples of materials that we're going to need to collect for the currently enrolled student, and we might need to take that. We might need to.

Select that year after year right? We might need to take it freshman and sophomore and junior every semester that they return something like that. You may while I just showed on the profile tab, I can show it a little bit differently by way of using custom tabs and entities. You can display course data that the student might be might be taking via this entity structure right where you're pulling in information about the student, maybe from another system.

This this information doesn't necessarily have to live in slate as kind of the system of conception or the system of record. This could be pulled in from your SAS or from the LMS to be displayed here at a frequency that fits your needs for for, for your institution. And this is all everything that I'm showing you today is is kind of entirely customized and and configured to your your scope in your process, right?

One thing before I start, before I continue down these tabs here you can see the one of the.

One of the kind of fundamental differences here, or the way that we're segmenting these records, at least in this use case, is I've added an additional person status. Slate comes standard with prospect inquiry. An applicant I've actually added an enrolled person status and a lot of what we're seeing here is a controlled or kind of displayed the either by this person status or I've got some some information displaying via population right one of the things that these persons status sees statuses are tide 2.

Is via a rule, and if you guys remember back from early days of your setup, right? We're talking person status rules here. Not gonna spend too much time in the weeds here, but note that you know the enrolled status right? This enrolled status? I actually don't have a set enrolled status. I just have to keep enrolled status rule. The concept here is that I don't. I actually don't want a piece of automation. I don't want to rule. Setting the enrolled steps. I actually want to do that kind of in batch in bulk.

And that the reason being, I want to make sure that everybody I have a known quantity. It might be first day of classes. It might be moving weekend, but it's just to make a point that you have control over this person status, whether it be the actual person status. You might set this kind of enrolled segmentation data element in a custom field. It could certainly be a decision that that lives on the application etc etc. So there's a number of different kind of data elements that could designate this person.

Record as an enrolled student, I use person status is the example for this this use case, but it could be persons status and a custom field. It could be person status and a decision. It could be just a decision. So just just note that there's a couple of different ways to do this, but you're ultimately going to want to segment these records away from all of the other records right back to the dashboards ANAN. Again, a lot of these tabs here are showing as a result of of.

The populations that these students are falling into. So because I have this student in an enrolled population, these tabs are actually dictating and structured to show for only students in that enrolled population. So if we go back to Layton, Layton is not in any enrolled population. Therefore none of the tabs are going to show all right.

I you might again this is just kind of continuing this conversation about this record becoming the centralized data repository. All things about the person record, whether they're coming from the SAS, whether they're starting and living inside of slate, or they're coming from the LMS or the financial aid system, or REZ life, whatever it is, Slate becomes this, this hub. This data hub. This one stop shop, right? If it's classifications, these points of information may look familiar to folks that maybe use banner. You know? What are those official classifications from the SAS where they're declared major?

And there standing so on and so forth. GPA information, right? So I can do some calculation for you, right? If you have an index, you know an emotional index or scoring rubric that you want either automated or somehow administratively managed or handled. You can have slate evaluate some type of overall emotional score, risk score, whatever you you can kind of define it as or calculated as, and then these other various kind of these are custom fields that live.

On a custom field that that live on a custom tag, right?

Finally, before we move on something like this is something comes up an awful lot this this concept of I want.

All all all my notes are all kind of the bits of information from a particular group of users or group of staff, right? I want them all kind of categorized on one tab and what I have here is another entity that's just categorizing these advising notes, right? So if all of your advisors go to one spot to submit their notes, you can have this to be a spot on the person record that all of your advisors go to land on. We can have this kind of, you know, you can sort of chronologically and say I just want this chronological view.

Kind of every touchpoint than that an advisor has had right with the with the student.

Let's pause for a little bit and talk about kind of the user experience. So I'm I'm logged in as as an admin, right as an admin user. But let's say I'm not. Let's take a look at somebody who may be logged in a little bit differently. Let's take a look at Cali. Cali Boucher is a faculty advisor and she she needs some access to slay. I've given her some faculty advisor. She's faculty advisor for the biology program. She's got some pretty basic permissioning, nothing crazy.

And she belongs with this within this advising Realm. OK, but we've given her this faculty advisor role and let's take a look at how she's going to experience this same person record. So this is I'm I'm pretending to be colleague, one of the first things we're going to revisit here after we talk a little bit is reporting in kind of this first dashboard that they view. But let's go back to that Kendrick record. You can see that the tab structure is just a little bit slimmed down, OK?

So you'll see that there is a research tab that popped up over here that is no longer visible, and the advisor notes is no longer visible. Maybe because you know if your user doesn't need to see certain tabs, you can absolutely control that down to the level of by user, by role, by permission. So the fact that you know you may have tabs that are housing these type of advisor notes that you don't really want everybody to have access to, even though they have access to the student record.

You can structure that and control that at the at the user level, right? So we're going to bounce out of this impersonation and you can see that these tabs open back up right, bouncing back here. These three excuse me, these four tabs here are representative of each of a time period. We actually have a pretty straightforward and standard period and round structure, and this period of these period around structures aren't associated with any applications that the student is going to be submitting right? These period around structures are actually solely for administrative.

Internal use, but I'm automatically creating them to represent a period of time during the students time at the University, right? And these tabs these rounds can actually be structured to house information that is specific to that year, so we might be able to take a look at somebody's financial aid structure or what type of awards they're receiving year by year over year, and see how that information is changed from first to second year. Having these structured behind.

Period and rounds is also a beautiful way to take advantage of things like checklists. So if you have documentation or materials that you need from each student each year, you can take advantage of of checklist items right and collect those those bits of information from the student and allow them to submit them to complete the checklist year after year. You can think about that concept from. I just need these to be able to register for classes. I need them so that my financial aid.

Uh gets renewed every single year, so on and so forth. So you've got the concept of these tabs, so let's bounce away from all these other tabs here, but the concept is that really, you know, you can house an awful lot of information.

That can be centralized here on this person record, right?

You can contact this student record. Alright, so the beautiful thing about Slate also is to say, well, you know what we need this to be. Our primary conduit for communication for our enrolled students. We want to take a look at engagement and how they are opening our emails. And if they're opening our emails. So, just like the admissions functionality, right or just like Slate offers, you have full access to communicate with these students at the ad hoc level, let's say I just need to get in touch with Kendrick. I'm as advisor.

I need to get in touch with Kendrick in a one off kind of ad hoc way. I need to send him an email or I need to call Kendrick right? You can call him directly from us late via Slate voice. You can call and leave a voicemail and then follow up with a text message, right? You can send a text message to Kendrick to say hey, it was so great chatting with you the other day at the advisement appointment, we can't wait to develop the relationship with you. All of this information as most of you know.

Is categorized and aggregated here on this comprehensive chronological timeline, so you have a beautiful kind of really rich data. Mine all of this information, and in fact you know this would even go longer at Kendricks, a relatively young quote unquote record here in in this database. But imagine you have then have all of this information that goes way back to when they went through the enrollment funnel, right? So maybe from the first day that they stepped on campus.

Their junior year in highschool. You've got this. This mega mega amount of data living here on their timeline so you really can get paid highly granular view of what the students kind of engagement, email, correspondence, texting, anything like that in their timeline, right?

Or bounce over to deliver so you can also get in touch with a ton of students at the same time too. So let's say you want to get in touch with a group of students that you're defining by a couple of variable data points. To say I want to send a message to all students that have the, let's see that have these. Do two data values. A class standing of Softmore right and declared major of undeclared right? So they're undeclared students. If these are two data points that you're keeping somewhere on the person record, you can.

Query upon them I want to send them an email that says, hey, you're a sophomore? Anuar undeclared OK, great so schedule your appointment. You can fill out this declaration of major form and or you can submit your. You can sign up for an advisement appointment. You might say I want to send a lot of emails or more than one email or can piece of communication to a lot of students right? So you can say I have three pieces of communication. I have 3 emails that I want to send out. I want these.

All these emails to go out to all of the first semester freshman, so by way of population, anybody who falls into this freshman population is scheduled to get these three messages right. And this beautiful thing here is, you know, it's kind of dripped out overtime. This concept of campaign marketing or campaign drip campaign management is that you can set these emails to go out days after they fall into the population. So two days after this student enters this freshman population.

Other scheduled to get this. Hey, welcome to campus. We can't wait to see what you're capable of achieving here. We can't wait to work with you and see how you grow as a student. Five days after that or seven days into the campaign, you can send them an email that says, hey, come register for the clubs and organizations fair on campus. We can't wait to see you. Register here, right? You know 65 days into the campaign were kind of now I'm just kind of taking this and and expanding it here. End of the semester type of conversation that says hey don't forget to register for.

Horses in and register for classes next semester. Course registration is open, OK and every single message comes with the delivery of the standard delivery statistics. As we know where you can take a look at sent delivered unique unique clicks, clicks, bounces so on and so forth, you've got this nice graphical representation here and or you can take a look how they're accessing it via which browser and where they are in kind of space and time when they are accessing that email.

Another concept I just want to visit very very quickly is this concept of nudging, right? So, let's do you know this this concept of soft nudging via text message, right? So we want to send some soft nudges to test via text to students, but we want them time to go out at a certain, maybe time of the semester, right? So I want to send this test test text message to any students who have this kind of data value. They're missing their fasa.

That's what's going to qualify them for this query, and we just want to send them a reminder that says, hey, do you want us to give you a text over Thanksgiving break to remind you to renew your Pfaff set? Just let us know, right? Or you know if they crossed some threshold right where they fall into a population or their GPA drops below a certain 2.00 or something. You can send a message that isn't exactly a direct acknowledgement of why they're being communicated with, but it just says, hey, we care about you.

We want you to be successful here, so don't don't be afraid to reach out.

There is this concept of positive nudging to hey, congratulations. Good job for attending this event. Basically, right? It's not necessarily this concept of only messaging students when they've done something bad or when they haven't done something, but this positive encouragement of like hey Congrats thanks so much for coming to this event. Did you know that you know 70% of students who are involved on campus graduate on time, so on and so forth, right? So you really have this option.

This at the at the person level I need to get in touch with just Kendrick, right? I need to get in touch with a group of students or a population of students and or I need to get in touch with a lot of students with a lot of messages overtime so they can really really enveloped a lot of those communication efforts that you have for currently enrolled students. If you so choose.

OK, jumping a little bit. We did talk about hey, register for an event here on campus so it can also manage your events if you like. The first thing that often comes up in conversation.

Is advisement right? So for the advisors out there, I want to manage my advise meant my schedule, my appointments. I want to schedule my availability and all of the appointments that I'm going to have available to me inside of Slate. This is kind of the internal view of the calendar, and you can structure your evnt templates where you can consume the information that you want from the student right where via the form editor where you can simply drag and drop, or you know.

Put information in that you like, or drag and drop. You can make fields that are internal only, that aren't necessarily going to be seen or visible to the students, but you want to consume information from the student here, but then you want to add in your advisor notes based on how the meeting went afterwards, and ultimately, what this looks like. You can actually, so you also have the ability to say I want this.

I want this.

Pavan scuse me. I want this type of event to be online. We're still doing virtual stuff, so we resume campus so and we have zoom event. We can host these advising events. These one on one advising events. The zoom so we can connect to our URL here and or you can use the native slate share platform that we're using right now. That's how I'm connecting with you all, so there's a lot of options here to manage your eventsin. You can create N number of events out at a time.

If you want to say I want to schedule my calendar, my availability or my appointments for the next month or the next semester or the next year, you can absolutely do that. The calendar here this this slate events calendar does fully integrate with Gmail and Outlook.

And if you integrate the calendars and make that connection, you can overlay one calendar over the other, but it ultimately looks like to the student is this landing page right? This event landing page where this will be wrapped in your branding and I find the student I'm engaging on Kendrick right, and I said, OK, cool. Here's the this month's availability for virtual advisements sessions. I want something this Friday. The 9th looks like there's an event available at one on Friday. You can see the information.

They're asking me for and or and. What we didn't notice here is that that advising notes that internal field that's going to be submitted later by the advisor or the person the staff who met with the student, right?

So you have this concept of managing your calendar and what could be forward facing to the student for all of your advisement advisement events.

Uhm?

If you wanted to something like that that portal it could, or that that landing page experience that could also be pushed behind a single sign on. So if you wanted your students to use their institutional credentials to log in right through some type of single sign on, that's that's also an opportunity as well so that you don't have to continue to ask them to identify themselves with with all of that, you know identifying information, right?

So everybody having fun so far, we're doing good. Let's talk a little bit about forms. OK, so this concept of a forms is kind of ever present throughout Slate. But now you're saying, OK, like heads, I've used forms. We use it for our request for information. We use it a lot for admissions. How can we do it for student success? So let's think about. Let's think about thanks Ken. That's awesome. I love the caps. Let's think about how we can do this for like a forward facing.

Or something that the student would be consuming, right? So it would be accessible through this URL again? Maybe it's through portal, maybe whatever it is right, and it's like a declaration of major for maybe the student. It's an advising intake form. You have these students fill this out at orientation or during their first week of classes, right where they're entering their information, their University ID, whatever it is, and their identifying what they want. You know what they're interested in for counseling? OK, how am I feeling about my semester? So on and so forth, right?

Or you're actually consuming information from that. You also have this concept of and then I had that declaration of major form as well. Yeah, so I'm a student and I'm I'm pushing in this information that I want to add and I want to enter into slate of you. Evaluated, right? You also have this opportunity for internal types of forms as well. Early alert forms. Earlier management is often something that comes up regularly in conversations, so let's say you have.

Well, let's actually. Let's take a look. Let's go back to Kendricks record. Let's say your staff has access to Kendrick's record and they know that they they want to submit. They want to raise a red flag. It could be a form. It could be A tag over here. It could be something like a watch flag that they do via adding an interaction. Whatever it is, right, they want to raise some type of alert. Alright, I have a couple of examples here we can. You can use tags. You can use the concept of I want to add a watch flag which is kind of high visual or.

That's going to stay very visible on the person record or I'm going to submit a form. OK, so if I'm on the person's record, you might give them access to that form directly from the person's record and it's going to pass through some information about that record so that they can not in, so that the staff Member doesn't have to fill out all that much information about the person they can say, Yep, something's going on, and he's not really showing up, and I'm going to submit that form alright. You can say, well, we don't really want that user.

To have access to the slate record, that's fine if you say we're going to push them. Actually, write to the registration form inside of Slate. OK, so that they can search by the name of the student across the database. They can name their course and they can say Kendricks not showing up. You might say, well, we actually really don't want that at all. We don't want at that particular users. Maybe we have faculty members that we don't. They don't need to be enslaved, right?

But we need to consume information from right. You can say, OK, fine, we're going to bounce them to you to a URL.

And this URL they have saved and they know that they're responsible for going in and saying, I know that I know that I have to fill out this form whenever I have a student who I have to raise a red flag on, right? You might also say that we want we don't even want to send them this link. We want to have them access this information via a portal, right? So now I'm operating inside of Slate as a colleague who is a faculty advisor for the Biology Department.

So she's going to be accessing a portal.

And this portal is going to show her just the students for whom she is responsible, where you can kind of stylized this. However, which way you like, and you can display a list of information to Cali to say here's a list of your advisors, and here's some basic information about them. And if you wanted to search across all of your advisors, you can absolutely do that, and you can take a look at one specific record. And let's say you do want to submit an alert for that student's record.

Bounce over to that same form once you click on that person's record, right? So this concept of we want to consume information from users from faculty from advisors, from coaches, whoever it might be. There are three or four different ways to provide them access to this type of information or this type of form where you're asking them for information, right? So this concept of early alert forms can really be something that.

That you can take advantage of, and that's going to answer a lot of the needs I think across campus and across those departments. You might have an early alert form.

That is going to push and create some things inside of slate upon the submission of the form. So let's say I'm still submitting the form about Kendrick.

I have a concern about Kendrick only I can't type. I'm going to say I'm typing this. It's a medium priority.

He is never in class, never class.

Didn't speak with the student, but I have responsibility for creating tasks that are going to go and be assigned to somebody else inside of slate, so I want Callie to have a task that's created to follow up with Kendrick because that's important and I might. There might be another task that needs to go to somebody else. These tasks upon the submission of this form, so the form would be submitted on behalf of Kendrick here, and the tasks would be created by way of automation.

And be associated with that particular person record inside of slave and then via automation and assignment also.

Be assigned to a user, so let's refresh here and we can take a look and see let's say OK, so it captured my form. It's commented, right? OK, great, I got my form here. No problem. Let's bounce to Kendrick's record to make sure that it got logged on his record. Alright, got logged. I have some messages going out as a result of the submission of that form, right? And we can take a look at that. Take a look back right? I can also see that something was created.

As it relates to responsibilities. So something just.

Happened here where a task was created as it relates to the submission of this form. So these tasks are situationally aware, so the task knows that I'm on Kendricks record and it also knows that I am logged in, so I have a test that's that for which I'm responsible specifically and I can see that this task has been assigned to me. I have to go do something I have to follow up with Kendrick and I can edit this task. I can take a look.

Now it's part of a bigger project. I can take a look at kind of the task individually, or I can see from an administrative kind of you how these tasks are being performed and completed, and if the deadlines are being met. So if you wanted to add kind of automation and alerts and notifications to these processes that are happening inside of slate, you can do that via these form submissions via task creation and assignment.

Right, that keeps your users aware of kind of what's going on, right?

I knew and I knew this was going to happen already running out of time and close to 49 already, but we're going to keep rocking and rolling everybody cool. So let's bounce back and say, alright, so one of these things that we're looking at here is what do you want to see? Maybe you want to have kind of a user experience that is dependent and kind of user specific based on based on what their role is or what the staff members responsibility is. So I have this here. I'm an administrative user, so this concept of showing.

Information here across the home page is something that's important. I might really be interested in showing this overall comprehensive retention report that gives us this bird's eye view of what's going on with charts and table structure. So on and so forth, but I might not be interested in that at all. Or I might be responsible for this enrollment. Enrolled Student Snapshot report, right? Where you can take a look at. Kind of these this overall data about about your enrolled students.

But I might just be a day-to-day user. I don't need access to these two reports, so the first thing that I might land on are these user aware and user specific widgets. So this is like my login page. That's really only pushing information forward to me, for which I'm responsible for that day, right? So if I want to breakdown of like, oh here, the tasks that I'm associated with here is a breakdown kind of graphically of my students. My tasks by type, maybe my students and kind of where they fall by major, effeminate.

Sir, you could bounce them to a query to that, send them a link to their tasks. That might be that might be incomplete, right? So I can see that OK, these are the tasks for which I'm responsible. These are the students, so I need to. I need to access that, right? I might want to send them a list or send them to a query for all of these. All of the students for whom their assigned right? Just again, this is bouncing them over to a query that's user aware. It's set to, you know.

At current user, where you're pushing information towards the user that specific to them that they can call on and look at every single time they log in right? It may be that the administrator or whoever is logged in needs to see all of this information right here, right? So that's absolutely something that could happen, all right.

Let's bounce a little bit to the reader quickly.

Let's say the reader is one of these beautiful tools inside of Slate. Again, my bias is showing, but I love it there where you can if you have a process that has a beginning and an end and needs some type of review it and people need to be involved in it, right? You can create workflows and structure in here that actually can carry a student through a particular process or a review. We think about it under the guise of, you know, applications and application review, and that's what you been structure looks like.

But think about the kind of case management concept in student success. Let's say you've got an academic hold, a review process, or students who are at risk, right? Any student who's at risk you want to be able to push them through a particular process. I'm going to use the example of. You might say we have a conduct review case, kind of management process that we have students go through, and this is the structure of it. Somebody looks at it first and reviews things. It then goes to a resolution plan, and then it falls. Ultimately, in one of these bins or categories.

If there was action taken or no action taken.

The submission of a form like a conduct, process or conduct violation of form you can structure and have available to start this kind of reader review process right? So you know you can take a look at this where this form was submitted, ID's the student an talks about kind of details, what the conduct violation is one of the other pit bits of information that may be important as the students transcript, but you have customization here to add any number of kind of reader tab groups and materials.

That you might be interested in reviewing right? And then all the benefits of the reader too. You can. You can add annotations. You can highlight. You can add notes and then ultimately, if I'm responsible for reviewing this, you can say here's my evaluation. I think the case should be dismissed, or I think it belongs in a formal hearing. I'm not responsible for this portion of the review form. It needs to go to the formal hearing been next, and I don't need to. I don't need to have next.

A separate viewer, a separate reader, so it's out of my queue and it has been pushed. It will be pushed through to the next bin, so this concept of utilizing the reader for your case management school for your case management process, excuse me, is really something that you can take advantage of here.

Uhm?

OK, so I'm going to pause so I talked about a lot in a little bit of time. We talked about Slate, the student record being the centralized data repository we talked about. Kind of all the related things to a student record, talked about communicating with that student record. We talked about the forms and how they are attached to student records and events. So on and so forth. You can talk about. Maybe let's talk about how you want to automate some of these processes you might create.

A bot, right? A UM student success by this chat bot that that has a conversation with students via text message. Maybe I'm going to go ahead and in person eight, I'm going to impersonate myself because Ken Higgins has some inbox rolls and Ken Higgins is going to start viewing information about Kendrick. So let's take a look. I'm going to send a text message to myself. Excuse me, I'm going to send a text message from my phone and I'm going to say hello.

And I've structured this bot actually too. I just texted and the bot actually said hello back. So this just happened just now. I sent the text message, but I have a bot to this. This AI chatbot that's going to be talking back to me via this. This structure and the bot is structured to have any number of intense that you may want to have if you want to prompt the the bot to say any type of incoming.

Information that comes in. You can respond this way and or it can actually consume FA Q. So if there is an FA Q that lives on your website or one of the web pages, you can have slate this chat bot read and consume that information and learn the answers that then become intense, right? So if I text that same number, how much?

Sleep do I need?

I'm texting right now and let's bounce back over.

To Kendrick's record here.

And we can see that this bot via this text message is having this automatic conversation with me. I'm texting on my phone literally as we're kind of having this conversation, and this AI chatbot is giving me this automated. These automated bits of information here, right? Lastly, you might say, alright, great, well I need to be able to aggregate information up. So what do you do with all of this data, right? We've talked a lot about aggregating data. We've talked a lot about associating data to a student's record.

And pulling it. So now what do we want to be able to do with this information? You can aggregate it up into a report. You can take a look at GPA, information, any datapoint that's captured and kept on a person record can be called upon and queried, and possibly aggregated up into a report, right? So you can take a look at this, start taking a look at retention metrics if you want to look withdrawn how it relates to 1st Gen or any other kind of data metric here, right? You also have the ability to.

Take a look at predict right? So predict allows you to enter in information historical set of information. I've got a pretty.

Basic structured model here where I want the information to be evaluated that's listed here. I want these exports to be evaluated on some type of historical set and then I want the predict model. I wanted to take a look and supply me with an outcome via this regression model analysis. This model was actually generated this morning.

Predict is operational. We actually have some supporting documentation articles that's going to be following up pretty shortly here with kind of some best practices for how to feed predict the right kind of data for it to operate effectively and efficiently, and to actually give you some regression analysis that's that's valuable to write the data that you have it evaluate is really, really important, so if.

There there is a huge value in making, you know, taking the data that exists on the person record or all of the information that you've collected on the person record and starting to use it to inform some of your decisions. Decisions right so you know if this information lives in your assassin, you're bringing it over from slate, from SAS into slate, or if it starts in slate by itself, you really want to be able to have this model. This predict tool consume that information and then maybe.

You know, offer up these kind of predictive.

Traits or data factors to help inform your decisions? I think ultimately that's what we're talking about here. I mean, one of the goals for student success is is exactly that. You know. Obviously, increasing your retention rate, and you know having? I mean, obviously it has budgetary impact, so on and so forth. Ultimately, what we're talking about is is helping the student be successful. So ultimately, that's that's how I want everybody to be using Slate.

Right and and taking full advantage of the tools that are available to you with that, there is literally one minute left, and I've I've run out of time to talk. I could talk all day about this because it's something I'm passionate about and and hopefully you guys enjoyed the bit that you saw. But to pivot, I really encourage that now if you liked what you saw or heard something like, wow, that's pretty cool. It's I'm going to take a look at this. I want to I want to move forward.

We have we have a lot of documentation and knowledge base. There's a getting started guide for student success, so it kind of put it. It puts things into perspective about some strategic conversations that you're going to want to think about before you head down the path of student success. We have a community forum. I think somebody mentioned it in the chat, but I absolutely love the sub cohort student success and advising Community forum. There's great chatter in that in that forum, so I really encourage that you join that.

That and start following and comment and share and ask questions there. We have learning lab where we have a fundamentals of student success course and those courses. The next one is actually available next week so you can access that all through your database of administrative tool in your database.

And we can actually request information. So if you just want to request information from the website and you want to follow up with more formal kind of demonstration for you and your team or any of the other stakeholders, then then that is available to you as well as an option I want to Lastly plug one more event that we have coming up prior to the festival. If you're interested next week Slate plus I wave our very own Sean Kelly.

General Manager of Advancement is going to be talking bout actionable fund raising intelligence for higher education, which is great. It's next Wednesday, April 14th at 1:00 o'clock and then shortly after that we've got our slate innovation festival where we've got this late stage happening in throughout May and June. We've got base camp and then obviously our in person. A summit next June in Nashville. So I talked a lot. It's there's one question.

Is there a showcase that will be available? Yes, so Joe. This showcase that we operated in entirely today. It's going to be available to you guys in very short order so you can take an pick and choose the any elements that you like. From it you can provision it into your clean slate environment. So with that, I absolutely want to thank you all for your time. This was fantastic conversation. I'm sorry you know there's so much to talk about. I I wish I could spend more time with you all, but you guys had some great great questions, great comments, and I encourage you to continue the conversation.

Thank you guys for attending and I look forward to the next time we get to see each other in person. Thank you to Aaron and Sean for keeping up in the in the comments to thank you all. Have a good one.

Everything inside.