DaemonLayer Logo
Ticket triage

Every ticket triaged before a human sees it

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.

Two ways in

Two intake paths.
One pipeline.

Nobody has to change how clients contact you. Requests arrive the way they do today, and both paths feed the same triage.

01 / Microsoft 365 email

Your support mailbox, read in real time.

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.

"Can't open the shared calendar" · priya@northstar.co.ukTicket · Northstar
"Quote for 20 laptops?" · buyer@ashby.co.ukForwarded to sales
"You've won a gift card" · promo@mailer.bizSpam · moved
02 / PSA boards & queues

Your PSA stays the intake source.

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.

Service Desk queueWatched
Client Portal queueWatched
Projects queueIgnored
Same pipeline on every PSA
How it works

Follow one ticket
from inbox to the right desk.

Five stages, a few seconds. This is what happens to "Email not sending" before anyone at the MSP opens it.

DaemonLayer"Email not sending" · emma@nordicdesign.com+0.0s
Intake · M365 support mailbox
From emma@nordicdesign.com · to support@nordicmsp.com · 1 attachment

"Hi, my email isn't sending since this morning. Screenshot attached. Can someone look?"

Client identified from the sender domain: Nordic Design.
On the ticket
Nordic Design
The full picture

The AI sees the full picture
before it decides.

Five sources are read for every ticket. If one is unavailable, that step is skipped and triage carries on. No ticket waits.

Microsoft 365

Who is asking: title, department, groups, licence, account status.

Screenshots

Error codes and app state the user never typed.

Ticket history

Similar resolved tickets ranked by usefulness, plus the reporter's and company's last three.

The user's devices

From the RMM. Only that user's own devices, never the fleet.

Hudu documentation

Matching assets and KB articles.

Extracted signals become data

Error codes, affected products and symptom phrases are stored on the ticket, so they can be searched and matched later.

0x80040115OutlookExchange Online"can't send email""since this morning"
One ticket per real problem

Duplicates merge.
Bundles split, reluctantly.

Two tickets about one problem waste a technician. One ticket hiding two problems loses one of them. Triage fixes both before routing.

01 / MERGE

The earlier ticket wins.

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.

Same reporter
Same error code 0x80040115
11 minutes apart, same client
Closed and cross-linked to T20261020.0019Merged
02 / SPLIT

Only when it's truly two jobs.

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."

Stays one ticketSymptoms of one problem

"Reset my password, and new hire Anna starts Monday."

Split into twoDifferent cause, different fix
A spike in duplicates on one issue raises an early major-incident signal.One request that needs several actions isn't split; it becomes a workflow plan →
Dispatch

The right technician,
at the right time.

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.

  1. 01Queue membership
  2. 02Current workload, weighted by priority
  3. 03Working hours
  4. 04Proven expertise in that category
Assignee · Service Desk teamEMAIL & COLLABORATION
Alex MorganAssigned
Ali HassanBusier
Sam ReidOff shift
Timing follows the SLA
LowWaits for the next morningFri 08:30
Medium / HighAssigned todayThu 16:00
CriticalAssigned immediatelySun 02:10
When it reaches a technician

Technicians arrive
informed, not blind.

  1. 01The triage reasoning
  2. 02The extracted signals
  3. 03Similar resolved tickets, and how they were fixed
  4. 04The reporter's history
  5. 05PSA fields pre-filled with your exact values: queue, issue type, sub-issue type
DaemonLayerInternal note · T20261016.0021
Reasoning

Outlook 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.

0x80040115Outlook"can't send email"
Similar resolved
T20260918.0004Rebuilt Outlook profile94%
T20260702.0011Cleared credential cache88%
Queue
Level I
Issue
Email
Sub-issue
Outlook
Too thin to act on

When a ticket is vague,
DaemonLayer asks.

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.

"Printer's not working."
Mia Clarke · Ashby & Co
Public reply · 3 questions
1. Which printer, and which floor is it on?
2. Is it offline for everyone, or only you?
3. Do you see an error on the printer screen?
"2nd floor HP. Everyone. It says paper jam but there isn't one."
Mia Clarke · Ashby & Co
Straight answers

Questions about
ticket triage.

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.

Related

Where triage connects

The next step

Every ticket triaged
before anyone opens it.

Connect your PSA and support inbox, and see the first ticket triaged in minutes.

No credit card. No sales deck. Cancel anytime.