AI security & operations for MSPs

Zammad

What Hal reads

Zammad is your helpdesk, and Hal reads it as a log source. Every update to a ticket your team is still working, new, open, pending reminder or pending action, arrives as an event: the ticket’s number (like Ticket#20261107170003), status, priority, type and subject; the requester, their organization and their email domain; the assignee; the channel the ticket came in by; the tags; and the newest article, whether a public reply or an agent’s internal note. A closed or merged ticket is passed over, and a closed ticket that a follow-up reopens is read again from its new update. The first read reaches back a week.

Each ticket is attributed to one of your clients through its Zammad organization: one whose Domain is a client’s email domain, or one that carries the client’s ID in an organization attribute named halclient. If the ticket has no organization, the requester’s own organization is tried, then the requester’s email domain. A ticket that matches no client is kept and marked unattributed.

Tickets are retained and searchable like every other source. Each update to a ticket that belongs to a client is reviewed on its own, never in a batch with the client’s other activity: Hal reads the whole ticket and decides whether it is a security matter. Most are not, and nothing happens. A user reporting a suspicious email, a password prompt they did not ask for, or a vendor asking to change bank details gets a second opinion and then an investigation, which reads that user’s sign-ins, mail, mailbox rules and app consents to decide whether the report is a false alarm or a real event. How your own agents handle a ticket is never the finding.

If you also run Zendesk, connect both: Hal reads each the same way, and the pipeline page shows them as one segment, Zendesk + Zammad. Zendesk’s page has its steps.

What Hal writes

Two things, both internal notes on your own tickets, visible to your agents and never to the requester or your client.

  • A note when a ticket leads to a report. When Hal raises a report from a ticket, he posts one internal note on that ticket: what he found, his verdict, and where the full report is. It is plain text.
  • An answer when an agent asks. When one of your agents writes an internal note that names Hal, Hal, is this phishing?, Hal can you check this user’s sign-ins, he answers on the same ticket with an internal note, from the ticket and from the evidence about the requester. The whole word “Hal” in an agent’s internal note is the trigger; a public article or a requester never triggers it. The answer arrives within a few minutes.

Hal never writes a public reply, changes a field or creates a ticket. Zammad has no notes-only level, so the agent Hal connects as could edit a ticket’s fields; Hal only ever adds internal notes. His notes are written on your own helpdesk, which is your system, not a client’s. Read-only by architecture →

Start in chat

As a Hal admin, open the portal chat and say Connect Zammad. Hal relays the steps on this page in order, with each client’s ID beside them. When you have pasted the token and say so, he verifies the setup: who Hal’s agent is and what it can reach, which organizations are mapped to clients, which are not, which conflict, and how many of the last week’s ticket updates he could attribute. It also reports anything that blocks the connection. Say you’re ready and he confirms, which turns the integration on; organizations can be fixed later at any time. The rest of this page is the same steps written out.

Before you start

  • You need a Zammad administrator who can create users and roles and set organization domains.
  • Note your Zammad address, the host name of your helpdesk, such as desk.yourcompany.com. It must be reachable over https:// on the public internet, with no port and no path.
  • Hal’s agent needs an email address your team can read. An alias on your helpdesk mailbox works.

Create Hal’s agent

  1. In Zammad, create a user named Hal with an email address your team reads, and give it the Agent role alone. Never Admin.
  2. Under Group permissions, give it read and change on every group whose tickets Hal should read. Not full: full access lets tickets be assigned to Hal, who owns none. Hal must be able to read every active group.

Hal checks both when he verifies. The Admin role, full access on a group, or an active group Hal cannot read each block the connection until fixed.

Create the token

Sign in to Zammad as Hal. Open Profile → Token Access and create a token with the permission ticket.agent alone. Copy it when Zammad shows it: it is shown once. The token does not expire. There is no OAuth client and no approval step.

Hand it to Hal

In the Hal portal, open Settings → Zammad, enter the Address and the Token, and Save. The token goes into this page, never into chat. Test Connection shows who Hal is in Zammad and with which roles.

The address is https:// and the host name alone. A port other than 443, a path, or a private or local address is refused. Saving a different address needs its own token and ends the old connection, and the new one is then verified and confirmed again.

Then tell Hal in chat that it’s pasted, and he verifies the setup.

If your Zammad sits behind Cloudflare Access or another sign-in gate, allow <address>/api/* from the address Hal connects from without a sign-in; ask HAL AI for that address. Zammad’s own token guards the API. A sign-in page in front of the API answers Hal with a web page rather than data, which he reports as unreachable.

Map organizations to clients

Hal maps each Zammad organization to a client in one of two ways:

  • The organization’s Domain set to the client’s email domain, with Assign users by domain turned on so a ticket’s requester reaches the organization. Do this for each client’s organization.
  • A halclient organization attribute holding the client’s ID, the value on Hal’s Clients page, which Hal also lists in chat. Use it for an organization whose domain does not name one of your clients. You create the attribute in Zammad’s organization settings, named halclient.

Settings → Zammad counts the organizations Hal has synced; Generate JSON shows every one with its domains, the client it maps to, and its state, and Download JSON saves the same map as a file. Under it is the count of ticket updates in the last 7 days that matched no client. Tickets that match no client are still kept and searchable, and Hal answers on them when an agent asks; they are never reviewed, because there is no client’s evidence to read them against.

Keeping the connection

The token does not expire, so the connection holds until something changes in Zammad. If Zammad refuses it, the agent deactivated or the token revoked or missing ticket.agent, check that the agent is active and its token carries that permission, then ask Hal to verify again. A network failure or a Zammad outage says nothing about Hal’s access: verify again in a minute.

If a note cannot be posted, because the agent lacks change on the ticket’s group, Hal retries it on each cycle, and after three cycles the health page says to give Hal’s Zammad agent read and change on that group. A ticket that was deleted, or merged since, settles without a note.

Cost

Each review of a ticket update shows on the Costs page as Ticket review. A ticket that escalates adds its second opinion and its investigation to those lines on the same page. Hal’s answers on tickets are chat turns on the interactive model, one per question, and show on the Costs page as chat.

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.