HaloPSA AI SERVICE DESK AUTOMATION

Running HaloPSA?
We want you.

We’re looking for MSPs to put DaemonLayer through its paces.

AI agents resolve password resets, mailbox access and group changes end to end — approved where you require it, completed in Microsoft 365 and written back to the HaloPSA ticket.

14 days free No credit card Start with one client tenant How the trial becomes a subscription
TICKET #1044 · NORTHSTAR STUDIO
Resolved
“Please give Alex access to the accounts mailbox.”
Access request · Workflow: Shared mailbox access
  1. Triaged
    Access request · 92% confidence · workflow selected
    09:31
  2. Verified in Microsoft 365
    User and mailbox found, no access in place yet
    09:31
  3. Approved
    Your approver signed off, as your rules require
    09:42
  4. Resolved and written back
    Full Access granted · note, status and time entry in HaloPSA
    09:42
Illustrative workflow · sample data
UK & EU DATA HOSTING READ-ONLY MODE AVAILABLE ICO REGISTERED · ZC054896 UK-BUILT · GDPR

Before you grant access

Start with one client.
Know what you’re connecting.

Your technical lead can review access before you connect HaloPSA or grant Microsoft 365 consent.

Access for the work you enable

Microsoft 365 uses OAuth and Microsoft Graph. Read-only mode gathers context; actions need additional permissions. Review the actual consent scopes before enabling write access.

One client tenant to begin

Connect a selected client’s Microsoft 365 tenant and start with a supported request. Your HaloPSA API account has its own permissions, which also need reviewing.

You can revoke consent

Your Microsoft 365 administrator can revoke the app’s permissions in Microsoft Entra. Review the HaloPSA API connection separately when disconnecting.

Know where data is processed

Published data hosting is in the UK and EU; AI processing uses EU data zones. Review the details for your clients’ residency requirements.

From request to recorded outcome

See how a mailbox request
becomes a completed action.

Follow a mailbox access request through an intelligent workflow. The checks and controls stay visible, and your engineer’s working record stays in HaloPSA.

Mailbox access
ILLUSTRATIVE · SAMPLE DATA
INCOMING REQUEST / #1044 New

“Please give Alex access to the accounts mailbox.”

SPSam Patel · Northstar Studio
01 / TRIAGED

The ticket is classified and routed.

The category and confidence are determined and the matching workflow is selected. Anything uncertain goes to a technician instead.

Access request · Workflow: Shared mailbox access Workflow selected
Category
access_request
Confidence
92%
Workflow
Shared mailbox access
Route
Workflow (enabled for this client)
Below 60% confidence, or with no enabled workflow, the ticket goes to your service desk.
Click through the example. This does not connect to or change a live system.

Your Halo configuration matters

Fits the way your HaloPSA desk works.

01

The right technician.

Tickets go to the client’s primary or secondary technician first. If neither is available within the SLA window, they go to another technician in the HaloPSA Team.

02

The right status.

Map statuses by ticket type, so updates follow the structure configured in your Halo instance.

03

A useful ticket record.

Write back notes, status updates and time entries. Send requester notifications through Halo email actions when configured.

What your AI agents can handle

Start with the requests
your team sees every week.

AI agents interpret the request and carry out supported actions. Predefined workflows supply the checks and boundaries, with context returned to HaloPSA when an engineer needs to take over.

Password resets and account unlocks

Verify identity, act only with the supported account actions and notify the user.

CONTROLS
Identity verificationConfigured approvals

Shared mailbox access

Grant supported mailbox and delegate permissions.

CONTROLS
Configured approvalsRequired M365 permissions

Group membership changes

Add or remove users from supported Microsoft 365 groups.

CONTROLS
Target and membership checksConfigured approvals

Out-of-office and forwarding

Configure supported automatic replies and forwarding requests.

CONTROLS
Mailbox accessWorkflow-specific controls

User profile updates

