Early access · AI teammate for MSP help desks

The ticket is worked before you open it.

Digby reads the ticket, runs read-only diagnostics on the machine, writes the note, and proposes the fix with a measured preview. Your technician clicks Approve. Nothing on the machine or the account changes until they do.

Runs inside your PSANo workflow builderShadow mode firstModel usage included

https://your-psa.example/tickets/TIC001006
TIC001006 · Front desk can't print
Retail Corner ComicsHardware / PrinterFRONT-DESK-01Open
Digby · TIC001006 · 2026-09-04 UTC
summary: The LaserJet shows offline on FRONT-DESK-01. Two other PCs at this site print to it right now.
peers checked: FRONT-DESK-02, OFFICE-PC: HP LaserJet M404 on TCP/IP port 192.168.4.20, wired, subnet 192.168.4.0/24
this PC: same driver and port 192.168.4.20, but on Wi-Fi "CornerComics-Guest" (192.168.50.23); Ethernet unplugged; 192.168.4.20 unreachable
likely cause: This PC is on the guest network. The printer and its configuration are fine.
next step: Put FRONT-DESK-01 back on the staff network, then confirm the printer comes online.
remembered: Front-desk printer golden config for this client, learned from FRONT-DESK-02
Digby#TIC001006 · Front desk can't print
ChatActivityMemoryRunbooks
list_client_devices · Retail Corner Comics ✓ 3 online
compare_devices FRONT-DESK-02, OFFICE-PC ✓ LaserJet on 192.168.4.20, wired
get-network-basics on FRONT-DESK-01 ✓ Wi-Fi: CornerComics-Guest · Ethernet: unplugged
Two other PCs here print to the LaserJet fine, so I compared. Same driver, same port. The difference is this PC: it's on the guest Wi-Fi and can't reach the printer's subnet, and the Ethernet cable is unplugged.
so the printer itself is fine?
Yes. Nothing to change on the printer. Fastest fix is the staff Wi-Fi profile, which OFFICE-PC already has.
Digby wants to run: add-wifi-profile on FRONT-DESK-01
  • Add profile "CornerComics-Staff", key from the Hudu vault (never shown to me)
  • Connect, then verify with get-network-basics
  • Re-check the LaserJet with get-printer-status
Message Digby…
Works with AlgaPSALevel RMMHuduMicrosoft 365IntuneExchange Online HaloPSA · NinjaOne and Huntress built, awaiting a live tenant · ConnectWise · IT Glue next
Why teams trust it

An agent that earns autonomy, not one that assumes it.

Every AI vendor promises a digital technician. Digby is built around the three things a help desk manager actually asks for first: control, proof, and memory.

Every fix behind a card

Disk cleanup, patching, password resets, offboarding: each one is a proposal with a preview run first, so the card says exactly what will happen. One click approves. One click declines. Every approved action leaves its own note and time entry.

Shadow mode with scores

On every ticket Digby privately records what he would have done. When the ticket closes, that guess is scored against what your technician actually did. You raise autonomy per client and per category on evidence, not on a demo.

How the trust ladder works

Memory you can correct

Primary users, apps, known issues, patch windows, fixes that worked. Learned from tickets and docs, corrected by technicians in plain English, and shown with the source of every fact. A client's facts never appear on another client's ticket; only a fix that worked elsewhere can, and only in an internal note.

The difference

Nobody else starts in shadow and shows you the score.

Workflow builders make you encode your process. Packaged packs run someone else's. AI technicians ask you to trust a resolution rate. Digby watches your desk, keeps a scored track record per client and category, and lets you turn the dial when the numbers earn it.

Shadow outcomes · Retail Corner Comicslast 30 days
TIC001005Disk space · would have proposed disk cleanupmatched
TIC001006Printer · would have cleared the queue and re-addedmatched
TIC001009Account access · would have reset the passwordpartial
TIC001012Software · would have reinstalled Officewrong
TIC001014Hardware · would have asked for the modelmatched
Disk space at this client8 of 10 matched · ready for propose
How it works

Five steps, one of them yours.

1

Triage

Intent read and the ticket filed into a category, related tickets cited, device matched only when the ticket is about a device. Filing is a switch you can turn off.

2

Dig

Read-only diagnostics on the PC, chosen by the symptoms. A working peer at the same client when it helps.

3

Write up

One likely cause, cited evidence, the next step, and the track record for this category at this client.

4

You approve

A card with a measured preview. Nothing on the machine changes until the click.

5

Verify and learn

Verify step, note and time entry on the ticket, KB article if worth keeping, memory for next time.

In the current build

Real numbers from a real run, not a slide.

36tickets across 6 clients triaged, analyzed and shadow-scored in one unattended runMeasured 2026-09-04
0changes to a machine or an account without a technician's click, at every autonomy levelOn the ticket itself he files a category and posts internal notes from day one
34+41read-only diagnostics and approval-gated actions on Windows endpointsPlus 16 Microsoft 365 actions
4 minfrom ticket close to a scored outcomeFirst live scoring run
Early access

Be first on the queue.

Pilots start in shadow mode: two weeks on your real tickets, writing up every one and fixing none, then you decide what Digby gets to touch. Tell us which PSA and RMM you run.

Get early access