Name: Slack Investigations Made Simple: How to Find What Matters Without the Headache
Uploaded: 2025-09-25T15:33:22.413Z
Duration: 44 min 52 s
Description: Slack Investigations Made Simple: How to Find What Matters Without the Headache

Transcript for "Slack Investigations Made Simple: How to Find What Matters Without the Headache": Hello, everyone, and welcome to today's webinar on Slack investigations made simple, how to find what matters without without a headache. My name is Constantina. I'm part of the Reveal marketing team, and today, I will be your event producer. So before I turn this webinar over to our panelists, I'd like to share a few housekeeping items, with you starting with the q and a section. You can find that on the right hand side of your screen. So feel free to drop in there any questions that you have at any point during the webinar, and we'll make sure to address them, address as many of them as possible, before we wrap up. This webinar will also be available on demand. So by tomorrow, all of you will be receiving an email with the on demand version, which you can also find on Reveal's website. And, finally, for those of you that would like to take a closer look at any of Reveal's products, I'd welcome you to schedule a demo on the by clicking on the button at the upper right hand side of the screen. So with that, it is my pleasure to pass this session over to our amazing panelists. Thank you. Thanks, Castellina. We are welcoming today two, great speakers. One is, Janessa Nelson, who is director of legal legal operations at AttentIt. You think I was the one with seven thirty in the morning instead of them. And but and and the other is Jeremy Robertson, who is discovery manager at Pelican. I will let each of them in a moment give a little bit more information about who they are and what they do because it matters for this discussion. I am George Sosha. I am at Reveal as SVP of brand awareness, which includes, among other things, moderating webinars like this. We would like, your questions early, your questions often. I will be doing my best to monitor them, on the side panel as well as, move this discussion along for the roughly forty five minutes we have here today. The focus of this webinar is as the title suggests Slack and Slack investigations, everyone's favorite or perhaps most most loathed topic because Slack presents, a series of special challenges that we haven't become used to in the same way that we are now with things like email. We've got some, points we'll be covering along the way. But before we even begin, I'd like to turn this over. First, Janessa, why don't you introduce yourself and then Jeremy? Hi. Thanks for having me, everyone. My name is Janessa Nelson, as George mentioned. I'm the director of legal operations at Attentive. I've been with Attentive for almost four years now. Attentive is a marketing technology company. So we're definitely still in the startup phase even though the company is several years old. We've not IPO'd. When I started at Attentive, they had very little, in regards to structure for the legal system. And so I've had to sort of build our tech stack and, build our processes, over the last four years, including, we needed we very heavily use Slack, internally at Attentive. And so, we needed something to utilize, for Slack eDiscovery. And as a part of my very long RFP process, I identified Reveal, now Reveal, and we implemented that, a couple years ago now. Thank you for having me. Thank you. Jeremy? Hi. Thanks for having me as well. My name is Jeremy Robertson. I am the discovery manager at Peloton. Similar to Janessa, I've been at Peloton for about four years. When I first came on, we had already onboarded Reveal for our Slack investigations as well, but it wasn't being used to its full capabilities. So through these through this time, and you'll hear, examples of how we've increased our productivity, been able to find data better using Reveal and also new technologies. Just like what most people say, these comments are my own and doesn't represent Peloton. So thank you. Well, let's let's just dive into it right away. What what is it about I mean, Slack is has been around for a little while, but it's much newer than things like email. What is it about Slack that makes it more challenging? Yeah. I mean, I can start first. With Slack versus email, some of the issues so we have a enterprise license of Slack, which allows us to do a lot more. So one thing is that depend upon the size of your company, the licenses and your capabilities vary, differently. Early stages, there wasn't a lot of applications that allowed you to go into Slack and take out messages. So as we talked about four years ago, Ona was like a game changer for us, because we were able to come in and individually search on records. The way that Slack is usually split up is into four different groups, direct messages, multi party messages, private channels, and public channels. And so the variance between the different channels and how people use it really changed a lot. And so and you're seeing an evolution as we continue to grow and how people did. It's like back in the Enron days where people were using emails and saying crazy stuff as most of us have seen in the different, in every single legal demo using Enron of the crazy stuff that people said, that has turned into Slack as well. So it makes it very difficult for you to really identify what you're looking for and, and really setting a standard in your company on how to use this because people don't really for us in the legal industry, we're like, oh, wait. We need to be careful what we say. Right? Because we saw what what other people but from a day to day perspective, Slack can feel more conversational and more, like, it has more of the ability just to say what's on your mind rather than thinking through, and it's more instant gratification rather than writing an email, going back, doing more information. And so those are some some reasons why I think, Slack makes it a little bit harder than email. Janessa, I'll let you add some more. When I was, you know, when I was looking into, okay, what's even available? How how do we even do ediscovery in Slack? I was like, can we just do it ourselves? And when I tried to do it myself, this was once again four years ago, it was exporting as a JSON. Now for, like, one message, sure, I could screenshot that or or or download it in some way. Right? But I'm I'm not getting the history in the same way. And the when I try and export that information, it exports in a weird manner. And so I was like, okay. Well, if we're gonna do this in a large scale, which we need to, and just sort of manage the organization from that sort of perspective, I need a tool that can allow me to actually do this in a a meaningful way. And, and so that's how I found SOTA, ONA, and and Reveal. I mean, for for us, Attentive also has the same issue of it's very conversational on Slack. People use it very heavily. But because people are sort of always in there, they're also putting in very valuable documents, and sort of sharing, important sort of, like, milestone steps or, just sort of information that's relevant to the company that doesn't always make it into a shared sort of Google Drive. So sometimes we've had to, like, go in and try and find a specific document, as a part of a sort of litigation that we had. And so that was useful to be able to sort of search through Slack and be able to find those documents and find any sort of relevant conversations. So it sounds like from what the two of you are saying, any organization that is using Slack and that has to deal with investigations and or litigation had better figure out some process to effectively find and work with messages in there because it's potentially gonna be a much richer trove of information, and potentially harmful information than a number of other sources. Is is that the case? In my experience, that is. I mean, because like like we both mentioned, sometimes you'll say something that you're not really thinking. And within a Slack, Slack is it depends. There's more advances on how you can collect the data, and there's been back and forth of, like, how do you produce this data? How do we preserve this data? How do we collect it? Because you might have a conversation about something irrelevant during that same day, then switch to like, I might be asking you, George, how your day is, how did everything go? And we might be talking unrelevant stuff, and then we might go into important information that will, impact our investigation. Right? But how do you also remove that kind of information that is not relevant, from a message and still have the work stuff. And so there's a lot of more complications in that because day in, day out, because it is a conversational piece. Right? It's just like there's so much landmines potential landmines that might have it might be relevant to the case, but might bring in more information than you might want that you have to be, like, look out for on the lookout for it. And I'm guessing from both of your comments that neither of you would be recommending that people try to do this manually. Look, I am a person who builds a lot of her own stuff, using, you know, technology that we already leverage. I legitimately tried to see if we could, to save money and, you know, not have to go through a whole RFP process, and I could not figure out a way to effectively do it on my own. So you in in my personal opinion, if you have Slack and you're needing it for a d discovery perspective, you know, you you need to get some level of software in place. So what what should you then be looking for in the software you're you're considering? Yeah. So for me, it was, it was a number of different things. Number one is that it integrated with Slack. I mean, easy. Number two was, we did like that ONA and Reveal had, multiple other integrations that we could utilize as well, including Jira. They did add in a a Google Workspace, element as well. There's and there's there's a number of other integrations. So we thought of it as, you know, we're giving this just for Slack right now as we're implementing, but we can use this for other applications in the future as well as we get more sophisticated. For us, the ability to sort of, like, easily, read and sort of search through the Slack messages was very essential. I think it's a very easy to use system for searching and filtering. Additionally, the, the ability to sort of see the history for us was very relevant. People can obviously delete Slack messages and delete or or edit Slack messages. And so you could also see, that information right there in the ONA system, and I don't have to do extra steps. So that was also an essential sort of component for me. And then we need to look for, like, very easily export, information, was very helpful. I mean, it's it's great having a to to go out for Janessa. It's great having a software that allows you, like she mentioned, to be able to see the messages. Because a lot of times, what we get is we'll get requests for investigations or something to look closely. A program like ONA will allow us to go in and run searches, find specific custodians, find specific time frames that allow us to pinpoint is do we want to build upon this, or do we need to have more information? The exports capability. So when you're looking for a product, finding something that gives you the ability to export as a load file so you can load into a litigation tool. Or maybe I just need to get you some PDFs, of the records of the Slack messages so that you can just review it. Maybe someone, says, hey. Can you look for messages between x x and y? And I can go and pull it up, and I can tell you we have five messages here. It makes it so much easier rather than having to export that JSON file going into the administration, finding the user, and then it expands greatly too. So then that then you have to double the work. Right? And so, having a tool that gives you that flexibility and allows you to pull more real time requests when things start changing and things need to happen quickly is something that's really invaluable for us. We have an audience question. But before I get to that, I wanna go back a little bit to something, Jeremy, you alluded to at the beginning, which is, does it matter what license of Slack an organization is using for these purposes? I I mean, so I can only speak for enterprise license. I don't I'm not sure whether you have, Janessa, but from an enterprise license, we're able to do a lot more from what I've heard through talking with other people. Like, exporting the JSON file and other Prius isn't as easy if you don't have that enterprise license. And so, and we're a bigger company, so it allows us to have more flexibility. But the licensing, I do believe, it impacts us significantly. It does. We, very unfortunately, a word of caution to everyone, we had signed the Slack enterprise license agreement with Slack, but we did not implement it before, we did this, which I was not aware of as a part of my big RFP process. I was told that we had it, and, we had not actually implemented. And so that does negatively affect your ability to do ediscovery. You pretty much need Slack Enterprise. I think it's grid is the plan. Maybe they've changed the names at this point. So just as an FYI for anybody looking into doing a discovery, that's sort of a requirement for for this whole process. Well, what happens if you don't have that enterprise license? It becomes a lot harder. I I believe I've I've had to utilize utilize before in ONA before we implemented. You can, there is sort of a capability, but it's it's not the same level of, being able to export or find or being able to access the information. So there is still some capability from my understanding, Enona, but, it's not to the same level. To our audience question then, are you able to see previous versions of edited Slack messages, or do you just know that there are were edits made? Do you want me to do it or or do you want me to do it? Or or do you want me to do it? Yeah. Go ahead. Yeah. Go ahead. So at least from my knowledge and and you utilizing the system, you can see, that it was edited, and you can also see what was edited. So it's almost like a redlining track changes sort of feature. So it's actually great. I didn't see that many other ediscovery platforms that sort of had this capability. So it's it's very obvious when you're actually looking at it. It looks like a track changes, and you can tell that it was edited. Yeah. And I would say that's something great with on it. It's like, it will so our version will sync. So if someone writes it and it cut takes it and then they change, as Janessa said, there's actually a line through the words and it says edited. So you see both versions and the time of each of the versions. I will say there is potential. So this is something I just wanna cover. There are potentials for, like, someone to do it before the sync happens or, like, say, you edit. So there might be some instances where you might not catch everything, but I think our sync happens pretty consistently through the day. But, that's one of the pitfalls you just have to like any kind of software, you can never be a 100% right, and it does its best to try and find it. But it's, it'll show deleted. It show edited. And so as long as it hits in the sync portion, you'll be able to see that information. One of the challenges I've heard talk about pretty regularly with respect to Slack is how you deal with a situation where, for example, you've got a channel and the communications in there are from a number of people and span a long period of time. And what you're trying to find and then hand over are just a limited number of communications from within that channel. And there are all sorts of different suggestions for approaches. One, which I think really doesn't make sense, is to generate a PDF version of the entire channel and then redact everything but the few communications that you want to turn over. How do you all suggest people approach, that type of issue? So so did you say, like, the whole channel history or, like, like recommendation I heard. It made no sense to me, but I did give that as an example. What what would be a better practice? So, I mean, this so best practice, I I feel like right now. So Ona has actually made quite a bit of updates within the four years that we've been using and allowing us to adjust. So this was something that we did come through before. It's like, hey. Can we make changes to pimp on what we need? ONA gives us the capability of exporting out twenty four hour sections, or individual messages. And the cool thing with the individual messages is during the export functionality, there's an option that you can select that allows you to select messages, around around the one that you searched on that hit on the search term. So these kind of capabilities has grown and give us more flexibility depend upon what is needed. So I would definitely say not to do full channels because, like, you the other thing that people don't always think about, right, sometimes you have so Slack is used as a communication for business, but then also if you're just exporting a full channel, maybe someone put a picture of their puppy in there. Right? And you have a humongous picture of their brand new puppy, adorable puppy that is super big. Right? And it can cause trouble, it can cause time out issues. So exporting a whole, like, channel and it might be nothing to do with that. Right? You have to imagine people are going to put in again, even these private channels or public channels, people might put in things that are irrelevant. So exporting everything out and having to try and explain why you did that, it seems to me as not. But just with the standard options that we have, it's actually been working pretty well, for us. So in my personal experience, I've always had whatever sort of outside counsel firm, or, you know, we'll we'll come up with specific search terms, that we'll utilize. So maybe I'm searching in the channel, but I'm searching for very specific criteria. And then only those messages that are relevant get exported. And it's it's pretty easy in ONA to, sort of do those searches, find the specific messages that contain that information, and then sort of, like, pull them away. So that way you can just export that sort of section. I definitely would not recommend anybody print out a PDF and redact a whole channel's history. I mean, unless that that is incredibly relevant to a litigation. But that just seems incredibly time intensive. And it is, I don't have the amount of time to to to to dedicate to that. I also don't wanna pay someone that amount of time to dedicate to that. So this, I think, makes it easier. It's from my perspective, a lower risk for the organization of of other information being included that shouldn't have been. One of the, another thing is that, Janessa, you mentioned briefly was, searching in the data. What sort of search capabilities do you have access to should people should people be looking for? Yeah. So, they're pretty standard search capabilities that any good e discovery platform would have. So we can do sort of the, we can do various sort of add ons. So, you know, I'm I'm searching for, a specific name. I'm searching for a specific keyword. I can use and or, you know, sort of any of the, filter query language that you wanna utilize, ONA is able to support, which from my perspective is very intuitive, with using any of these sort of eDiscovery platforms. I'm very used to those, and so that was nice. I I felt very comfortable, going and using the system immediately, because I was familiar with other ediscovery platforms, and and also, like, Vault Google Vault is very similar in in the same setup. Jeremy, your thoughts? Yeah. So very similar. One of the things that I found very useful in this is as you go through, sometimes you'll find other channels that you might not really know that you're looking for while you're doing an investigation because, I mean, there are so many channels that are being added. One of the very useful search capabilities is like, oh, can you find this channel? And so you're able to search on specific channels. A lot of searches also will do a specific custodians and time frames. I will be honest. I do usually, from a forensic perspective, we will collect a little bit more. It's better than using a JSON, but I'll use more and and ors and just be a little bit more wide net, and then we can move it into a review application to be allowed us to go into more detail. So it depends on what part of an investigation that we are at. If we're looking just more, okay. Can you find is there stuff for here? I'll do more specific keywords and kinda give people understanding of what we have. Right? Because it gives the attorneys the ability to make something what what is our strategy, right, by allowing them to know what we have, and then I can go in and be more, broad with the collection or be more specific depend upon what is needed for them. And this the search capabilities have also grown significantly since we first started using it four years ago. It's as Janessa said, I feel like it's more user friendly, especially for people in the legal industry that have used other review tools. They are they'll be like, oh, this makes sense. One of the great things too is the color coding. I know that sounds very nerdy, but, like, if you're writing your query and the query is incorrect, it'll be red. Then once you, like, put your proper, parentheses or or whatever or if you have a or and, but it's loose, once you make it complete, then it turns back. And it will also, change the color of any, operators as well. So you can see and, I think, it's like a brownish color once you do it correctly. And then it it just for myself, it's nice to see that color differential because sometimes you have long queries and you're like, wait. Where did I mess up? Where did I mess up? And then you put the right comma in the right place or you put the right operator in the right place, and then you it's a great feeling having it turn green and working again. And so, so those that's just, like, one of the things that I've really enjoyed, and it really helped us with searching within, the application, that it would be so much harder without our tools. Right? Because then we'd have to export a JSON, and then you have to again, it adds time where you might need a quick answer that can that you potentially could get in five minutes rather than export and then import and then run the searches. To the extent that you end up needing to export content to deliver to someone else, someone inside your own organization, an opposing party in a lawsuit, but an an agency conducting an investigation? What are what are the options for for producing content out? I mean, there's a lot. Just so just so you can go first. Yeah. I think that there's probably more export, you know, capabilities that I'm not even able to leverage because it's it's so massive of, like, the amount of information and, sort of, like, specificity that you can that you can really get into the the weeds if you want. But the nice thing is, for me, it's being able to easily export if I just wanna use it internally. You know, maybe I need one conversation or or one file, and that's easy to sort of, like, find an export if I need to. Versus we've had to do investigations and litigations. And so being able to easily export and send that to, our outside counsel, not only saves us a lot of money, but saves us a lot of time, because they don't have to go in and sort of utilize their own systems. We can sort of do some of the work on our end, which, is just helpful for us. We're a little bit more nimble and lean, than an outside counsel would be. So, they have I've I've never had any issue with exporting any data from ONA and sending it to outside counsel. They've always been like, this looks great. Thank you. Yeah. So and to add to that, sometimes what I'll do is I mean, they'll give you a lot of like we mentioned, there's a lot of options. Sometimes when you're looking for the specific, you don't even have to do an export from the page. You can download a PDF or an HTML file of the message. Or if it's an attachment, you can download the attachment itself directly from the system. So it really depends then when you go into, exporting to a litigation tool or natives. Right? You have options to export as natives. You can export as a CSV with metadata fields or a DAT file, whichever system can intake. Right? And you have a lot of different options of fields. One of the things earlier that we always had issues with that was a pitfall for us was finding the members, active members, and mentioned members in channels. And so that wasn't always an option that we were able to export, and that was that came up quite a bit. Right? It's like who's actually in this channel, who's active, who's in this message active in this message. And these are options that were as we worked together with Ona, were included, for us to be able to export, and that's helped us significantly because before that, you'd have to do different scripts or something else to try and pull that information out. So that has saved us a ton of time by just letting it be all in one metadata field. And so, having a load file with the metadata field, it's it's so easy and, like, any system can take a DAT file. Right? And so as Janessa said, we give it to outside counsel and they're like, great. Or we can load it ourselves, into our different platforms. And so it's really useful and just gives you a ton of flexibility depending upon what you need. You might I've used it for DSARs where I just wanted to export out messages. Right? So that someone could just redact or put into another system. So, I've exported out just PDFs itself, and you can do it with control numbers or you can do it with, file names, and you can save your profile. So as you continue to export this, it allows you to export very seamless. Any ediscovery process and the use of any ediscovery technology, can be susceptible to challenge. Folks saying what you're doing isn't defensible. The technology you're using isn't defensible. That certainly happens fairly frequently in in lawsuits. It can happen as well when an agency is investigating, or they may not wanna put it in terms of how can you how can you defend what you have done, but rather what are you going to do to make sure that what you do is defensible. What sort of defensibility issues do you encounter when it comes to Slack, and what ways do you see to address those issues? I mean, for us, I mean, one of the defensibility issues in the collection is, like, a repeatable process, making sure you have a clear audit log and the searches that are done is repeatable, consistently. So, like, what we do when I run these searches is I create my own log to allow what did I search on, where did I search on, what were the cert what were the criteria so we can repeat and show them. The nice thing with having a program like ONA where it's keeping the archive of it, you're not losing data. You're not, taking away data. ONA does have capabilities for data retention as well and also legal holds. And so that's usually what we point to. We haven't really ran into. I mean, that's what I would say in those kind of situations. It's like, this is how we have it set up, have a good understanding of the system, of our capabilities and how we do it, and be able to go back, show them like, hey. Let me show you this. It's done again the same way and it get the same results. And that has been, work it has worked for us. For me, you know, if you're trying to do this yourself, you're probably not gonna get a great audit of of messages, just from the sort of JSON file. Not saying that it's not possible, but it would be a lot of work for somebody. ONA allows me a lot more information about sort of audit, of different files and different, you know, especially Slack messages. So that I think makes the system a lot more defensible than you just doing it yourself. Like Jeremy mentioned, anytime that we're doing searches, we always save with the searches and that gets sent, as a part to be able to sort of defend what we're doing and and show sort of show our work. Right? The the other sort of key feature there is, like Jeremy was mentioning, you know, it's something that we're actively still working on is making sure that our retention process and retention period, you know, sort of aligns with what we need. Obviously, there's always a carve out for any litigation hold that might be ongoing. But making sure that we're sort of only maintaining data, that we actually need to be maintaining. That is something that we're currently struggling with still, and I know that a lot of other organizations are too as well. That's a little bit less defensibility and and just sort of, like, internal processes of what are we doing, and how do we sort of best protect the organization. Not all outside counsel have experience dealing with Slack. When you assuming you encounter outside counsel who are new to this area, what are the best ways to have a productive relationship when it comes to finding the Slack messages that are necessary, assuring the council that things are being done well, appropriately, defensively, and all of that? What what do you see? I mean, for me, anytime we're working outside counsels about relationship and communication and laying all your cards on the table, so to speak. Right? You wanna tell them what your process has been and being open with what you guys do, what you've done in the past, what you have expected. I always like working with outside counsel because we have our own processes that we've worked through, that we are continually evolving based on technology, based on changes that we see and then that we believe make it better. I like the open communication with our council because then maybe we learn something as well. Right? Keeping an open mind because in your example, you said, what if they don't know a lot about Slack, but there are a lot of people that are using more and more Slack and then also taking ideas from Microsoft Teams. Right? Similar applications in the say, like, can we apply those theories, those workflows to Slack itself. Right? We're talking about Slack in this message, but a lot of the stuff we're talking about can be applied to other areas. Right? It's not Slack specific. They all kinda like with ediscovery tools. Right? They all kinda do the same thing. Just the buttons are in different spots. Right? So being very open and having a plan, I feel like having as much of a plan and being able to talk to them, having someone like Janessa on your side that can be like talking to outside counsel and say, like, this is what we do. This is where we've learned. This have been pitfalls, and this has been success for us. And then just being very open and honest allows you to, get step on the right foot in the beginning and then to continue to grow together with your, relationship. I'm gonna always echo everything Jeremy says. So I will even sort of occasionally get on a call with outside counsel, and we can just sort of I can share my screen and I can show them Ona, and we can sort of do searches together. And pretty quickly, they're like, oh, I completely understand what this is. And, you know, once I start exporting data, I am a lot you know, I communicate with them and say, what format's best for you? Some of them have their own sort of ediscovery review tools, that they utilize in house. And so I'll export it in a way that is best for them for uploading into their system. But like Jeremy mentioned, I can sort of export in a number of different formats. And so it's it's whatever outside counsel, it works best for them. So I like a a system that's flexible in that way. For me personally, it's, you know, any outside counsel is probably dealing with Slack at this point related to litigation. So, it's becoming a lot more common. And I know that outside counsel is working hard to sort of get, up to speed on that. And I I think it's becoming more and more rare that an outside counsel is not dealt with Slack at this point. What are as we come closer to the end of our our time, what are some, practical strategies people could use, in in two key areas? There's always the question of cost and how to contain control and ideally reduce cost and the related question about how to get this stuff done faster and better. Some practical pointers for folks. From a cost perspective to help with timings, have a good data retention policy in place. Right? Because otherwise, you're going to have a lot of Slack messages. Right? And then that will just increase your population that you need to search on. As you've heard us discuss throughout this call is having a tool like ONA allows you to go in. I think I've mentioned multiple times about how how happy we are that allows us to go in right away. So if you think of the cost of the software versus the cost of time that you save your attorneys and be able to give them information and the ability to be defensible, because as Janessa said, you might have some tech IT tech person on your team that's like, I can build whatever you want. Right? That's great. You can build whatever you want, but then when it comes to defensibility, how did you know it was tested? How do you know? Do you have someone that can talk about how it was developed? What if they miss something? ONA is programs such as ONA is trying to intrude and you guys have an engineers that are going through it daily, making, probably, not daily, but making updates. Right? And I mean, it works on maintenance hourly. Yeah. Mint by the way. Right? So you have someone backing you. So that is a big cost savings because when you don't right? You might have that IT guy. It might save you a little bit in front end, but then when you have a problem, it's gonna be a big problem. So just making sure you really have workflows that will allow you to go in, let your team know what you're capable of doing, and let outside counsel know what you're capable of doing and having a program like ONA, really helps a lot. For me, the cost is a lot less than asking an outside counsel to come in and do this themselves. You know, I know how expensive litigation can get, and it gets even more expensive the more you have them do ediscovery for you. So this sort of allows me to control that. We use it internally outside of just, you know, that sort of capability. If we need to find things, someone is gone, from the organization. I can search through and and find relevant documents that were maybe only shared in Slack that has happened for us. But just from, like, a cost perspective, it saves me so so much, if we are in a litigation situation. It very much is an ROI very quickly. So, you know, if if if anyone is questioning and you have litigation matters that are coming up, it's definitely something to consider, and just sort of think about how much it's gonna cost for an outside counsel to do this work for you. You know, it it pretty quickly adds up. Why don't, you each take a minute or so and give us final thoughts and suggestions? Jeremy, I'll start with you. Yeah. I mean, Slack can be difficult, and there's no question about it. Between how people communicate, between how complicated our people and channels are not in channels, having a tool such as ONA allows you to take control back and to build in plans and to build in a workflow that allows you to identify issues and to work around it so that you can have the best possible outcome while also keeping an open mind. Because as the technology like we mentioned throughout, as the technology continues to change, such as adding the metadata fields members, mentioned members, active members, you have to be able to go back and look at your workflows and adjust what you're doing. And so just always keep an open mind with any kind of technology. I mean, especially with, like, Gen AI stuff now, everything's moving a million miles a minute. So so just be very open and ready for change and do the best with the best knowledge you have and usually things work out. And Janessa? Ediscovery is only gonna get more complicated the further we get into everything. So, you know, if you're sort of at the beginning of your ediscovery journey or maybe even halfway, you know, there's a couple different, obviously, internal processes that, we're all working and struggling with, data retention policies, our own sort of personal workflows and processes. But, you know, the one thing that is needed is we need to meet the organization where they're at from a technology perspective. What are they using? Because we need to be able to access that from a new discovery perspective. So, you know, maybe you hate that we're using Slack because it's really hard to to get that data, but the organization is going to and they're probably going to continue. So, I'm always a a person who tries to meet the organization where they're at. And then, you know, we're gonna potentially work to to make sure that we're as sort of secure and covered as possible. Partnering with the IT, team for for me is sort of an essential part. I got lucky our IT person that we brought on, as we were sort of, implementing, Ona. She had already used it before and was like, oh, great. I'm already familiar with this, and I, like this eDiscovery platform. So that was an easy sell for me, which was probably abnormal, that many years ago. But, you know, your other stakeholders are going to also be sort of wanting this. So, you know, being able to get other people on board, and sort of secure and defend the organization and manage sort of our risk is is what our jobs are. So this is just another sort of tool in my toolkit that I can utilize. Well, Janessa Nelson, Jeremy Robertson, thank you both very much for joining us today. This has been, at least for me, an enlightening educational session, and I am sure the same, is true for the folks who have, joined us live or who are looking at this recording later on. So once again, thank you both very much. Thanks for having me. Thanks for having me as well.