Name: Agiloft Product Release
Uploaded: 2025-12-02T17:46:13.304Z
Duration: 35 min 56 s
Description: Agiloft Product Release

Transcript for "Agiloft Product Release": Hello, everyone. Thanks for joining us. We're gonna give it a couple of minutes to let people trickle in here, and then we'll get started. We're just getting giving it a minute or two for people to join, and we'll get started here in just a second. We'll just give it one more minute here. Alright. Good morning or good afternoon, depending on where you're joining us from today. My name is Ann Marie Pollitt. I am on the product marketing team here at Agiloft. I'm excited to be here today joined by two of our product managers to take you through everything that was included in Agiloft's fall product release. So we're going to hit some of the highlights today. If there are things that you might have seen in your email, related to this release that we don't cover, make sure you check-in on the release notes and we'll have an event in our community in a couple of weeks to dive a little bit deeper. But before we get started today, I'm gonna pass it on to, our two product managers here to introduce themselves. Marissa? Thanks, Marie. Hi, everyone. I'm Marissa Hobbs. I'm based on Bob from Massachusetts, and I am a product manager focused largely on the pre signature portions of screens. James Lowe? Hi. Thanks, Risa. Hi, Ron. So I'm James. I lead one of our AI product development teams here at Agiloft. And today, I'm gonna be talking about obligation management. I'm also super excited to be introducing a new feature that we launched, with this latest release in November. Awesome. Thank you both. As mentioned, we're going to go through some of the elements included in the fall release, which really you'll see focuses around risk mitigation. So Marissa is going to take us through some of the updates in the screens app. Then as James mentioned, we are going to talk through the new AI enhanced obligation management feature that we are extremely excited about. Quickly, before we dive in here, just a few more things. What you'll be seeing today is all part of our new AI inclusive AI on the inside package. If you have not made the transition to that new package yet and have questions about it, please do not hesitate to reach out to your customer success or account manager. They can answer all of your questions. Then additionally, if you have any questions live about what you're seeing today, please do not hesitate to use the chat or the Q and A feature. Let's dive in here. On the influence and scale side, as mentioned, we have been just ecstatic about the power that screens has been able to bring to our users since the acquisition. A lot of what we've been focused on in this latest release is really taking that platform to the next level and making it enterprise grade and usable for all of our customers. What you're going to see and what Marissa is going to go over is setting you up to expand the reach and the impact of screens across your organization. You're going to see a little bit more control, a little bit more influence and customization. Marissa. Awesome. Yeah. So we're gonna start with role based access controls. So in November, we introduced role based access controls to your screen workspace. So previously, it was just a open workspace. Anyone who authenticated into the platform had all the same permissions. But we received and heard the feedback that users have concern that they've created these vetted screens, or kind of like digitized playbooks. And even after they're finalized, there's this risk that others can go in and make undesirable modifications to it. So that's the pinpoint that we were really focused on in this particular rollout. So we introduced three roles, our reviewer, editor, and admin role. The reviewer role is the lowest level of privilege, but it still allows for a lot of functionality. So we want everyone to still be able to go in and experiment with building a screen and understand how they're configured. So a reviewer can go and do that but what they cannot do is go and modify screens that are not there. So if they're not the owner of it, they can't make modifications. An editor has full privileges, so they can go in and they can create their own screens, modify those of others, create new labels, etcetera. And then an admin has all of those privileges plus the ability to manage workspace settings. So we're gonna pop into the workspace and log in as each of these types of users just so you can get, a sense of what it will look like. Alright. Perfect. So in this particular workspace, I am logged in as an admin. So we're gonna pop over to settings. You may have noticed that that role appeared within the past few weeks. So that's how you can figure out what role you were assigned to. You'll notice if you're logged in as an admin that you can see what every member of the workplace is assigned as. Now it's important to note that for AgileOps users, we're not identifying the role type based off your permissions over in the KB. This is separate. Anyone who was already in the workspace prior to this rollout is by default an admin, and any new joiner will be set as a reviewer because we wanted to minimize the risk of disruption. So an admin can go in and edit the roles of anyone. So if you don't want those default settings, you can go in. I just changed that one to an editor and you can see that it updated. As an admin, you can also manage some other workspace settings. Like, here, I'm popping into the workspace details where you can modify the name of the workspace or the company names. I'm not gonna change anything here at this moment, but just to give you an example. And then you can also manage the access to community screens. So now you just need to be an admin of your screens workspace, and you're able to set that off if you so desire. The rest of the platform will look the same because as an admin, you have the full functionality and screens and documents. So I'm flipping over now to log in under an editor role. And one of the first differences you'll see is that when you scroll down, the functionality of being able to change the role that someone has or remove them, is no longer there. And you also can't update any of the workspace settings that you saw before. Hopping into screens, this section should look the same as before because you have the full functionality. If you take a look at any screen, you can modify it. I'm gonna pop into this one, and you'll see that I can add labels to it. I see this edit configuration section. So all of this is still the same as before for an editor. And then in the documents tab, which there were many changes made on the recent release, you have full functionality here too. So here, I'm just creating a label to organize the documents. I can go ahead and save that. I also could do a bulk delete if I wanted to. So a lot of privileges are available to an editor. Last one I'm popping into is a reviewer rule, and this is the one we will probably notice in those changes. So over here, it looks similar to what an editor sees, and it's really in the screen section where I notice the difference. So looking at this, you'll see right away that now that screen is view only. So I can't go in and disrupt it or make modifications. I can't add labels, which could disrupt organization. I also can't change the configuration. You'll notice that this is just a read only and it is blocked. So, again, really try to address that pain point, and we don't want vetted screens to be disrupted. In the documents, oh, sorry. I forgot to call out that you can still create a screen. So as a reviewer, we still want you to be able to make your own and experiment because it's important to understand how screens work. So I'm quickly just gonna show a sample one or a viewer screen and save it. And you'll notice for that particular one that I made, I now have full functionality where I can make edits at any time. So that's really one of the biggest differences. Now what I'm gonna do is pop over to documents just to flag one other change here and that is these are the documents that I uploaded as a reviewer. And so I can add labels, I can delete them, but I can't create a new label, which is something that a editor admin can do. And that's so that you don't disrupt the organization that you've established, within your workspace because those do affect other users. Cool. So that those are the updates on the role based access controls. I'm now gonna pivot to a particular portion of the standard configuration. So the biggest change that we just rolled out is that in November, you will now see every time you go to configure or edit a screen, a section under the standard configuration that is focused solely on redlining. So we heard a lot of feedback that every organization has a particular way that they want to redline. They want to have their preferred language shape the redlines as opposed to just being guidance, which is how it operated before in screens. And people also wanna be able to tailor the approach. Do they want it to be surgical edits or they do they want it to be really heavy handed and, as verbatim as possible and align it with their preferred language. And then in addition, we previously had default comment or we had AI generated comments that were added to describe why a particular red line was made. But a lot of organizations have boilerplate language that they wanna appear in association with a given set of changes. So this whole section is what we added and there's one part that is unique just to AgileSoft integrated customers and that is the ability to add content from your clause library. So in a minute, I'll walk through this, but essentially, you have a model that will pop open from directly within the screens web app and you're able to search the clause library that you have stored over in your KB. And you can add preferred language right to that standard configuration, and that will shape your red line. So let's walk through an example just to explain this a little bit more. So I'm going to, hop into this low value SaaS contract screen. So this is designed for, like, a a company like ours going and buying, a SaaS platform. So I'm gonna focus on this audit fee restrictions requirement, which essentially is saying that we don't want that vendor to charge us for any overages that they see in usage unless they are consulting with us and we have said, yes. We see that that usage is an overage, and we're willing to pay those fees. So that's really what I have here in my standard text. Don't want the vendor to assess additional fees without our verification and consent. Put some standard details in there just saying that if there's the absence of this language, it's okay to pass the requirement. And just to make sure that it's operating that way in this not addressed section, I've said it will pass if this isn't addressed. So that part has existed for a bit of time. It's this redlining configuration section, which is new. So preferred language is going to directly shape the red line. And what we're gonna do in this example is actually go into our clause library and take preferred language from there. So I'm gonna pop open this model. I could just use the search bar, but in this case, I'm gonna use the filter. I'm gonna say it's a fast agreement. The clause type, it's gonna be focused on fees and payment, so I'll select that. And then I see here that I've got this audit fee restriction clause, essentially giving me some, vetted language about how we wanna handle this. If I want to, I can hover over the guidance section as well just to confirm that this is, the clause that I wanna use, by seeing how we typically use that. So this all looks good to me. So what we can do is over on the left, select that radio button and click submit, and you'll notice that it copies and pastes that language right into that preferred language section. So now I need to think about how do I want the redlining to, be managed. Do I want it to be surgical, which would mean that it's going to really precisely, make changes just as lightly as possible, or do I want it to be heavy, like, as verbatim as possible based off that preferred language? Then I'm also going to scroll down just a little bit to the default comment. This is just a kind of boilerplate response explaining we don't want the vendor to charge us additional fees unless we have done a thorough review. And I similarly have a choice here as to whether I want that comment to be adapted by our AI model, so just tailoring the comments, or if I want it to actually be just a copy paste where it's going to be verbatim. So in both cases, I went with the heavy red line approach and the verbatim comment for the example to show you how it's using a preferred language and the default comment. The rest of this is unmodified in this release. So risk configuration, if this fails, how much risk is presented for the business, and then user guidance doesn't affect any of the AI. It's just for user to understand how to use this standard and this screen. So now that we populated that, I'm just gonna click save, and we're gonna show this screen in action. So I'm popping into the KB. I've got a fast agreement here. I'm just going to open this document. It's important I do check out to edit from the KB or it could be synced, between screens and Agile Opt. I did already log in and run this screen just to save us a little bit of time, and I'm going to search for that audit fee standard. So clicking into here, you can see that it failed this requirement. And if I look at the details, it makes sense as to why because it is explicitly saying that this vendor will actually invoice us for overages, which is not what we want without our consent. If you recall, this is the preferred language that we added from our clause library back in the web app. If I wanted to, I could just copy and paste it direct from there and overwrite that, Or I could use the redlining suggestion here, which because I selected heavy, it pretty much verbatim inserted that language here, and you can see that with those blue red lines. Before I apply that, I'm just gonna scroll down and show you that the default comment that we put in the configuration is also here. And because we selected verbatim, it is, copy paste there. So I'm just gonna go ahead and click apply, and we'll now see that the preferred language shapes those red lines. And if I just scroll over a little bit, we'll see that the default comment has also been added. So the goal here is really to allow for more, tailoring to your particular organizational needs when it comes to Redline. Alright. Emery, those are the two updates that I wanted to cover. So I'll hand it back to you. Awesome. Thanks, Marissa. And we we know that that's one of the things that makes AgileFT great, some of that flexibility and control, so we're excited to bring that to screens. Before I pass the mic over to James, I want to touch on two things real quick and then we're going to go into obligation management. We're not going to go into detail today, but what you'll notice in your release notes and in your specific upgrade emails, I encourage you to read those, is there are new models available for Prompt Labs. We have the option for you to choose your own model and ChatGPT 4.1 Mini and five Mini are now available. Beyond that, for those of you who are already on AI on the inside or have AI platform, you might have noticed updates to natural language search in the contract table. That is an early iteration of being able to search your KB using natural language. We're very excited about it. It is at the contract table level now, and we will give you more detail and talk a lot more about that as we continue to expand that ability. Diving into obligation management. A few things, and I'm not going to steal James thunder because him and his team have been working incredibly hard on this. But just a little bit of background, we ultimately know that this is still an issue. Even with the evolution and the innovation in technology today, there are still nuanced obligations that can get missed. That is a problem that we decided to tackle, and we're very excited to show it to you. So, James, without further ado. Great. Thanks, Amari. Okay. Yeah. So I'm gonna talk about obligation management. And, you know, I've listened to many customers, in the past or and recently describe kind of the many challenges that they can face after a contract is signed. And I think this quote, from our recent market research captures it perfectly. Right? Managing, post signature obligations remains one of their biggest challenges. We see so much effort going into negotiating hard fought terms, but yet once the contract's signed, this is really it's tracking these terms, which is really where many teams can fall short. Now if we move to the next slide, please. Okay. So this is, this is where we can help customers. Right? We can help our customers eliminate some of these, common pitfalls that we see simply by improving how obligations are identified and tracked in Agiloft today. Now we know from our research that many businesses still rely on manual process today, and terms can easily be lost, especially when signed contracts are just being filed into platforms like SharePoint. And a common problem that we see that I imagine many of you watching today could also relate to is just the time we're spending reading contracts line by line, and copying and pasting relevant sections into an Excel spreadsheet or a Word document. If we can move to the next slide, please. So this is where our new obligation extraction feature comes in. It's powered by the same AI service that we use for screens today, and, we're giving our users the ability to extract obligations with just a single click. So no more copying and pasting into Excel. And with a precision score of more than 85, we're really greatly reducing the risk of errors that you can get with, your manual data entry today. So how does this all work? We've essentially built a set of obligation screens that are available in the screens community covering, eight topics, 70 subtopics, and three agreement types. Now the screens community provides access to deep industry know how, and it can enable our users to not only create their own screens, but also to customize anything that we have prebuilt for you. So with obligation extraction, using screens, we're able to deliver concise, actionable summaries, which are fully transparent, and we offer the ability for users to customize. Now, if we take a look at the feature set on the next slide. So here are all the features that are listed, to do with this feature set, which are part of that r thirty two release. The highlight really being is that the the screens run action is now out of beta. And this is what enables, obligations to be extracted from a contract with just a single click. Sounds pretty cool. Right? Alright. Let's see it in action. Okay. So finding obligations in contracts, can be time consuming. It can be tedious. But now with automated extraction, procurement teams can instantly surface answers without having to dig through pages and pages of text. So in this demo, we've taken a supplier SaaS agreement, and we're gonna use using the screens run action, we're going to extract the obligations to help answer some essential questions. So things like, you know, what's my notice period in the event of a breach? What's my agreed availability uptime each month? And what are my payment terms so I can notify my finance team? So Agilof now not only extracts and summarizes, the relevant text in the contract, but we're also able to categorize each obligation, identify any relevant triggers, and as well as the responsible parties. And the coolest thing we're now able to do is we create structured metadata. So this makes working with data much easier. You can now report on this data. You could potentially send it to another integrated system. Now, of course, no obligation management solution would be complete without the use of tasks. So we're linking the extraction, to our existing task management capability so users can now track ownership as well as deadlines. Finally, we can use something like the prompt lab action to go ahead, summarize all of the payment details, and just even go ahead and draft that email to send to finance. So with obligation extraction, we can now deliver precise, actionable summaries in just a few clicks so users don't need to waste time searching through files. I think this brings an end to, my part of the presentation, and we should have got five minutes left for any questions. Awesome. Thank you so much, James. We do have some questions here. So, Marissa, I know that you answered one in the chat. Do you also just want to reiterate that live here for the group? Yeah. Sure. So I just wanna emphasize again that the I and I realize it can be a little confusing, but the rules that we have over in the screens workspace are independent of the rules that you have over in your KB. So when I showed a reviewer role in screens, that does not have any correlation to the reviewer role that you have over in your KB. So the way it works is that if you're coming from an AgileFT KB, we, in the back end, are detecting your license type. If you're a power user, you are allowed into that web space or into the word add in. And then within screens, you can have different roles for every individual in there, either an admin, an editor, or a viewer. And anyone who's an admin within that workspace can switch around the roles of the users there. Awesome. Thank you. James, this one's for you. Can I run obligation extractions in bulk? Great question. So, with this release, the extraction will happen across a single contract, and, we'll release the bulk extraction in, an up and coming release probably, targeted for some time next year, probably around February. Awesome. And a follow-up to that is, can we auto extract the the metadata when a document is submitted? Can you auto extract the metadata when a document is submitted? You we extract some metadata, yes, from particularly for obligation. So we've got a number of obligation topics or types as we call them. And within those, we will extract certain pieces of metadata. So for things like notice periods, we might extract the number of days that those periods given. I think we've got some SLA calculations or extractions in there as well. But you could you? could potentially use screens, actually. Sorry. Just restart that. You could you could use, using screens. One of the benefits of using screens is that, you know, you could define any question or essentially any extraction that you want to, extract, as part of that screen. So you've got a bit of flexibility there. Awesome. So this is asked twice, I think, actually. What are the contract types that the obligation tool works on? What document types are covered in the community? Okay. So we've got an overarching one for general commercial agreements, which kind of like a catch all. It should be, fairly comprehensive. And then we also have one for statement works and SAS agreements. Awesome. Thank you. Let's see. We do have a couple of questions about, about this webinar being recorded. It absolutely is being recorded. Everyone here will get a recording in your email. Where can I find the list of available fields for extraction, or is that customizable, James? List of fields. So if you go into, so there'll be some details as part of the release notes, I believe, around exactly what's being extracted. But, actually, if you want to see what's coming out, as part of those extractions, you can go to the screens community. You can see there's a section in there called obligations. You should be able to click into each one, and it will give you a bit of detail around what what's available. And then if you've if you've got the screens integrated or you've got screens already set up, you should be able to download those screens. And you can when I say it's fully transparent, you can go into the detail of those screens and and look at exactly what's being extracted. And then to the second point, is that also how and where you would customize? Yes. And then you have the ability once you're in screens in your screens workspace to customize that screen. We put some guardrails or some template questions into the screens itself to help you understand how to curate those extractions. Awesome. To that point, there's a question here that these features are only available if you have screens. Is it not included in the base package? As we're finishing up here and running low on time, screens is now part of our new base package that is the AI inclusive, AI in the inside package. Actually, for anyone who's on this call that is a member already of the AgileFT community, in one hour at 01:30PM Eastern time, we are going to be having an Ask Me Anything session about that new AI Inclusive package with our VP of Account Management and Customer Success, Jack Davis. So I highly encourage you for any questions on the package and platform itself, to please attend that session and that's starting in the community in one hour. But if we did not get to your question today, we will make sure that someone from our team follows up with you directly in email. Marissa, James, thank you so much for your time. We appreciate it and we hope everyone is excited as we are, for this latest release. We'll see you at the next one. Thank you. Right.