Name: Pathify Demo | March 2026
Uploaded: 2026-03-17T17:01:22.356Z
Duration: 25 min 12 s
Description: Pathify Demo | March 2026

Transcript for "Pathify Demo | March 2026": Hello, hello. I believe I am live now. Welcome, everybody. Another day, another webinar. I'll give everyone a couple minutes to hop on. Happy Saint Patrick's Day to those who enjoy that. And while we're waiting, if you have anything that you're particularly interested in talking about or anything that you're wondering, feel free to drop into the chat or the Q and A if you have anything in particular. And I'll get it for everyone another minute. Welcome to anyone who's piling in. We'll get started in about thirty seconds here. Again, feel free to drop any questions in the q and a or any topics you're interested in in the chat. Ah, perfect. Integrations with Banner, we can absolutely talk about that. Okay. And let's go ahead and get started. My name is Julie Gummerman. I'm the senior sales engineer here at Pathify. And today, we're going to be talking about the platform. We'll talk about what we do in general. I'll do a demo, and then we'll do some more q and a. Again, feel free to drop things in the chat. I know we already have a question about Banner that we'll definitely cover here in a bit. So right now, our student at any higher ed institution is navigating an ever expanding digital ecosystem. Back when I started at the university, so I'm gonna date myself, that was 2001 to 2005, I had to keep track of a library system, the SIS, which I didn't know was an SIS at the time, but registering for classes, checking grades. If I was taking summer classes, I'd have to use WebCT, and then I had my email. Things have gotten so much more complicated in the last twenty to twenty five years. Now it's not just those systems. It's registering for housing. It's finding financial aid. It's accessing the forms that you need because you're not just going to offices to pick them up like we did back in the day. You're having to find out ways to communicate with people. You have email to check on, events that are living in all sorts of different systems. It's really a challenge for students to keep track of that. So enter Pathify, the campus experience platform, and that is going to be a unifying solution to make sure that all of those disparate systems are able to come into one system so people know what's going on on campus, what the latest news is. They're able to keep track of their peers. They're able to keep track of their classes and their upcoming assignments without having to navigate between 37 different systems. So we do have some tech consolidation benefits that go into that. So, for example, some people are finding that they're moving off of one Linkfarm portal and one mobile app and moving that all into one instance of Pathify. Some people have been able to consolidate student Internet with staff Internet. Some people are, dropping some of their other events functionality systems, in order to bring those into Pathfi as well. So you're really able to not just consolidate things for your users, but presumably cut down on, what your expenditure is on software as well. We've had schools that have cut, some 20% to 50% off of their budgets for IT solutions simply by switching to Pathify. So speaking of moving from OneLakeFarm Internet into, and mobile solution, moving those into one solution with Pathify, we do have full parity between a web app and a true mobile app, making sure that any content that's created from a desktop is visible in the mobile app as soon as it gets published to go live, making sure that any communications that might happen on mobile are also viewable to a user on their desktop. It's fully responsive. It's gonna look great whether you're on a mobile view or if you're on a huge desktop monitor like the one that I'm gonna be showing here in just a bit. So one of the other bonuses of going along with Pathify is the ability to bring in roles from your source systems. And those roles are gonna make sure that not only are users accessing all of their content out of one system, but it's also gonna make sure that users are only seeing the things that are beneficial to them. A student who's not working on campus doesn't need to see employee content. But if they become an employee, that role can get assigned to them along with that student role, and then they'll be able to see content for both students and staff. Similarly, if you're a freshman, you don't need to see the same content that you would if you're getting ready to graduate. Your needs are different. The roles that you get assigned are going to make sure that the content that you see actually reflects what your needs are at any given time. And one of the other pieces that we offer along with that role based visibility is zero cost vendor agnostic integrations. What we're seeing is that you're able to have access to these no code solutions through the recipe library. No. It does not require a flow license. Anyone who has the Core Campus offering, which we're now referring to as the hub, will be able to run those recipes and get those integrations going without any technical knowledge necessary, without any money necessary. As long as you have the system that we're integrating with, we should be able to integrate with it. And we have a 150 of those, or actually a 175 at this point that are customer facing. And then meanwhile, speaking of no code, we do offer quick implementations that don't require full time devs. So rather than needing to use your developer team to get Pathfinder to go live, You bring in your system admins. They set up some service accounts, and you're off to the races. Right now, we're looking at about four weeks of technical turnover time and then another eight weeks of content training, so about twelve weeks before a go live. We work with you to make sure that you have everything in place that you need for that go live. And I see that we have another question in q and a. The tech skills required to create custom recipes, we can absolutely talk about that as well. So some of our success stories, and my coworker Colleen behind the scenes will be dropping these in chat here in just a bit. And I believe actually she already has them in the Docs tab. So we do have some success stories, some case studies that we've done with some of our customers. Everything from Grand View and how it reduced emails by 90%, making sure that the only emails that users got were the ones that were actually relevant to them. The ability to get students online successfully that Franciscan recently did. And then Alabama A and M, one of our major movers and shakers in terms of system consolidation and being able to cut down on IT budget by implementing Pathify. But let's not just, take my word for it. Let's go ahead and take a look. And, Khalid, I know you had some questions. We'll get into those as well. So let me go ahead and share my screen, and we're gonna take a look at this from the point of view of a student. So right now, you should be seeing my screen, and we're taking a look at what a dashboard might look like for a student user. Of course, it doesn't have to look like this. It'll be branded for your institution. You'll be able to use your university branding hex codes in order to make it look like you want. You'll be able to change around, the logo that you're seeing. You'll even be able to name your app so students aren't looking for a Pathfi app. They're looking for my university app, whatever your university or community college, name happens to be. And I'm gonna be able to come down here, and I'm gonna be able to find out more information about my classes, pulling for the l from the LMS. Any tasks, if you're using the tasks module might be pinned here. I'm also going to go in and see any content being surfaced for me from widgets. So I know that I had a question in the, in the chat about what our Banner integrations might be. So we'll integrate with Banner in order to provision users. You're also going to integrate with Banner to pull information like academic profile, possibly your advisers, any holds and restrictions. We also do have a balances widget that connects with Banner as well. If you're a Banner school, a lot of our customers are we have multiple ways to be able to integrate with Banner for your users, that will include Ethos, Ellucian Cloud. Oh, did I hear that right that I'm on mute? Are folks hearing me okay? Okay. Alright. Just wanted to check and make sure. So, getting back into that banner piece. So we can connect via Ellucian Cloud. We can go ahead and connect with Ethos. We can do universal API connectors in case you have an iPass system or a MuleSoft, Boomi, Informatica, end to end, any of those, we'd be able to integrate with that. And then last but not least, if you none of those work for you or you're going for the quick and easy route rather than the instant route, I would recommend flat file. So lots of different ways that we can connect with Banner. For the students, it's all going to look about the same to them. No matter what LMS or SIS you're using, they'll just know that, hey. I see my GPA. I see my majors and my minors and my advisers, and everything's going well. Behind the scenes, you'll know that whatever method you're using to connect to whichever SIS, that student's gonna find the information that they need for them. So some other pieces that I know that people were interested in. And, again, I know Khalid also had some questions about building your own widgets. We'll go ahead and talk about that one here in a bit, toward the end. Right now, I want to go into tasks. So tasks are going to be an add on module, and those will enable a user to see any to do items that they have. So where do those to do items come from? They can come from five different places. Of course, there's the basic I can add a task for myself and, give myself a little reminder. They can come from a source system behind the scenes, such as Banner. They can also come over from the administrative interface behind the scenes at Pathify where you can give permissioned users permissions to send out tasks to users based on their role or based on their individual identity. You can even do sequential tasks in there. Right now, I don't have any set up for this particular user, but that's one of your options. And then one additional option that you have would be if you're turning on communities, which we're going to talk about after this, these tasks can bubble up to this module from communities as well. Each community or student organization can send out their own task if that's enabled. So questions, comments, or concerns before I move on to the next thing? Alright. We're gonna go ahead and do a skim through of communities before we hit up the AI agent. So communities are going to be your student groups. They're going to be that interface where users are connecting with each other if I can actually type today, which apparently I cannot. Alright. And here we go. This is going to be the UI that a user would see if they access communities. Sometimes you might enter a community that has all of this content turned on, the announcements, the FAQs, maybe some forms, maybe though you also have communities that are only running with dashboard and events. We've actually seen communities that have high adoption rates that are nothing but a discussion board and some basic group information. One way or another though, your users are gonna be able to come in here and interact with each other. Don't think of this as being only for clubs and orgs, though. There's some incredible functionality in here that would really benefit staff as an Internet, maybe allowing the IT team or the English department to all come in and interface with each other. Or maybe there's an HR group that's going to allow your staff to all come in and find different forms related to taxes and benefits and asking questions. So lots and lots of options in here. One of the really cool pieces in here is chats, and I'm just gonna I'm gonna impersonate this user so we can see that chat functionality. So this is what group chats will look like. They're going to allow your users to come in, and if they're permission, they can actually come in and create a chat and give it a description and choose which individuals are gonna be involved in that chat. So maybe I am wanting only group admins in this. I can go ahead and set this up so this is a chat only for group admins, and they would then be able to access this not only from this group, but they're also gonna be able to see it from their chat emoji, and they're gonna be able to participate in here just like they would on WhatsApp. So some pretty cool stuff. One last piece, though, that I wanna go over is the AI agent. Let me just scoot on back to my dashboard here. Okay. So this I AI agent is going to be able to answer students' questions. So, of course, you have a ton of systems. You have a ton of content, and you know that one of the most urgent needs for you as a higher ed institution is to make sure that you get students answers quickly. And at times where it might not be regular business hours, a lot of our students happen to be night owls. Or if you happen to be me, I've always been an early morning person. I'm always up and running before nine, and that means that I'm going to wanna get my information at seven in the morning before offices have opened up. And with the use of this AI agent, I'll be able to do that. What it's going to do is you don't actually have to train it. It's going to be able to search the content within Pathify, and it's gonna be able to synthesize answers that are role based just like what you'd find, in any of the other aspect of the platform. So if I come over here and I ask it, maybe I wanna know my grades. And it's gonna think about it for a second. It's gonna bring up those grades. Again, this is another way that we'd be connecting for our Banner users out there, connecting with Banner. Or maybe I'm asking about who are my advisers. At this point, I'm actually leaving Gemini LLM in order to go out to Pathify's proprietary middleware flow, send out API calls, bring these back. So the AI agent, the Gemini LLM, never touches user data. This information about what's being brought back right in here, not even stored within Pathify's data records. So your user's data is, staying safe, and our test user, Julie Student, here is able to find what she needs. So let's say she's looking for something that's not completely specific to her. Let's say she's looking for something a little more broad. Let's say she is knowing that maybe the grades came back and they weren't quite what she had wanted. She's gonna come down in here, and maybe she's gonna say, how do I get a tutor? And so it looks like this is one of those points where okay. So she's asking for a tutor. She can't quite find that information. She'd probably give this a thumbs down. And at that point, your, people behind the scenes who are administrating the chatbot or the AI agent rather are going to be able to go in and say, oh, we don't have any tutoring information in here. We're gonna go ahead and put some pages and some FAQs into the platform, and then the AI agent is going to be able to go in and actually find out more information. One of the other cool guardrails that this AI agent has is the ability to, go ahead and segment off, like, hey. You're not gonna be able to ask me to write a paper about anything because of the fact that I'm an AI agent. I'm not your personal tutor. This isn't what we do. So it is going to prevent things like cheating. And then there are some pieces that are in beta testing surrounding sending notifications out if a student's talking about self harm or the harm of others. So questions, comments, or concerns before we talk more about integrations? Alright. Looks like we're good. So, again, with the AI agent and also with the widgets, we're seeing the pulling of data from your source systems. Again, that's one of the things that really differentiates Pathify as being system agnostic. At this point, we can boast that no matter what your, SIS is, even if it's homegrown, we'll be able to integrate, and we'll have some easy pieces set up. Again, those pieces that are ready to go from the SIS, those are gonna be your academic profile widget, your balances widget, holds and restrictions, advisers, pieces like that. So those are out of the box integrations. That said, the rule of thumb here at Pathify is that if you can move information out of that source system into a neutral third party space, granted an authentic third party space like Pathfinder's middleware, we can integrate. Whether that looks like an API call, custom API wrapper, maybe we're talking flat file RSS feed, but we will be able to, pull information through that source system. We're also able to go bidirectional. In fact, at this point, we've even seen some custom pieces where data comes into a widget and then gets sent over to another third party source system without ever actually living in Pathify itself. So, really, the sky is the limit. As long as you can move that data, you can do an integration. So recipes, as we know, are out of the box. That said, back when I started at Pathify some six years ago, we didn't have recipes yet. We had maybe seven or eight customers, and there were junior devs like myself who were building all of those integrations out. At this point, we've done those integrations so many times that at this point, we could put a recipe library over top and make it a form based solution where you just type in your information. It fires off the code base. That said, if you wanna go with the flow license, we are able to teach you how to build your own integrations much in the way that I learned six years ago. And so if you're interested in doing that, there are a couple of skill sets that you might be interested in having. If you have built integrations in any system whatsoever, and if you have a technical background, you will be able to build integrations and flow. In fact, we've had customers who don't have JavaScript developers on staff, but they have a ton of experience doing integrations in other systems with Python. Those folks did fine. We did five or six hours of training, and they were off to the races right away because the principles that make an integration work in Pathify are so similar to the principles that would make an integration work in any other system. Obviously, being comfortable with coding, very important, but the syntax is less important than understanding those concepts that make that fly. That said, the language that you'd use to script your own integrations within Pathify, For front end, we're talking you can use jQuery. We've also had schools use Angular and React for more complicated widgets. Those widgets get hosted on our flow server, and you're good to go. So having some sort of front end framework that you're comfortable working in, a great idea. Those scriptings for the actual integrations themselves happen through JavaScript, but it's JavaScript that's very flow specific. And so there's some little quirks and nuances. So understanding JavaScript is usually pretty good, but it's not as important as understanding how an integration works. But one of the other added bonuses of having a Flow license and doing that is that not only are you able to build your own integrations from scratch, but you're also able to go in to recipes that have already been run, and you you're able to adapt and adopt that code to do what you want it to do. So on that note, we've talked about a number of things so far. We've talked about communities and using communities for student organizations as well as for for Internet. We've talked about consolidating systems. We talked a little bit about the mobile experience as well as the browser experience and that full parity in between. We've talked tasks. We've talked AI agent. We've also talked integrations and flow license. So on that note, if you have any questions, comments, or concerns, curiosities, feel free to drop them off in the chat or in Q and A. Alright. Well, thank you so much, everybody. Thank you for being a wonderful audience. If you are in, emailing me, I'm gonna drop my email into the chat. It's Julie@Pathfi.com. And feel free to hit me up. Hope to see everyone around. Thank you so much.