Video: Pathify Demo | April 2026 | Duration: 1708s | Summary: Pathify Demo | April 2026 | Chapters: Welcome and Introduction (6.08s), Pathify Platform Overview (127.29s), Platform Demo Walkthrough (810.48s), Q&A and Closing (1635.95s)
Transcript for "Pathify Demo | April 2026":
Hello, everybody. Thanks for coming to our webinar today. I'll give everyone another minute or two to pile on. It is 11AM here in the mountain time zone, and it is a beautiful day. I was actually able to get up between meetings earlier and pick a couple of weeds in my front yard. Weeding season has begun, it appears, in earnest here in Colorado, and I hear that allergy season in, back east is going full throttle as well. But, hey. That means it's green, and it means everything's in bloom. So I'll take it. I'll go ahead and give everyone another minute or so. I see my accomplice in crime behind the scenes. Colleen is mentioning, yep, constant sneezing in Philly. We finally started to have the lilacs be in bloom here in Colorado, so I know any day now it's gonna start out here too. So now that everyone's on, let's not talk about the weather. Let's talk about Pathify. So a lot of you've met me before. My name is Julie Gummerman. I'm the senior sales engineer here at Pathify. I've been working here for the better part of six years now. Started here first as a developer and doing implementations on the technical side of things, but I've been over on the sales department for about four and a half, five years now and love talking to people about the product and how it works and possibly getting into some of those deeper integration questions as well. So let's go ahead and start talking about Pathify then. We're gonna start off talking about what we do, the problems we solve, where we fit in, the ecosystem of the software systems that a higher ed institution will have on campus, what how we fix problems related to that, a little bit more about how we support students and staff in that journey. We'll do an actual demo of some of our offerings, and then we'll do some q and a. I will be keeping an eye on both the chat and QA or, and the question and answer section as we go, so feel free to drop any questions in there. Even if I don't see that, my, my friend behind the scenes, Colleen, will be noticing, and we'll get you some answers. So as we dive in, we are starting to see, a veritable explosion in the number of systems that students and staff members have to keep track of in order to successfully go through life on campus. We're seeing for students, we have everything from those event management systems to form systems. We have the student information system and the LMS. We have event calendars. We have email. We have files. We have housing systems, deadlines that are coming up, people who don't know where to go because they don't know even that there are balances that are they have due and restrictions they have until they go to register for courses. In short, everything is a little bit every of everywhere. We have a lot of these, systems that do amazing things. They're very good at what they do, but there's really not a consolidated place to find all of those. Meanwhile, we also end up in a situation where users are very used to having these very customized experiences when they're going on to Spotify, and they see all of their music and the genres related to them them showing up. They're shopping on Amazon. And whenever you go on Amazon, you're seeing everything you need and possibly a few things that you don't that you've looked at in the background. And then all of a sudden, students are and staff members are getting to that higher ed ecosystem, and they're realizing, wow. Everything looks very much like it did twenty years ago. That UI and UX piece just hasn't kept up in the way that it might in other spheres of life. So this is where Pathify and the campus experience platform come into play. You're taking all of those systems, some maybe 15 if we're lucky and way up into the thirties if we're not quite so lucky, but we have a very industrious campus. We're taking all of those pieces and leaving them nicely and neatly sorted And the widgets, the notifications, we're accessing that data. From an AI agent, we're finding resources with files. We're able to organize our tasks. All of a sudden, we've gone from all of these disparate systems to a system that not only looks modern, but everything is organized so I can find it. So I might still need to access those third party systems that are a little all over the place, but all of a sudden, everything has gotten a lot more streamlined for me because I'm, for one, not having to branch out to other systems to find things like document uploads and links, and I'm not needing to go into other systems to find events or to do wayfinding. It's all in one spot organized with these nice, neat, organized jumping off places. So regarding it's not just better for that student. It's not just better for that staff member. Also, it tends to benefit teams that are implementing as well. So in the meantime, as you are centralizing that content, you're realizing you're fielding fewer questions from people trying to find where on earth everything is and when it's due and things that are broken, all of a sudden, hey. Everything is in one system. It's just a matter of using that system to branch out when you need to. Meanwhile, we were finding stories and more stories from our customers about cost savings through being able to eliminate third party systems. So, for example, one of the newer pieces of Pathify functionality is maps and being able to help students through wayfinding. All of a sudden, you're realizing, oh, wow. People aren't having to branch out to these other systems. You're all of a sudden not needing to use third party form solutions because you're using Pathify. Again, things are a lot easier. There's also a reduced security risk simply because everything's living in one place, and that place is very secure. Another added bonus of the Pathify ecosystem and its campus experience platform would be the full parity between web and mobile. Even as a verified old person in the world of tech, most of my life happens on my cell phone. For students, it's also no different. For a lot of staff members, it's no different. You're accessing the world at your fingertips with your cell phone as you're navigating from place to place, even just walking around, sitting in line, waiting for coffee, you're drinking your morning coffee, you're checking your phone. So Pathify is there for you for you to figure out what's going on on campus, what due dates are and deadlines are coming up if you have holds and restrictions. You're able to check if you're a staff member on what your leave balances are as you're thinking about taking that nice new vacation you've been thinking about taking for years. Everything is right there. Meanwhile, though, it has full parity to a browser app. Much as I am a mobile app person and I have way too many mobile apps on my phone. And, yes, I love them all. Meanwhile, I'm not wanting to create content in Pathify from my phone. That sounds a little cumbersome. You have a browser app so that on my nice, neat, full screen, I can go ahead and I can be creating events and pages and building integrations without having to do it from my phone. But I know that as soon as those go live for me on my browser app, they're automatically live on the mobile app. There's no lag time. There's no extra deployment. One of the other things that's gonna modernize your user experience is the ability to cater the content of that browser and mobile app to your users' needs. So we know that there are a lot of other solutions that allow you to flip back and forth between staff and faculty and student experiences, but Pathify is able to surface everything based on your roles all in one fell swoop so you're not really having to change out between personas. So at the bare minimum, what is a role in Pathify? Okay. Well, it might be a student or a staff member or faculty member or a platform administrator, But there are so many other roles that one could bring in. What's your major? Are you an at risk student, a first gen student? Are you an honors student? Are you an athlete as well? Are you an employee as well as a student? Are you a first year student? Are you a graduate student who's building classes? We're able to import all of those roles from third party systems and then every piece of content that a user experiences within the campus experience platform, the file uploads, the communities that one can participate in, the widgets that appear on a dashboard, the announcements you're receiving, the task notifications you're receiving. All of that is contingent based on roles. So in terms of what this might look like for you, we have some schools that skate by very nicely on four or five different, roles, but the larger an institution, the more we are seeing the need for those role designations. What campus are you a part of? Again, what sort of student are you? Where are you in that student journey? Are you an alumni? All of those roles are pieces that would come over from the SIS. They make your experience a lot nicer as a user of Pathify. Meanwhile, from the IT team's perspective, you set that up, through scripting or through just in time SAML two point o provisioning or an event listener, and you don't have to touch it again. Things run itself. Even if you decide, hey. It'd be really nice to have this one extra role in here. As soon as that's configured within the SIS or within Active Directory, there's nothing you need to do on the Pathify side. That role is automatically gonna be created and users automatically provision then deprovision. So it is a pretty sweet setup, and I see no questions in a in the chat, no questions in q and a. Sounds like I must be doing a great job, and you are absolutely awestruck with the marvels of what we offer. But we're not quite done with that yet. So we're talking about also in the midst of Pathify's value add, zero cost vendor agnostic integrations. So rather than having to involve your developer team who probably has a lot on their plate already, if you're not interested in building integrations from scratch, and we do have that option too, we have those integrations that sit on top of a form, the form sits on top of a code base, You fill out the form. You hit install, and that is enough to get those integrations up and running for you. Again, if you wanted to actually, bring in a developer team to build, DIY integrations, Love that part of the house. We have a number of customers who do that too. But if that's not what you're looking for and you're looking for some quick wins with integrations that are really gonna hit home and help your students and your staff members, what we call our recipe library, those out of the box integrations will be wonderful for you. Speaking of which, we do offer a twelve week implementation that does not require full time devs, A system admin and some nontechnical content creators are all that you need in order to get things rolling. But rather than just taking my word from for it, we'd like to link you over to some case studies that talk about our success, whether we're talking about Grandview that reduced emails by 90% with Pathify, ensuring that the emails that users do get are ones for information that they actually need for the things that they need to see. For Franciscan University of Steubenville, they were able to, build student awareness by 80% with Pathify, making sure everyone had a lot more of an idea of what was going on on campus and what they needed to know at a given time. And then last but not least, we have Alabama A and M University, and they were able to, do some incredible budget savings with Pathify. I wanna say that they saved 50% of their budget, and they had some five disparate systems like a staff intranet, a student portal, a student mobile app, a different chatbot solution, and they were able to consolidate those all into the Pathify CXP. And so I definitely suggest that you do check out those customer success stories. But without further ado, I would also like to go ahead and start demoing what things actually look like from a user perspective. So without further ado, let's go ahead and talk about it. Right now, you should be seeing, my dashboard of Pathify with the Pathify branding. Don't worry about the branding. Everything is white labeled to your institution. So, say, when users are going to the URL for this, it's actually going to be, going through a custom URL, custom domain name that you've chosen. And then meanwhile, same thing with the mobile app. Users are going to be looking for an app like my campus name, campus name three sixty, something like that, something that has been chosen by you to express your branding for your campus. And as I'm a student, I go through and I start navigating the platform. I'm seeing any announcements that are pertinent to my roles, and, yes, they are able to be targeted to users based on their role. I am seeing quick link capsules with time sensitive relevant links, related to what I'm doing. I might see a couple of widgets pinned for me pulling from the LMS and pulling from Pathify's homegrown tasks module. And I'm also seeing we mentioned those disparate systems, those systems living all over the place. I'm seeing those integrations with those systems surfacing data live for me, but also linking me over through an SSO, enabled link to make sure that I'm able to nicely and smoothly transition into those third party systems to take care of business. But it goes well and beyond these widgets at this point in time. As a user, what I'm going to be able to do is I'm also going to be able to navigate my way through the platform and, hopefully, maybe take some third party systems out of it. We mentioned that piece about those document uploads. Under resources, I can find all of those PDFs and spreadsheets and docs and links to third party systems organized neatly for me based off of role. So, for example, if I un impersonate this user right now, all of a sudden, you're gonna see this glorious hodgepodge that I, as in May a person who maintains this platform instance would need to see, so I know it's there. My test user, Julie Student, doesn't need that. She just needs to see the information related to her student role and her on campus, residential status. She doesn't and maybe stuff for her major. She doesn't need to see things related to HR. She's not an employee. But if she does become an employee, she'll all of a sudden be able to see that here too. She's also going to be able to come in and access forms. Forms can come from a couple of different places. They might be, bubbling up for communities. If you decide to buy the communities, platform content, in which you're actually bringing in clubs and orgs and you're bringing in staff Internet functionality, those would be displaying here. I'm also, as a user, gonna be able to come in and access anything that's been assigned to me based on, the roles that I have. So, for example, community concern. Let's say I wanna do some campus reporting. Let's say, also, it looks like the student user might be a little bit of, a a little bit of a tattletale, but that's okay. She's gonna be able to come in and report that, yes, she is aware of who exactly it was who, did graffiti on the inside of the dorm. Granted, it was beautiful street art, but we won't talk about that here. She's able to go ahead and submit it. Behind the scenes, somebody for this form category is able to actually go in and get notifications that somebody has been submitting forms. So it's a wonderful way to take care of everything from on campus student elections to doing things like silent witness and reporting down to, things like, hey. I need to do an address change. And I know chances are there's somebody in the audience out there who's like, well, that's cool. Thanks. Love that story. What does this mean in terms of integrating these with third party systems? Well, each form that is created within the system has an API endpoint that's connected to it. If you want to export that data to a third party system like the SIS, Fire Away, that's what it's there for. I also mentioned the piece about maps. Again, this is one of the newer pieces of Pathify functionality. It is a wayfinding solution build built upon the Google Maps API that allows users as they go in, they're going to be able to come in and actually take a look at, say, University of Denver. They're gonna be coming in and navigating. So let's say I wanna find Daniels College of Business. I'd be able if I'm a user on my cell phone, I can come in and bring up walking directions from another building, like perhaps, Butcher Auditoriums. And I'm gonna go to navigate, and it's actually going to help me wayfind. I'm not seeing the wayfind right here because of the fact that I'm on a desktop. But, again, as a student, I'm able to bring this up on my mobile app, and it's actually gonna show the dot. So instead of having to go out to Apple Maps or Google Maps, I'm all of a sudden wayfinding in the platform eliminating the need to bump around between systems. Some other things that I'm gonna be accessing over here would be things like pages. So as a student, I am able to come in and possibly take a look at information like student employment. All of the things like pages are actually going to be, again, geared to me based off of my roles. So, for example, with that student piece, as I look at all pages, I'm not seeing anything related to staff, although I am seeing some extra hodgepodge because this is a demo instance. I'm only gonna see things related to the roles that I have and the content that I need. Same sort of thing with maps. So as I go over here, I'm realizing, wow. I, as a person, need to go in and clean up my maps functionality because I'm seeing a little bit of everything. A user is not gonna see need to see things in this much detail. They just need things related to the campuses to which they're connected. This would be a much more minimal view. So some other pieces that I would love to talk about right now would be some of the newer pieces of Pathify functionality Available in prod hours of this Monday, we do have cocurricular transcripts available. So as a student, I'm actually able to go in and track things that I've been up to on campus. I've always been a nerd. I was a very good student, but, also, I had a lot of things going on outside of the classroom. I was always involved in some sort of student org, whether it was, broomball or some of the any other number of activities available on campus. Also, fun fact about me, I ran for city council while I was, a junior in college and did not win, but those were things that I wanted to trace. And it would have been really nice when I was applying for my first jobs to be able to be like, yes. I was a student leader. These are all the things that I did. I ran for city council. Here's the evidence of my leadership. Students are now able to do that. So a student is able to go in. They're able to earn badges that people have configured for them behind the scenes. They're able to submit activities such as, hey. I ran for student council. I was on the front page of the daily Kent Stater. That is actually a true story. And I would be able to actually submit pictures of my Julie Gummerman for Ward four city council and the, newspaper articles about me. And I'd be able to actually get credit for, say, leadership or public service based off of that if someone behind the this behind the scenes wanted to give me credit for that. Meanwhile, I can also choose to make all of these public. So, for example, let's say I've really been going big or going home related to leadership. I want to take my competencies that I've been working for. I want to make them available to all users, and this, unfortunately, for me behind the scenes hasn't quite yet, and this is, like, an actual Julie the content creator problem. Haven't yet turned it on, but I would be able, as a user, to make this public. So all of a sudden, I would be able to go in and actually have a link that I could share with future employers. Another piece that's brand new as of Monday is the ability for me to be able to download my co curricular transcripts as a PDF so that I can start as I'm going through that student journey. I'm looking for internship opportunities. I'm gonna start networking. I'm looking for my first job out of college. I'm gonna be able to take that PDF, and I'm gonna show off my badges, and I'm gonna show off my competencies, and I'm gonna be able to show off my verified activities surrounding community service and leadership. And being a citizen of the platform and a citizen on campus, I'm gonna be able to make that something where I can actually market myself and have something to show for not only am I a an a list student, but I've also been continually involved on campus. So really gonna push that student toward being able to be, a productive member of the professional community once I leave campus, something which as a student I'm very, very concerned about. So incredible functionality right there. Another piece of functionality that I would love to draw your attention to would be communities. Communities are a piece that was formerly known as clubs. That said, I feel like these are incredibly understated in terms of what they also offer staff and departments in terms of being able to communicate within an intranet. In a particular community, and these are also role based, they can be public, they can be private. You can either allow users to find these on their own, or you can upload a boatload of users who are actually automatically going to be added to this particular community. And then you can start configuring what that user is actually gonna see within that community. Within this particular community, for example, everything's turned up for a blast. I have a dashboard that's displaying tools and events and discussion boards and announcements. I'm also able to come in and take a look at those events. Any FAQs? I wanna find more about this group. Okay. I don't know anything about developing video games, but it sure sounds interesting. Can I participate? I can go in and find information like that that's also searchable from the navigation, bar. I can find, again, uploads, pages related to my community. I can even access group chats, and I apologize that I am being paged behind the scenes. Lesson learned. Lesson learned. You cannot, turn off disruptions on your Mac and also leave your Slack turned off different permission. Definitely something to talk about in IT intranet within a group. Do as I, say, not as I do. As I unimpersonate my user, I'm actually gonna be able to access group chats within here, wherein a community, I'm able to actually have messaging going on that's related to different topics within that community. So tons and tons and tons of functionality available to me. That said, within communities, here at Pathify, we have seen everything from communities that are turned on full blast that are used for, residence halls to allow their RAs to communicate and plan. So So we've seen everything for that use case to small social groups that are nothing but a dashboard, the a discussion board and information. So incredibly configurable. And the beauty of Pathify is that it's really able to evolve with you and with your needs on campus. Maybe you're realizing, hey. All we need is the CXP. We need some dashboards. We need some pages. We need announcements functionality and some awesome widgets, and that's that. Maybe down the road, you decide to add tasks or communities, or maybe you realize, well, things were a lot at the beginning, but now we're ready to start building our own integrations and you add a flow license. So, again, we're able to move and adapt as needed. But I have been running my mouth for the better part of twenty seven minutes, and I would love to hear if you have any questions in the next couple of minutes. So pile them on in in the chat, in the q and a. If If you have anything, I will go ahead and answer them. If you don't, that's also great, and I'll catch up with you later. But I'll give you another thirty seconds or so to ask some questions before we sign off. And as you're thinking, fun fact about me as a person, I used to be a middle school teacher. I used to do two minute wait times, but that said, in the professional world, two wait minute wait times are really just awkward. So I'll give everyone another thirty seconds or so to send any functionality questions my way or implementations. And if not, we can call it a day. And I am still not seeing anything, so we'll go ahead and call it. Thank you so much. I hope you walk away with some food for thought, and I will be catching up with you down the road. Have a wonderful day. See y'all later.