When I wrote Built for Your Workflows: A Guide to AI in LogMeIn Resolve, my goal was to introduce some of the AI capabilities available in Resolve and show how they fit into the work IT teams are already doing every day.
If you've had a chance to try one of those features since then, you've probably already started to see where they can save time and reduce manual work. What we’ll focus on this time is what happens when they start working together.
Beyond Individual Features
When we talk about AI, it's easy to focus on individual capabilities.
- AI Session Notes helps document support sessions.
- Dynamic Insights helps you quickly find answers in your data.
- Virtual Technician can automate repetitive work.
Individually, each feature delivers value. Combined, they build on one another, helping your team get more from the work it's already doing.
Together, we'll walk through how Resolve AI can help your team capture knowledge → preserve it → automate repetitive work.
Capture
Before you can preserve that knowledge or automate a solution, you first need to capture what happened. That's where AI Session Notes comes in.
In the previous article, I shared how AI Session Notes helps reduce the time technicians spend documenting support sessions, while keeping notes consistent for reporting and compliance. But documentation is just one benefit. Those same notes also power analysis, insights, and knowledge sharing.
From notes to insights
Every completed session becomes another data point. Session Insights analyzes session notes to identify issue categories and the applications involved. Over time, that gives admins and managers a clearer picture of where support time is being spent and which issues come up most often.
From insights to answers
That same information can then be explored through Dynamic Insights using natural language. Instead of manually reviewing session records, you can start asking larger questions about your support organization:
- Which issue categories consumed the most support time last month?
- Which applications show up most frequently in support sessions?
By capturing what happens during a support session, you're doing more than creating a record. You're adding session data to everything else Resolve already knows about your environment, from device health to tickets and alerts. That's the foundation for better reporting, better decisions, and ultimately identifying the issues worth preserving and automating.
Resources:
Learn about AI-generated session notes
Using Session Insights in LogMeIn Resolve
Create custom reports with Dynamic Insights
Go to Session Insights
Preserve
Typically, when a technician solves an issue, that knowledge stays with them unless they take the time to document it for the rest of the team. But now that AI Session Notes is capturing their work, you can turn a successful resolution into knowledge your entire team can use.
From session to article
This is where your team's work starts to pay off. Instead of writing an article from scratch, you can generate one directly from your AI Session Notes. Resolve AI creates a draft based on the issue and the steps used to resolve it.
From there, take a few minutes to make it your own. Add context that only your team would know, like why a particular step mattered, when to use the fix, or any environment-specific considerations. You can also remove anything that shouldn't be shared more broadly.
Where knowledge starts working
Once an article is published, it becomes more than documentation. It becomes a shared resource across your account, so your technicians, your customers, and AI-powered tools all work from the same information.
The more knowledge your team preserves, the more it can be put to work.
Resources:
Generate a knowledge base article
Learn about knowledge base management
Learn more about GoPilot
Automate
Even with a great Knowledge Base article, someone still has to follow the steps every time the issue comes up. Same fix, different device, over and over again. When the resolution has been captured and preserved, there's one more step you can take: let Virtual Technician handle it.
From knowledge to action
When you generate a Knowledge Base article from AI Session Notes, Resolve can also include a Virtual Technician plan built from the same steps your technician took. So instead of reading the article and working through each step by hand, your team can let Virtual Technician run them directly on the device. Your technician reviews the plan and stays in control the whole time.
That's where it all comes together. What started as one support session has become documentation, shared knowledge, and now a fix your team can use repeatedly.
Where automation starts working
Once a plan exists, your team doesn't have to rebuild it every time. They can:
- Run it from the Knowledge Base: start the plan right from the article
- Use it in a session: choose a saved plan from the Virtual Technician panel during a remote session
- Build on it: create new plans that draw on what's already in your Knowledge Base
Since every use of Virtual Technician happens in a remote session, AI Session Notes captures it too. The cycle starts all over again, and your team will keep building on what it already knows.
Resources:
Working with the Virtual Technician
Import sample articles to your Knowledge Base
Go to Knowledge Base
Putting it all together
Every support session your team runs holds knowledge worth keeping. With Resolve AI, you don't have to choose between quickly solving the issue in front of you or documenting it for later.
- Capture: AI Session Notes records what happened, and Session Insights and Dynamic Insights show you which issues keep coming back
- Preserve: Knowledge Base articles turn one technician's resolution into something your whole team can use
- Automate: Virtual Technician turns that knowledge into a fix your team can run again and again
You don't have to set it all up at once. Start with one recurring issue, follow it through each step, and build from there.
We'd love to hear how your team is putting these features to work.
Use your GoTo account to Sign in to the community and share in the comments below: what's the first recurring issue you'd hand off to Virtual Technician?