Welcome to today's webinar with FileVine and Foundation AI. We are so excited that you have decided to spend some of your precious time with us on this beautiful Wednesday. Thank you for joining us. Today, we're going to dive into a special partnership and relationship with Foundation AI, unlocking document intelligence and automating document driven work. We're excited you're with us. We're gonna dive into some really neat things that are going to propel your practice forward. My name is Eric Bermudez. I'll be your host today. I'm the Vice President of Strategic Partnerships here with FileVine. And it's my honor to now present our presenters with us today. Next slide. We have with us the co founder and CEO of Foundation AI, Vivek Rao. We also have a customer that will be speaking to us in a few moments, Mark Anajar, senior partner and attorney from Anajar and Levine. We also have with us Tiffany Lubke from FileVine, principal product solutions, and then, of course, myself, Eric Bermudez. We are glad that you're with us, and thank you for joining us. Next slide. Today's agenda. We're going through the introduction now. We're excited to dive into why FileVine has decided to partner with Foundation AI and vice versa. There are some special things that we saw, and we're excited to dive into those. Thirdly, we'll go into what is Foundation AI. Vivek has prepared an amazing demonstration for us, and we're gonna get into the details of how Foundation AI works with FileVine and your firm to advance your work. And lastly, we'll dive into a customer's experience with Tiffany and Mark Anajar. We do also have q and a reserved at the end. So if you have any questions, please throw those into the chat. If you go down at your Zoom bar, you can enter those questions. We'll be sure to answer those towards the end, or we'll answer those as we go along. So please don't hold back. We're excited for those questions. Vivek also has from Foundation AI an amazing offer that he's excited to share with you at the end, so please wait till the end. We're gonna we're gonna hold you till the end of the webinar to find out what that offer is, and he'll share those details shortly. Next slide. Today, I'm excited to dive into our strategic partnership with Foundation AI. In a world where hundreds of AI apps surface in our feeds and across our desks, we here at FileVine saw something special and incredibly unique with the team and the technology at Foundation AI. It didn't take long to realize that when coupled together with Lois, FileVine's legal operating intelligence system, the numbers, efficiencies, and results are incredible and probably ones that you have not seen before. This partnership actually started a little bit of time ago with a mutual customer voicing the significant impact that Foundation AI has made on their firm, and even beyond that, the impact that it's made on their utility of FileVine. Lois is the best in world legal AI that truly advances your ability to execute legal work with excellence. But Lois works even better when the right documents and the right data are in the right place. This is where Foundation AI comes in. Their intelligent system takes documents from any source then ensures that it lands in the right place in the right file at the right time. Having this allows Lois and your teams to operate at their highest levels of efficiencies and effectiveness. Never again do you have to wait for a team member or an outdated email rule to appropriately file or save a document. This is why FileVine strategically partners with Foundation AI. Coupled together with the best in class team, our technologies together allow FileVine customers and Lois to operate at their highest level of performance. So you might be asking yourself, how does this all work? To show us, it's my pleasure to turn turn the time over to Foundation AI CEO and founder, Vivek Rao. Vivek, I'll turn the time over to you. Yeah. Well, thank you so much, Eric Favon. Thanks for having us. Really excited to be here. And I think one of the things you said at know, when you were talking just now is really important. Not all AI is the same, and you gotta think of AI for the purpose that it was built to do the things it's meant to do. Same way you wouldn't hire a family law attorney to handle your PI case. I wouldn't use ChatGPT to build my MedCron and, because it wouldn't be able to do it in a way that's focusing on what matters for you as an attorney. And I wouldn't trust any other AI to do what we do because, frankly, there is no other AI out there that does what we do. So without further ado, what is it we do? Eric talked about it a little bit, but the short story is we are the bridge between all the ways that documents enter your law firm. That's your physical mail, that centralized email boxes, like service boxes at your law firm, like eFax boxes. That's all the individual email boxes across all the attorneys and staff at your law firm. And so the bridge between all those documents coming in and your system of action where work gets done. So that's FileVine. Whether or not that work is getting done by people, by your attorneys, your staffing paralegals, or that work is gonna be automated by Lois and FileVine's AI. So our software is gonna integrate with all the ways that documents come in. It's gonna automatically ingest those documents from all those upstream sources on the one end. And then through its integration with BioVine on the other, it's gonna use information on the documents compared against BioVine to figure out which project each each document goes to. Then it's gonna classify that document based on document type. And we've got we've trained the system on millions of documents to understand and be able to identify hundreds of different document types. And then based on that classification, it's going to name the document and save it to the name it to your naming convention, save it to the right folder and even the right section in file line. It's going to then effectuate the appropriate action, whether that is through alerting the responsible attorney or responsible staff member or triggering FileVine's automation and AI to take the next step. And so this is what we do as a company, and it's pretty much all we do. We don't do med crumbs. We don't do demands. We just focus on capturing every single document that enters your law firm and ensuring that they are all processed consistently, seamlessly, and efficiently into your systems of record. So that's that kinda manual, mundane, error prone work that people really don't wanna do and and, frankly, as far as we're concerned, shouldn't be doing anymore with the advances in technology. And so we've been doing this for little over six years. We didn't just start the company when when ChatGPT came out, and we do it for hundreds of law firms across the country, including many of the the largest law firms, and, you know, a lot of some of those prominent file buying firms across the country. And so we've been primarily focused on injury litigation. And so personal injury, workers' compensation, Social Security disability, vendors administration, and we've moved now into sort of claims litigation, property damage. And, also, in this year, we'll be expanding out into consumer bankruptcy and also working with FileVine to support all of its clients across multiple practice areas. So that's that's what we're very excited to start doing this year. So just explain to you a bit about what we do. Naturally, I think the question is, how do we get here? We've been doing this for six years, and and, you know, most tech dorks don't just wake up one day and think that they're gonna, you know, start automating mailrooms for law firms. So how we got here, my story, starts with me, I guess, started very much like a lot of yours with law school. I actually, am a lawyer by trade. I graduated law school in two thousand nine, so that's me getting my degree. Very shortly after that, I was cut from my big law job, and I had to figure out what I was gonna do. I moved back to Los Angeles and started working with a number of startups. But I needed a real job to pay the bills, and so I found that real job doing workers' compensation defense in California. So that was the first time I saw really high volume litigation. California work comp, it's one of the most document intensive legal practices imaginable. So we would receive thousands of individual documents every single day, and we had about twenty people in our mailroom and in our scanning department that were responsible for, you know, identifying what these documents were, naming, and saving them into our system. Now around two thousand fourteen, so this is a while ago, I started working with a health care AI company, and that was the first time I saw AI. Now these guys were building models that could look at fundoscopic images of eyes and detect diabetic retinopathy, look at CT scans and and detect tuberculosis. They were building natural language processing models that could derive ICD ten codes from clinical free text. So all this stuff that took, you know, really smart people, four years of medical school and residency to learn how to do. But meanwhile, in our firm, we had, you know, twenty people. And every one of these people were looking at every document that came in, you know, searching the system to figure out what matter or project it belonged to. At one point, I had four cases that were all Juan Ramirez versus Costco. The firm had six. So they're trying to figure out what matter it is, what type of document it is. Because based on the document, we would have them put it in the appropriate folder, whether it was a medical or a medical legal. They would have naming conventions based on the document. So if it's a medical record, it might be the date of service, the type of report, the doctor's name. And then we had all kinds of complex workflow. Like, if it's a, you know, a medical record, you alert the case manager. If it is a motion, you alert the handling attorney, but a discovery motion, the paralegal, all this workflow that we had people trying to keep up with. And, invariably, even when it was done right, it would take days, if not weeks, for a document to come in. And a lot of this, if you had physical mail, it got stamped before it actually got to the person that needed to, you know, look at this document or work on it. But, you know, it was done wrong all the time. Stuff would go into the wrong folder. Stuff would go into you know, stuff would be named incorrectly. They'd forget to alert people. It would go into the wrong matter. And so looking at this, you know, the idea that this is the kind of thing that oh, the other part of it is that the people doing this job didn't really wanna do it. We had a revolving door of temps and various people that would come in for this job. And when they would leave, we'd have to try to train new people to do it. And during that process, you know, the whole system would go for a toss. Things would be everywhere. And so we're reliant on these manual processes to power all this digital stuff that we've got going on, and it just seemed crazy. It seemed like this was the exact kind of thing that AI should be taking over. And so in twenty, seventeen, this much smarter, tech founders of of that health care AI company sold it off, and I convinced them to take all of that brainpower and apply it to the legal industry. And this is before legal tech was as big as it was right now, but but I got these AI guys to sit there and look at this problem and how to solve it for law firms. And so seven years later, you know, we've now solved it, and we're solving it for hundreds of law firms across the country. And so, you know, over the last seven years, things have definitely changed. Right? In the early days, the majority of the volume we dealt with was scanned physical mail. That was the biggest source. Now everything's moved digital. Most of our firms receive even more documents digitally than they do in physical mail even though depending on your state. There's still a ton of physical mail depending on your practice area and your state. And though it's always been best practice to have a centralized system, one system of record file line, one source of truth where all your documents live, now to truly leverage these systems and the advances in practice management, the AI driven capabilities that Lois can drive, you absolutely it's absolutely necessary for all these documents to be in one centralized place. And a lot of firms know this. You know? They know that it's necessary. And as a result, you know, they've built, you know, really crazy processes to deal with this. You know? Most firms are still relying on analog processes to function in this now digital world. And so, you know, we see across the board all sorts of different a so this is an example here where a crazy workflow has been set up to handle inbound documents. The truth is most law firms don't actually know when we talk to them how crazy, slow, risky, inefficient their processes are. Like, in a example like this, a law firm owner might say, well, you know, this is a typical example for a mailroom in a mid sized growing firm with, you know, few attorneys, number of staff. They might not have a full mailroom team of twenty people like the one I was talking about at at my old firm. But in a situation like this, the firm owner might say, well, my receptionist handles this, and that might be true. But in actuality, when you dive under the surface, the receptionist might be opening mail, then searching to figure out, you know, what matter it is, but then they're usually handing it off to the paralegals or the case manager legal assistants who are then spending their time to relook things up, to name the document, to put it in the right place. Oftentimes, this person's now responsible for actioning the document, understanding who on the case team needs to see the document. Do I need to send this to the attorney, or do I send this to the paralegal? All of this secondary triage. And so when you look at it, you actually have many more people in the process than just that receptionist. Or a lot of our firms also have situations where every single person on the case team gets alerted for every single document. So you're the handling attorney, and a bill comes in, and you're getting alerted that there's a bill. And you get so many alerts that you actually stop looking at anything, and you miss looking at the things that actually matter for you to see. And that happens all the time as well. So a lot of manual processes, handoffs, distractions, and really time taken from people that have better things to do. And so, you know, a larger law firm, even more crazy and complex. You've got the entire team of people in this situation. But we see often where this team of people is, you know, sorting documents and still, like, by lit or prelit or whatever, and then still handing it off to different teams to do a lot of this naming and saving. And, you know, even with all these people doing it, emails are their own crazy process where everyone in the firm is receiving them, and oftentimes, it's the Wild West. Firm owners might be able to tell you how physical mail gets where it's going, but all the emails that every single person receives across the firm, if those aren't in your system, it's like they might as well not exist. And especially if you're gonna be leveraging AI, that AI is only as good as the documents it has access to. And so when you look at this and you look at your own processes critically, think about all the wasted time and energy, not just among entry level clerical workers, but of your legal assistants, your paralegals, your case managers, your attorneys when they're bombarded by alerts for things they don't need to look at, when they're spending time searching for documents because the names are inconsistent or the way their folder is inconsistent and they're spending their time doing that, there's a lot more generally at stake with having an inefficient first mile process than just the time spent by clerical administrative staff. And so it's important to think about that as you look at your own processes. So spoken a bunch about about what we do. Now I'm gonna actually take you guys into a demo and show you a little bit about how this works. So make sure you can still see my screen, and I'm gonna take you into While you're while you're pulling that up, maybe I'll ask a question. I'm sure you look at some of these maps, and I'm sure a lot of, you know, legal professionals on the call are thinking, okay. Now that you lay it out like this, it is incredibly complex. Yeah. And so there may be a question and you you might get to this down the road, but if you look at how in the world can how difficult is it for a foundation to be set up to replace this entire slide I'm looking at now, it seems overwhelming. Or is it is it simple? And so I'm wondering if are are you gonna share thoughts on how the setup process works for Affirm? Yeah. I think let's see you can jump in. Yeah. I have to say, I think, looking at our a hundred and thirty nine names, I probably know more than half of you on this call, and I think, Vivek I mean, definitely, you can speak to this. But I think it would really be helpful for me to speak to your question, Eric. From an implementation standpoint or a setup standpoint, those of you that know me, which is most of you on this call, implementation is can be an absolute nightmare. I personally worked myself from a side and an Anajar and Levine side, for implementing Foundation AI. Number one, the team, I hope they're on this call, at Foundation AI was one of the best teams I have ever worked with, and I've probably implemented, you know, thousands of firms. And if I can back up a product, Foundation AI is definitely it. It was extremely seamless, very, very, very, responsive, individuals. We Mark's gonna share a little bit about this, and I I won't go too far into it. But but, anyway, as far as your your question, how hard is the setup? It is not difficult at all. It's somewhat time consuming on your end to know what you have from a document standpoint, but the Foundation AI experience, the implementation process, and the platform itself has been unbelievably user friendly and very, very efficient from a setup, standpoint. Does that answer your question? No. That does. I was just gonna I I can already see the wheels turning on some participants' minds thinking, well, this is hard. So how hard is the setup? Vivica, I'll talk to as well just stop talking and let Tiffany talk for me because Sorry. I'll I'll stop. I'll stop. No. No. No. That's way better than I could have said it, but but and I appreciate. And I'm sure my team appreciates everything you said, Tiffany. But Absolutely. But to but it's a great question. Right? Because implementing software is a pain, like Tiffany said. One of the things that we'll we'll talk about briefly is and, Tiffany, I'm glad you you said it. It's important to know, you know, what you want. Our software, we know FileVine users have bought FileVine and configured it to their specifications. And so we've made our software so configurable that it really meets users where they are. We don't generally ask users to do much changing of how their processes work. Rather, Foundation AI is configured to meet, the Fiveline users process as they're seven and Fiveline. I'll show you some of that. We might, recommend some best practices, and some of our firms that we deal with are really happy to see that because, you know, they haven't set their FileVine up as well as as they would've liked to because it requires people to put things in the right place. Now with with Foundation AI putting documents in and with FileVines AI's ability to extract information and fill fields out and all that, you know, you could actually have FileVine humming and operating the way you want through the use of some of these tools. So it it's pretty great. Let me let me jump in and show you all a bit of how this works, and I'll and I'll keep it pretty brief. And, obviously, we'd love to show you all a deeper demo, if you all want to. But right now, taking you quickly in, this is what our user interface might look like for what we call the work list. This is where users would do any of this validation as is necessary because it's critically important to know that no AI system is gonna be a hundred percent accurate at everything, and our system knows what it knows and knows what it doesn't know. So there are a lot of situations where it is optimizing like an Iron Man suit, a person on your team to do this job, and situations where it can actually do the process end to end, and it knows which one is which. So as an example, this is a batch for a queue for all the different documents that might come in through a mailroom. So users at Affirm might stack up documents and use one of our separator sheets, and these are the same every time. There's no creation of a separator. They just usually keep a stack next to the scanner, and they might scan things all in a batch. And they're putting these separators in just to tell the system that this envelope came in together. No sorting necessary. These are all belonging to different projects and just a number of different documents. So now that batch of documents, when I click into that in Foundation AI, what I see the system has done is first thrown all those separator sheets away, and it split out all these documents and categorize them. And so I'm gonna take a look at this event notice first, and I'm gonna jump in there. And first thing we see is what the system has done is it's mapped it to a category, and that's gonna become important because that can align with your folder structure. So these categories are yours to determine just like everything else based on folders that you either have or you'd like to have in your file line. It's matched it to the right project. And the way it does that is it's looking at the document, and it might have looked at something like this name. And let's say there's several matters that have an associated name. It knows it has to look at more than that to find to be certain it's the right document. So it's gonna look at multiple data points across your system to be able to narrow down to to just one to know that it got the right one. And in this case, when it's confident, it'll surface that automatically. When it's not confident in something or when it needs any sort of human guidance, it will actually highlight that field like this here. So here, you know, we're looking at this demo time. It looks like it got ten. Maybe it needs my help, so I'll put in an AM there. We know it's got the event date. It's confident in that. And so for this depot notice, the system has matched it to the right project. It knows what category it is. And because we've said for depot notices, we want you to pull out various information, the deponent's name, the event time, it's done all that. Also, it's applied these tags, which are gonna be important. I'll show you later when we get into FileVine with these tags are gonna trigger and be able to do various things downstream inside FileVine. It's also given it a naming convention based on what we've told it to do. So a firm can sit there and choose based on document type what kinds of naming conventions it wants. So I'm gonna go ahead and validate this document. Now here's an example of another document where, as we can see, it's highlight this matter ID for me. So I'm gonna click on that. And what's going on here is if I look at this document and the system has looked at all the information available on this document, this claim number, the state of injury, and it's narrowed down to two choices. And because all of that information's on both, it is not gonna try to break the tie itself. It's gonna give this to a person to do. And so I, as a user, might say, okay. I gotta close and open. I'll put it into the open matter. And so now that it knows that's done, right, it can now it's taken my validation rather than the machine making a decision that could be wrong and putting in the wrong file. It will give it to a person when it can't conclusively determine that it's one matter versus the other. We talked about medicals and naming conventions. So in a case like this one, not always it matches to the matter, but it's pulled out the information like the date of service, the type of report, the doctor name, and it's gonna actually match that, as I'll show you, to the appropriate section and collection within FileVine and all that. And it's given in a naming convention, so I'm gonna validate that document. Now some of these, as I said, there are situations where the system didn't require a human. So in this case, with this policy declaration, we didn't ask it to take out too much stuff that's gonna require, so these will go right through. This document has already been automatically validated by the system and was already pushed into FileVine. So let's go into FileVine and and take a look at how some of this works, starting with this event notice. So we took a look at this event notice. Now let's take a look at what's going on with it in FileVine. So I'm gonna go into FileVine, and I'm first gonna start in the docs tab for that particular matter. Now first, we see a lot of firms. We see, just put documents in this sort of area right here. We kinda see this document chaos often with unnamed documents people hunting and pecking to figure out what's what in there, and we can do that. If you want a document to go in just into the docs tab, we can do that with naming conventions to make that easier to use. So that policy deck that got automatically validated pushed right there into into the docs tab. But for a lot of firms, have folder structure set up in FileVine. And remember, that document was classified to an event notice. So when I go in this event notices, I see that document has been pushed in, and it's right here in FileVine accessible to me in the docs tab. So that's the first thing. You can be put into documents into the appropriate folder or subfolder, however your FileVine setup, we map the rules to your workflows. I'm gonna jump into the activity tab because I'm gonna show some of the alerting and other things that we can do. So in this case, for this particular, depot notice, we can see that it has created a task for someone to schedule that depo notice and given them the information they need for it. In fact, we can actually automatically calendar events in FileVine. But for many of our firms, this was that tab, that task within our system that knows for certain document types that you choose, when that document comes in, it can alert either someone based on the role that they have within FileVine. So if you thought in your firm that this activity of calendaring is done by a particular person, let's say, the paralegal on the file, the system will look in FileVine and knows who the paralegal is assigned to that matter and will task them with the task or activity. Or it can be a static person like the calendar clerk for your firm. And in this case, it's also prepared a task automatically for the handling attorney to prepare for that deposition. And so these can be tasks. We can use hashtags. We can do all kinds of ways to alert people in your to your workflows when documents come in. And that can be what we call dynamic role based tasking where certain people are alerted based on the type of document or any other way that you can think of doing it. So that's an example right there. Now I wanna go back and now talk about that medical record and show you really quickly, you know, what we could do there. So we have this medical that we looked at. And so going back into FileVine now, we'll jump into the treatment tab or the treatment section in Biovine. And so I'm gonna find that same provider, Thomas Jefferson. And so in this case, we've been able to put that document directly into the appropriate collection for that provider. This can be done with bills and so on. Now what that does not only gets in the right place, but now that document is where it needs to be to be accessible via FileVinds AI to not only make summaries, med crons, and do all the wonderful things that FileVinds AI can do, but make it accessible as part of the foundation for all of the all of the different things that Five Line AI can do for you. By us putting it in the right place without any human interaction or requiring a person to remember exactly where to put that in all these workflows, these documents are going into the right project and into the right place to be accessible and be leverageable by FileVine. So I can click, you know, right into that document here and so on, and it'll open right inside FileVine ready for the AI. Just as another another point of what we can do, you know, we took a look at that, that policy deck, and we might have had, you know, an urgent tag associated with it. We also, can email documents and send email alerts to roles within from our system to roles within Fivevine. And so you might have just for certain document types, have an email alert sent to someone, like maybe the handling attorney for very urgent documents, and they could go ahead and click on that. And it would not only tell them in the subject line what it was, but when they click on that, it would go ahead and open it for them directly in FileVine. So just some of the different ways that we can that we can use our system to really put documents in and build the data foundation necessary and help make sure it's continuously updated for Lois to do all the amazing things it can do. So happy to answer any questions later or talk more, but that's that's basically the demo that I wanted to show you about just quick and dirty and how the system works. Well, Vivek, I'm gonna jump in it. Oh, go ahead. No. No. I was gonna say, yeah. Thank you, Vivek. And and, Mark, you're a customer. You're living and breathing this right now. Please share us a little bit, about your experience with FileBind and Foundation AI. Yeah. So for the last twenty five minutes, I was listening to Vivek. And as a guy who doesn't really do tech that well, like, I was like, what the hell is he talking about? Half the time, that's when it felt like the implementation was. So if anyone, like, listening to that seems confused, it's it's very, very normal, but it's actually very simple. So, again, for those of you who don't know me, Mark Anujar, I'm in Florida, primarily practicing personal injury law in the state of Florida. We have offices throughout the state. Again, like I said from the start, I'm forty eight, so tech was not my my my biggest strong suit. And for the longest time, I kept trying to push Vivek into naming the documents the way I was accustomed to. So I wanted it to be called an initial record. I wanted to be called a final report. I wanted to be called SOAP notes. That way, would have the ease of finding these documents within the old system that I was accustomed to. And that is literally no longer necessary. So at some point, Vivek said, you gotta just trust the system. And, basically, we've created naming conditions, which are just the way you call a document for laypeople. So MRI, initial report, orthopedic, you know, evaluation. So we create these naming conditions, and then it automatically will file that document into the into the FileVine folder. And like he showed you in his demo, you can create those subfolders in FileVine where the documents will automatically go in, and we do that because we're able to. But it really becomes unnecessary. At some point, you gotta look at AI as a tool that's gonna make your life easier. And in this situation, we had all these documents that were coming into the office and, like, showed you in that picture, all these people scanning these documents in and naming them. And by creating these naming templates, all the documents automatically get filed away into the appropriate file. So that's most important for the use of AI because when AI produces when and it's called Lois now, I would say a better name would probably be Superman. But, you know, once she takes that data and creates a medical chronology for you, you can actually click within there and find the document that where it it extracted that information, and now you know where the document is. So where it's actually placed is almost irrelevant because that med summary is gonna give you all the information you need with footnotes as to where you can get the documents from. Solve the problem in terms of basically putting the file in the right place, naming it the right way. We actually opened it up to our full exchange. So a lot of times, we had secretaries and everyone deals with turnover today in your office or employees who are no longer there or staff members who receive an email and don't follow instructions and actually file the document into the file. By opening up Foundation AI to the whole exchange, it would automatically identify the document, name it appropriately, and put it into the file with an email notification that you got the document. And that was the biggest challenge, especially my litigation department with deadlines. You know, they would get documents, and they would get filed right into the file, and and they would be like, how come no one told me about this, or how do I not get notified that this document came in? It was so important that I respond timely. And here with the email notification, that solves that problem immediately. There's no way they weren't notified. They just didn't read the email. So it creates accountability also on your staff. You know, I think when you're looking at implementation of AI anywhere in the office, you gotta look at where you're having constraints. And that constraint was getting the most useful information in front of you at that moment. So that specialist report with the surgical recommendation that would increase value to the case. Those are the things that we wanted to make sure we had. So the naming uniformity, the making sure you get the email notification, working with, FileVines AI demand or called low Lois now. I just keep forgetting the name. I'm sorry. So Lois now, and she would just spit out that MedCron, which allows you to talk to the client with the most recent recommendations from the physician saying what how it applies to your case. You know, if the client was recommended an epidural, you would know that that just took place on January fourth. Discuss that with your client, make sure they're aware, explain the treatment, and then move forward. So like I said, if you can make quicker, better decisions, that's what's gonna make AI work for you, and you have to embrace that challenge. So I think once you change that mindset of how you used to think about naming everything the same way to making sure it's just in the appropriate file in the right repository, So that way, the AI can spit out the information in a way that you can utilize. That's what's gonna make the efficiencies and the scale possible. In terms of reduction of, you know, cost and payroll, we had a a team of eight people that were just designated to scanning documents every single day. You know, we kinda ripped the Band Aid off and just kinda went with it. And, obviously, there are some issues, but there is a trust and verify component to it like he showed you. In in South Florida, we have a lot of people with the same last name, Rodriguez. You know? And at that point, it wouldn't know which file to do to place that document into it, and it would give you the option of which file would you like it to go into. We have clients that have due more than one claim over a calendar year. You know, you have clients who had a subsequent accident. In that situation, which file should it go to? It would give you that instruction to choose which file you want that document going into. So all those safeguards ensure that documents were appropriately filed, put into the right place, and they're at your fingertips for use. So it really just becomes, again, working with Tiffany and and and Vivic's team, you know, there was, like, eighty five percent accuracy, ninety percent accuracy relatively At that point, the last ten percent, our team would kinda manually, you know, verify. And, eventually, we switched over to Vivix premium product, which allows his team every single night to go through those documents and verify them for us. And now every single morning, we wake up and we have nothing left to scan. I literally had my scanning department staring at their phone not knowing what to do, which ultimately led to me having to let some of them go, which is unfortunate for them, but obviously good for my bottom line. But that's exactly what AI is gonna do for all of us. You know? It's implementing that strategy. It's basically executing it, and it's learning to think of how you manage your documents, how you review your records, and how you process the information in a slightly different way. Vivek, is there anything you thought, I should add to that in your opinion? You're you're muted, I think. No. I think I think, you know, your experience, it sounds like it's been great. I don't know if Tiffany has anything more. I think we have a lot of questions in the q and a coming in. I'm even getting text messages from people who know me on the call. So I think that we should go to q and a. And, Mark, good job. Yeah, Mark. Thank you. Let me ask you this, Mark. If if there's one recommendation you've been through this now. You you you've you've been through this not only on the FileVine side and FileVine AI, but also with Foundation AI. If there's a firm with a little bit of hesitation or do I do this? Is it worth it? What what's the one thing you would say to that managing partner? I think with FileVine, our implementation took a year for everyone in the firm to get comfortable with using it. Right? So they're used to time matters, which was our old office management software. They wanna add that familiarity of how things work and where things go, and you have to change that mindset. And there's not there's never a good time to do it. You just gotta do it, and then eventually, everyone will get accustomed to how things are laid out in the new platform, and then eventually, it becomes second nature. So it's one of those things that you just have to kinda jump in both feet and just get it done. Learning along the way after we implemented FileVine, and, obviously, we were one of the first people to use the FileVine AI, We now realize that you have to implement a tech stack to facilitate, you know, that usage. So that's where Foundation AI kind of filled in that void. Right? Because the FileVine was working seamlessly, and then we were struggling on the manual side of things with our our employees getting the documents into the right places. And now Foundation AI has solved that problem to in its totality. So now everything is instant. There's no delay. And in order to be successful today, especially the way AI is evolving, you need speed. You know, you need speed in your documents, speed in your chronologies. You know, especially now in Florida, our judges are are really rocket docking all our litigation. So we need to have that information at hand, you know, as quickly as possible to make the best possible decisions. And then you work on old information, and then you realize why mistakes happen. So I think Foundation AI will solve that problem by making sure that, you know, thankfully, US Postal Service and FedEx, you know, they deliver on time and the mail is always there. Now it's what do you do with it? And that is the delay that we have eliminated by making sure those documents are in the file and at our disposal whenever we need them. Mark, thank you for sharing your thoughts. We'll now shift into the q and a portion. And for all the participants and audience, please submit those questions. We do have quite a few questions. So let's let's dive in. We'll try to get to as many as we can over the next about ten minutes, and then, and then we'll go ahead and close this out. And reminder, I know at the end, Vivek will go to the QR code that if you wanna learn more about pricing, specifics, and a one off demo, I know Foundation team would love to do that with you, and you can scan the QR codes, submit your information, and they'll reach out promptly to schedule that demonstration and phone call. Let's go ahead and dive in. There's one question that seems to keep surfacing here, duplicates. How does Foundation AI handle duplicates? Vivek, you mind taking a a minute in answering that? Yeah. So there's two ways to think about duplicates. There are duplicates that come in, at the same time that are exact duplicates, and there are also duplicates that aren't exact duplicates that may be in your system. What I mean by that is, let's say, a medical record, and you might have gotten it via fax because that still happens. And that copy is in your system, and then you get another copy of the same record. But now this is a physical mail that got scanned in. That's one scenario. Another scenario is, you know, a document gets emailed to multiple people in the firm, and so multiple people get the same document. And so if multiple people are saving that document within your system, that creates duplicates. Or the same, you know, emailed copy of a PDF gets emailed in, at different times the same way. And so I'll I'll address those scenarios just so we're clear, separately. So the first the second scenario I talked about, which is the same physical the same digital document coming in, Foundation AI for every document it processes, it then recognizes the unique signature of that document if it comes in again. And this works not just if two people in the firm let's say our total email capture solution is implemented where all of the email boxes within your firm are plugged into Foundation AI. So if any third party attachment if any email with an attachment from a third party comes in, then Foundation AI will actually take the attachment, automatically download it, and route it through the system. Now if there are multiple people that receive that email, it will know, dedupe them, and only process one. Not only if those come in at the same time, like in the scenario I said, but even if that same email, that same attachment comes in again, that same exact attachment, it would know it already processed that and not processed it a second time. And so that's important. Also, with that total email capture, it's not gonna pick up any internal emails. So I receive an email with an attachment, I forward that internally to someone else in the firm. That will not get picked up again by Foundation AI anyway. But now there's the other problem of, you know, you already have the document in your file. Now a new document has come in. It's now going into FileVine. Well, because we are not the system of record and we're not storing your documents long term, right, if it's a different copy of the same document, we can't automatically know that you have it nor would we wanna, nor and we also, we've seen that there could be some minor differences. One could have an additional page or or something else to it. But what will happen is because of the uniform naming conventions and the uniform foldering, that document will end up going into FileVine in the same folder with the same naming dimension and be easily identified as a duplicate within FileVine. So then when whoever's tasked to review that document is tasked to review it in FileVine, they would be able to see we already have this document and choose which one they wanna keep. Often, there's, like, a a crap copy, pardon my French, or or, like, you know, that's been, coming through fax, and they get a cleaner copy. They can see them right next to each other because they have the exact same naming convention, keep the one they want, and get rid of the other one. So I think we can help with that challenge, and we can solve it with multiple people getting the same document and trying to upload it in. Also, when they're coming in through email, those people are no longer responsible for actually, for saving the document into Five nine themselves. And I could show you actually, if it's helpful, what our what our our Outlook integration sort of looks like. But in our Outlook integration, all these documents as they come in with an attachment, our software would automatically pick them up, and it would show the user within their UI, and this can be changed, that this this attachment that came in on this particular email has already been processed into FileVine. And so the users are no longer thinking about saving them themselves, and you don't end up with multiple people saving the document in various different names, in various different ways, the same thing. Every single document that comes in your firm is gonna be processed uniformly into your system. And so that does help alleviate the challenge of duplicates. So in this case, I know there's a lot of questions around links. It's a shared link. Right? Yeah. How does that work with foundation? Yeah. So links are obviously hugely important. Right? There's not just shared links like Dropbox links that you might have to go into. Court notices often, like in Florida, it's a link you click on to go in and get the court notice. And then there's portals like ChartSwap, which a lot of PI attorneys use, obviously, that you have to go in and download documents. And so we have solutions that are rolling out for, a few of those immediately. So, for example, the Florida court notices or any court notice where you're clicking on a link and it takes you directly to a document, that our software can identify those links and download those documents, into the system. Right now, with, the portals, what clients are generally doing is they still are manually going on those portals and downloading those, and then they can either upload them into our system, or we can set up a shared folder, a specific folder in their environment. Maybe that's a SharePoint folder or a Google Drive depending on how their infrastructure's set up, that they just drag those documents into that folder, and then our software syncs and pulls them in automatically. But on our road map, we are working actively on ways to use AgenTik AI to actually go in there and download those so that people in the future will not even have to go in to those various portals and download those documents. Once the alert comes in that a document is there to be downloaded by a human, AI will be able to go in there and take care of that and put it all in. So that that's very, very heavily on our road map right now. Great. If you wouldn't mind going to your QR code, I wanna make sure as as we're ending here in the last few minutes, Vivek. And then you wanna take a moment and we're still gonna have a few more minutes of q and a, so we're not ending. But I wanna make sure that our audience, while they're still on, they understand your offer and then what are next steps once they once they scan the QR code. Yeah. That would be thank you very much. You know? So, essentially, by scanning the QR code, what you can do is go ahead and book a demo with our team. And and some of these people are much more knowledgeable about the product than I am. I was the founder, and I I'm a user. But we have people that are that can answer all of your questions around how it's priced, how to implement it, specific questions about how it'll work with your workflows and all of that. Now as part of the way our system our process does work, though, there is essentially an implementation period just like with any other software where our team will understand your workflows and suggest, you know, ways in which to implement the software, with your custom build of file line to make it all work the way you want, and that's our implementation. We do the implementation ourselves. So there's one team. The same team that does your implementation will be the team that works with you as you're a customer. So that's a relationship that we hold the entire time. And our offer for those of you on this webinar that that book a demo, through this webinar and, you know, end up going with Foundation AI is we're gonna cut that implementation fee in half. So we're gonna do half off implementation for anyone who comes in through this demo and so on. So that's the offer right now for those of you. But if you're interested in learning more at all, it doesn't it's, you know, completely complementary, obviously, to have a consultative call where our team can walk you through how this works and probably just share best practice with you anyway now you can operate your five I more effectively and leverage our software to do it. Awesome. Thank you, Vivien, and especially thank you for for the generous offer to our attendees today. Let let's continue on. We have a couple of more minutes. We'll try to get through as many. We're not gonna be able to get to all questions. So so type answers too. Sorry. I have to interrupt. Thank you, Tiffany. Thank you. So, Tiffany, we're gonna in. A sum, but I'm trying to, like, type answers for you guys. Wonderful. So one thing that seems to be at least repetitive theme is it's trying to route to a file or maybe, in a specific section that isn't yet in FileVine, Vivek. The name's not there, and and it seems like there would be a jam. How does Foundation AI work through that jam? Does it does it create something? Does it go into a general box, or where does it how does it work? So a couple ways, I think this comes up. This comes up first if, let's say, a document comes in and it doesn't match to any matter in your system. There's an exception handling workflow, there's numbers of ways we can do this. The most common is that the law firm would create a project within FileVine for unmatched matters. And our software would know if it can't be matched, it would just be very easy from the user interface. And this would require a person to make these are ones ones that would be exception handling. It doesn't match anything. That would then put it into this we call it the default matter or the unmatched matter. Generally, that will have a workflow associated that will trigger an alert or monitoring by some admin within the staff. Often, are doc those are matters that haven't been set up yet or maybe you receiving documents before you receive the actual, matter referral. Some reasons why that would happen. And so very common and a very easy exception handling workflow. But another that might happen is with collections. Right? So let's say, you know, a medical record comes in, and that particular provider and that software is able to match that to a provider in your file line, but that provider is not yet on the matter. So we know what matter it is. We have a medical record, and but that provider is not on the matter. The software, as long as that provider matched you is within your contacts in FileVine, we can actually add and create that collection in the medical in the appropriate section within FileVine. Now if it's a new provider that doesn't exist at all, that would also go through an exception handling workflow because we're not just gonna create providers for you. You know, one of the challenges a lot of firms have is having a number of you know, people creating too many providers, and so they don't have enough matches. So one of the things we recommend during implementation is to help clean up that provider table, clean up some of the data in your system because our system will fun will only function as well as the data in your system just like Bob Minds AI. The data in will function as well as the data is accessed too. So there are exceptionally in the workflows for all of this, whether the matter isn't there or whether the contact is there, but the collection but that contact is not set up as a collection on a particular project yet. I love that. I'm going to Eric, let me just because there's a few things here, Vivek. I can't Yeah. Answer. Yeah. Would love to pretend that I could. But first, I think this is an important one. Is there any malware virus scan before it processes processes a document received by an email? I don't know the answer to that. It's a great question. It's one that would affect, I will say this. I I'm yeah. They're without being my lawyer answer, I believe there is, but I'll get back to you. But the thing the thing that matters is is the document that gets pushed into FileVine could never contain a virus. Because when we get a document into our system, we are actually going to OCR that document as part of our process. And so the PDF that we push into FileVine would come through our system, and that we can guarantee would not have any virus. So the document that comes in would actually get turned into a machine readable searchable PDF and pushed into file line. So if it had a virus or some malware coming in, that would be on our system to catch before we process it. But before it goes from our system to yours, it would certainly be cleansed because we're the ones who are pushing a document that we create that's, you know, coming from our system into your file line. Awesome. Okay. So those that's gonna go with Vicky's. Also, how does it protect against attachments that are risky? So we had two that were similar. Yeah. And then, the QR code form doesn't work. Clicking submit doesn't do anything. I thought maybe we have Tina and Dylan both on this call, who are gonna love that I'm calling them out. Maybe they can help you with that. And then the other one I have no idea is how or can Foundation AI connect to Pacer accounts to pull port filings and feed them into the AI for extraction and workflow automation? I do not know that. So we have we've spoken with Pacer. There's a number of different sort of companies that integrate with Pacer, like Pacer Pro or ECFX. We have ways of working with them. I think our team would be able to answer more specific questions to how you're set up, but these are all things that are actively on our road map. And so if, for example, you already have a system that is taking documents and giving them to you via email, like a lot of the pacer systems are doing, we can pull those automatically. Or if they're going into a folder already. And we have ways to work with you to build to figure out how to integrate the documents coming in into our system. So I think we can work with you, on that. Perfect. Okay. And then just a comment. The QR code is working fine for me. You also help Yeah. It looks like we've had a number of inbounds come in, so I think it might may have been for that particular user. But if there is a challenge, you know, also, my email is just my name, v I v e k at foundation a I dot com. Any of you can also email me directly, and I can either answer the question or direct you to someone much more capable than me on my team who could answer for you. And so feel free to do that if there's any challenge with the QR code. Vivek and works with Gmail the same fashion it works with Outlook? Correct. Yeah. We're working on our Gmail integration to do to, to create the same functionality. There are some things that we're still working on, like being able to show the the tag in Gmail, and that's gonna be coming out very soon, though. Perfect. And then for those of you that have texted me, I will do whatever I'm telling you I'm we'll do in text. Some of it will be directly to Vivix. So feel free if you have my number, and quite a few of you are already texting me. So, Vivic, I'll direct I'll direct that to you. I hate to cons I hate to conscript you to another job, Tiffany. Tiffany's so called solicited solicited number. Yeah. I think it looks like we do not have any additional open questions. So I think we are good to to wrap up. First of all, thank you to all of our presenters, Vivek, Tiffany, Mark. Thank you so much for spending your time with us this day and sharing your insights. Thank you, Vivek, for going through Foundation AI, how it can help FileLine customers propel their work forward. We are very excited about the partnership, and we're even more excited for the customers that can reap the benefits of our partnership and the integration with Foundation AI. With that, we're going to end today's webinar. Thank you for joining us everyone. If you have any questions, feel free to email Vivek, myself. Again, my my email is e r I k at filevine dot com or even better, scan that QR code, and we would love to continue the discussion. The recording will be sent out in the next couple of business days once it is prepared. Thank you again for joining. Have a wonderful Wednesday, everyone.