Transcript
My name is Dima. Welcome to today's AI Copilot webinar. I see people started to join in just to check that you can hear me all right and you can see me all right. On the right-hand side, you will see the chat tab, and just let me know if you can hear me and where you're joining from. Okay. Okay, amazing. Rice, I hope I didn't mispronounce your name, Steve, Julio. Okay, got it. My mic is working. So, okay, amazing. Okay, welcome, Texas. Okay, amazing. North Carolina, Michigan. Welcome, guys. Pleasure to see you all. Pleasure to see you in the chat. Before we begin, a couple of housekeeping rules. Right next to the chat tab, you will see the Q&A tab. This is where your questions about AI Copilot should go. We will dedicate some time at the very end of the session, and our today's workshop is about AI Copilot, use cases, and something beyond just the basic functionality, and I try to structure something that is useful for your day-to-day work. Our part one is dedicated to more like RMM and PSA day-to-day focused. Our part two will be focused around more advanced things with AI Copilot, but for the ones who are just joining us for the very first time and for the ones who don't know what AI Copilot is, we'll also provide a very, very thorough explanation about it. Okay. Let's begin. Okay. So, to answer one of the questions up front, the recording of this session will be sent to you as soon as we are done and as soon as it's uploaded to the cloud. Usually, it happens in the next 24 hours, so don't skip it in your inbox and just wait for it to arrive. So, the Q&A window, I send it to you, and also any of your feedback, both in QA and chat sections, is appreciated, always welcome, and we pay great attention to those details and try to address as much as we can. Okay. So, our today's agenda is introduction, what the session is about, what is AI Copilot specifically, then we'll move forward on to the demo itself. We'll summarize everything that we will cover during the session and we'll move on to the Q&A section of the webinar. Okay. Okay. I just received a comment that someone cannot hear me, but please check your speakers because many people just shared information they can't hear me. And also, my mic is operational. I can see it in the UI. But just to double check, I'll redo the mute unmute. Okay. My name is Dima. I'm Technical Product Marketing Manager at Eterra. Previously, I've been busy with professional services project and customer success, so I'm pretty customer-facing and I've talked to customers a lot. I was responsible for the most complex implementations back in the day. Now I'm responsible for everything that is cool about the product and everything that is technical, transforming it into like a language that everyone can understand, relate. And I'm making sure you're making the most out of these sessions and your time is precious. We know that. And let's begin. Okay. AI Copilot, our today's subject. So we, as a company, offer two AI products, one of which is Robin, which is not the subject of today's session. We had a session about Robin yesterday. The session is available on demand. Our today's topic is AI Copilot. What's special about it? AI Copilot is a part of Eterra that is technician-facing AI assistant. It helps you to do RMM-focused tasks, PSA-focused tasks, meaning that it's not only a chatbot that leaves on the side panel and works like any other AI chatbot. No, it's something else. First off, AI Copilot has certain agentic traits, meaning that as soon as Eterra agent is deployed and telemetry is received by your Eterra console, you start to get benefits from it because Copilot becomes context-aware. It can do actions, health checks, diagnostics, help you answer tickets, help you summarize your day, and even help you with advanced reporting needs. But we'll talk about it a little bit further down the line. Okay. What is AI Copilot, where it lives in Eterra's UI? You can access it from literally almost any page in the product. It lives on the tickets page, alerts page, devices page, and most importantly, it's context-aware. Let me switch to the UI real quick to demonstrate. If you click on the devices page, you will see the AI icon, and you will be able to go through anything that is related to a specific device. You can ask certain questions in the chat, which can be tenant-wide. The same goes out to alerts page, but I don't have any. Good on me. Also, if you go to the tickets page, you will also see that you can get AI assistance here. But what does it mean in real life? In the use cases that I wanted to demonstrate, I want to focus on them one by one. Let's start with one of the use cases that I personally love is the general query about the account and something that helps you to either start your day or finish your day with success. Okay. Our first use case is, and by the way, before I proceed, I'll pause for a second. In the screen sharing area, at the bottom right corner, you will see the magnification icon, so you can zoom in if your screen resolution is too high. You can zoom in and see what's happening, but I will read most of the things out loud just in case. Okay. Our first use case is about a general query about the account. There is no device-specific context happening. There is no ticket-specific context happening or alert. So my question is, let's check if there are any devices that are offline for one month. And I'm specifically visiting the devices page, and as you can see, also I wanted to make sure not only that they are online, but also I wanted to check the reboots and the last logins just to make sure the picture is full. So after thinking for several seconds, AI Copilot returns to me and giving me an answer that you don't have any devices that are offline for 30-plus days, which is accurate. The next question that I'm asking is I want to be more specific and prove that it's not just giving a random piece of information, so this is context-aware. Can you please let me know if there are any devices that have not been rebooted in the past 24 hours, to be exact? And as you can see, most of the devices that you see on the screen, starting from the device number one till device number two inclusive, you should see that I initiated a reboot at almost the same time. And on May 19, which is yesterday, on May 19, 2026, they've all been rebooted, and I intentionally didn't reboot two virtual machines just for demonstration purposes. And I'm asking this question, and AI Copilot goes in, and even if I was not here on the devices page, I just use it for the context. And it sends a query and returns back with information that actually no devices have been rebooted in the past 24 hours, which is also accurate. Let's wait for it to respond. And there we are. Okay, so yes, there are 10 devices, which is the exact amount of devices you see on the screen, which haven't been rebooted in the last 24 hours. That is accurate, because it's been a little bit more than that. And as you can see, two PCs specifically, 1101 and 1103, haven't been rebooted since March, which is also accurate. And I'm trying to expand my query to see if any devices have been rebooted in the past 48 hours. To get a bird's eye view, whenever I'm trying to do some patch management, make sure that everything is completed, and maybe some devices keep to beat, and maybe they were flying at the time of the IT automation profile execution, this is why this can be helpful. And this is where you can actually get a bird's eye view without even filtering the devices. It will be actionable from there. So as you can see, I expand the 24 to 48 hours, and it will return to me with, run the query and return to me with basically the same information, but for the devices, for the same devices, but for the expanded period of time, which is 48 hours in our case. And as you can see, it identified only two devices that haven't been rebooted in the last 48 hours, which is accurate. Today is May 20th, and yesterday, May 19th, it hasn't been more than 48 hours, obviously, and March 16th is way above 48 hours. And as you can see, it also mentioned that they belong to a specific site, which is Cranton Warehouse. And yes, it's a little bit of a funny reference to the Office TV series. Okay, our next stop. Our next stop is to prove we'll go into device-specific mode from tenant-wide context mode. So this is one of the ways to use AI Copilot, because depending on the context, it can start a chat, which will be, as I said, specific to a ticket, to a device, to an alert, or it can be specific, or it can be like general, just IT knowledge. It can be like your knowledge base-oriented, but regardless of that, in whichever mode you're choosing, it slightly chooses which tools it's calling in because it just reduces the time to get back to you with relevant results. And as you can see at the top right-hand side, where I'm hovering my mouse, it's in the device-specific context mode, which is PMM Test Laptop, the one you see on the screen. That's a Lenovo laptop. And as you can see, I'm asking a question, list startup apps on this device. It will run a query, and as you can see, it not only knows the Atera display device, but it also knows the real device name, which is accurate. It's 395A, and it will run the query to identify the startup apps which are running on the device. I'll pause for a second here, and as you can see, among all the applications that we're focusing on, it's like OneDrive Setup, AnyDesk, Atera Client, Security Health, Help Desk Agent, which is a Tera agent, and Logitech Download Assistant. And if you want, we can remove or disable any of these. So basically, usually what it takes is usually a script or remoting into a device, but it can be just a free text request, and a copilot will proceed and assist you exactly with this. So let's remove Logitech Download. I didn't bother to type the whole thing because it will do it anyway. And let's take a look at what's happening. So basically, the startup removal action starts to take place, and as soon as it does, the respective, after your approval, of course, the respective app will be removed from the startup, which I do. And it confirms that it's all done, and it ran a recheck that everything was completed, and right after this, it was considered done. Next, something that involves a potential remote session, or maybe not as much. However, I just wanted to present to you a use case where we incorporate the agentic nature of Atera's AI Copilot, as well as Robin. They share the same Atera agent-based connectivity with a device, so they understand to which device they're talking to and which user is currently logged in. So the use case that I will be demonstrating now, it will be looking not for a specific app, but for a specific process, because for instance, you had a ticket, and the person is complaining about, let's say, an application that is running as a process, and it's visible in an activity monitor. However, you cannot start an app, and the user is not aware how to stop and restart the service. And I'm just showing the end user's laptop here, so you can understand what they experience. It's not necessary to run a Splashtop or any desk remote session for this. It's just for demonstration purposes. Okay, so what we're emulating here is that we start a session. So I enlarge the screen, and I put in the password. I'm logging into the system, and as soon as we load into the desktop, yeah, here we are. You can see that, like, it's a fresh boot after a reboot sequence, because it's still loading. And as you can see, our agent has been loaded. This is what I just talked about, about the agentic nature of everything, and I'm starting a task manager just to show you what's happening on the laptop. The process that we'll be looking at will be Microsoft Teams, and apparently the user is complaining that they cannot chat with their colleagues, and we will try to help. Okay, we'll start an AI copilot chat, and I will check the top five processes just as a diagnostic step to utilize one of the out-of-the-box actions that we offer. So the diagnostics are running on a specific device, as you can see, that I can pull live top five CPU consuming processes, so it's also checking, and we can also compare what it's seeing and what's the delay. And the process, as you can see, because the laptop has just booted, they're a little bit jumpy, and they're a little bit all over the place, but you will see five very familiar names, and what is happening from the CPU load. So it's the percentage value, so it's like two and a half percent, half percent, and respectively. So as you can see, it's going pretty well, and as you can see, it's going from like a fraction of a percent all the way up to a couple. Nothing crazy here, but the user's complaint is that Microsoft Teams seems to be running, but they cannot open the application. Sometimes the reason is that the process is actually running in the background, but apparently they cannot identify the reason why it's not rebooting. Now we'll filter by name, and we'll take a look at the Microsoft Teams specifically. Yeah, there it is. As you can see, Microsoft Teams runs eight operations. It consumes RAM, but apparently not running as expected. I will even unfold it to make sure that I'm looking at the right thing. So it's not an app. It's a process in this context for AI Copilot, and as you can see, I ran a command that I tried to close an application, but the application was not open, and AI Copilot was able to identify it. Right after that, it wasn't found as a running app. This is what AI Copilot is mentioning, and it asked a follow-up question. Do you want me to go and try to find the process that is responsible for this app and maybe kill something in the background so you can maybe restart the app after? And what I'm showing, again, pausing here for a second, what I'm showing here is an emulation of a scenario when instead of remoting in to the end user and waiting for their approval, then maybe they're not at their desk. Maybe they need to tell you their password depending on the security preferences of your organization. You don't have to wait for them to be there because Eterra's agent is running, and without remoting in to the device, you can definitely do what you're supposed to. Help the person while they're having coffee and save yourself 10 to 15 minutes instead of remoting in to the device, and it's easy math when it piles up over the weeks and months of work. Okay, and as you can see, the Teams process, it's proceeding with killing the process, and after several seconds, we should stop seeing the Microsoft Teams being present on the device. Okay, it found msteams.exe. Now I say yes to killing the process, and it proceeds with the execution of the following command. Yep, it just did it. So this capture happens in almost real time, so this represents how fast it acts on the device. Okay, the process has been successfully stopped, and if the user needs Teams again, you can relaunch it normally, or AI Copilot can assist you with doing so, which is what we're doing exactly on the screen. So, and as you can see, I did nothing on the laptop itself, but I initiated AI Copilot command, and it relaunched Teams as an app, which proves the point that Tara is there to help you out. But again, what I'm showing is what end users are seeing, because there is no other clever way to demonstrate it, unfortunately, but on the right-hand side, you're seeing what AI Copilot sees, what AI Copilot does, based on the IT technician's commands. So you don't have to remote, you can do this without seeing the screen, so it will inform you on what's happening there. Okay, our next use case lives in the realm, lives in the scripts realm, because as far as any IT technician day goes, there are almost no days without scripts, creating those, maybe like editing those, and everything in between. So the next use case in where AI Copilot will help you is to not only create a script, which is something that you can achieve with any assistant out there, however, what is different is that, A, it's happening right inside your environment, which is happening in this prompt window. You can enable or disable specific scripts to be able to be used after an approval by an IT technician. You can use or not use them, it's totally up to you. You can create a PowerShell script, you can create the terminal scripts for Mac and Linux, but in this specific use case, what I'm trying to demonstrate, as you can see, you have several formats here. And by the way, depending on the extension or the script that you are going for, the extension that you're choosing will define for which OS the prompt will write the script. I hope that makes sense. So basically, if you select the PS1, it will be a Windows script, and if it's .sh, it will be a Unix-based script. Okay, now we're trying to go a little bit deeper into the settings, so you can run scripts as a system as a current user. This is standard settings for the scripts. What is not standard is enable it for AI assistance. So AI Copilot is one component, and Robin is another component here. As soon as I flip the switch, and as you can see, I have both. And also, do I need the user confirmation to do it, or is it safe to run without one? Usually, what happens is that, let's say, if you have any type of safe scripts that end users can use on their own, which is not AI Copilot use script, but more of a Robin use case scenario. You can ask them an additional question or run it without one. But yeah, and also, you can see the three options. You can run it on user devices, the main controller, or a specific device. So you can enable or disable any of those, and you can pick and choose whatever fits your specific use case. I'll just use one of the examples, which are present here, but it just proves the point that it's happening. So clear all files from the recycle bin. So the script will be generated, and a couple of things that I talked with many, many customers in my days in PS, the most common things that are getting overlooked. Number one is that you can select a sandbox device on which you can test the script before rolling it out to the masses. In this specific use case, it will run the PowerShell emulator here based on the laptop selection, and right next to it, you will see the play button. Yep. And I have an item in the recycle bin. Okay, let's go back to the script. And then what also gets overlooked time and time again, if you start on a new string of text with a hashtag symbol, it acts as a prompt, which is not rewriting the whole code, but it adds an incremental change to the script, because maybe like 90% of the script is ready to go, and you want to make iterative changes just to a specific section of the script. And to do so, you don't need to rewrite the prompt or to start talking about it, and this is where it gets more convenient than doing it elsewhere. You can see what script is doing, you can edit it live, and you can add additional sections of the script, which start with... Sorry, by an accident. So I'm adding a section of the script. Wait 30 seconds. Check if something is in the recycle bin, and if there is something, rerun the script once again. It's maybe not the most technically advanced use case, but however, I just wanted to demonstrate what happens when you're adding iterations to a script. So in the string number 38, so you will see right next to the number, you will see a spark symbol right as soon as I hit enter, and it took a split second to do so, and it added a specific part of the script, and it didn't touch anything that was above. You can also add the strings of code in between the sections, and you can just prompt them here. And for A, B, the versioning reason, so it will keep the previous part of the text, and if you have very similar two blocks of text, it will allow you to compare them head-to-head on the screen and delete whichever part is not relevant to you. Okay, and then we can, while we are having our sandbox device selected, we can hit play and test the script and see if it runs out of the box. And as you can see, recycle bin emptied successfully, and the script ran, and there was a folder which was just a couple megabytes, and it just did what it was supposed to. Our next use case, moving on from there, switches the gear and lives apparently in the PSA role. What do I mean by that? So, doing RMM things and remoting into the devices, executing RMM actions is one part of some people's jobs who joined our today's sessions. Kudos to you guys for doing the hard work day in, day out. But sometimes we have the need to summarize the day before. Maybe you had to take a sick day. Maybe you're just a team lead who is managing a team and you want to know what happened without you while you were not at your desk. For that, we have capabilities that are related to all tickets at once and specific tickets on the left-hand side if you need to. So, let's start the demonstration. So, what I'm prompting is, please list resolved tickets for May 19, 2026. And as you can see, I have a bunch. I intentionally brought them back and I applied a filter because I had the ticket 131, 125, 124, and the rest of those, I have several tickets that have been resolved. Not all of them were resolved on a given day, but let's see. Okay. So, tickets 131, 129, 125, 124, they were resolved. So, this is accurate and the rest was not touched because it happened a couple of weeks before. So, you can go deeper than this and ask a question about, for instance, were there any tickets that, hardware-specific ones? Let's imagine there's like not four tickets, but more than this. So, were there any hardware-related requests? Simple question, but it can bring you back a specific ticket, which is ticket 129, request power supply. So, if you'd like, I can pull the full details just for that ticket. And, yeah, I say go and I'll grab the full details for the ticket so we can review the hardware requests. And what happens now on the screen? It's pulling the details, reading through the ticket. So, as you can see, the request power supply came from Michael Scott, which is accurate. Apparently, he is the only dude who needs a T-shirt. And 70 minutes of logged work and it was categorized as a request. And there was no SLA and it returns this code because this is the value for the blank. So, a link to the contract ID number two. So, this is something that pulls from the back end to give you more details. And this is something AI Copilot has access to. Okay, I'm happy with the results, but I'm not going to go into the details. But I want to take it one step further without even accessing the ticket itself. So, based on the ticket summary and the ticket information that's being pulled, do I need to buy something? So, it adds a little bit of action here, action layer. So, based on the ticket, it's a request for a power supply, but it does not specify that there needs to be something purchased. Which is accurate, and we will see it in the next use case when I will switch to the ticket UI. So, let's go ahead and run this. Which is accurate, and we will see it in the next use case when I will switch to the ticket UI itself. Which is here. Okay. No, here. So, the ticket one to nine. And before I go any further. So, it was a Robin Resolved ticket, but as you can see, we're dealing with the same laptop, which is Lenovo ThinkPad P14S. The model and the required charger based on the model was listed here. And the user was asking about a power supply because they were intended to be traveling for business to another country. And this is exactly what happened on this ticket. So, as you can see, the ticket timeline is pretty rich. Many things happen. So, the reason for escalation, work done, everything is here. It was done by Robin. But before we move forward, I wanted to draw your attention to something. So, it gets overlooked very often. So, in the ticket UI, as soon as it's resolved, there are like two ways to do the thing that I'm about to talk about. To talk about. Yeah, sorry. Number one. So, let's imagine you have a ticket that is super close to being resolved. And you can go ahead and generate KB article. Why is it needed? It's needed for a very specific reason. And the reason is that AI Copilot is as good as any other AI solution without context. KB articles are used as fuel to beef up the brains to give you more context-aware and company-aware responses whenever you're asking it something or you want to know how things are done. And the better KBs are, the better responses are, and it just makes everything better. And this is why the generate article exists as well as the generate reply, which we're not covering in this specific demonstration. But if this ticket was an ongoing one, we could have saved some time typing, because apparently AI types several times faster than human beings, especially when it comes to typing stuff and saving your time by just doing so. Okay. So, as soon as we click the generate KB article, we go into the article content, and as you can see, the KB is generated based on the provided info. This is where you get your time saved, and you can create an internal or an external KB article for future use and for future context. Because this is something that will define the quality of responses moving forward. And as soon as we identify that this KB is good enough to be part of our day-to-day work, we can add in which sections should be displayed. The priority, because the article title is apparently filled in, you just need to add keywords, edit the text, maybe add some pictures, and call it a day. What else is here? Also, I'm pointing there where you can create it for an internal use, and also you can make it customer or site-specific. Okay. Okay. In the next part, I wanted to point your attention, guys, to one of the components of the system which might be super beneficial for your day-to-day work, which is AI Center. What is it? AI Center is the HQ for everything that touches the AI realm, meaning that it's like how prepped your environment is, how many potential KB article candidates do you have, how many remote sessions could have been a script. It's especially valuable for those of you who is using Splashtop as their remote tool of choice. And as soon as you click on AI Center and you go into the actionable insights, you will get two types of insights which are offered as of today, which might be subject to change, but I didn't tell you anything. So, basically, as soon as the ticket gets resolved, it might end up as a drafted KB article candidate. It's not blending in your environment without your approval, and you can just click on the review article button, and it will lead you straight to the KB which is generated and just needs your post-editing skills. But also, based on the two remote sessions that could have been a script number one, which is like the change power settings to configure the action which should be taken when the lid is closed, and the second is like clear the recycle bin to free up space on the client system. And as you can see, the script is suggested based on two remote sessions and one remote session, respectively, which is pretty neat. And as you can see, you can either review an article or review another one. You can save it for later. They will be marked in the section at the very top, and you can implement them, and the more you implement, the merrier. And let's go into one of the specific scripts, which is like based on two remote sessions. These remote sessions could have been a script, and you can filter by the insight type at the very top right-hand side. As soon as you click review scripts, you will see that the prompt is already there, toggles are there, the extension is there, a script name, script description, and the script itself gets populated because of the prompt and auto-prompting here, because the prompt is generated because it described the remote session log. Very important disclaimer here. So to the ones of you who are using Splashtop, we offer the Splashtop AI summary, but it's not based on the screen capturing. It's based off of the actions taken from the log perspective on a specific device, which are tracked in the recent processes to a certain extent. Sorry, I need to go back. Yeah, so here's the script, and basically that concludes this specific use case. Okay, last but not least, something that we added just recently, and something that is pretty simple, but it's super important. Why do I even mention it? Because it's relevant for both AI Copilot customers, for broadband customers, it's relevant for anyone who is trying to get their data hygiene to the highest level, especially the ones who are syncing their entry IDs and environments into Eterra, and they're populating certain contact fields alongside with it. So what does this report do and what is it good for? Short answer, it gives you a perspective of which site has which agents installed, meaning which site has which agents installed, how many of them have contacts assigned, I will show it in a second. When was it last seen, which is apparently today, I did a fresh screenshot just for you, and user mobile phone is key here, and I intentionally removed just one, which contacts without a phone number, which have contact but don't have a phone number, and agents without a contact email is three here. And I don't have any filters present, but let me show you where to find this report specifically. It lives in the report section, analytical reports, lives in the presets, and you go all the way down to AI readiness. And as soon as the report loads, even before you see the report itself, I'll probably zoom in here, you will see the disclaimer. The AI readiness is one of the small experiments that we're doing to put things in perspective. Before you use the report, please read what this report does, how to read the numbers before you do anything, because sometimes it's better to be informed rather than to do things and then say that the numbers were not there. So it gives you the total number of agents, AI ready agents, but what is contact data good for? Prime reason is that as soon as you attach a device to an end user, it gives a specific benefit. For instance, whenever a user is initiating a ticket, the user starts a ticket, but if the device is associated, in the ticket page, you will see the remote button. If it's not done right, you won't see the remote button. Easy as that. Second part is the presence or the absence of the mobile phone number will be super good for the ones who is trying to utilize such advanced functions as local password resets, Entry ID password resets, and everything in between, because the temporary password upon request will be sent to the person's phone number, and this is exactly what this report is trying to address. So you get a better understanding of what's happening here from the data population, so the total number of agents, which of those agents are fully AI ready, they can fully benefit from having AI in your environment, and everything that is related to it is located here. This report is available as a preset starting from Tier 2 of our subscriptions, both for MSPs and ITDs and higher. The customization starts at plans which are Tier 3. And ladies and gentlemen, this was probably it for today for demonstrations, and it's time for questions and answers. Okay, so I saw a couple questions in the chat. Let me spend a couple minutes reading them. So Nathan is asking, correct me if I'm wrong, are you showing us that when you're connected remotely to a client's PC copilot, it automatically sees what you're doing and gives you suggestions without asking it? Now, the use case that was also having an end user's screen there was for demonstration purposes what an end user is experiencing. The remoting into the end user's machine is not required. You can just talk to AI copilot to execute the very same actions. I was showing the end user's laptop to demonstrate what happens on their end to prove that it's actually taking place on the end user's device. Regarding the video quality noted, I'll take a look and we'll do everything that is in our possession to correct it for the future sessions. Okay, it's clear now. It must be just a low upload bitrate. It might be. I'll check. Okay, and the only question that I see in the Q&A, which is a question, so does the agent have to have been installed for the duration of the period? You're querying. So, a tera agent is the foundation of the agentic component for a tera. It allows it to fetch the device's telemetry and make judgment based on that. So, if it's hardware related, OS related, software related, and everything that involves an actual action on the device needs device context to do so. Otherwise, the device will be irrelevant. And this is why without assigning the, let's say, aside the device context, it will be as good as any other chatbot out there. And it's not what AI can be used for in 2026. And this is what we tried our best to show you today. But we also have the part two where we'll be demonstrating more advanced use cases on how to level up your reporting and how to utilize the conversation with third party tools. And we'll talk about this on the part two. I'm just throwing in a couple spoilers before we wrap up because we have a couple minutes left. The last question is, why does a tera have a galaxy theme? And good presentation. Thanks. Thanks for the compliment. Why do we have a galaxy theme? Well, apparently, we consider every person who is doing IT or so-called autonauts and people who are actually going above and beyond into the depths of the computer world, which is endless, almost. So we appreciate you and what you do, the scale of your impact to any organization. And this is why we share this type of vibe. Okay, I see no more questions. And we're right on time. That part. So just got a question last minute. So when will you be doing the part two? The part two will be announced shortly. And please pay attention to our website. And we'll think about how we can also invite anyone who participated in part one so we can invite you so you don't miss it. And you have it in your calendar and you have dedicated time for this. Okay, so Patrick, so you just elaborated on your question, so I will answer it. Which devices have not been rebooted in the last 30 days? If a Tera agent was just installed a week ago, will it answer properly? So it's not something that is, as far as I'm concerned, as a Tera agent related, it goes back into the registry and checks when it was rebooted to find the exact value. So this might be the short answer to your question. And Steve and all the rest of the participants, thank you so much for staying either late or early to this session. Thank you so much. See you in part two. And we have more cool webinars coming up. Please don't be a stranger to Tera.com slash webinars. And on the top right hand side, you will see the request to demo button if you want to know more. And if you're just checking out a Tera as your next RMM, PSA, and how we call it now, autonomous IT solution to be in sync with the modern technology. Be in sync with the modern trends in enterprise world. Request a demo and we'll answer all your questions in great detail. Okay, so thank you so much and see you on the next one. Thank you. Bye bye. Transcribed by https://otter.ai
