OneNote
Documentation

Client procedures and notes, ready to use and update from the ticket.

A ticket needs a client-specific procedure. Junto pulls the relevant OneNote page into triage, so the tech follows the documented steps instead of guessing or asking around.

Plenty of MSPs keep client procedures, account notes, and tribal knowledge in OneNote rather than a formal documentation tool. Junto connects to OneNote and reads notebooks, sections, and pages so that content becomes triage and runbook context, surfaced on the ticket when it's relevant instead of buried in a notebook nobody opens. When a ticket matches a documented procedure, the agent brings the steps forward; when a runbook needs a client-specific detail, it can pull it from the right page. Mapped notebooks can also sync into the knowledge base. When documentation needs an update, Junto can create a page or append content with approval, scoped to the client on the ticket.

What this means for your team

Client SOPs and notes in OneNote surface during triage
Documented procedures reach the tech on the ticket, not in a separate app
Runbooks can draw client-specific details from OneNote pages
Mapped notebooks sync into the knowledge base for search
Create pages or append updates with approval in the right client notebook

Ready to connect OneNote?

Setup takes minutes. Our docs walk you through every step.

View setup guide

See OneNote + Junto in action

15-minute demo. We'll walk you through exactly how Junto works with OneNote.

Book a demo