Only alerts that stay open become tickets. User device problems are checked on their own computer. Both are fixed with scripts you approved and then verified, or handed to a technician half-solved.
A device problem arrives as a monitoring alert or as a user's report. Both are handled the same careful way, and both end in a verified fix or a technician who already has the context.
An alert has to stay open for a grace period, 10 minutes by default, before it reaches your PSA. Every alert that does ends in one of three ways.
Before that, muted monitors and unlinked sites are filtered, a repeat becomes a note on the open ticket, and priority follows the alert's severity.
When a user reports a problem with their computer, DaemonLayer looks at that device through your RMM, finds the cause, and picks a fix from the scripts you allowed. A technician approves it; the user confirms it worked.
A user only ever sees their own devices. Servers are never linked to users.
"I can't open PDFs on my laptop."
No PDF reader installed.
From your allowed scripts · sent for approval
Script runs on LAP-0142 only
"We're installing a PDF reader on your laptop. Please try again in about 10 minutes."
"Works now, thanks."
Resolved
Approval request · T20261020.0041WaitingC: at 94%. 11.2 GB in temp and Windows Update cache. A read-only disk check found no large user files to touch.
This script cleared the same monitor on 6 devices at this client in the last 30 days.
You choose which scripts DaemonLayer may use and write when each one applies. It only ever picks from that list.
Scripts · Nordic Systems5 OF 38 ALLOWEDRisky, recurring or unclear problems go to a person with one internal note: why it escalated, what automation found, and the first checks to try. The top of the note comes from your ticket history, not from AI.
Every closed ticket records what fixed it, so the next alert on that monitor proposes the fix that worked.
Internal note · T20261020.0034Windows Update service stopped on NS-LAP-0217 for the 3rd time in 7 days. Recurring alerts are not auto-fixed.
Service startup type is Manual. Last stop at 09:24, 2 minutes after a Group Policy refresh.
Datto RMM today, with more coming. The safety model is the same for every RMM.
Most alerts clear themselves. Only alerts still open after the grace period (10 minutes by default) become tickets.
No. Reboot and shutdown are on a hard block list that cannot be enabled.
Devices sync from the RMM hourly and are matched from login history, hostnames in tickets and, with Microsoft 365 connected, Entra device owner and sign-in activity. Devices unseen for 90 days are ignored, admin accounts never link, and technicians can override any link.
No. Only alerts that become a triaged ticket count.
If an alert is still open after verification, or the user says it still fails, the ticket goes to a technician with everything found so far.
Yes. The grace period, recurrence rule and verification delay are set per RMM connection.
Connect your PSA and Datto RMM, allow your first scripts, and see the next alert handled end to end.
No credit card. No sales deck. Cancel anytime.