Update details such as job title, department or phone number.

CONTROLS
Supported fieldsAuthorisation checks

Joiners and leavers

Carry out supported account setup and offboarding tasks.

CONTROLS
Client configurationLifecycle safeguards

Anything outside a supported workflow goes to your engineers in HaloPSA, with the context already gathered.

Automation you can account for

Your rules govern what
the AI agents can do.

Define access and approval requirements before a workflow makes changes in a client’s environment.

Explore authorisation controls ↗

Review sensitive changes before they run.

Sensitive requests pause where the selected workflow requires authorisation. Your team can review the proposed change and its context.

Inspect the record of each workflow.

External-system workflow steps have cryptographically linked records to help detect changes to the execution history. Outcomes return to HaloPSA.

Review security and data handling ↗

14-day trial, no credit card

Start with one client tenant. Cancel in the admin panel.

What happens after the trial?

We contact you to agree a plan. Unless you cancel, if no plan is agreed your account converts automatically to the matching paid plan based on ticket volume. Pricing is confirmed before you are charged.

A first step you can assess

Start with one client’s
Microsoft 365 tenant.

Choose a client you are authorised to connect. Review consent with your technical lead, then evaluate a routine request before extending automation to more clients.

Start with one client
14 days free · No credit card
  1. 01

    Choose your first client

    Agree the client scope, set up the HaloPSA API connection and review ticket-type and status mappings.

  2. 02

    Review Microsoft 365 consent

    Ask the client’s authorised administrator to review the Microsoft Graph permissions. Choose read-only or the access needed for your selected action.

  3. 03

    Run a request and review the result

    Set the approval rules, run a supported request and inspect its outcome in HaloPSA before connecting more clients.

Before you connect

Your HaloPSA questions,
answered.

Need to discuss your setup?

Book a demo ↓
Can we start with just one client?

Yes. Begin with a selected client’s Microsoft 365 tenant and a supported request. Review the HaloPSA intake scope as well as the Microsoft 365 connection, then expand after you have checked the results.

What Microsoft 365 permissions are needed?

Context gathering can use read-only access. Password resets, group changes and mailbox actions require the appropriate write permissions. An authorised administrator reviews the consent scopes for the connection. Workflow controls limit execution but do not themselves narrow an underlying API permission grant.

Where is our data held?

The published privacy policy specifies UK and EU cloud hosting. AI processing takes place in EU data zones. If a client requires US or Australian residency, confirm the arrangement before connecting them; local hosting in those regions is not stated.

What happens when the AI is wrong or unsure?

AI can make mistakes. Configured confidence thresholds and approval gates limit when actions run. Requests that cannot proceed go to the service desk with context and execution history. Review initial results and sensitive actions before expanding; do not assume every change is automatically reversible.

How can we revoke access?

An authorised administrator can review and revoke the app permissions in the client’s Microsoft Entra tenant. Review the HaloPSA API application separately.

When does the trial start, and what happens at the end?

The published offer is a 14-day trial with no credit card. An activation-based start is not specified; confirm the start date if client consent may take time. DaemonLayer contacts you to agree a plan. Unless you cancel, if nothing is agreed the account converts to the matching paid plan, with pricing confirmed before charging.

Is DaemonLayer SOC 2 certified, and what support is available?

The published terms describe work towards formal certification; they do not establish completed SOC 2 certification. Confirm current certification evidence, support hours and response arrangements for your time zone on the demo call.

Your next routine request

Less repetition.
More room for your team.

Start with one client, or book a 30-minute walkthrough and see routine Microsoft 365 requests completed through your HaloPSA service desk.

  • A live walkthrough with someone who builds DaemonLayer
  • Real tickets from inbox to resolution, on a HaloPSA desk
  • Permissions, approvals and rollout covered. Bring your technical lead.
14 days free · No credit card · Review trial and subscription terms

Form not loading? Open it in a new tab.