Getting More Out of ITGlue: AI-Powered Documentation During Triage

Every MSP knows they should document everything. And most MSPs do — or at least they try. ITGlue folders are full of network diagrams, SOPs, configuration notes, password entries, and client-specific procedures. The documentation exists. The problem is that it doesn’t get found at the right moment.

A technician picks up a ticket about a VPN issue at a client site. There’s an ITGlue article describing that client’s exact VPN configuration, including a known workaround for the specific error message in the ticket. But the technician doesn’t search for it — either because they don’t think to, they’re in a rush, or they search with the wrong keywords and get no results. They spend 20 minutes troubleshooting from scratch, arrive at the same workaround that was already documented, and the cycle repeats next time.

This isn’t a documentation quality problem. It’s a documentation discovery problem. And it’s one of the biggest reasons MSPs don’t get a full return on their investment in tools like ITGlue.

The Documentation Discovery Gap

The gap between “documentation exists” and “documentation gets used” is wider than most MSP owners realize.

Technicians Don’t Search When They Should

Under the pressure of a growing ticket queue, searching documentation feels like a detour. A technician looking at a straightforward-seeming issue is more likely to start troubleshooting directly than to stop and search ITGlue first. The irony is that the search would often save them time — but in the moment, it feels like it’s adding time.

Search Requires Knowing What to Search For

ITGlue’s search works well when you know the right keywords. But tickets don’t always use the same terminology as documentation. A ticket says “internet is down at the reception desk” — the ITGlue article is titled “Branch Office Network Configuration” and describes the specific switch port assignments and VLAN configuration for that location. The connection is obvious to a human who knows the client, but not to a keyword search.

Documentation Is Organized for Writing, Not for Finding

Most ITGlue environments are organized by client, then by category — networks, applications, passwords, SOPs. That structure makes sense when you’re creating and maintaining documentation. But when a technician is triaging a ticket, they’re not thinking in terms of ITGlue categories. They’re thinking about a problem, and the relevant documentation might span multiple categories or be filed under a heading they wouldn’t guess.

The Knowledge Stays in Senior Heads

Your most experienced technicians have mental maps of your ITGlue environment. They know that Acme Corp’s printer issues are documented under “Office Equipment,” that the VPN workaround is in a flexible asset, and that the password for the legacy system is stored under a non-obvious name. New hires don’t have those maps. The documentation is equally available to everyone in theory, but wildly unequal in practice.

How AI Changes Documentation Discovery

Junto integrates directly with ITGlue and changes when and how documentation gets surfaced. Instead of relying on technicians to search proactively, Junto’s AI processors automatically search ITGlue as part of the triage pipeline. Every ticket triggers a documentation lookup — no manual action required.

Automatic Relevance Matching

When a ticket arrives, Junto’s documentation processor doesn’t just search for keywords from the ticket subject. It uses the full context — the classified issue type, the client, the affected device, the user — to search ITGlue intelligently.

A ticket about “Outlook keeps crashing” at Acme Corp triggers searches for:

• Acme Corp’s email configuration documentation
• Known Outlook issues across all clients
• The specific device’s configuration notes
• Recent changes documented for Acme’s M365 environment
• SOPs for Outlook troubleshooting

The processor searches across categories, flexible assets, and embedded documents — not just top-level articles. It finds documentation that a keyword search would miss because it understands the relationship between the ticket and the documentation, not just the text overlap.

Documentation Surfaces Before the Technician Acts

The critical difference is timing. In the traditional workflow, documentation search happens during troubleshooting — if it happens at all. With Junto, documentation surfaces during triage, before the technician starts working.

The technician opens the ticket and sees relevant ITGlue articles already linked. They didn’t have to search. They didn’t have to know where to look. The documentation found the ticket, rather than the other way around.

Context-Aware Prioritization

Not all documentation results are equally relevant. The processor ranks results based on how closely they match the specific issue, how recently they were updated, and how often they’ve been useful for similar tickets in the past. The most relevant article appears first, not buried in a list of marginally related results.

What This Looks Like in Practice

Scenario: Password Reset with Client-Specific Requirements

A ticket arrives: “New employee at Baker & Associates needs access to all systems.”

Junto searches ITGlue for Baker & Associates’ onboarding documentation and finds:

• Baker & Associates — New User Onboarding SOP — Step-by-step procedure including specific distribution groups, SharePoint sites, and line-of-business applications required for new hires.
• Baker & Associates — M365 License Matrix — Which license tier new users should receive based on their role.
• Baker & Associates — Phone System Configuration — How to provision a new extension in their VoIP system.

Without the documentation lookup, a technician would create a basic M365 account and mark the ticket as done — missing the client-specific distribution groups, the VoIP setup, and the correct license tier. With it, they follow the client’s documented process exactly.

Scenario: Recurring Network Issue

A ticket arrives: “Internet slow at Johnson Manufacturing warehouse.”

Junto finds:

• Johnson Manufacturing — Warehouse Network — Documents a known issue with the warehouse AP that requires a firmware-specific fix, not a standard restart.
• Previous ticket resolution — A linked ticket from 3 months ago with the same issue and the exact steps used to resolve it.

The technician skips the troubleshooting tree entirely and goes straight to the documented fix.

Scenario: Security Alert Triage

A Sophos alert generates a ticket: “Malware detected on device WIN-FIN-04 at Meridian Financial.”

Junto searches ITGlue and surfaces:

• Meridian Financial — Incident Response Procedure — The client’s required notification steps, including who to contact and within what timeframe.
• Meridian Financial — Compliance Requirements — FINRA documentation requirements for security incidents.
• WIN-FIN-04 Configuration — The device’s role, installed software, and data sensitivity classification.

Without this, the technician might handle the malware remediation technically but miss the compliance notification requirements — a potentially serious oversight for a financial services client.

Making Your Documentation Work Harder

AI-powered documentation discovery doesn’t just help technicians find existing docs. It also reveals gaps. When Junto searches ITGlue for a ticket and finds nothing relevant, that’s a signal: this is a topic that should be documented.

Over time, you can track which types of tickets consistently lack documentation coverage and prioritize your documentation efforts accordingly. Instead of documenting everything and hoping it gets found, you document based on actual demand.

You can also use Junto’s General Assistant to query your ITGlue environment directly — asking questions like “What do we have documented for Baker’s network?” or “Is there an SOP for onboarding at any of our healthcare clients?” This turns ITGlue from a static repository into a queryable knowledge base.

The Documentation ROI You Were Promised

Every MSP that invests in ITGlue does so with the expectation that good documentation will make the team faster and more consistent. That ROI depends entirely on whether the documentation gets used at the right time.

Manual documentation workflows rely on technician initiative and institutional knowledge. AI-powered documentation workflows ensure that every ticket gets the benefit of your documentation investment — automatically, consistently, and without depending on who’s working the queue.

Your team already did the hard work of creating the documentation. AI just makes sure it actually gets found.

Connect ITGlue to Junto and put your documentation to work automatically. Get started or explore the ITGlue integration docs.