Runbooks

Runbooks that build themselves from tickets your team already creates

Lexful pulls resolution steps from your closed tickets and structures them into reusable runbooks by client environment. The second incident is faster than the first.

~18 min Saved per incident lookup on average, across early-access pilots
Auto Populated from closed PSA tickets without manual entry
Linked Each step connects to credentials and assets it references
How It Works

From ticket close to reusable runbook in under a minute

When your tech resolves a ticket, Lexful parses the resolution notes and suggests a structured runbook. They confirm, tag the client environment, and it's live for the next incident.

  • Reads from ConnectWise and Autotask resolution notes
  • AI structures steps from free-text notes
  • Tech reviews and confirms in 30 seconds
  • Linked to client environment, not buried in a generic wiki
  • Steps auto-link to credentials and assets they reference
VPN tunnel down: Meridian Medical Group
From ticket CW#50141 · Confirmed by S. Patel · 2026-08-01
01
Check ISP status for Meridian's Comcast circuit
Asset ref: Comcast Business gateway (SN: TG1682G-04421) in asset records
02
Log into Fortigate at 172.16.100.1
Credential: meridian-fg-admin (vault)
03
Navigate VPN > IPsec > Tunnels and check phase-2 status
If DOWN: right-click tunnel, Bring Up
04
Ping far end 10.8.50.1 and confirm round-trip <20ms
If fails: escalate to ISP conference bridge (asset record: meridian-isp-bridge)
Who Uses Runbooks

Common scenarios where runbooks cut resolution time

2am on-call incident

An overnight alert fires. Your on-call tech pulls the runbook for that client's firewall, credential link and steps already in front of them, and resolves in 8 minutes instead of 40.

New tech onboarding

A junior hire joins your team. Instead of shadowing a senior tech for 6 weeks, they can pull any client's runbook library on day one and start handling routine tickets from week two.

Staff departure

Your senior tech quits. Their six years of client knowledge didn't leave with them because Lexful captured it from every ticket they ever closed. The remaining team carries on.

Recurring maintenance

Monthly patching and quarterly reviews have the same steps every time. One runbook, linked to the right assets, keeps patching consistent across all client environments without reinventing the process.

"We had months of closed-ticket resolution notes that nobody went back to read. Once Lexful structured them into runbooks, the next time those same issues came back my techs found the answer before they even had a chance to ask someone. That's the whole point."
Alex Merritt, NOC Lead, 65-environment MSP, from our early-access program
Get started

See your first runbooks in 20 minutes

Connect your PSA, and Lexful builds a runbook library from your existing closed tickets. Free to start, no migration required.