Name: Pathify Demo | December 2025
Uploaded: 2025-12-11T19:00:05.892Z
Duration: 29 min 8 s
Description: Pathify Demo | December 2025

Transcript for "Pathify Demo | December 2025": Hello, everybody. Welcome. Welcome. I'll give everyone another minute or two to pile in. I hear that there might be some folks who haven't met me yet on this call, some folks pretty new to Pathify. So I'll introduce myself here in just a second, but, again, we'll give people some time. And I hope wherever you are, the weather is treating you well. I am in Colorado Springs, Colorado, and we got some mad crazy snow last week. And now it is up warm enough that you can go out and do chores outside in a T shirt. And so I'm a little confused about all of this, but that's okay. I figure some of you are probably getting hit by snow, and some of you are like, it never gets below 60 where I'm at. So wherever you're at, that is awesome, and we'll go ahead and get started. I won't waste any more time talking about the weather, although, let's face it, it's one of those subjects that's near and dear to my heart. Most of you who are on this call probably haven't met me yet. My name is Julie Gummerman. I'm the senior sales engineer here at Pathify, and I'm gonna be talking to you a little bit more about the platform. So a little bit about me, I started here about five and a half years ago now, as a junior dev and did integrations back before we had our out of the box recipe library for integrations. And so then I moved over to the sales department. I've been a middle school teacher for some twelve years or so. And so while I intended to just do development, my reputation as a talker preceded me. And now I'm here to talk to you about Pathify product. I've been over on the sales team now for about four and a half years now. So what we're gonna talk about in today's session, we can definitely get more deeply into integrations if that's what people are interested in. I love to let these demos be slightly driven by the folks who are attending them just because it makes it more interesting and relevant to you. But we are gonna start talking about the why of Pathify, what makes it relevant, what makes it worthy as an investment, what are the, benefits that you get from implementing it, and the problems that we solve in the process. We're gonna talk a little bit more about why institutions choose Pathify, and then we're going to get into the demo itself. Again, I do have a technical background, so we can go as deeply into integrations as you want. But the things that I was actually hoping that I could cover today would be things like communications. I know that most institutions are facing the issue of students really don't read email. You can send emails all day long, but people are missing things because they're getting notification fatigue, what to do about that, and how to make things more relevant to your users. So we're gonna talk a bit about that, as my primary focus. We're also gonna talk a bit about accessibility. I know it's December now. In April, there are some new laws going into effect about how accessible your programs need to be. We're gonna talk a little bit about how we meet that criteria. But first, the why. So back when I started college, way back in the day, I will go ahead and date myself 2,001 to 2005, we had maybe four systems that I had a as a student had to keep track of. We had the SIS for checking grades and registering for courses. We had the library. We had email. And then if I was taking summer courses, and usually I was because I'm an overachiever like that, we were using WebCT. Things have just ballooned and blossomed over the last twenty or so years. And so now we're not only talking about those core LMS, SIS, email, and library. We're also talking about retention systems. We're talking about StarRez and similar systems for registering for, housing and maintaining housing. We're talking about ticketing systems. Oh my goodness. So many systems floating around out there. And somehow or another, all your users are going to have to figure out what's going on and when the deadlines are and where those systems actually live. There's this, a lot of times, this big black hole at the center of the campus, and Pathify is designed to fill that hole. So rather than having to hunt around for where is the library, where is the ticketing system, There are five different event calendars, and they all live in different systems. How on earth do I find all of that? Pathify becomes that organizing force, that campus experience platform that lives in the middle of it all. So no matter what your major is, no matter whether you're staff or student, you're gonna be able to have access to all of that functionality at your fingertips, and you're gonna know exactly where you need to be and when. And we'll talk a little bit more about how this happens in a second. That said, I have a couple of case studies for you about the why and the benefit of choosing Pathify. So it's not just about making sure that your users are linked to all of their systems and that those systems are integrating with Pathify. It's also about that, ability to bundle a bunch of your systems into one. So, for example, we have University of the Pacific. They were able to consolidate their LinkFarm student portal, their basic mobile app, and their student group and activities platforms and bring that all into Pathify, getting rid of some of those systems. They no longer have a separate portal and mobile app. They do it all with Pathify student groups. It all happens within Pathify. The IT teams, reduce their budget by, 45%, freeing up funds for other things and other initiatives. And but the time when all was said and done, they were able to bring 29 systems down into five. Because the University of the Pacific all has also has one of the best use cases and success stories that I've ever heard about at Pathify where every year, once actually twice a year, once a semester, there would be a particular day where they knew that everyone would be registering for classes. And on that particular day, that group of students, and it was usually around 800 or so, those users would go to register for classes and find out that they had holds and restrictions that were outstanding, and they'd be locked out. And so the registrar's office would just brace themselves for the fact that this day was happening. Well, they implemented Pathify, and they started sending out announcements, which is one of the functionalities we're gonna talk about today. They'd sent out announcements, but they were bracing themselves, not realizing that things were about to change dramatically. That day comes and goes, and lo and behold, there were only 80 students with outstanding holds and restrictions. They thought their banner system was broken because of the fact that 800 down to 80. Like, surely, there's a zero missing in there. Something's wrong. Nope. It turned out that actually you had 700 users that now no longer needed to call the office because they knew exactly when and where to take care of their, their balances before it actually came to fruition. So not only a, savings in money, but also a savings in time and energy. Meanwhile, you also have Alabama A and M University. They were able to consolidate several systems into one. They brought their student portal and their employee Internet into Pathify. They were able to get rid of their mobile app that was separate from their portal just like what University of the Pacific did. It now lives in Pathify. They were also able to utilize Pathify's chatbot, and the end result was saving $25,000 a year on systems. So enough about the why. Let's talk about how this one actually works. And I'm gonna do a quick shout out. Never mind. I was about to be like, okay. I need to get help unsharing my screen despite being a developer. Sometimes, platforms that you see in a GUI kinda throw me for a loop, but not today because we are about to go into the dashboard. So within the dashboard and, by the way, you have full control over your branding. We would expect that by the time is all is said and done, your Pathify instance would not look like a Pathify instance. It will look like your instance branded for you, whether you're talking about the dashboard here or whether we're talking about the mobile app. But I'm coming in as a portal admin. So right now, things are looking a little busy. I'm seeing a bunch of announcements. I'm seeing pretty much every content that this platform has to offer, and we're gonna take a look at the student experience here in a bit. But what I really wanted to do right now was take you behind the scenes into announcements. So, again, I know that we've talked a bit about the fact that students just don't read email, and what do you do in order to make sure that your students know what they need to know when they need to know it without them going into overload. So we all know that most students don't read emails, and a solid way to get them to interact is to provide a push notification. We're gonna talk about how to make that happen. So with an announcements, this would be the piece that is going to allow that to happen. This is what allows those banners, if you will, to pop up across my user experience. And, in fact, I believe we just saw another one pop up right now. That's because someone's demoing behind the scenes while I'm demoing. As a portal admin, I see everything going on. But I would come over here, and I would be able to add an announcement. These are highly permissioned. You can even set these so that maybe there's a user or a role that only that only announces to students. They can't accidentally hit up staff. And you might have people working in the HR department that can send announcements to staff but not to students. That said, as a highly permissioned user, I am going to see content that would go out to any of these roles. And today, I'm actually going to send them to a role that's associated only with my test users, so I don't throw anyone else for a loop when my announcement hits them. Also, though, you can send to individual users. If you have seven users and you know who those users are and you wanna tap them on the shoulder about something, you could absolutely go in and add them one by one. Also, let's say you're working on some project related to students who want to be involved in a study abroad program. You don't have a role in your SIS for those students, but you do have a CSV with the 59 students who are interested. Few too many to want to add them manually one by one. What you do instead is you'd upload that CSV, and that's gonna populate those users getting the those announcements. From here, we can also go ahead and choose our delivery channel. So, again, email, not super popular among students. Staff tend to be a little better, but the more email you send, the more trouble you tend to run into with people not reading things. So I'd probably go ahead and send this to the notification bell, the push notifications, and the activity feed for my users. And I'm going to decide whether or not this is going to require user acknowledgment. If it does, we're gonna see a little pop up for that user that they have to acknowledge. And, of course, your students would never do this. And, actually, for the most part, most people, when they know that something's going on, they'll take care of business when and where they're supposed to. That said, if you ever ran into a situation where people are saying, but you never told me, You wanted to put require user acknowledgment. You can actually pull a report of these particular users and who saw it and who acknowledged it. So I'm gonna go ahead and let's say this is an emergency alert. So we're gonna announce about a snow day. Again, I have snow and weather on the brain. That's usually where my brain is. I mean, we might wanna say just, hey. Continue your studies online. And on that note, I can go ahead and and I'm also gonna allow users to dismiss it, and it's gonna be an emergency alert. It'll target a push notification to my users. And sure enough, as a user who received this announcement, I just got a notification that I need to go ahead and acknowledge before I actually go back into the platform. So as a user, I'd see this as a push notification. I saw it as a pop up. I'm also gonna see a pop up here on my screen as a portal admin. Any other portal admins would be able to see it as well. And as a user, I can go and say, yep. Got it. I know that I need to check the LMS. I'm gonna go ahead and dismiss that. So behind the scenes, if I came back into announcements, I could actually go in, and I can start pulling analytics. I can pull an acknowledgment report that's going to show the users who received it, the users who acknowledged it, their users who have not acknowledged it, and I can download a nice spiffy CSV that's going to allow me to target those users who didn't acknowledge it a little bit more aggressively. So, by the way, I'm about fifteen minutes in. Again, my reputation as a talker precedes me. If you have any questions for me, please drop them in the chat. Please drop them in q and a. I'll make sure that I'm checking those, and we'll get to anything that you wanna bring up. That said, announcements, there is another place that these can originate within the platform as well. So if you end up going with the communities module that plat that Pathify has, you also have the ability to send notices to your users. So not quite that real estate taking up level of urgency that an emergency alert or an alert would have, but plenty so that I can actually, be targeting the users I need. There's another piece of functionality that Pathify offers, though, that if this is a major pain point for you of people knowing where to go and what to do at particular points, you might wanna take a look at success, which includes the tasks module. So if I come in, I'm gonna come in under Julie's student, who has student permissions, and we're gonna see that pop up again. And Julie's student has a somewhat less cluttered view than, I did as a portal admin. In fact, I'm only seeing two announcements, an emergency alert and an alert, rather than me as a staff member who saw everything. As a student, I'm coming in. I'm seeing information pulled straight from me for me from those source systems, and I'm seeing a widget called tasks. Tasks is connected quite deeply to the tasks module. And, in fact, as I come in here as a user, I'm seeing tasks that have pull been pulled in from different locations. So maybe I am seeing a task I left for myself about needing to catch up with one of my classmates about a group project. I can definitely say, yes. I got that done. I'm gonna check it off. I'm also seeing a task that originated for me from a group, the computer science group that I'm a part of, something about reviewing potential careers in community computer science. And last but not least, I am seeing a register for spring courses task, and I can say, yep. I did that already just like I was supposed to. And lo and behold, I'm seeing that that filled in part of this chart, and it triggered two more tasks to take its place. This is part of task pathways, which is included within tasks. This is great for onboarding and moving students between different sections of the user journey where you can actually set off a series of tasks and groups of tasks that will trigger other tasks in their creation, another piece where you can actually pull those reports of who's done what behind the scenes. There's one other place where these tasks can come from. Those would be third party systems like the SIS, where you could actually sync your SIS with Pathify to let people know that they have this particular piece of functionality or this particular task that they have to do. It is your choice whether or not those come with call to action buttons. I know some folks are partial to having call to action buttons so people know exactly where they need to go in order to complete a task at a given time. We also have some tasks where maybe we want to, leave those, off of the radar. Maybe it's like the housing discussion. Maybe you just wanna remind people, hey. You need to be thinking about this and get sitting set up, but there isn't necessarily a place to go to take care of it. So tasks, a pretty useful piece of functionality. So it looks like we still don't have any questions in the chat. So on that note, I wanna talk a little bit about accessibility because I know that our platform is very blue right now, with Pathify's new branding, but I also know that it is entirely accessible, and I would love to talk about to you about the functionality that makes that possible. So what's going on, in the world of higher ed right now is that I know that campuses have until late April to make sure that they're meeting, WCAG 2.2 or 2.1 a a accessibility. I'd like to talk a little bit more about how Pathify does that. So depending on how much you've talked to us already, you know, Pathify has three week release cycles, and we do an accessibility, check before every single one of those. So what we're gonna do is we're actually gonna run things through a number of screen readers. We're going to do a visual check. We're gonna make sure that with the new functionality we've released, headers are still nested, that we're gonna make sure that any of these icons being added on the left hand side, those are gonna be hidden to a screen reader because they're gonna clutter up that user's experience. But we're also making sure that with any of the new functionality we've added, that we're allowing users to make sure that it is accessible. And so one of those pieces behind the scenes would be if I go into pages and I'm going to go into advising for student services. If I go and Julie's student's not gonna be able to edit this, but as a portal admin, I can if I go under edit page and I go to this little person right here, I'm going to be able to actually verify that this content is accessible to my users on screen readers. It's gonna verify, hey. Is everything looking okay with color contrast? Are there headers that are out of order? Some other things available to me is that if I wanted to I'm just gonna go ahead and upload a picture. I can add alt tags right here. I don't have to be technical to do it. So that's gonna be one of those pieces that allows me to keep things so that a screen reader can use them. Same sort of thing with if I wanted to add a link, I'm going to be able to not only include the text that displays for my users who are accessing this through the browser, I'm also gonna be able to add titles for screen readers. That said, there's also some pretty sweet functionality that goes on behind the scenes within the Hub experience where you can create dashboards and set branding. So I'm gonna go ahead and flip over to Hub experience. So behind the scenes with themes, this would be where I can actually set up my branding. So if I came in here and I'm a new customer like some of you are hopefully about to be, I could come in here and I can start actually setting up rather than seeing Pathify branding. I wanna bring in my default logo. I wanna bring in my stacked logo that's a little smaller. I'm gonna be ready to go with that. That said, in order to check the, the accessibility, I'd actually come over here where all my colors are, and I'm gonna be able to start seeing what that accessibility is looking like. If I came in under main menu text hover, I can come in, and I can actually play around with okay. I put in my branded color. It's still not accessible. I can actually adjust my color scheme until I start seeing things turn green. And this is also where I might go in and perhaps my color one of my colors for my institution is orange, kind of like the salmon color. It's sometimes a little hard to make orange work if you're talking about buttons. We're also gonna walk you through okay. So you might wanna use your navy for those buttons and use your oranges for pieces where it's going to be a little more accessible to your users. So accessibility, near and dear to our hearts. We're gonna make sure that your users are gonna be able to use it on the screen reader. So we've talked about announcements. We've talked about accessibility. Let's see. And I see that folks are asking whether or not this is being recorded. Yes. Indeed. It is. So I have eight more minutes with you folks, and I wanna make sure that I'm actually talking about the things that you are interested in. So I'm gonna go ahead and post a poll, and I'm going to let you folks choose what it is that you are taking a look at. So you should be able to see that poll on the screen. Okay. And because of the fact that I'm not seeing answers in there, I'm gonna assume that I am doing an absolutely wonderful job of presenting and that you are loving using your lunch break in order to listen to me talk about Pathify. And on that note, I'm actually going to jump back onto my screen. And we're gonna talk more about the user experience. So we've talked about accessibility. We've talked about announcements. What we haven't talked about is me as a student user and how it knows who I am and what to be showing me. So I'm gonna go back in as Julie student. And if I were a student in a live demo or a live instance rather than a demo instance, I wouldn't necessarily care where this information was coming from. All I would care about was knowing that it has been associated with me, and then I'm seeing everything that I need to see. I'm not seeing my friends' information. I'm just, seeing my own information up, and I see that some people are curious about chatbot. We can absolutely get into chatbot here momentarily. Chatbot's gonna follow the same rules of knowing who I am as a user that the widgets will. So I'm gonna see that my information is pulled over from the LMS. What's actually happened behind the scenes is that Pathify Middleware has been able to identify what is happening, with me as a user. It's gonna say, hey. Who's this person? Are they logged in? They are. Sweet. It's Julie's student. Amazing. What's her unique identifier for Canvas? Oh, it looks like it's our her alternate ID. And the middleware is gonna proceed to make API calls on behalf of me, the user, and return that information from me. That's very similar to what's actually happening with Pathify's chatbot as well. So as a student, I can come in, and I can start finding out information that I might need. Maybe I'm wanting to know what my GPA is. Pathify is built on the Gemini LLM. I can guarantee you the Gemini LLM does not know what my grade is. What's happening here is that the same middleware that actually powers my widgets, this chatbot and the LLM have determined, hey. She just asked about her GPA. That is not something the LLM covers. And at that point, the chatbot actually bumps me out without my being aware of it as a user. It bumps me out to the middleware where the middleware is able to pull data for me and then return it for me. As a student, again, I don't really care where that information is coming from as long as it's right. But what's happening is that there are integrations at play with the different systems that are operating on your campus that are gonna bring that information to the users at the right time. As a student, if I cared about where my information was coming from and not just where whether it was right, what I might notice is this little certificate, icon that we're seeing over here. This is gonna show that this is a verified source. This means that behind the scenes, someone on the IT team actually set up an integration out of the box, that's associated with, Pathfind, its middleware, and also customer instances to guarantee that this would be, an answer that's correct. Some other things I might be able to pull through this would be let's say I need to talk to my advisers. Maybe it's gonna bring back some live information about my advisers for me. Maybe it's gonna bring back my course schedule, my balances, my holds, and restrictions. It's capable of doing all of that. If you ever wanna do some DIY integrations, we also have the capability to allow customers into our middleware if they've purchased a Flow license as well as the chatbot, and they'd be actually able to build their own integrations from scratch with your source systems. As a student, though, it might not be, information purely from a database that I'm looking for related to grades and advisers. Maybe I'm looking for tutoring. Maybe a 3.8 isn't quite high enough for me as a GPA, and I wanna go for something above a four point. I'm gonna look up information about tutoring. And it's gonna think about it for a second. And, wow, it wrote me a small essay about where and when and what's available to me as someone who's in the computer science department. This chatbot, just like everything else in the platform, it is all role based. It's gonna be able to tell that I am a student. It's gonna be able to tell that I'm in the computer science and STEM programs, and it's gonna write me an answer. And if I were a student who was actually curious about where this information was coming from, I would actually be able to see this little, magnifying glass over here in the right hand corner, and this would tell me this is a sourced answer with information coming from the platform. That's been pulled for me based on my roles. It synthesized a nice answer for me, and I probably do something as a user very similar to what I do when I'm googling things, and I get that Gemini AI answer. I'd come in under sources, and I'd be like, that's all very cool and interesting. Let's check out pages and find out a little bit more, and then I could come in and find out. Yep. Computer science tutoring, 08:30 to six. Looks like it's available. I am going to walk on over there right now and find out some information and get some help. So on that note, that was the chatbot. I'd be happy to hop on, a call with you and your account executive to talk more about the chatbot. If you want to email me, what you could do is you could hit me up at, let me share my slides, julia pathify dot com, and we can talk a little bit more about chatbot. Thank you for being a wonderful audience. I hope that I was able to clear up some questions you might have had and given you some stuff to think about. Have an awesome rest of your day.