Video: The Logikcull Intake Portal: How to Receive, Assign and Track Requests | Duration: 2052s | Summary: The Logikcull Intake Portal: How to Receive, Assign and Track Requests | Chapters: Welcome and Introduction (13.245s), Webinar Introduction (155.365s), Request Management Overview (273.405s), Portal Request Demo (505.53s), Agency Request Processing (775.365s), Portal Customization (1065.505s), Form Customization Options (1187.47s), Routing and AI Features (1394.71s), Multiple Requests Management (1533.66s), Session Wrap-Up (1791.58s), Closing and Resources (1935.85s), Closing Remarks (2030.632s)
Transcript for "The Logikcull Intake Portal: How to Receive, Assign and Track Requests": Here we are. Hi, everyone, and welcome to the first session of our four part webinar series on Logical for Public Records. I am Laura from the Reveal team and I'll be your host for today's session. And, if you work in public records, which probably most of you do, you you probably don't need us or me to tell you that managing requests is getting more and more challenging. Volumes are growing exponentially due to AI and the social political environment. The information you need to respond is increasingly complex, and deadlines are not moving for the most part. And for, many agencies, all of this is happening without, additional staff or resources. And in some cases, we're hearing about budget cuts. So in some cases, even fewer resources than what you used to have. And one of the biggest challenges apart from these that we hear about is just how fragmented the process can be. You can have one system to receive and track requests, another set of tools to collect and search for responsive records, and then often a very, manual process to review, redact, and prepare those records for disclosure. So that is the very problem that we're solving with Logical for public records. We've brought request management together with Logical's powerful collection, search, and review review and reduction capabilities so agencies can manage the entire process end to end in one connected workflow. And with that, you would get less manual work, fewer handoffs, better visibility overall, and ultimately faster and more accurate responses. And that's exactly what we... We're gonna be exploring throughout this series. And today, we're starting at the very beginning of that process, intake and request management. And to walk you through that part of the process, we have brought together Daniel Schuring, our principal product manager, and Jason Christian, our principal strategic sales engineer. They will run a live demonstration and show you how all of this works in practice. And we will also leave, some time, throughout for q and a and also a little bit of time at the end. So please feel free to submit your questions on the chat on the little q and a section at any time. And with that, I'll hand it over to, Daniel and Jason. Thank you, Laura. So let's take the way, Jason. So thanks you everybody for joining today. My name is Daniel Schrodinger, the principal product manager at Refill. As you might hear, I'm lost from the, from a different continent, based in Amsterdam. And also here, we have a lot to do with, FOIA requests and basically the same process as we see in The US. And so I hope to bring a little bit of international experience to this webinar today. As we already mentioned, we have four sessions because I think if we have to go through the whole process and explain everything in detail, it will take a very long time. So I hope you will join us also for the other sessions that we have planned, today about the intake of request, leveraging the, FOIA portal, what you call request, where we will give you a detailed demo from. On November 10, we have collect and find as a session to, show you how you can easily collect data from various sources and, quickly find the relevant data that is part of the request. Of course, very important is also the rejection part. We don't want to leak any personal data, so rejection is a very important part, and we'll dive into how you can easily automate your reduction process. And the last session, of course, is, disclosing the information, producing the information to the requester. And we have a very nice solution for that with our reading room, but also the way how we handle productions and create productions will help you in this process. So don't forget to register for all these other webinars. And I think we're all here with experts in the field, so probably this is quite familiar for you. We get requests from various, directions. Also, like Laura already mentioned, a lot of AI driven requests recently. So we see this request also get longer and longer, more extensive, and we need to, yeah, be able to handle that. There are various laws, definitely in The US, but also here in EMEA. We have various laws. Every country has their own FOIA law, so to say, with, certain regulations, deadlines, and other items. And, of course, yeah, there are always these difficult requests that you need to, take care of, which can be really large requests, but also requests which are duplicates, which you want to prevent to do duplicate work, of course, but also you want to make sure that the request you're getting in as an agency, that those are very clear and specified. So it's easy for the agency itself to find that information and deliver that to the request. So today, what we will show you in a live demo, our public intake portal where requesters can submit their request. We'll talk a little bit about how you can, create your own custom form so that, you get the information that you need from the requester. We'll talk about deadlines and reminders. You can set it open how we help, you meet the timelines and make sure that we have, reminders for certain requests. It might take a little bit longer. We will talk about routing, automated routing, and also assignment of requests to, certain officers or certain departments within your organization, deflection and, communicating with the requester. I think also very important parts in this whole process. That is where you basically decide how large the request can also be. So, it's very important always to have a proper communication line with the requester to kind of minimize the request. At least that's the strategy that I see here in EMEA a lot to communicate with the requester and see what they really, really need because, yeah, like I said, requests are these days built a lot with AI, and those can be very extensive. And some people think the larger the request, the better. But, yeah, it's really important to understand what they really, really want to know and what type of information they request. So, also, we'll talk a little bit about that. What we're going to show you in the demo is, we're going to submit a request as a citizen. I will do that. So I will be, making a request today. And then Jason will take over in the demo and show you how the request will land in the dashboards that we have in place, how to accept the request, assign it, and go basically through the process until you have set up a project in our what you call ediscovery solution, where you can start collecting the data and filtering and, in the end, redact the data, which will save this last part for one of the other webinars and also show you a little bit how you can customize the portal and, yeah, set up the proper branding for your organization. So let me start, with the actual demo. So what you'll see is here, a browser. And in the browser, I have over top here at the portal. This is our demonstration portal, review foyer. And what you see in the middle are three main tiles that we have where as a requester, I can request documents. I can also track my request so I can see the status where my request is in the process of the agency. And what we also have is a document room or reading room, where we will store all the documents for... From on the request or from specific request. That's up to how the organization agency decides on how to do that. So let me start with, request documents. So what you'll see here, I will open up the submit records request option as a citizen, and this will ask me to fill out some information. And in this case, the only required information is the email address and the full name, but you can define the form as you like. That's also what Jason will show you later on. So a few optional items that I can fill out. Also selecting, for example, target departments. So, for example, if you want to do, go for the planning and billing department, and you can fill out a description of the records that you would like to see. So I just stated here my request that I would like to see some email communications. There's one thing that we can help, with, for the person performing the request is that we can help refine the request using generative AI. And what you can do as an organization, as an agency, that you can define your own prompt, your own rules, how a request should look like. And based on that, those rules, we will give advice to the requester on how to improve their request. For now, I'll just skip it at the moment. But if you are interested, we can give you also a personal demo how that looks. And, of course, you can add supporting documents like, files. Next step is that I can review my request, and then I can submit the request. Everything which you see here is customizable. And one thing that we don't do is that we let the user create an account. So there's no no need for people to create their own accounts, but what we want to do is make sure that we act... Have a real person. So we want to have a verification. And what we'll do is that we send the requester a verification code so that we know that this is an actual person. And only after filling out the verification code, the submit... The request will be submitted. As a requester, I can also track my request. So I immediately go to tracking the status, and every request gets a unique number. Of course, after I have submitted, my request, I will receive an email, from the agency that the request was received, also with the code in here. And I can always use this code to track the status. And you will see here the request progress. Right? It's now submitted. You see here the description. But, also, you see here the option that I can actually send here an additional message to the agency. So if I have additional requests or if I have any comments, Yes. So always... We say re up. That's probably what you hear as well. When do I get the documents? I can just send here, use the portal as a way to communicate with the agency. So there's no need for emails and storing emails, and one of three mailboxes. All communication can go through the portal. And now this request ended up, with Jason. So what I will do, I will stop sharing my screen. Awesome. And, then yeah, Daniel. Thank you. And I think this is where I will take over and bring you into the other side of the persona here. So as you guys can see that Daniel took on the role as the request or as the citizen, I'm going to be jumping in and showing the portion of the portal where I am now one of the FOIA officers wants to... In taking the public records request for the actual agency. So I'm gonna come in here and I'm going to share my screen with you here really quick. So what I've come into is when I've logged in, I have come in as the dashboard so I can see all of my requests that are in here. And the request that Danla just put in is right here. And so this has come through the agency. I'm gonna come through. I'm going to click into this one right here. So we have a request. It has been submitted. This is the current workflow, the status. What we're going to do is we're going to start the review. Right? And this has also sent a notification out to the requester saying, hey. We've now received this. We're gonna start looking at it. Okay? Now we have two options down here. We have accept and process requests, and we have decline requests. And I'm actually gonna address this right after I kinda go through a quick workflow because we understand in public records, a lot of you accept all requests. There's no decline. Right? There's no exemption to this really quick. Once you come through and accept a request in here, this is gonna bring up an automated email template, and we're gonna talk about in our settings yesterday... A little bit later. So you can come in, customize, and you can configure actual messages that have already been prebuilt to be able to say to the requester, we have your... We have received your request. It is within scope. We are going to start work on this request. And so you will come in, email template fills it out, you're going to send the request, that has now changed our workflow to agency review, and now the, requester hasn't been notified of that. And to show you really quick, we're gonna talk about some internal notes, but let's look at messages. Messages are between the external requester and the internal agency only. So a couple things is, as you can see, requester Daniel, citizen Daniel, told me to hurry up. My automated message went back to, him to be able to say how long we're going to put... How long this is going to take, and we're going to start working on that. And we can certainly put more questions in here or have more correspondence back and forth. But meanwhile, we're going to start work on this. So we're going to add some internal notes. So first of all, we're gonna come in here and we're going to assign an officer to work this. You can assign as many officers as you want to this. There's different levels of permissions, and we'll be talking about some of those permissions in a later, in some of the later webinars that we have in sessions for this. But I've now assigned, William Fenton, the officer, to this. So I need to communicate and let him know, number one, he's been notified he's been added to this, but he needs instructions. Right? So we're going to come in here and say at William Fenton, please begin collecting Philip Allen's email and process in Logic hall. You can add this note. So William Fenton has now been notified and has now received this, has been given specific instructions to collect email and to go into LogiCal and start processing this data, which brings us down to what we call records. And this is where the integration of the portal and LogiCal call come in. And a quick thing to kinda add to this, when it comes to FOIA, public records requests, DSARs, logic call has been around for a very long time. We have been doing search. We have been doing redactions. We have been building productions, deliverables, requests. Right? The piece of it that was missing was this portal request, and now we have the two talking and working hand in hand. And so the next step is this, is to create a project in Logical. Okay? You're gonna get a project name, fully customizable. This is a template that's built as well too. You're going to be able to pick a template. So if you have different jurisdictions or different departments within your school, your template in LogiCal may look a little bit different. We want things to look different. You might have redaction labels, you might have auto redactions, you might have particular users, particular officers that should be a part of that project. Templatize all of that so you don't have to recreate that wheel. And we're gonna come over here, and we're going to create a project. This is now creating a project in Logical, so I could come over, I could click here, I can take either the data that I have collected, or if you have Office three sixty five, or if you have Google, we can go directly into those and start processing directly into the project. Okay? And so this really is the intake all the way up to starting the project in a logical to be able to process and get all of this going. So what I'd like to do now is now take a step back, and I wanna jump into some of the settings here and look at some of the magic that has kinda happened behind the scenes here a little bit. So I'm gonna start with the general really quick, and I'm gonna talk about branding. So number one, obviously, schools have their own branding. Cities have their own branding. States have their own branding. We can put the logos and everything that are in there. You're going to have a website. This is the URL. So you can actually put this URL into your website when people come in to actually do requests and put things through in there. But one thing I wanted to show you, and I kind of, pointed this out, is auto accept all requests. We understand that not everyone is... Has the ability to decline or to be able to say there's an exemption here. We are not gonna go forward with this request. Auto accept the request. What that does is that eliminates the start review, and that eliminates accept and start working. Right? So we're eliminating some clicks for you, and, automatically, we're just going to accept those. So if that workflow fits for you, just know that we can do it. Going into branding. Right? We can brand the whole look and feel of this portal. Remember, the school has branding, the state has branding, the city has branding. We can go all the way down into how it's going to look into the color, the actual look and feel of subjects and emails going out, all of those tiles. You saw Daniel submitting a request. You can give the look and feel to the buttons and the feel of requesting documents, tracker request, and search that document room. All the way down, tracker request, the portal text. Right? All complete look and feel, and I think you guys kinda get the whole, you know, point here is we can absolutely brand this. And right now, these are the Englishes, the, the languages that we do support. I do know Spanish is gonna be one of the ones that are next. We have talked to a few customers where they get requests in other languages and just know that we're gonna be look... Working on that and adding to that. So that is branding the look and feel to all of this. So on top of this, coming into the request form, we mentioned that the request form is fully customizable. This is how we've configured ours, but you can come in here and add as many fields as you want in here. You can make them required. You can make them optional. Right? So you can customize your form all the way through. All the way down to target departments, you'll see that our requester had the ability to add a department, and you can put the various departments that are in here and be able to do that. And the description of records, this comes down to helping with clarification, and Daniel kinda pointed this out. The requester is going to put here, hey. This is what I need from you. We also have an AI piece to help you give a better description of what's needed so you don't have to go back and forth on clarification. We have some we have some agencies that have twenty four hour deadlines. Some are allowed to pause the clock if they need more clarification, and some are not allowed to pause the clock, if they need more clarification. This would be helpful, and so is turning on that AI as well too. And then diversion rules. This is actually very cool. So the diversion rules is maybe a particular department for a request was picked incorrectly. You can put in a trigger phase. For example, a nine one one tape. We're asking for body cam footage, but they decided to give it to maybe the, city administrators or the city clerk's office or something like that. Well, we're gonna give you a message that says, yeah. You probably should have sent this to the police department, And what we'll do is we'll basically send that statement back, send that message. We also have the ability to reroute that for you, and then there'll be another session where we actually talk about adding locations, customizing locations, and being able to route request accordingly to different departments. So that is customizing the form that's in here. We also talked about the email templates. If you noticed, when I accepted the request for the requester, the request confirmation, there was the verification code that he had to put in, but coming into here and being able to say, verification code that he had to put in, but coming into here and being able to say request accepted, this is the one we saw. This is the one that we sent out. But you can see all the customization, all the messages that you can see in here and put all the way through. So fully customizable. Don't recreate the wheel. Build the templates in on top of that. And, of course, what's most important, everyone has different deadlines. Right? So you can put in the various jurisdictions of where you belong, where you are, different cities, different countries, different states. We can come in here, your response deadline. What is your response deadline? If you're allowed to give extensions, how long are you allowed to give extensions? Right? The notifications being sent back. Hey. This is gonna be due soon. Officer alert thresholds. In five days, we have something coming up. In two days, this is due. In one day, this is due. Escalations. Right? If you have any requests that are overdue, do we need to set an escalate... Escalation to be able to do this? And then being able to set a clarification pause, per request. Right? So if you need to pause a request, how long can you pause this for if you are allowed to do that? And then, of course, holidays. What holidays are observed, and if there is a deadline, we can come in and put on a holiday here so that part of the deadline, these are not taken into factor for the particular deadlines that are in here. Routing rules. We talked about routing here a little bit. I just wanna jump into this as my last here. So what the routing does here is number one, we can assign officers in different departments, but we can also automate a routing role. I'm gonna show you some templates here really quick. So if you have multiple jurisdictions like a city, if there are any trigger things in here, basically, you know, if we see the word body worn camera or body cam, body cam dash cam or anything like that, these will automatically reroute that to whoever handles those, probably the police department wherever these are being stored. So if a request comes in and you have multiple jurisdictions, right, so these could be rerouted to public works. This could be rerouted to the city clerk's office. This could be rerouted to legal. Right? The city attorney's office. You can build custom rules to automatically send these over there because the officers and the people involved are gonna be completely different. Daniel, are there any questions. that I need to answer or any other questions that we have in the chat? Because we have about five minutes left in this. Yeah. We do have some questions, and I left these especially for you. There's a question about can logical get property deeds? And that's probably more US specific. So probably you know more about was than, I do. property? Well, say that one more time. I apologize. Property deeds. I hope I can put it on screen, I think. Can I put it on screen? Okay. Can logical get property deeds? Well, yes. Probably. So we do have some AI built in to Logical. We have a couple different types of AI. One is what we call Ask. Ask is our generative AI. It's the ability to ask natural language questions. Right? So if you're looking for a property deed, a deed number, a deed that belongs to somebody, what you can do is you can ask the natural language question, are there any deeds or any deed numbers that are associated with this property and see if anything comes back from that. And so that is an additional option to add to logical, but will give you some power to kind of be able to ask natural language questions to kind of interrogate your data to get a narrative or a summary back. Yeah. Thanks. And I've seen another interesting question, which I think is a really good question. It's about that there is coming in one single request, but it has multiple topics. So, basically, it's one email request with multiple topics. So I don't know. Maybe we can solve that with, splitting the request and creating additional requests for that and using the manual function and to to set up a request. But I think also this can be overcome this by using the AI assistant. Also, the way, it inspires people to put in one request, one single request in one. email, basically. Yep. I would say in its current state today, if you do get a request that has multiple requests across multiple departments, it might make more sense to answer them individually. Right? And so with our current current ability, a, you can turn on that AI assistant to probably help guide the request or put in a good request. We also understand that not every requester puts in a great request. Know that you have the ability to automate... Put in your own request here as well too. Right? So right now, there might be a little bit of manual, but you could break that single request up into an individual request. Right? So if there's four or five things that have been asked, you have the ability to put one in yourself, and you can come in here and fill this out. So then you have... So for... Let's say it's four or five requests, you have four or five distinguished tracking numbers going to specific departments so that you could organize this appropriately internally and get them to those departments and get the right officers on them. So those four or five requests aren't gonna be handled by one officer. They're gonna be handled by multiple people in those areas. Yeah. And I think the dashboard, you can easily track that because we can filter by requester. So you can have a clear overview, of how many requests there are per requester. So I think we have... Yeah. We can probably organize it like that, I think. Yeah. Are there person other... is asking... Yeah. The same person is asking if they can all be rolled up into one project in logical. Those multiple requests that may come from a single one. Yeah. So it's something we've been talking about because right now it's, what you could do... There's a couple different things you could do. It's always gonna create a project. So instead of submitting the collection through here, it creates one project. Right? And so when you drag and drop the data, what you could do is you'll just create what we call another upload. Right? Another processing job, and you can bring those into there. And there are ways when you upload the data, create projects, we can put we can put labels on them. Right? They may have different, tracking IDs. And so what you would do, if you're familiar with Logicals, each one of the labels could be their own, tracking ID, and then you can put that on there with the upload and put that into the, platform. Yeah. I just think we can link multiple requests to one single project in logical, so Yeah. that might be a solution as well. Can you... Shall I share. my screen again Yeah. for. Yeah. the last slide? it. We have a little bit of buffer. If anyone needs to jump off, obviously, they're welcome. But we have a a few more minutes, to cover any additional questions and for Daniel to show us how that works. Yeah. So this is actually the request that I put in earlier. So you'll see that now the, request progress is updated. So we're now in the processing stage as Jason now took on this. And you also see here the message that I got from, the agency that they received the records request, and they will, start working on this. So that's all there. So we've gone through, the demo. So we've shown you the the portal, the deadline reminders, how we can do the request deflection, the custom forms, routing, and request the communications. So I think that was all covered in this first session, the intake part. You see... You've seen, what Jason just showed is that it's a very flexible system. So it's really built for basically any type of law. It's also built with the, let's say, other countries in mind, Canada, and all the European countries that have the same sort of laws related to freedom of information. So it's really customizable for all the needs. Basically, every type of request that you have, we should be able to fulfill that with, the customization that you can do yourself. And so that's really something that... It's self-service. So that's something that you can do yourself. There's no need for us to go into, the back end to do stuff for you. It's really a self serve solution. So like you said, we have four sessions. We have now covered the intake. So the request arrives in the portal, and we have now a request that is being tracked and assigned with a deadline, and, we will have a project ready and logical to start collecting all the data. So our next session will be November 10. I don't know, Laura. The links are up there. Here's. the link. People can find the link on the document section, here next to the QA. It's like the the last link in there. Okay. Yep. So there you can register for the second part, session two. And I think, yeah, we have a few minutes more to see any questions. Yeah. Are there any questions? I'll... We'll leave people maybe a couple minutes if they wanna ask anything else, but I want, I wanted also to point, attendees to some additional resources that we have made available through the docs section. Obviously, on that link, you can register for not just the next episode that is happening on November 10, but to all the episodes in this session. So you can pick and choose the ones that, you're more... Most interested in depending on the parts of the process that you handle. But we've also made available a public records software RFP template that you can find on the docs section. This is a great starting point if your agency is evaluating new tools or is, like, getting ready to go into an RFP stage. We've built it, taken... Built built it, taking into consideration all the criteria that agencies usually have for bringing in new records, request management software. And we've based it on multiple hour fees that we've had to fill out ourselves throughout the years, for example, for Boston... For City of Boston, for Duke University. So it has a... You know, it's very loaded with, like, all the criteria that you you could, keep in mind. And if you're interested in seeing what other agencies are doing and how they're succeeding in managing, you know, an increasing volume of requests, we're also also sharing three customer stories with different agency types like City of Corona, and, a public school district. And these are great examples of how these teams are handling a growing volume of requests and improving their process overall. And, of course, if you'd like to see how logical for public records would work for your own agency, we would be happy to set up a more personalized demonstration, which you can request by hitting the log... Request logical demo bottom above. And I don't see any new questions in the chat. So, thank you, Daniel. Thank you, Jason, for the great demonstration, and thanks, everyone, who attended for spending a part of your day with us. And we really hope to see you back here on November 10. Thank you, Bye. everybody. Thanks, everyone. Thanks, Jason, Laura. Thank you, Laura. Thank you, Daniel. It's a nice bite.