 to you and the TechSoup team for hosting this and helping us to share this message. And we did this about a month ago and we've got another plan. And so we just appreciate your support. And I told the group, as we were getting started, I'm dialing in from a coffee shop today. Hopefully the audio is okay. But I also thought I'd share the brief design that today you may be standing next to someone who is doing their best not to fall apart. So whatever you do, do it with your kindest heart. That was a good message to start to carry on through the day. So, yeah, quickly wanted to do just intros of our group. So maybe we will do that. And then we'll go into the agenda. As you said, my name is Jesse Maddox. I lead our nonprofit and personal impact customer based on the efforts with agentduty.org. I've put this in the face for quite a long time, working with this intersection of enterprise technology and so forth and back. We've always loved to connect with folks that are doing the work and hearing stories about how these tools actually really helped to transport the folks. So happy to be here. I'll turn it over real quickly to Laura Ferredi from Slack to do an intro and we'll go through quickly and jump in here and get in there. Perfect. Thank you, Jesse. Hi, everyone. I'm Laura from Slack. And I'm here from sunny or not so sunny Miami, Florida. I'm a success manager and I work specifically with nonprofit clients and my background is obviously in nonprofit. So it's interesting to be on the other side and I'm excited to share a little bit about how Slack can help you further your mission. Let's go over to Matt. Hi, everybody. I'm Matt Schutloffel. I lead our nonprofit program at New Relic as part of the New Relic.org social impact team. I'm here with my dear colleague, Holly. We're so happy to be with you here today and to be part of your success. So I'll pass it over to Holly. Hello, guys. Welcome. Thank you so much for joining us. I am Holly and I work alongside Matt at New Relic. It is my honor and privilege to all nonprofits, not for profits globally, to really empower you to do your best work. And so I'm very excited to be at this webinar today and learn all about how to set up your digital HQ. I will hand it over to Jesse. Great. Thank you, Holly. And as we go into the agenda, we have a quick poll question to kind of kick things off. So we'll do that, but we want to get a sense of the size of the organization. It's always helpful to just know from the context of where folks are kind of working with in terms of the size and the dynamics of that place. So I'd love to have you go ahead and share with us what this organization is. And as we do that, we're going to just quick over to you here. We're going to take a quick look back. Some of you may have been on your first webinar. Thank you for coming back. Hopefully it was valuable information. So we'll just very briefly touch on sort of the context of that discussion and how it leads into this. We'll do a brief overview of the tech stack and how New Relic, page duty and Slack all tie together. We'll talk about why you need a digital HQ and then do a Slack overview in the context of the digital HQ. And then we're fortunate to have Kate Edmondson from New York Public Radio to the Q&A and discussion about their experience. So that's our plan. And I'm going to jump right in. It looks like we've got about 42% of folks that are small, very small organizations, less than 20, smaller amounts, kind of 21 to 75, good number in the 76 to 250 and small in the large. So it's a good mix and we'll try and keep that range of experience. I think we have another full question that we'll launch as we go through this. So we wanted to just get a sense of what process currently describes your internet response. So we'll get that up. But just in terms of what we talked about in the first webinar, this whole series is really about modern and consumer response and kind of process of digital transformation. And then you can have a return response, hop to the small process. So we talked about a lot of hearing responding to the dissolving and all we talked about how to kind of come back to pay off and redistribute the signals that are coming in from your various digital tools. Even if you're a small organization, it's toolbox of digital tools. And so these leads and some of the challenges are unique just to the large percentage of people think they actually are pre-relevant across the wide frame. And then we also talked about why your objectives for the sub-workloads between culture are key points for excellence. And that actually I think will really speak well into the point of today's webinar, really around how to help your team communicate, collaborate and tie the techs back together to get the work done. That would be our focus today. And with that, we will move on to the next one. Sorry, I'm seeing the audio is a little off. So I don't have too much more and then we'll turn it over to someone else and hopefully that'll help. I'll try and speak up as we're all due to logic. Did you launch that poll, Aretha, for this one? Oh yeah, great, all right. Yeah, so as expected, kind of again, a range of the workflow, some folks said what workflow can be difficult to detect on the UK country. So that's our goal is to try and speak to some of the tools that we can bring to be able to help address some of those challenges. So thank you for that. Okay, we can go on to the next one. So yeah, I think just kind of setting the stage, just what often we hear and have to be invested out of the scenario with again, a wide range of organizations, regardless of the size, obviously as it gets larger, maybe it happens in more cycles and more layers. The idea being that, you know, from the beginning, you have a problem with subjective system. You know, I'll call engineer and investigate and find the cause. They set up a video call to pull in teams and that cycle comes in pulling more people, people ask, summary, they can continuously bring in more very large individuals and try and address what the challenge is. And so we want to help, but suggest what is an upper up as sort of a constant and who can help to reduce that through a layered toil amongst teams to diagnose what's happened. And again, we think that even with smaller ones, some of these new challenges the digital process of storming, boiling to get to the bottom two is really relevant across organizations as well. And I believe, if I'm not wrong, we may have one more poll question here, is that correct? Did we already, there we go. Great. Yeah, here it is. Are you, I'm seeing, I still have a couple of messages there. Folks hear me okay? We can hear you for the most part, it's a little choppy, but I can still hear you. This is my last slide. I'll do that, we'll speak into this and then I'm going to turn it over. But this is really, just again, we're doing kind of a map of what some of the tools are. So we're going to see it a little bit, that's going to speak to New Relic and a little New Relic plays in this, really the monitoring tool. We've got all the different signals from the system. Major duty really takes those signals and helps to digest them and give you some intelligence into what's going on, what needs to be addressed, really being able to read between the lines, understand what incidents, and I see the question of what kind of incidents we're talking about, this could really be a number of incidents. This might be an incident that is related to your website for one of your digital tools. There's also incidents, we see folks using these tools to provide alerts around incidents that are happening out in the community and in the field, what they're doing. So we've got organizations that are using to send out an alert around an incident, violence, community violence reduction or online community states as where folks are engaging around a certain issue or a certain need. And there's key words that are flagged and those are flagged and it's an incident or an alert comes in. So think of incidents pretty broadly and they oftentimes kind of have initial references around your systems, your digital tools that you're using and if an incident arises from there, you'll be able to address that to ensure that the system, whenever it is your website, you know, your client service tools, things like that, that they're up and running, provide the services you're trying to provide to your decision, but it really can be a lot of trouble. And then, you know, what we're really going to focus on most of today is around the OWL Slack and be again, that kind of digital headquarter of the command center and interact with New Relic and PagerDuty and other tools to provide one space to communicate and collaborate and keep you working from within that space without having to transition between a bunch of different environments or tools. And again, it's in the smallest of directions. You know, we know that you have more than just one or two tools that you're using to serve your institution or execute on your mission. So with that, I'm going to turn it over to Matt to talk a little bit about New Relic and the whole process. Wonderful. Thank you so much, Jesse. Really appreciate that. So from a New Relic perspective, we can take in source information from just about any bit of technology that you might have. So what I'm going to speak to over the next few slides here is really going to be what the traditional sense of incident response is about within your technology landscape. So just to give that a little bit of extra context for the content on these next few slides and where New Relic specifically fits in. When it comes to incident response, you want to act quickly and smoothly. With our dear friends here from PagerDuty and Slack, we can make that happen. We've got you covered. As you can see on the slide here, we can take in information from a variety of technology sources, platforms, systems. And we go beyond what you might think of with traditional monitoring tools. We provide comprehensive, what we call observability and you might immediately stop and think when you hear that word, what does that mean? We provide visibility across your entire landscape so that you're not in the dark, so that there are not as many creepy unknowns. And we refine all of the heaps of data about those systems, their health, their performance, all of what's going on under the hood. And we reduce that down. We refine the heaps of data that we take in so that you're prepared to take action, provide you specifically in real time what you need to take action more easily, more confidently and quickly. We are a source of truth, as I mentioned, for the reliability, availability and performance across your technology. It could be cloud systems, it could be servers, it could be websites, it could be custom applications, APIs, any number of things, you name it, it won't waste your time with all of the possibilities. Reach out to us, we'd be happy to talk to you more about it. The whole point though, as far as this goes is to save you and your team time and energy so that you can focus your attention and act in a way that's pointed towards where your energy and time is best used and most needed, moving the needle on your organization's mission. So by using our technology, the New Relic platform in conjunction with PagerDuty and Slack, as you saw in the prior slide, we're in effect upstream, we're collecting all of this information around your systems and we provide not only the visibility so that you can see and better understand what's going on across the landscape, but more importantly, and as we're gonna talk about today to help facilitate action, the specific actions to be taken by you or your teams in the response setting. We really are better together and today we're going to focus on the actions that you can take, both from the perspective of getting the coverage and visibility, but specifically today, we're gonna hone in on, as you've heard, incident response, the steps that you can take to help set yourself and your team up for success. We want to help you organize that process to consolidate the information and separate noise from signal, give you exactly what you and your team need to move quickly in the heat of the moment. And by focusing on incident response, we know it's needed in every organization. It's relevant regardless of the size or domain of the organization and the work that it's doing. And more importantly, the tools and techniques that we're here to share with you, they're proven. And we know that getting it right can be a huge win for you and for your organization. All right, so with such an important topic, let's set the stage with a couple of visual examples that bring the theory into practice. So you can start to think about what we're about to talk about and we'll go into more detail. One example is something that everyone can and should do. It's somewhat, I would say ubiquitous in terms of the opportunity. The other is more about the art of the possible. With New Relic, we integrate seamlessly with Slack just like we do with PagerDuty too. And we bring the information you need to be fully informed to take action when and how you need to. We're working together across these platforms and bringing that information to you in a way to streamline and simplify and to meet you where you are and where your teams are. On the left-hand side is an example of just a simple notification in Slack. So for those of you who are familiar in work in Slack, as I'm sure you'll hear more from Laura here in a bit, we wanna provide that information and meet you where you are. New Relic, in this case, is presenting a significant increase in errors that have popped up in a billing service. Now, just to be clear, that's just a basic example. This same concept around notification to create awareness and keep teams informed could apply to your website, it could apply to servers or other systems. Like I said, we've got you covered. Importantly though, an update is also made when this error rate in the example has subsided and returned to normal. So we keep you updated. We can bring this kind of awareness about your technology's health and performance right to where your teams are and where they're working every day. But more than that, combined with the power of PagerDuty and the advanced intelligence natively within the New Relic platform, we can hone in on exactly what your teams need to know, what actions should be taken, and to cut through the clutter and noise to sharpen your operations capability, speed and responsiveness, starting today. Now, let's take a quick look at the right hand side. You can see there a quick but sophisticated example of what's possible. At the very foundation, you'll hear throughout our session, the heart of the story is having a well-defined process and streamlining and supporting that process, making it easier for the people doing the work, setting them up for success and lightning their load. And we do that with the power of process meeting the combined platforms were better together. The example here on the right hand side shows how our incident management process at New Relic uses Slack to collect and share incident details from responders. And we do that by using a custom bot built within the Slack platform. And by doing that, we're streamlining and simplifying the information gathering process and facilitating better communication coordination. Today, you're gonna hear about action, how your workflow can change to help teams stay focused. And, you know, so let's take a quick step back and speak to the broader perspective of why. The main success factors that propel thriving collaborative operations and even more broadly the success factors for modern operations. All right, so you've gotten that sample that I just talked about with the visual, the theory to practice, the what and how. I'm super excited because there's so much goodness that Laura is about to share with you. So let's just take this quick moment right now to set the table and speak to what we're seeing, what's consistently proven not only to be successful but to elevate success. The four pillars that you see here are exactly why we're all here to partner together and to help you and your organization succeed. Factors like reliability, efficiency, delivering an outstanding experience for your donors, your members or constituents. And while continuing to innovate, these are foundational pillars that are just important to nonprofits, charities and NGOs and your stakeholders and beneficiaries as they are for commercial companies and their customers. So just to reiterate because it's so important to us on behalf of PagerDuty Slack and New Relic, we're all committed to your success together and as you'll hear, these pillars of success are interconnected just as our platforms can be interconnected and your work can be connected. The work can be clarified, refined and simplified and with the ModernOps toolkit and the power of a digital HQ and Slack, we're here to enable your success. So let's go over to you Lapa. Thank you, Matt. So I saw in the poll that some of you are already using Slack to handle incidents and that's really amazing news. So let's chat a little bit about Slack and the importance of having a digital headquarters in any sort of organization. I think especially organizations with limited resources, urgency of mission, folks that are wearing 10 different hats. I don't know if this rings a bell or this sound like anyone on here. Like I said, most of my career has been in the nonprofit sector. So I really understand that we need to do as much as we can with as little as possible and as efficiently and effectively as possible. So what we did is we kind of created this digital headquarters and we architected it around three pillars. We created a space without silos. For everyone where employees can share knowledge, culture and identity. So with Slack, anyone within your nonprofit, your charity, your organization, whether you're in the fundraising department, whether you're an executive assistant, a therapist, a legal advisor, whether you're out in the field, inside the office, everyone can automate tasks that take away from that deep meaningful work or time that you could be spending with your team or those who you serve. Thank you. So the first thing is we break down communication and collaboration silos across your organization. And the way we do that is through Slack channels. So Slack channels really transform how your teams work together, which results in increased performance because the structure of people's work in channels mirrors the priorities of your nonprofit. And we really take this one step further. We get you out of email silos, phone calls, even faxes, and we invite your partners, your donors, your vendors, your constituents in to Slack through Slack Connect and provide the ability to collaborate securely in real time. The second thing that we do is we help you embrace flexibility so all of your employees can do their best work from anywhere in any way. Obviously COVID changed everything. And at Slack, we really try to be as inclusive as possible in everything that we do. So last year, we actually conducted a survey and we found that the desire for flexibility was actually strongest amongst those who have been historically underrepresented. So these are people of color, these are women and these are working mothers. So Slack really gives you the ability to work synchronously, that's my dog, in an asynchronous manner, right? So it doesn't matter if you're on your couch, you're in a coffee shop, you're in a park, and we like to do this through something called huddles or clips. So your employees can choose where and how they participate and contribute their best work. And then lastly, automate work, right? And so the future really is now, we bring the power of automation to everybody in your company throughout every department. 80% of workflows that are built in Slack are actually created by non-technical folks, non-developers. So everybody has the chance to automate their tasks, their daily processes with our building blocks and our workflows. So honestly, I'm not the most technical person and it really is sort of a lovely intuitive process that even the least technical folks can engage with. So how can Slack and your digital headquarters improve incident management? Obviously we've heard quite a bit about it. We did a survey of some of our customers who are using Slack for incidents response and found some really incredible statistics as you can see here, right? So 17% faster time to detect incidents, 19% reduced mean time to resolve incidents, and then 86% agree that Slack makes it easier to share learnings, right? And this is within Slack, but also Slack and leveraging these various integrations, such as PagerDuty and New Relic. So three simple tricks to get started, right? How do I even get started? So step one would be to integrate your monitoring or observability tools, again, such as PagerDuty and New Relic to Slack, so that you can get real-time alerts in channels where your team works and to automate parts of your incident response. Number two would be to start using incident channels to collaborate and document incidents, to supplement what you already use now. So like a video war room with Zoom or you can integrate it right into Slack, or we have our native tool called Huddles. And then number three is you don't need everything sort of automated on day one to start getting the value out of Slack and its integrations. I'll simply recommend that you start to use channels to collaborate during the incident and control the chaos. Now, you know, I saw in the questions that there was like what kind of incidents and Jessie, I just wanna reiterate your point, right? An incident can be, hey, maybe your website is down but an incident can be like, hey, we have violence here, right? And so it's kind of like your definition of what that looks like for your own specific organization. And something just important to call out in terms of Slack during incidents. Number one is you wanna take those conversations out of DMs, right? You wanna be able to have this incident be as transparent as possible and get the most visibility as possible to those who need to be aware of that. And then another recommendation would be to use threads, right, threading in that message just to keep everything organized and you're not like flooding the channel and the larger team. So these kind of three simple steps, I'm gonna break them down into more detail. So, now that you know that Slack can help you sort of transform your incident management process, something that's really valuable again is sort of this very specific guidance and some best practices. So before your incident even begins, your monitoring tool automatically will send an alert to the appropriate channel like an alerts channel, right? Or somewhere where your integrated app sends that to. Again, this would be through something like pager duty which helps automate that response. Then responders can quickly discuss the level of response needed. It can be in a Zoom call, discuss it in a thread, use huddles, whatever works best for you. And then once you understand the impact, you can declare it as an incident along with the severity and whatever other details need to be known. You can do this with just the push of a button or a simple slash command, all done within Slack. And then a notification with incident details could be sent to a maybe all incident channel for visibility across the larger engineering team or the ops team or the folks on the ground, folks on the fields so that they can be aware of the situation even if they aren't needed to actually resolve the incident. So again, automation is really the theme here. And then we can go on to the next slide. So as the situation evolves, other team members can enter the channel but when they join, there's no interruption because instead of announcing themselves and asking for an update, they can just literally scroll up and they can see exactly what's happened. They have all the data there, all the historical information. And then each team or each squad can have a separate thread for very specific topics, right? When there's a lot of back and forth, you don't flood that channel. You're keeping everything organized in your threads. And if you need like a real-time discussion, again, you just use Slack Huddle and you can talk it through right in Slack. And something that I really love, which is just really like super low hanging fruit is to use emojis as a way to dictate where you are. And so for example, a thumbs up, right? Just to show support for the approach that you wanna take or if something was completed, you can put a little check mark or it's like, hey, I've got eyes on it, I'm working on it. You could put the two little eyes. And so this is just like a very easy way for people to have a summary of where you're at. And then you can see how this sufficient collaboration and sort of total visibility across the team results in faster time to resolution. And I'm gonna go to the next slide, please. And then of course, when something happens, right, they're really stressful. So building an incident report or doing like a postmortem, it can take a lot of time and a lot of times you don't have all the information, a lot of time it can be quite biased because you don't really have everything recorded. You definitely don't have time to like take notes while this incident is going on. And so what's really great is, for example, as you're looking through your messages, you could put a little light bulb just to be like, hey, you know, this is something we can look at or hey, this is something we did right. And you can also even search for that specific emoji. And then that, so you can use that emoji when you place it under a message, it'll send that message to another channel where you could essentially just be keeping all of your ideas or your light bulb moments. So the incident reviewer can quickly kind of scan the channel and put it together very easily into a timeline, into an incident review, and then you can directly assign action items right from Slack, right, or you can integrate whatever project management tool you're using. So your postmortems and your incident reviews are really just painless and easy with Slack. You also have everything time-stamped. You have an audit trail of exactly what happens, the decisions that were made, whatever metrics you might be using, who said what, et cetera. So this really helps your incident review be blameless, non-biased, and extremely accurate. So that's actually all I've got today. And we can move on to the next slide. Thank you so much. Thank you so much, Lara. That was great. So I am very happy to introduce to the webinar, Kate from NYPR. Kate, maybe you want to introduce yourself and tell us what you do at New York Public Radio. Sure, thanks for having me. My name is Kate Edmondson. I work at New York Public Radio and the senior manager of platform engineering. And what that means is, I am a software engineer working on websites and apps, but I'm also in charge of the platform group. So that covers sort of backend engineering and DevOps. So some of the parts that we've been hearing about, monitoring and making sure our services are healthy and our websites are up and things like that. That's what I do. Awesome. And how is that going? What are you guys currently doing for incident management? Reporting, philosophy, thinking, systems. How's it going? Yeah, I would say it's at a workable state with room for improvement. We, as our team has been, New York Public Radio is an organization of about 350 people. Our team, the digital and sort of product oriented team is maybe more like 20. So we're a small team within the large organization. And my little team is three or three people or four people. So the rest are designers and engineers. And we, our team has been kind of maturing over the past 15 to 20 years. And we have, we use all three products that are being discussed today. But we also have sort of a smattering of other things that we have used over the years. So I think that the place where we're in today is we have, we do have a process in place for incidents kind of at all levels. Small things that are not necessarily big issues, maybe a certain page on one of our websites is throwing a bunch of errors to giant emergencies like the live stream is not playing or WNYC.org is down or something like that. It's, so yes. So it's workable with room for improvement is I guess how I would say we have monitoring set up. We use AWS for quite a lot of our monitoring and increasingly New Relic. We've had an account and a couple of monitors set up with New Relic for several years, maybe even many years, but we were kind of under utilizing it. They were mostly keeping track of our apps. And those have been somewhat neglected. So we just ended a two week engagement with New Relic actually as customers of their pro bono week and got some recommendations and next steps and are planning to, in fact, are already implementing some of those recommendations. So we do have, and we also have a couple of other products that we've used in the past that give us sort of automatic information about errors across our websites. Some of those are integrated into Slack as well. We use Slack very heavily at our organization. And then finally we do use PagerDuty on my team specifically. So PagerDuty is kind of our currently reserved for our big emergencies. We have across a few teams, in fact, our broadcast engineering team also uses PagerDuty so people are on call. And if the live stream is down, whoever's on the schedule at that moment gets, according to their communication preferences, a call or a text and or an email and proceeds from there. So there are, and then I guess the part I skipped is some of the lesser things and also maybe including those bigger emergencies we have integrated into Slack as well. So we do have an alerts channel. We also have a sort of catch all emergencies channel that has gathers many of the people on our team as well as some, you know, our chief product officer and some stakeholders that not everybody, because this is a sort of ongoing channel, but a place where you know if you see something in there you should go and look and see what's going on. So I would say that we have the infrastructure pretty well covered, but some of the connections could be more sophisticated and the way we fill in the gaps is with human communication. I think some of the things, ways we could improve are we, we've noticed some places where we're missing some automatic information, some monitoring and we end up getting error reports from either our listeners or more commonly other people at the organization. So a producer is having in trouble accessing the content management system or someone on a show realizes that the podcast episode hasn't been updated even though it was supposed to be in Spotify an hour ago. So those are the places where we're getting the information but it would be nice to have it sooner before we get, you know, sort of complaint some other people. And I think we're in a very good place with where we can go from here. We have information and we're setting aside resources right now and time to kind of consolidate and hone all that information. So it's been happy with these three products and now we kind of need to add some finesse. Right, exactly. I mean, I think it's ever going. If anyone does have any questions, I can't see the chat but if one of the other hosts can see if there's any questions in the chat that they would like to ask Kate or Laura or Matt or Jesse, anyone who would like to ask a question now is a great time to do so. I can also ask you another question, Kate. I was thinking, what would you not recommend that you guys have done that just was like, oh my God, let's not do that again. That was an epic fail. Well, like war stories that you can share that we should not do. In the world of sort of managing incidents? Yes, in, yes, managing incidents. Well, the first thing that comes to mind is our choices about where to discuss incidents and where to triage and how soon to bring people in. And I think that really, that needs to be revisited constantly because it depends on the stakeholders involved and it also depends on the people involved and their preferences. But usually, transparency was mentioned and we've found that that's really important. Transparency is so helpful. It makes things go more quickly. It makes people feel less worried. So I think when, where we've gone wrong is when we've quietly tried to solve the problem over here for too long. Right. And the improvements we've made have been, tell the project manager immediately who can communicate to whoever needs to know we're aware of this and it's being worked on. Yeah, that's what I would say. That's awesome. Are there any questions or anyone opening it up? There's a question in the chat from John. Isn't this the role of the CTO of an organization? Incidents, are they always related to technology? So it's, I guess, a couple of different questions. I can speak to that. I think it depends on the size of your organization. If you have an organization of five or 10 or 20, it may be the role of the CTO if it's a technical incident. But as you say, their incidents don't necessarily have to be related to technology. I think the monitoring tools are, we're mostly dealing with things that can be automated and sort of tracked technologically. So, but there's certainly things that where we need to skip right to the communication part of this sort of workflow. I think in a bigger organization, we don't have a, well, we do have a CTO that technically is our sort of broadcast side, the audio side of the business. But more often it's the people who are a little bit closer to the ground in the size of our organization. So we're telling the sort of people who are on the CTO level as soon as we feel like they need to know, but more often we're coming up with a solution as engineers. Do you guys conduct like Laura was talking about regular postmortems or retros? Is that like a thing you guys do regularly for instant management and like to get better at it basically? We do, yeah. We haven't leveraged many of the things that Lauda was showing in Slack. We do use Slack very heavily, but mostly we will. In fact, we regularly do a postmortem after something successful too, like a bread or something. But yes, after a big incident, we will have a meeting retrospective and write it up and put it on our internal wiki as a sort of like what happened last time, place to go look and we do do that. Yeah, it's very useful. And it's, you know, if nothing else, it also helps with the human side of things, which is someone getting to say, you know, I really would have preferred we had opened up a kind of Zoom room or, you know, a Slack huddle or something because I was too busy trying to solve the problem to also be communicating out what was happening to stakeholders. So it's really helpful to have rules defined early and often. I really liked that, Laura, the postmortem where you have that kind of like report system kind of already in Slack, because as you said, it's an archive for literally everything that happened within the incident. So I feel like we should use that. I'm going to steal that. Yeah, and I think with, and I think, like I mentioned, like you can make it work for you and your size of organization. But I think to Kate's point, what's really important is you do have these wonderful tools. You do have these wonderful integrations. But I do think step one is assigning roles for folks to be really clear what's an incident and what is my role here. Because if you have that strong foundation, then you can really make the tools work for you. I would also add that some of the things you showed, I was surprised. I was like, oh, I didn't know you could do that. You could add an emoji. So I think if there's anyone listening who has never used something like Slack or New Relic or PedroDuty, don't be overwhelmed by all the possibilities. We've been using Slack for probably six or seven years. And we weren't starting with the level of sophistication. I think it's OK to begin. And then if everybody wants to have text responses, that's great. And that will still help. And then over time, if you realize, hey, there's this fancy add-on or process we can use, then you can layer that in. You don't have to do that on the first day. Totally. Yeah, even that simple trick of the threading, just keeping all the noise in that one single communication helps when you've got hundreds of different channels open. Any other questions for Kate, Laura, Matt, or Jesse? I can't see the chat. There's a question in the Q&A from John. It said, would you sum up a sample use case for Slack and New Relic integration? And that's for anybody. I can certainly jump in on that. There are several. One is, again, just sort of New Relic can present what we call notifications or alerts through Slack, because that's where the users are. So if there's something going on, like, say, for example, a web server is down, just as the cleanest, simplest example, you can know about it as it happens. It's not something that you have to go out and look and see. We do have a wonderful user interface that you can do some fantastic things with. But one of the key messages for today is that we want to meet you where you are. And that is the digital HQ. That is within Slack. So we can take it as broad as any of the information that we're collecting. We can refine it down and make sense of it and present that to you where you are so that you can take action. What we saw earlier in the little screen snip example was just for awareness. The billing service was experiencing a bunch of errors. It could just as easily have been turned into an alert where someone does have to respond and that that response actually can be taken in terms of the team or the individual who's responsible going back to the example of a web server being down. When that web server is brought back up and the incident is resolved, you can communicate that back in through Slack, not only to the folks who are in the channel, but also just have a simple action to resolve the issue so that it's acknowledged and to loudest point. The data is collected. Everything's resolved. And so that the quality of information that everybody has is right at their fingertips, right where they are in Slack. They're seeing the updates as they happen. Those who are needing to take action or responsible for taking action can do that natively within the Slack user interface, something that they're very familiar with. So John, I'd be happy to follow up with some additional detail. Feel free to reach out to Holly or to me. We can talk about the very basics of getting you up and running with that integration. It's really simple and turnkey, as well as what other ideas you might have on how to take things to the next level for you and your team. Thank you, Matt. I might add also that what Matt's getting, he mentioned, is you don't necessarily have to respond to everything. And once you start getting information flowing in, that's a great time to then say, OK, how much of this do we want to hold any of this back? Do we want to funnel any of this to something like pager duty when you escalate it? It's really getting data is a great feeling because you're seeing a nice picture of how your website or all your services are doing. And then you can start to imagine the kinds of responses that you might want to take. Before you have that, it's hard to imagine what your process might be, but getting that information is really key. Thank you, Kate. That's exactly, exactly right. Start with getting the information flowing. And then it's basically just an exercise of continuous improvement. You'll get a sense of what really matters the most. And you can fine tune and make sure that you're just getting what you need and can separate out. What do you just need to be aware of versus what really is something that requires immediate action and who should be doing that? We'll also provide some additional resources in our follow up to to give you some additional perspective on this that maybe provide some more specifics and more to sink your teeth into. Yes, we will. We'll be following up. Aretha will be sending out the slide deck and also some links. So we'll make sure to include the quick start guides. Any other questions, I can see a couple more messages that I can click on it. I was just sharing our info. Nice, thank you. Yeah, we have a saying at New Relic. You don't know what you don't know. It's a very like right on Matt's point of, you know, and to answer what Kate was saying too, once you get that data in and flowing, it's then you can kind of make, you know, a more guided decision on what needs to happen. And and again, back to those rules and responsibilities. So people can actually act and solve the incidents. And John, I do see your your info there will be happily following up with you. So thank you so much for sharing that. Awesome. This is great. I learned a lot too. Anybody want to have any closing remarks? My message on behalf of all of us today is a huge thank you. Special thanks go to Kate. Thank you for joining us. We we love you. We love to continue working with you and taking things to the next level. Many thanks to my fellow panelists. And thanks to all of the attendees. Thanks for bearing with us with a couple of those early audio challenges. As I mentioned, please do reach out to us. If there's anything we can help you with, we are here. We're motivated by helping you and your organizations succeed. That's what we're here for. That's what gets us fired up. Similarly, I'll just reiterate, we'll be following up with some additional resources. Please do know that we will be joined by AWS for our next chapter in this series, the third of three in December. So keep an eye on your inbox for that as well as the resources we'll be sharing with you. We'll send out a copy of the presentation that will have some additional resources at a detail level at the end. Awesome. Thank you, everybody. Have a great day. Bye bye. Thank you all. Take care. Have a great day. Thank you. Thank you, Kate. Bye. Bye, everybody.