DaemonLayer reads tickets from your PSA queues and your M365 support inbox, classifies them with AI, and routes them to automation or your service desk, fully enriched, in seconds.
Nobody has to change how clients contact you. Requests arrive the way they do today, and both paths feed the same triage.
DaemonLayer connects to your M365 support mailbox via Microsoft Graph. Spam is filtered and moved automatically, sales enquiries are forwarded to your sales address, and everything else becomes a ticket with the client identified from the sender domain.
Connect DaemonLayer directly to ConnectWise Manage, Autotask or HaloPSA. New tickets from the boards and queues you choose are picked up as they arrive, from the same portal and phone process your clients already use.
Five stages, a few seconds. This is what happens to "Email not sending" before anyone at the MSP opens it.
"Email not sending" · emma@nordicdesign.com+0.0s"Hi, my email isn't sending since this morning. Screenshot attached. Can someone look?"
Five sources are read for every ticket. If one is unavailable, that step is skipped and triage carries on. No ticket waits.
Who is asking: title, department, groups, licence, account status.
Error codes and app state the user never typed.
Similar resolved tickets ranked by usefulness, plus the reporter's and company's last three.
From the RMM. Only that user's own devices, never the fleet.
Matching assets and KB articles.
Error codes, affected products and symptom phrases are stored on the ticket, so they can be searched and matched later.
Two tickets about one problem waste a technician. One ticket hiding two problems loses one of them. Triage fixes both before routing.
Triage finds the ticket already in progress and shows its evidence. A merge needs high confidence, can require admin approval, and never happens across clients.
A request is split out only if it can be actioned on its own, has a different cause and needs a different fix.
"I can't log in and Outlook won't open."
"Reset my password, and new hire Anna starts Monday."
Four signals pick the assignee, and the ticket's SLA decides when. Even when a ticket goes to the desk manually, it carries a suggested assignee with a reason.
Internal note · T20261016.0021Outlook fails to send for one user only; error 0x80040115 points to a cached profile issue, not a tenant outage. Confidence 71, below the automation threshold.
Up to three targeted questions go out as a public reply on the ticket. When the user answers, triage runs again with the whole conversation.
Your M365 support mailbox and the PSA boards or queues you choose. Clients keep contacting you the way they do today.
Every ticket gets a confidence score from 0 to 100. Automation runs only when the score clears your threshold and a matching workflow is enabled. Everything else goes to your team, already enriched.
DaemonLayer asks up to three targeted questions as a public reply on the ticket, and triages again when the user answers.
No. This is hard-coded, not a setting. Merges need a confidence of 85 by default, and you can require admin approval.
Only when the requests are independent: a different cause and a different fix. At most three issues, never more than one level deep. Symptoms of one problem, and steps of one request, stay together.
From queue membership, workload, working hours and category expertise, timed against the ticket's SLA.
Resolved tickets are re-indexed automatically and used as reference cases. They are never used to train AI models.
That step is skipped and triage continues. No ticket is blocked.
Connect your PSA and support inbox, and see the first ticket triaged in minutes.
No credit card. No sales deck. Cancel anytime.