Name: Pathify Demo | January 2026
Uploaded: 2026-01-28T18:00:06.112Z
Duration: 22 min 32 s
Description: Pathify Demo | January 2026

Transcript for "Pathify Demo | January 2026": Hello, everybody. Welcome. Welcome. Let me give everyone another minute or so to pile in, and then I'll introduce myself and get us started. Keep on piling in. Good to have everyone on here this morning. I do know we have some some West Coast schools on here. So for those of you who are from the West Coast, good morning. I suppose from those of you who are on the East Coast, I believe we have some folks from North Carolina on here. I guess for you, it's just after lunch. Thanks for spending the time. It is much appreciated. I'll go ahead and get us started now. So my name is Julie Guberman. I'm the senior sales engineer here at Pathify. I've been here for almost six years and have seen the platform evolve from being some pages and some groups and some events and announcements to being the campus experience platform that we have now. So I'm excited to talk to you about what we do, why we do it, the problems that we solve, the ways that we can solve it, and then we'll get more into the functionality. So at this point, I will assume that we have a full house and go ahead and kick us off. So I did just go over the agenda to a certain extent, but we'll talk about it a little bit more. So we'll talk about Pathfi and the problem it solves within the software ecosystem that goes on on university and college campuses in terms of having a lot of different softwares going on and needing one one surfacing platform for everything to show up on. We'll talk about why institutions choose Pathify to be that surface layer, and then we'll get into the demo and talk a little bit more about the platform and what it looks like and why it looks like that. So to start us off, we'll talk about the ever expanding digital universe of campus software systems. So back when I will go ahead and date myself. Back when I was in college, we had maybe four systems that I needed to be aware of. I needed to be able to access the library, and the online article database and such. I needed to be able to keep tabs on my grades and register through courses through the SIS. I needed my email. And then when I was taking summer classes, I needed access to WebCT. Now things have grown and evolved far past what I needed as an undergraduate student. We have events and calendars, communications, emergency alerts, information systems, retention softwares, housing systems, so many pieces that I didn't used to need to be involved with as a student. And the question becomes, hey. Let's say you have 30 softwares as a student. How are you supposed to be able to find those? How do you even know what's due and when? It's gotten so complicated out there. And plus you add the fact that portals exist everywhere, whether you're talking about classes or chatbots or activities. You need one way to know what's going on, when the deadlines are, and where to go to complete those tasks. And enter the Pathify campus experience platform where we're able to surface to do items, events and calendars, schedules, resources, uploads, communications, student organizations. We're able to surface that all in one place so that users, whether we're talking students or staff, prospects, alumni, even now parents, we're gonna be able to help those users get in and know exactly what they need to do and where they need to go in order to complete that. But let's go ahead and talk about why Pathify. So we're gonna talk a little bit about University of the Pacific. One of the success stories that University of the Pacific experienced was very early early on after their launch. There was one date in the semester where they just knew, okay. Registration just opened up. There are about to be 700 or 800 students calling us up because they didn't know where to go at a particular time in order to pay their bills. They didn't know they were due. They just assumed that students didn't care, and they was waiting for that onslaught of calls from all their students who couldn't register for courses. Well, registration day comes in, and no phone calls happen. And so whether or not this is how it actually went down or whether this is just the mental image I've created for myself, you have a registrar with a printout report of these 70 or so students who are the only students who haven't paid their bills and thinking that Banner had gone down because there's no record of those users and everyone's fine. Well, turns out Banner was right, and there were only 70 students who didn't play their pay their holds. Rather, instead, what happened was that everybody used announcements and knew what was coming up and when to take care of it and where to go to take care of it, and they got their bills paid on time for the first time in the history of ever. Meanwhile, though, behind the scenes, University of the Pacific also had another victory with the implementation of Pathify. Rather than having 29 different free floating systems and no way to unify those, they were able to consolidate those into five. To do this, the budget went down by 45 they only used 45% of their budget. Usually, it had been filled to the max. And furthermore, instead of having a Linkfarm student portal, a basic mobile app, and then a separate student group and activities platform, they were able to consolidate that down into one. So not only did users know where to go, but they didn't have to go to as many places in order to take care of business. We also have another success story from Alabama A and M regarding systems consolidated into Pathify. They used to have a separate chatbot. Employee Internet was separated from the student legacy portal. Furthermore, you had a campus mobile app as well as a student portal, which meant that users needed to go to two separate locations to do the same thing. And then if you're an employee and also a student, that all of a sudden means you're hitting up three different systems. They were able to consolidate that all down into Pathify, which saved them around $25,000 a year and reduced their budget by 18%. So I'll admit it. I'm a little bit biased about our software solution, but let's not just talk about what it does. Let's actually take a look and see that hole in the software universe that Pathfi actually fills. I'm gonna go ahead and share my screen, And here we go. So your Pathify platform would not have to look like this. In fact, everyone's looks a little bit different. You have full control over the branding. Everything would be white labeled for your institution. You're gonna have a mobile app as well as a browser app. And furthermore, you have control over the layout with our dashboard creator. But let's just say we're in Julie's student as Julie's student, and we're going into the platform to see what all we have going on today. So I might have an announcement. Hey. Snow day can't classes are canceled. Let's take a look at that. Check-in the LMS for any messages from my instructors. I can totally do that. I can come on down into my quick click capsules and get quick access to maybe information that I need related to student success. We're gonna talk about maybe I have tutoring needs. I know that I'm doing well in my courses, but that I could be understanding things a little bit more deeply. I might be linking over into Pathify resources to take care of that. Maybe I'm finding information about classes, or maybe I'm reporting the fact that my bike got stolen because I left it unlocked outside my dorm. As I come on down, I'm seeing information pulled live for me from various sites, whether we're talking about job opportunities being posted through Handshake or my personal, school email that's being displayed for me off in the productivity suite widget. I'm also able to come down into my courses and well, I know it's a snow day. I might come under my assignments and think, well, this is a really sweet opportunity for me to catch up on some of my classes because I don't have to deal with, walking the class or sitting through a lecture. As I scroll on down, I'm also gonna see information about my upcoming events. Maybe these upcoming events are classes that I'm enrolled in. Maybe I'm looking at special interest things such as an artist luncheon conversation. I can find out information about my groups. In fact, I might even wanna take out a look at Beach Bites, which would be where all the free food is located on campus. And yes, we do have institutions that actually have that group in place. And then I'm seeing suggested groups for me based on the roles that I hold within the campus itself and also based on my connections who might be involved in similar groups. As I come on through the platform, I'm able to see things such as my to do items that are coming over from different systems or possibly created within Pathfi themselves. So for example, maybe I'm seeing that I need to review potential careers in computer science. Already took care of that. That's awesome. Finances for next year. I can schedule an appointment with my financial adviser, or I can just notice, hey. I'm done with that. And I can start to see a little gamification going on the left hand side as I'm completing those. Some other pieces that I can see that are pretty awesome are related to events that are happening on campus. All I know is that I'm seeing the calendars I'm subscribed to that have been made available to me based on my roles, and I can also go in and find other ones. So, for example, I'm looking at the library. I wanna go ahead and unsubscribe to that, but I do want to subscribe to Discog Club because I know I need to get out more. I can control my user experience like that. A question, though, that I get a lot of times as a sales engineer on calls is where exactly are these events coming from? Are they created in Pathfind, or do they come over from third party systems? The answer to that is actually yes. So if I'm a permissioned user, I'm going to be able to create events within the Pathify ecosystem. I'm going to be able to subscribe them to different calendars and make them visible to different roles. So maybe I'm in a situation where there's no central calendar right now for staff schedule for the year. I could go in and create a staff scheduled calendar as a permissioned user and start populating events that staff would be able to see, but Julie's student would not be able to see because she's not a staff member. She doesn't need to clutter up her user interface with that. That said, a lot of times there might be a system that is going on in terms of how structuring your events and scheduling events and dealing with room reservations and stuff. Maybe it's Accruent EMS. Maybe it's 25 Live. We see a lot of those. Maybe you're also in a situation where you're using a couple of central calendaring systems, but maybe you have different departments and colleges on campus that are using systems that you don't even know what they're using. Well, we're able to solve that one too. Permission user is also able to go into Pathify and hook up iCals and RSS feeds and unauthenticated JSON feeds to the events and calendars module to be able to bring in those events. So maybe the English department has a Google Calendar, and maybe the biology department is using 25 lives still. No worries. You'd be able to incorporate both of those feeds, permissioned users would be able to see them right over here. Some other pieces going on within the Pathify ecosystem that we're pretty proud of would be resources where permissioned users are able to upload documents and store links so that users who have the appropriate roles would be able to come in and view them. So as a student, I might be able to come in and find information about first year students and computer science requirements. Maybe I'm finding some student policies in residential life. Maybe Colleen's staff, though, is coming in, and she's seeing information like the staff handbook, guidelines for hiring employees, various policies, various procedures. So, again, you're really able to customize what that user is going to be seeing based on their roles. And let's say Julie's student is in love with Pathfi University, and she's a Pathfi University person for life. When she graduates, she'd start seeing not only alumni content, but if she's coming on as a staff member of the registrar's office, she's also going to be able to see staff content without the need for creating different accounts within different systems. She's gonna see it all surfaced in here. Some other pieces that Pathfi is pretty proud of would be its forms solution with the ability to create forms globally with visibility based on roles, but we're also going to be able to see forms that are coming over from groups within the communities module. And I see I'm fifteen minutes in. You've been listening to me ramble. I have some more rambling that I can do, but if you want to drop some questions into the q and a or into the chat, I will happily answer any of your UI questions, implementation questions, best practice questions. Keep it coming. Let's keep it interactive because there are a million interesting things in the world and that have to do with Pathfi that don't have to do with me rambling. That said, let's go ahead and keep on looking at this functionality in the meantime. So some other pieces we already took a look at tasks. Some other pieces that play here within Pathify would be the directory in which users are able to actually come in and find users of different roles, maybe users who have similar interests or involved in the same department or the same campus location that they are. And then last but not least, we have maps, and I don't think that my screen share bumped over to that. So maps is actually the ability to put it in places on campus. And maybe if you're one of those institutions that have multiple campuses, this will be especially applicable to you that will allow your users to find their way from building to building without having to actually leave the Pathify ecosystem. And then as we get down into further content, so we do have tools which would be links out to third party systems, but we also have something called pages. Pages would be the lightweight CMS that Pathfi has, and that's going to allow permissioned users, and they don't have to be technical, by the way, to come in and start creating content. So, again, we'll see that I'm seeing only student related content. Staff would see staff content. Maybe you have the delegates hub where you're allowing parents to log in. They'd see parent content. But as a student, I can come in, and I can check out I need. Maybe I'm looking for information on advising. I know I want to change my major, add a major. I don't know what that looks like. I don't quite know how that's going to impact the fact that I'm already several credit hours in in my first year, and I don't wanna totally mess things up and have to go for three additional years because I postponed changing my major. Well, I can find out information about my advisers and come in and actually start scheduling some time. And one last piece that I'd like to show you before the end of the demo would be communities. Communities are otherwise known as groups. Sometimes these groups might be actual student organizations, so maybe I'm coming in to student clubs, and I'm taking a look at the video game development club. And in here, I'm going to be able to access pages specific to this club. Maybe I'm seeing some announcements like this announcement about bug bash. Maybe I'm participating in a group discussion, and I'm gonna mention hey. Anyone good at front front end animation development? I'm gonna post that, and it's gonna show up. And I can have other users go in and actually comment on what I'm up to. I can see events that are coming up, FAQs. Again, resources, which would be those uploads as well as pages, tools, and maybe I'm even seeing tasks and forms. That said, I might also see information that's related to a department. So if you're looking at using Pathify as a way to bring in an Internet, not only with pages, but also with groups, you could easily get a lot of mileage. So for example, maybe you have a library group, and you'd allow users not only to come in to discuss and to find information about the library, maybe hours, maybe people who are in charge, events related to that group. I'm also, as a user, going to be able to come in and find FAQs. So maybe I'm curious about checking out materials and renewing the loan on a book. I'd be able to find out information about that. I'm gonna be able to see uploads as well as things like pages. So some of the ways that we've been seeing groups be used, some of them are completely built out like this. We have one institution that's using these for different residence halls on campus in order to get all the the residents who are leading things on each floor to get them all involved in a group together so that they can talk about what they're experiencing within that dorm. Right now, we're seeing the groups all built out with dashboards and the nines, but we have another institution that's gotten a lot of mileage out of only having the discussion board turned on. So we've seen this both with an online institution that has a group for students who are parents. We've also seen this for one of our business schools that has discussion boards for just hobbies and common interest groups like makerspaces, and they'll just have discussion boards turned on so that people can share what they're experiencing and what they're interested in, whether we're talking again about students who are parents or whether we're just talking about a group of makerspace folks who want to share what they've made over the weekend. So you can get a lot of mileage out of that. And that brings us to about the end of the platform. I am not seeing anything in chat. I figure there are probably a bunch of people who are out there eating lunch while they're listening in to this one. So I'm gonna go ahead and wrap this one up. So thank you so much for joining me today. Again, I know you're really busy. It's still fairly early on in the semester, and you're still fielding issues that students are having, maybe issues your tech teams are having. So thanks for hopping on. If you have any questions for me, I know that for me, usually, I'm sitting around thinking, yeah. Yeah. Yeah. Okay. Okay. Okay. And it's not until after I get home and I'm walking my dog or I'm doing dishes that I remember all the questions that I wish I had asked. If that happens to be you, go ahead and reach out to me. Again, my name is Julie. My email address is julie@pathify.com. I would love to answer any questions you have or get on a call where we can walk through some functionality in more depth. So thank you again, and I will head out if there are no further questions.