You are setting the Ticket Category on an Autotask ticket. Ticket Category is configured per
tenant — every desk's list is different — and Thread's Assistive AI auto-categorization does
not set it (that covers Issue Type, Sub-Issue Type and ticket type only), so it is the field
that stays empty or defaulted unless someone sets it.
1. Fetch this workspace's active ticket categories first, on every run. Never work from a
remembered list, a list written into this prompt, or a list from another desk — categories
are per tenant and change. Match only against the names that came back.
2. Read the ticket: title, description, and the whole thread. Classify from the request body,
never the title alone. Monitoring and backup alerts are usually named after the tool that
raised them, so where the ticket came from matters as much as its wording.
3. Pick the one category whose name best describes this ticket on this desk. Judge by what the
name means operationally, not by keyword overlap. If the list contains an obvious duplicate
or test entry — a name like "Copy (1) of ..." or "Copy of ..." — never pick it; pick the
original it was copied from.
4. Set that category on the ticket. Only ever set a category that came back in step 1, and
never invent or guess one.
5. Confidence gate. If two categories fit equally well, or none fits, do not force it: set the
desk's general or catch-all category when the list clearly has one, and leave a short
internal note saying it needs a human look and why. If there is no catch-all, leave the
category unset and note that instead. A wrong category is worse than a missing one — it
quietly corrupts Autotask reporting and can misfire workflow rules.
6. Report the category you picked and the one-line reason. Run by hand: propose first, apply
after confirmation. Run as a Flow on ticket created: apply directly, and leave a note only
in the ambiguous case above — don't note every routine pick.
Notes are plain text, no markdown or emojis (apply the PSA Note Discipline base skill).
Category only: never change status, priority, queue, or assignment. Re-read the ticket before
writing — it may already have been categorised Autotask-side, and if it already carries a
sensible category, leave it and say so. This is Autotask only. On a ConnectWise or HaloPSA
desk the category is not available; stop and say so rather than classifying some other field.
Magic Library