AI security & operations for MSPs

Zammad

A user’s report to the helpdesk is often the first sign of a compromise. Hal reviews each open ticket as it changes, investigates the requester’s sign-ins and mail when one reads as a security matter, and answers on the ticket when your agents ask him.

The helpdesk is where compromises are first reported

Most breaches are noticed by a person before any tool: a user forwards a strange invoice, asks why they got a sign-in code, or cannot get into their mailbox. That report lands in your helpdesk, minutes to hours after the events behind it. Hal reads it there, ties it to the client by the requester’s organization, and reviews it on its own. When it reads as a security matter, he investigates what that account did, and the report’s note lands on that ticket.

Ask him on the ticket

Your agents already work in Zammad. An internal note that names Hal gets an internal note back, from the ticket and the evidence about the requester, visible to your team and never to the requester.

Zendesk too

If your team runs Zendesk instead, or as well, Hal reads it the same way: Zendesk.

What Hal reads
Every update to an open ticket: number, status, priority, subject, requester and organization, assignee, channel, tags, and the newest article.
What it enables
A reported phishing email or an unexpected MFA prompt is reviewed as its own case and, when it is a security matter, investigated against the requester’s sign-ins, mailbox rules and mail.
What Hal writes
Internal notes on your own tickets: one when a ticket leads to a report, and an answer when an agent names him. Never a public reply, never a field change, never a new ticket.
How it connects
An agent of your own and an API token with read and change on the groups Hal should cover. Zammad has no notes-only level, so Hal writes internal notes only. What that means →
Setup
The agent, the token, the mapping and the steps: in the docs →

See what Hal surfaces on your own clients.

No deck. Ask us anything first. When you want to see Hal on your own tenants, we sign a short evaluation agreement and stand up your instance; you connect one tenant, Hal watches it for 14 days, and we walk you through what he found.

  1. 01You ask us your questions. No deck, no demo dataset.
  2. 02You sign a short evaluation agreement, and we stand up your own instance.
  3. 03You connect one tenant from your own admin console. Hal watches it for 14 days.
  4. 04We walk through what he found. Keep going month to month, or revoke the scopes yourself and stop.