 What we're showing off today, I think, is a really remarkable new piece of technology. The problem that we were kind of addressing is looking for a fully mobile, cloud-based, mobile automated document platform that is also scalable and will grow not only with us, but unmuted. And we'll get into some of that smart intelligence that goes along with it. But first things first, just we wanted to show off a little bit, get our hands in it, get your hands into it, the mobile automated document platform. So with that, I'll let Jason speak a little bit. Jason is my West Coast buddy and a tech guru and legal guru and a good friend of mine, Jason. All right. Hey, thanks, Vince, for the kind words and thank you, Brian, for making this opportunity available. In watching previous webinars, I kind of saw that there is a little slide component, so I put one together. We're hoping to actually spend more time in the potential doing and showing, but I thought that we can walk through a little bit of what the product is. And so I think, can everybody see my screen? Vince and Brian, the AUX logo there, automation for the documents and tasks. Definitely good. If we're going to be serving people in this 21st century in the kind of mobile smartphone on the go world, it's important that the delivery system be not just mobile friendly, but I'll even go a step further and say mobile native. And I have a lot of respect for the people that have been fighting the battle with serving the many with limited resources. And I think people have seen that websites, even mobile responsive friendly websites, don't always translate well to a mobile phone experience. And if we don't have a good experience, people, they're not going to use it. If the send button ends up being under the fold, so to speak, and it's not intuitive to swipe up or of a box that needs to be checked isn't there. So I'm a big believer that it's a lot easier to start mobile native and then go back to a web type of experience rather than trying to push the web experience into the mobile. Another piece is that as we move forward in whether it's artificial intelligence, machine learning, expert systems, what I like to call augmented legal, because I think at the end of the day, people do need a voice. That's why they're kind of our lawyers in the first place is that people can't always stand up for themselves or articulate their issues. And that's why lawyers have a job. So the DocuBot platform, as I mentioned here, we're looking to leverage artificial intelligence or expert systems. I don't want to pin myself or offend people that there's so many terms being thrown about. But as we see it right now, you have a document assembly, questionnaires, diagnostics, FAQs. Vince, what was your term you coined yesterday? The operational, you had a term. If you don't remember it, we'll get to it, but it was basically an assistant of some sort. Did you remember? I do. I was calling it an onboarding agent bringing clients in to not just the intake portal, but actually have an assistant through it and onboarding them with documents, et cetera, questions. Right. And I think that that, I want to say that that hits a big part of the challenge facing, you know, LSCs, legal aids, and even just private practice small town attorneys or small attorney shops. And that is, if somebody calls an institution and that call is regarding a document, a letter they received in the mail, if we don't have as practitioners, if we don't have that document in front of us, it's not going to be very helpful. And so I'm digressing a bit from the document assembly, but the idea of the onboarding agent is to when a person is going to be talking to a lawyer who is valuable or limited, we need to have more substance and less procedure. And that's where artificial intelligence and onboarding agent can help. Now, these are many things that can be imagined and built going forward. What we've done right now is we have the document automation served up via chat bot. And so we'll, I think, well, you know, one of the best things we'll do to just get in and show it to you. But we can take a look, but just in wrapping up here, the reason that I mentioned the native platform is that we've got, you know, it's got to be mobile friendly. The data is there, the statistics of everybody's moving to smartphone. For lower socioeconomic, many people, that's their only access to a broadband connection. So the platform itself, mobile friendly client service, communication. People are very comfortable dealing with a chat or a text-based media rather than simply, you know, a box and then moving the mouse or touching your finger into a box and typing there. It's just more intuitive, more fluid, you know, content control. As you'll see today, we have a submission tool and we only anticipate, and actually one of my motivation in speaking with Vince and getting before this audience is we are looking to discuss how we kind of make this a little more uniform, the experience of actually submitting documents. And we'll get into some of the discussion of variables and whatnot in a bit. But some of that needs to be standardized. Reporting. Reporting is essential. The nice thing about doing something in a native mobile app is reporting it. You know, very easy to take all of these touches. That kind of ties into five, the CRM or the management system that the LSC may use. And then with this platform, you can not only send an email or a communication to the LSC that somebody spilled out a document. If you have a pro bono attorney, they can be CC'd so to speak. So it's a nice integration. So I can send this. These are just if people are going to be looking on how to jump in. So what do you think, Vince? Should we show them? Maybe you all walk them through the document that you did a little earlier? Sure. Yeah. Yeah. So you want to navigate to the submission form? Yeah. So quick question here. So all of the tech behind Docu, but it looks like it's all sort of open source here on GitHub. And then you're running stuff on WordPress also. So anybody else can take kind of see how it works behind the scenes. Is that correct? Well, and now I've got sitting right next to me, Brian. We have a special guest. I have Tray Richards, who's my lead developer on this. So I wanted to make sure Vince said we might have a fairly tech savvy crowd. So I wanted to make sure, you know, I'd buttress that. I'll let Tray speak to that. I have my own opinions, but Tray can speak to that. Yeah. So. Like the, the document, like the actual engine behind the like natural language stuff and the AI and all of that is actually not open source. All of the open source stuff that we have is how people can integrate with that engine using like open source libraries or using open source plugins. You mentioned the WordPress plugin. So, so basically we, it's kind of a two tiered thing, but the backend engine is not open source, but access to the, the API that it provides is open source. And we have a few different libraries available on GitHub. Okay. So, so individuals that are working with you do not have the opportunity to see the source code, but it's the interface that's open source or what, what talks to the source code. Yeah. Yeah. I mean the source code for the documents themselves aren't readily available, but aren't necessarily proprietary, like on our end, they may be on the end of the people who are submitting the documents, but the, the source code for the actual AI and like the chat bot itself is closed source. Okay. And if, if people work with you on this, what type of statistics or reporting or that type of stuff are available to them? And well that is a fair bit. I mean all of the, the calls you can say or there's, there's two, there's kind of open lines, which is initiating a thread. And then there's actually calls to the, the server. And so we can make that available. The document, I guess if I go back here to kind of this, the reporting, the reporting I would anticipate as you see content origination, duration and notes, those type of, of things will be available. We're not really looking to hide that part. But a matter of fact, the, what the creation, they'll get every time somebody's creating a document is, we'll jump into that in a minute as you see the, the process a little more, but they'll get notification of that. They can get notification of how many documents were started, but not finished, how, how many calls if you would, you know, if you, if you think from what is your name to great hit here to print or email a copy of your document. You know, there's so many hits that would take place or calls and they would be able to see information like that. So it's fairly, fairly open where we are and what's kind of exciting to me and being before this audience and, you know, we're. Okay. I think that definitely answers my question there. And people, I've got a few comments here. People are very excited to see the demo. Excellent. Excellent. All right. Let me jump over to, and so I'm just going to show you on a, on, this is the plugin on, on our, so, and actually I wonder if I should do it. You know, I mentioned mobile friendly. I think it would be kind of cool to, is to, is to just show them what it would look like on the mobile device that might be an interesting. I think that'd be great. And while you're pulling that up, I'll just speak a little bit to what Trace said. I think to translate it maybe in a legal aid world a little bit. All the plugins are open source. There's a WordPress plugin. We've requested working with a group on a tick or a Drupal plugin for all Drupal 7 open app again and all that. The documents that you submit and the code within the documents are all open. So it's kind of like hot doc, you know, the documents are used and everything. You can't crack the kernel really in hot doc. So it's similar in nature to that except a lot of the kernel here is, you know, some AI interface with a Watson. And then are you guys seeing my screen? You should just see a little screen shot of me. We currently see the doc you bought. Dancing around. Yep. Well, while he's setting that up, this is Vince again. So just this morning I went to this submit field right here and marked up a document. It took about 15 minutes. It was a quick claim deed. Submitted it. The markup language is remarkably easy. And I'm not sure what Jason is doing here. But we'll scroll down in a moment below. Okay. Can you guys see my phone screen? Yep. Got it. All right. I was just, so I'm just jumping into, you know, one of the apps that DocuBot exists on, but this can give you a little bit of a feel. And this app is available in the Apple store, Google Play. Yeah. And then this is something we can speak to. Sorry, I moved my phone around. So I'm just going to hit, I'm going to start a new, a new one here. So you see, hey, I'm the DocuBot and I'm just going to walk you through one of my favorites because it's, it's quick. So right now you're on your mobile phone, Jason, correct? Right. Can they, can you see kind of the classic iPhone? Yes. Definitely. We can see it. And then you can also speak into it, but I think you get a little confusing with all. I don't want to get any latency. So we can do voice detect along with this mobile. So you could actually speak to the phone. Speak to your mobile phone. Yes. Washington, Utah, mail. See that, that didn't like what it picked up. So it gave us a little, I'm flummo problem. And then I'm going to show you a little thing. I believe it'll tell us. I thought previously sometimes it'll grab a misspelling. And so this is something cool that exists with DocuBot that is not typical in a lot of with the AI or machine learning that you see where it says, let's double check. I understood that. It's all a bit correct. If I say no, I'm now able, it'll ask me what part did I get wrong? I don't have to go back through and redo all of that. So I can just say something like state. It's okay. Let's try that again. What state? Okay. Now I'm going to say yes. And now we just generated the power of attorney. I'll try to zoom in. Jason Bella is appointed Tyler Todd of Washington County, Utah. It's just simple. Right. It's not, you know, it's a fair little visual. It's a power of attorney. And so that's what it looks like in real life. We can, we'll provide some links. So people can, let me just jump out of this. So, so people can go, we'll give the link. They can try it there. Like I said, there's a WordPress plugin they can get. They could launch it on their own site and then hit Vince or I up for the, they'll need to get the credentials from us, but that word, we don't have a problem with that. We can make those available and they can play with it on their website. I'll just jump on the site here. What can you do? And he'll give us, we got about, you've got what a will request for repairs. There's actually some documents that are direct link only that are not appearing on the list. We have a, some, some demo documents, but it's pretty, pretty easy to interface. Do you have any questions at this point? Nope. I guess no. Looking good. All right. So let me show you, I'm going to work a little bit backwards here. I was just going to show this is, this is what the, the plugin looks like on the back end. So you can see I'm in the back end of my side. I got the little doc you bought there. You get the key, the secret, where we want the VCCs to come from. You can upload an image of your later whatnot. And then you got a little visual editor here where you can put some text that could be instruction. Hey, this is how we do it. What we anticipate is that in the upcoming, you know, I'd say, I'd say realistically by the, the summer, probably mid-summer, August timeframe, there will be a more robust type of interface on here that will accomplish some of the tasks we're going to see today. We fully anticipate that people will be able, we can have a submission tool, but we really want to get into a much more automated flow. And that, and that part of why we're here is to talk to people about what they see as the, you know, some of the standards. So what do we need to do? Yeah, what are the areas? So Vince, do you want to, I'm trying to think if we want to walk them through, do we want to submit one? Yeah, up there. I don't think we have to actually do it, but do open invite anyone out there to navigate to this URL. I don't think you might not be able to see it in the address bar. Or I can throw it up for them so they can, I'll just put it quick so they can. So if anyone has, you know, just maybe a one pager or something, not a dozen inserts or any inserts really, something to submit, we'll walk you through it and talk about the process and how the process will be, how the process is currently in so far as having a document automated. So if you got like a little letter or I don't know, I did a quick claim deed, something like that, not too horribly complex. You're welcome to go to this URL and follow the instructions that we're just about to walk through and we'll see if that'll be automated. How many can be automated before the end of this program? What do you think, Jason? There we go. There we go. So, yeah, he's teasing me a little bit because I got Tracy sitting with me here, but let's, if people can hopefully they can do that. Can I put it, can we put it on the message to the group? Is there a way to do that? Yeah, yeah. I'll chat it out. Or here. One long. So yeah, if you want to, if you want to go back to the submission page. Yeah, I wouldn't care. I just, I don't get it. So there. So yeah, so if anybody wants to play around, I mean, this is very, you know, it's pretty easy. So, all right, so we're back to the, the submission page and you can just kind of see, you know, it'd be your first name, last name, emails, verify emails, some info. You would provide a document title. You can provide the, the, the, the, what you see is what you get editor here. And maybe what I can do, let me just show them. I'll try to see if I can parallel this because I think that, that could all. Okay. I think I'm going to send that link out to organizers and panelists only. If, if so, Ron, maybe get that out to everyone. So this is, I'm going to see if I can get these upside by side, by side real quick. So here's what, so this is an email that Vince would have received. And then you can see here, submitter info. And then we're here in the email, Vincent Morris, Vince Morris company name, open law, his website. And then now let me just, sorry guys, I'm not this. So Vince, I have upgraded you to organizer. So you should now have the ability to put it in the chat. If we head back to that URL, I can also type it into the chat. I'm good, brother. Thanks. Excellent. All right. So I don't, let me see if I can kind of at least. Jason, just maybe go a little more chronologically. If we could, yeah, let's pull up the, let's pull up the submit screen before we see what happens after that. Okay. Sure. Sure. So, so we're here in the, the docking lock. You want, you want me to grab one that I, you know, it looks like you want to switch screens and you, you go to the URL and you play around or what's more comfortable for you? You go ahead and drop, you can grab something. I'll just talk a little bit while you're getting that ready. Let's actually submit a document. Sure. So just to clarify the way that this works is somebody can submit a document through this form. And then the AI tries to figure out what would go into each of the different spots there. No, no, no. Go ahead, Jason. I was going to say what, what we're looking similar to, so we're going to look at, you should have my screen here is a special power of attorney. Okay. This is what the document looks like in work. Is everybody seeing that? So now I took that. All I did was a, no, let me go. Yeah, you get it. Oh, I needed to squeak really sorry. That was my, that was my template now. Okay. So we're back here. We got the text. So I copy it and I pasted. Now this is, I've already added my variables. Now this should look somewhat familiar to people that are, you know, whether it's hot docs or the A2J, the different, the different things that are available. So I have now through my, my squigglies. That's why the document is called squiggly, my double squigglies and then inside my variable. So now I've taken those. So what I would do, and I'll just do it here, I would not copy this. And then you can do, you know, you could do it, you could do it either way. I've already edited it. So I can do it from the top here and just copy that text and then move that over to my submission tool. So now in my submission tool, I've got a, a, a WYSIWYG editor here. It's going to be fairly, fairly true. And then if I've got document title, we will call this. So I'm there. If I had any, but the header, this could be, you know, this document is a provided courtesy of, you know, whatever you know, whatever we want to say. Now I come down here. Now it's going to, same thing with the footer, but now we're going to have to go to our variable name. So the first variable name we have in here is going to be principal first name. Okay. So the principal first name, again, you can, and this is where we're working with getting some form of standardization because as I pulled up a document, and let me just jump because I thought it was interesting to take a look at, but this is from the LSE standards and practices for, for hot doc applications. And this thing, I believe there were eight best practices. So sorry. The best, the best practices is just there, there is no standardization. There are some suggestions, but I think that maybe this could be a space where collectively, and this is I talked events. And if there are people that are interested in working with us on this library, we are very interested in, in trying to somewhat standardize. I mean, because the issue that I see is if you look at fillable PDFs, for example, in the judicial council forms in California, they have one index. If you look at the hot docs, it appears there's another index. If you look at some of the A to J stuff, so, so I think this is one area that everybody would be well served in picking one. And again, I don't know if that's even possible, but that's something I'm interested in and would love to work with anybody who's interested in trying to do that. So again, so the variable name, you know, first name, then you could view a description. What is the name of the person giving the power of attorney? Okay, so question mark. So now that's, and now you can add, you would go through each of those, I hit enter, sorry. Well, how do you hit that hit plus? Oh, there we go. Okay. So now I can go in and you say I can minus that and I can go plus. I must have hit the keyboard. So, so you go through and you add your question. What we'll do is once that's done, the user is going to get an email of essentially what they've done. So we've got the document title. There was no header document. We've got the information there. That's, you kind of see what the document looks like. You can see there's page breaks. Now we have variables named grantor and so everybody can see that. So this is the, we'll call this the coding if you would of the document. And I believe many of the listeners and the participants are aware that they've put in more documents than I have, but they should be able to use a lot of their existing work to now move that into the chat bot interface. And that's probably one of the most exciting things, I believe that, that is going on right now. So if you've got a bunch of documents that have already been coded for hot docs or for something else, you've already got this type of setup put in place. That is correct. And we would also, we are working, there's different components of it. I will just say that we are working on interfacing with existing index library. So if you have coded a bunch of your own documents, you have a library that will save you some time over the long haul. This I'm not saying you could just magically, right now, but we have that well in mind. That's why I believe the standardized or a greater standard for the library or the variable index is very important for this community. Because I think a lot of the legwork has been done, but now what we want to do is deliver it in a greater usable format, right? That's kind of where I see it going. And if I could pipe in for a minute, Jason, this has been, a thing I'm really excited about is not just the natural language learning. We haven't gotten into kind of the cursive feedback loops of the AI and everything. But as we go in, and right now we're just hard programming as you see the names of the variables and the questions, but that itself has become in a library and is learning, currently supervised learning. And the more consistent we can get with nomenclature, the better. Those variables at some point will be able to be recognized, right? And in a way, automated programming to an extent, if we can see that there's hundreds of variables from pre-existing hot dogs, templates that use this same nomenclature and same variable structure, then inserts can go ahead and happen. So in a way, we're talking about robot programming to an extent and tell me if I'm all faced, Jason, I know we're big dreamers and this is a little bit out, but it's not just teaching on the AI end, which we'll get to in a bit, the natural language, but the computer language as well, if that makes sense. Jason, correct me if I'm wrong? 100% is the goal to basically have the AI right itself. And secondly, I just add, and why I'm excited about this is because it's not, it's collaborative, right? It's not competitive. We're building off and trust me, I know I've been doing it for a long time, I've programmed a lot of hot dogs and there's so much investment in that for those who've gone that route and for those who don't, it looks very daunting and I think this might be a little easier interface, a lot easier interface, but for those that's already invested in such, you can't just let that go, but yet to get hot dogs into a mobile friendly way that's accessible to so many more people, you don't want to forgo that, but yet you want to do that. And so I find this is a bridge technology that not just a bridge, but an extension into the future, but I'm getting all dreamy and sappy. Jason, go ahead, man. Well, I think we're about to- You and I, it's kind of funny because Vince and I share, Vince from the decade and a half in the trenches and me from a love of problem solving, and I'll just go just by a little bit of a segue. I've been working personally on document automation for about six years, so I had this, I went and my thought was when I saw LegalZoom, I was so offended if you would by the fact that they were charging for some of the stuff. And so I started out free will. I have free will attorney as domain I own and I was set about for my WordPress to build an automated will. And it was functional. The problem was every time I updated the website, it messed with the code because it was embedded. The code wasn't- The code was actually part of the website for the document automation. And so like I was beating my head against the wall and for years and trying to get there and it really wasn't until I came across the idea of a native mobile app. Because some of these things, I will tell everybody participating that if they are considering moving forward in the machine learning AI realm that they really need to consider writing in Swift. And there's a lot of languages and a lot of people have spent many years and decades with some code, but it has to be deliverable to the mobile. And if we don't have that, it just makes it- You could have some of the greatest logic available, but if people won't use it or if it's difficult to use, you're just not going to- It's not what we're trying to accomplish. And that's Brian earlier to your question about kind of the open sourceness of this. This is why I've essentially made our engine available to people that want to play with it is because I think there is a greater work here. You know, there's a great- I completely agree with you both in that it's got to be mobile first. Our client demographic views already to our website are heavily headed in that direction and the collaborative community aspects of sharing variable names, creating a standardized dictionary, that type of stuff. The more people that participate in these projects like this, the better it is for the community and the easier it will become. We recently at one of the hackathons talked about an open data standard and assembling that or creating it ourselves currently would be very encumbered some, but if we had thousands of documents that were already coded and then started to be standardized, creating that standard would be so much easier. Absolutely. This is what excites me about this juncture in legal technology, serving the public. I mean, it's almost like something that has been thought about when computers first came and then the internet and then all of these things and it's really culminating because people are walking around with a laptop computer connected to the internet that they are very comfortable interfacing with and that's their smartphone. It's amazing to have that right now and I think that's where we need to leverage that and leverage it collaboratively with the numbers that you see thrown out, 80% 80 plus percent of people not represented not seeking help. There's no reason for that. It's more of a let's give them what they need and then use our resources again. I always say procedure is for the robots. Substance is for the attorneys and I think that we're really getting to that space. If I may, let me jump over. I wanted to show everybody because this is something that I believe in just again going back to serving everyone but so Docubot does exist on Facebook and it's the site here. It's AUX AI, Facebook slash AUX AI but you can just do the same things that we've done. Let's see. I'm just trying to see if it might... Is it... Oh, test button. I'm the admin, that's right. So in the mobile component aspect right now you can create automated documents in Facebook. You can patch this just about anywhere you want. Facebook, you've seen the world internet maps. That's where a lot of people go. Why go to a statewide website? If that's where you're connected. Each click matters, right? I like that. Each click matters. And here he is doing an AI integrated automated document on Facebook. Am I right, Jason? No, you are right. You're right. I mean, there's even... I don't want to scare people but there are some things. It can be set in. There's automation. The permeations and believe me, I'm just trying to show the strongest... I'm leading with my strongest stuff here but we're working on... You can make it... If there's stumbling blocks, if somebody is having a problem with the document they can type help and be connected with a human operator. Things of that nature. Again, I go back to that first part. We didn't really touch on intake but there is an intake form in the docubot and that can be... That's something that can be specialized for the different LSCs that are out there because they might have different poverty level guidelines or different. They serve a particular community or a particular subset of the law but gathering those documents beforehand, letting people know what to expect. This can be integrated with videos that people have done on what to expect and say a child custody determination or something like that. We're really taking the learning experience and now applying it again to this whole AI that have you ever filed something ever before? How about just something on decorum? Don't show up to court in a tank top or with flip-flops and shorts on. Dressed for court like you might do for a business meeting, something like that. Just these little things that could help people not be so intimidated by the system and then more likely to use the DIY or the DIY plus tools that we're going to be making available. When I say we, I mean the greater community. Jason, if I could, stay on that screen. If you'll notice what happens, it's the little things, man. Sometimes you bury the lead, brother. You were doing, I believe, an expungement form. It looks like an Arkansas expungement. Then you typed in intake form or you could have spoke intake form and then up pops an intake form. You didn't click, every click matters. That means no clicks are the best clicks, right? Immediately you didn't go to another page. You didn't go to another link. You started an intake form right there immediately. That is kind of like, I don't want to use the word portal, but every automated document that you have is at one place. You can make it. You could parse it out with different links if you wanted to for whatever reason, but you don't have to. It's one place. You type or select what you want and there you go. Marketing is easier. Navigation, which is the hardest thing, is getting a client or a user to the resource that they need. So they're already at the resource. Yeah, you got to figure out what resource within that resource, but it takes away so many clicks, which has been a struggle my entire career is getting people where they need to be, right? That was just amazing, Jason. I didn't want that to be overlooked. That's one of my favorite parts. Let me also make a jump so people, because I think this is, I do have a, it's a little more limited of a site. I mean, it's very functional, but I just, this might be easy. So AUX.AI is kind of a Docubots home turf here, and that's, people can come over here and we've got, these are just quick buttons here, the intake, expungement, legal wellness, that Vince mentioned on the expungement, and then the legal wellness is a diagnostic tool. Do you have a checking account? No, if not, here's a bank that'll give you 50 bucks for opening a checking account. Do you have credit card debt? Yes, then here's a consumer credit management. Whatever you can do, financial wellness, legal wellness, do you have it, are you eligible for an expungement? Do you have a misdemeanor conviction that's more than five years old? Hey, is it not a DUI? Hey, here you go, jump into this. Things like, but you can come here, there is Docubots here at the bottom, if you see on this, it's just a one page site, but you can come here and then play with Docubots. Well, you can click on the buttons or play with Docubots on this site. Let's see what can do, see if he got that. So, here's the list of Docubots. You've got that. My goal is to make tools, and I shouldn't say our goal, because Vince has guided me, as you see, he finds all the kernels that I'm big picture, and we need big, small, and then on also other opinions, outside of my own and Vince's, that's why we're reaching out to this community, is we wanna make something that works, that will be you. On that note, I'll jump in here too, and I don't know how the other invitation is going, I don't know if anybody chose to submit anything or not, but on this one, a little easier invite, go there, and I call it tricking the robot, and you know, you gotta type something somewhat sensible, but when we started out, the thing wasn't nearly as smart as it is now, and it's still a baby, fair enough, I think, but it's getting smarter. What can do? It wouldn't have caught that a few months ago, I don't think, or at least about four or five months ago, and it caught that. It pulled that up, right? It got your N-O-N instead of N-O-N-E, I noticed earlier. So, the more people participating or using it, the better, well, at least the smarter it gets, and I like when it gets flustered too, because it's a funny dancing robot. Jason, is that a fair invite or no? Absolutely, absolutely. I mean, it is, I will tell you that, with all sincerity, I mean, we're working, this is kind of pioneering type of stuff, and the people that are getting involved are the people that are getting more of a say, because if we look at it, it's like, hey, that's a great idea, gee, how can we, we're not so set in our code base that we're saying, hey, sorry, we cannot make any changes. We are trying to be agile, but over time, you get less agile. That's just part of the unfortunate world of developing software. But right now, if people think that this is interesting, I welcome any communication, and we're here wanting to make it, not only user-friendly to the public, but we want to make it user-friendly for the technician, for the developers, the LSC developers, because everybody, there is a lot of programming that is going on historically. That's why I love the LSCs have been trying to do this job for a long time. And if I can give or we can give them a tool that doesn't tell them to scrap what they've done, but it allows them to bring that logic over, to bring the coding over, I think we can do great things, and that's just where I'm coming from. Right on, right on. Hey, man, we were talking earlier, and I don't know where we're at on it, but we're able to push some of this on the intakes and the diagnostic tools to a case management system you successfully have got it into Clio yesterday. Is that right? That is correct. Let me, we have a Zapier, so we have an API, I'll go to the open API, so we're building a, we can just jump to Zapier. You want to jump over Zapier? Yeah, I mean I can just talk about it. We, I mean only recently have we started opening up our API. We've been working on kind of standardizing certain things, but we recently opened up certain pieces of our API so that people can now automate these connections. We discussed actually building integrations to each of these services, but there's just so many out there that it's pretty difficult to keep everybody happy. But the good news is that there's things like Zapier and you know tools that help connect services online and they've got tons of integrations and so we've been working on our end to get some, some of our API functionality into some of these services in particular Zapier to begin with and from there you can then automate the integrations that you need as opposed to us trying to guess where the best place to put our resources are. Right, yeah. And that's kind of a, again going back to hopefully the sincerity of what we're trying to do is we, we want to help the community that is at, you know, kind of at large to let's see, let's pull up a tray. And, you know, and part of what we believe is giving people tools to use the way they kind of, you know, look to use them. So you can see here that these were some tests from yesterday, the early ones. So one law call app with Trey Richard, the call it gives the start time, the end time, the notes. Over here, you know, here you can see this is what I would, I typed in. Obviously we will look at, you know, final integrations of the document. The document, when documents are done in DocuBot, the user, the user can receive the copy. The LSC can receive, it depends on how you want to create the flow. Sometimes people want to actually have the document, you know, okay, it's ready for you to pick up here because there may be a requirement of funding that they, you know, come to a physical office, but that it can be printed from the phone as you saw me do the power of attorney or emailed from there, or it can just say great contact Jason over here to get a copy of your document. Let me take a look here. Let's see, I'm just looking for, I was actually the first zap. And let's see here, I'm just going to show, let's see if it matters. And by calls and zaps, we're talking about just talking to each other, the database, the application, is that correct Jason? Correct, so basically the idea is, whatever happens on the app, you shouldn't have to go input that into the CRM. It should just push over. It would be Jason Bell has created a power of attorney on 329 at 1030 Pacific or whatever, you know, something along those lines. Absolutely. Well, and to think about that, just as someone who's done a lot of automated documents and a lot of pro se and assisted crochet work to have a log of that. Now, of course you could strip any identifying information that you need, but that, you know, this document was completed at this point at this time and have a log of that. I think it's pretty amazing to have. While we have Trey on the phone, let's talk just a little bit since he's primary developer. You mentioned, you know, how we're working in Swift and on the server side go and with most of the client side stuff and PHP, HTML and PDF output, along with the inference engine that we're using, which is currently using IBM Watson, although we're thinking about some different AI aspects, but also wanted to, so maybe Trey could speak a little bit about that environment, but also mainly wanted him to address the security output and input both on rest and on pushing the encryption. Currently, we're using buckets on Amazon, but Trey, could you speak to a little bit to the effort put towards security? Yeah, so I mean, starting out, obviously, you know, we want to just hit all of like the low hanging fruit as far as security is concerned, make sure that there's no transmissions over the wire that aren't encrypted and, you know, make sure that we store all of the sensitive data in encrypted formats and, you know, just make sure that we knock out all of that stuff to begin with. Then, like you said, most of our architecture currently is housed on Amazon's cloud services and uses a lot of the built-in security features that they've developed to try to keep this stuff secure, but a lot of the stuff that maybe people might not see initially or like we never provide a raw link to any document. It's always a short lived link that will expire after a certain amount of time so that there's never any like any personal data floating out there that could just be scraped. I mean, I don't know if there's anything specifically that you're looking to hear about the security on, but we definitely try to make sure that all of the sensitive data is encrypted at all times and all data is encrypted over the wire so there can't be any snipping going on. Yeah, that was about it, man. I appreciate it. I appreciate the work you've done on it, too. There's a bunch of paranoid freaks here in legal aid, man. Just let me know how we are. Well, then that's one thing to speak to that again, talking about, and the standardization is not the right word, but maybe some best practices. I think with Docubot and going forward, we are going to be able to move people into a more closed environment, into a password protected environment, and you don't have to. That's all you can see. I went right to a website. I didn't have to log in, but we have the functionality to allow it to be password protected. Again, going without the clicks, allowing that to embed or to exist on the LSC website. That's part of these Drupal integrations and otherwise, but I think that is some smart behavior in this world ever growing. I mean, heck, they just said whatever. I mean, our internet search history is now going to be sold for even more ads or whatnot, and I like the idea of especially around legal documents and legal conversations to password protect that, to have them step through the door. They don't need to start there. You could do the whole document and experience, and maybe if you want to actually receive the document, you're going to need to verify yourself, and maybe I'll show one more teaser for the fun one. All right, you're all on. That's definitely an interesting conversation to have in the future is what type of access controls are those type of things. I think that there is also some argument for allowing users to use products anonymously and then ask for data to be destroyed at a certain period of time. The more data that is being collected, the more chances there are of data leaks or security violations. If there's data destruction policies that enable information to be removed, that has a positive. On the other hand, if users can create accounts that keep consistent variables, there's data integrity issues over time, and it can make filling out future documents much easier. In the Civil Legal Need Study that we did here in Washington State, we found out that most of our low-income clients have an average of eight or nine legal issues and being able to address multiple legal issues with accurate information that has already been entered on another document could have a very positive effect. But once you start storing that data, the security things that you are already putting in place, best practices, are essential for keeping client data safe long-term. So a lot of stuff to think about there and very important topics as we move forward in doing more of this type of online service through AI. No. Well put, Brian. I'd also, some of the data that we are looking at, we don't really need identifying information, but the data on which choices and which branches to teach the AI. And then the user selection of like, wipe my data. I love that. I look forward to that future conversation, Brian. Well put. Oh, the driver's license scan. Yeah. I just thought this is just a fun one to let you know where my mind is. But so driver's license scan, this is in our app and it says, start scan. I just wanted to, I'll show you here. So this is my license. And then I turn it over and leveraging the information on the back of the license there. You can see I just pulled all of my info. And so think of how valuable that is in correctness of it. So now if we have people start the automated documents by scanning their license, their ID, their matricula consular, I mean whatever we want to do, that can really, one, we're saving steps. We're probably reducing typos, assuming the information is correct. And we can validate and ask them if it's correct. But that's where it's going. These are things that are fun tools. Did everybody catch that? Did I go through it too fast or did that come across? No, I think maybe I've just done it so many times. I love this. I use it because I always misspell people's names and clients' names. And it's so quick, boom, integrating that into the automated document platform. Hey, we got a couple of minutes before questions. Yeah, that's what I was hoping you would do. And so that app, one law right there is, yeah, open it up, man, or another aspect. We're really, we see this as a platform. So the automated document aspect is a huge aspect. But documents is just one aspect. Lawyers do at least three things. They talk, and they write, and they're supposed to think. So again, this is a huge component, but only one part of an AI automated platform. And that's why I was thinking of that whole term that we talked about in the beginning, an onboarding agent, if you will. So are you going to show them around one law real quick while we wrap up? Sure, sure. So I didn't mean to, I mean, I guess we're here, so I guess the cat's out of the bag. So basically, you know, you jump in, again, as my belief in the messaging being the important part of this whole thing, because people are very text chat savvy, is that that needs to be the core of the document, or core is not a document, core of the environment. So we can see here, this is just an easy way to add a user. So this is, I'm just going to throw in, I guess I could do Brian's and think about that. But I've already thrown that one in, but I threw an email, it knew who I was. Once that person is in the environment, it is going to now connect them with, it can be an attorney, this can be an LSC. So this can be, this entire process is white labeled. When you have an attorney, you see you have the function to chat with them. It could also be a client though, and you're protecting your number and everything since you're in this environment. Yeah, it's all password protected. I'll show you one of the sexy features right next to my attorney is my file. So now, normally clients will send images, because they're basically pictures, right? They get a document in the mail, so they're going to send a picture. So then that can be the pictures that they've been sent, or as the attorney, you're going to send them files. So you're going to send them, I'm just hitting this in new document PDF. This was a filing. So this is where we see it going as far as interacting there. We have resources. Resources can be just information. Again, as I mentioned with the videos, what to expect in a scenario. You can put in stuff from a website. This is all easy to grab and can be pointed wherever we want to. Sure. We're going to do a little demo. This is going to hit me up so you can see what it looks like. I'm actually going to go to see my phone. It looks like I'm getting a regular Apple call there. So I will jump over. I'll log in there. And then we might get a little feedback, because we're in the same room here. But now I'm talking to Trey, and I'm plugged into the computer, so we're probably not going to hear him. I'm done. Now I can put the notes in. Call from Trey Richards. Save that. I will get an email saying, there's my email, my one law, your call. Here is the details. Caller's name, phone number, the state, and the notes. Of course that can all be customized to the LSD. I don't know if you can get it. I don't know if you can get it. You can get it. But if you offer, offer a white label version of the app. So people don't have to feel like they've invested in, you know, our particular product. Let's, I want to see how. I don't know if Cleo is going to get it that quick. It does sometimes. Yeah. At least a four minute. I think. Our system. Oh, yeah. Just pipe up. Yeah. Yeah. Yeah. Yeah. Yeah. We provide adequate time for the attorney to type any notes before it gets loaded into their CRM. Our system set on a 30 minute delay. Gotcha. So. Yeah. So all the stuff will show up in like your. Various CRM's 30 minutes after the call takes place. And if you don't type your notes in 30 minutes, then you need to get faster. So I'm going to go through it real quick before we go to questioning. So as Vince mentioned at eight 37 this morning to the project, two hours ago, he sent a submitted a document through the submission tool. And if I go over here. And so you could go to the Facebook or wherever, you know, it's it's then. So if I were to type here. Quit claim. Perfect. Let's get started on a quick claim to you. What's the full legal name of the grant or the person buying or selling the property? Then you go here. You can see where Vince's first question. What's the foot is a full legal name of the grant or the person buying and selling the property. So that it went from submission to and that was done a little bit ago. So we're running out. We got a little, you know, there's some latency right now. We're getting it, you know, it's going to be quicker and quicker and better and better. But that is that, you know, that's what that's what's happening. You know, so for people that are interested in getting their documents submitted and, you know, and working with this and we can, you can see my little icon here. We went with a neutral icon because we don't know if the person is male or female. And so instead we tried to be originally it was just the default and, you know, kind of not thinking the default was a male icon that still exists in some of the places. But we've moved to this more of a neutral to try to be friendly, you know, just kind of showing that and that was actually something that one of the, I don't know if they're the LSC or, you know, there's, I don't know who funds them, but one of the groups made that comment and we were able to integrate because somebody told us and because people were actually using it. So I don't know if it's question time or, you know, any. Actually, one last thing if we could just have one more minute. Is your phone still up? I'm getting it up. I would definitely also want to invite people to start typing in questions if they have any in the question box so that we can read those off here at the end. Additionally, if there are features that you have questions about or things that you think that this could do that you please also type those in. Awesome. Great. I hope you'll do. I think we just missed a step there. You showed the messaging and all that and you're getting the documents and the driver's stand. But if you could pull up the Uber of law, if you will, real quick so we can just give them a preview. We don't have to actually video conference. But, you know, the map. Right. Right. So this is something that and it's open to any legal aid org or any do go to work. And what you see here pretend like they're little Uber cars, but they're lawyers, right? So, uh, well, there's Lee Richard's Arkansas and Arkansas. Yeah, yeah, better go to California, man. So you can actually find the lawyer closest to you or the legal aid closest to you. And here you have the option within a secure app where you could do a video conference call and there's all kinds of reasons, you know, to do so and so far as learning and taking in what you're hearing. But, um, there I am. And, uh, but even if not, you can still contact your text or whatever and then stand that driver's license, upload that document and have that intake so much quicker. And I don't know any legal aid attorneys out there like getting them to return, uh, you know, your, uh, statement of citizenship or anything like that can take weeks and weeks if ever sometimes and, um, it can be done almost entertainably. Really cool thing off legal aid topic though. You select one of those dots on the map and you do go ahead and select your attorney say, I know Vincent Morris, I like him. I'm going to take him as my go to or your legal aid or whoever. And then if you do have a need and the attorney is receptive, um, you could have a video conference call in some really heightened, um, situations, uh, just thinking of the last couple of years where there's been interactions with maybe the police or with anyone imagine being pulled over and able to just press your attorney automatic video conference and, uh, recording and witness of a traffic pullover, um, little off legal aid topic, but just showing the platform that all these tools can plug into. So that was the last little bit. I wanted to show, um, Jason. Perfect. I'm sorry. I was playing around here. Um, yeah, I just, just, just to speak to that one final thing. I mean, we are, uh, looking and speaking with, uh, you know, different with the, you know, the, you know, the way the Mexican consulate works every state in Mexico has their own kind of consulate. And so we're speaking with a number of those in the Los Angeles area to essentially provide what, uh, Vince just said, right? Somebody's knocking on the door and you now have access to somebody that can walk them through asking them, cause it's not, it's more, almost like more support really, but hey, do they have a warrant? You know, hey, what is the, you know, what's going on? You know, that type of thing. And, and that is, is where it's going. I mean, you know, the, the virtual practice of law, you know, when we're talking about serving, uh, under, uh, you know, under served or lower economic or people economically challenged, why are we making them spend gas to come down to an office when we should be able to provide almost all of it. And I'm a big, big believer in them. The E notary, uh, which is I think in about 20, no, it might not be 23, might be 13 or so states right now, but if people can notarize documents over a platform, there's really not going to be a whole bunch of need for, you know, in person, unless there, there's a reason for it. Right. If you're preparing someone for trial, you probably want to do it, you know, in face to face to kind of read them a little better. But if it's just a matter of document collection and, and giving a better comfort level, you know, I believe that the virtual experience is going to suffice. And that's, that's where video, that's where chat is good for gathering information, creating that closeness. If you would, that's what video is for. But I mean, that's a whole another. I didn't mean to, to, to go off topic. And I apologize for that. Yeah, brother Jason just went off on the notary, but I mean, let's just leave it with imagining someone knocking at your door and we can be there as attorneys or as any support system when needed with the documents available immediately or just the voice of advocacy. So I think that's amazing, brother. Good work with Los Angeles and Mexican consulate there, man. Anything else before we take questions? No, I'm sorry. I would just sit back became a listener. Sorry. No, I'm good. I'm more than I think I've spoken too much. Well, Brian, thank you for the time letting us show off some of the work we're doing. We're super excited about it. Highly collaborative. So we hope some people might be interested in, in dancing with the robot. So if people are interested in collaborating, collaborating with you or giving you a try, what is the best way for them to get a hold of you? Excellent. Jason, actually, I did want to address this. So they could go ahead and download the WordPress plugin. The Drupal is going to be a little bit. They can go ahead and integrate Facebook, correct? Yeah, they can. They can just, the Facebook, they can just, I just put my email there that can be forwarded with the Facebook. Really, it's just reach out to me and what they would like to see. You know, what they're, what they need because it's on Facebook. You know, you need to give them an app for their web, not websites, excuse me, for their Facebook page, for their LSC or they can just go right to the AUX Facebook page and put the stuff there and that's really what I'm trying to do is, is hopefully have a little bit of a community. You can see I've put our, there's the Facebook, Twitter at AUXAUX, they didn't have AUXAI on Twitter, but so, you know, we're just kind of getting going that people want to show us some love or communicate that way, that would be great. I mean, I think I got three followers on Twitter, it's pretty new, but there's email and then, you know, but it's just, you know, I'm pretty accessible. This is what I do. I still practice a little bit of law, but not much. I really am spending full time developing the stuff and, you know, it's exciting. They, you know, they've kind of made this a collaboration with Vince and, you know, it's good stuff. And Jason also, oh, I'm sorry, brother. They can download the OneLaw app, actually, from the Apple Store and for Android, correct? They can. They can. I mean, I didn't want to be gratuitous about that, but I mean, it's, you know, they can, I think if they just go to any of the sites, I mean, it's not hard to find. Jason, I got to indoctrinate you, man. Lee Laid, dude, we pirate and take for free and it's all good if you're out there to play with, man. I'm more than willing to be, you know, pirated and I've been inviting people for a while now. It's not, you know, I will pull on and, you know, let them check it out. So, and one of the reasons that I'm sorry, I'm just going to say if you do the WordPress plug-in, you're going to need the key, right? You need to contact Jason, the holder of the key for that. Or, yeah, either of us. I mean, you know, but, you know, just, you know, we'll get it. There's not, it's not difficult. I mean, we can just send them one. What we like to do is just, you know, know who's got them so we don't, you know, so we know that, hey, this is a real a real person. It's just a little bit of quality control, right? I mean, because it is, you know, something that's still in the good faith realm and we're probably slowly moving, you know, a little bit more to just, hey, you know, we've got a lot of documents in there and but it's just fun stuff. I mean, this is what I enjoy. Well, thank you guys so much for two additional resources. I want to make sure that people are aware of. We have a email list through LSNTAP that is specific to AI that I'm going to drop a link into and we can get people added to that. We are also doing another full webinar on AI related topics this fall. I'll drop a link into the chat there and we'll have it in the about section. This whole discussion has been recorded and will be up on our YouTube channel as are all of our past trainings. One of the things I really like about this is the best practices that are coming out of this so that anybody who is developing these types of technologies can have a leg up and learn from what is already being put into this project to use on other projects also. Thank you guys so much for coming out here and doing this demo for us. If there's any questions, please feel free to drop those into the question box at this point but we've covered so many different topics at this point. It's been great. Thanks a lot, Brian. Appreciate you man. Yes, thank you.