Triage and Categorize ITSM Incidents Agentic Workflow
A ServiceNow agentic workflow in IT Service Management that runs a team of three AI agents to autonomously set an incident's category and subcategory, assign service, service offering and configuration item, and link the incident to a related major incident or problem. Documented for the Australia release.
Recorded characteristics
- Function
- ServiceNow documents this as an AI agent team, not a single agent. Executed in order: the Categorize ITSM incident AI agent assigns Category and Subcategory from the incident short description and updates Work notes; the Classify service and CI AI agent assigns Service, Service offering and Configuration item and updates Additional comments and Work notes; the Link major incident or problem AI agent links the most similar major incident and ends the workflow, or, if none is found, links a matching ongoing problem, updating the parent incident or problem field and Additional comments. Triggering is automatic when State is New or updated to In progress, Assigned to is empty and Priority is 3, 4 or 5; triggering is manual when State is In progress and Assigned to is not empty. Documentation states all executions are autonomous and the workflow does not require user input during execution.
- Data access
- Reads the incident record, principally the short description and context, and searches services, service offerings, configuration items, major incidents and problems. Linking to related problems relies on semantic indexing of the Problem table when the workflow is duplicated. Writes are limited to the documented incident fields: Category, Subcategory, Service, Service offering, Configuration item, parent incident or problem, Work notes and Additional comments. No documented setting of assignment group, assignee, priority or incident state by this workflow.
- Actions
- Can take actions
- External actions
- Unknown
- Human confirmation
- Not required
- Permission basis
- Mixed
- Administrative control
- Configured in AI Agent Studio under Create and manage. Administrators control the trigger Active flag, the trigger user (a user with the itil role), each AI agent's Status on the Define availability screen, the Run as entity, and role-based access on the Select display screen where the itil role is added by default. Linking to major incidents requires activating the Incident Management - Major Incident Management plugin (com.snc.incident.mim). The workflow can be duplicated and modified.
- Default state
- Conditional
- Availability
- Documented for the Australia release (page updated 12 March 2026) and also present in Zurich documentation. Requires installation of the ServiceNow Otto for IT Service Management (ITSM) (sn_itsm_gen_ai) plugin and the Incident Management application. The workflow ships with the ITSM agentic AI application but must be activated by turning on the trigger and enabling each AI agent's status.
- Licensing
- Not established from ServiceNow documentation reviewed. No SKU or edition requirement is stated on the pages cited.
- External model or provider
- Not established. No model or model provider is named in the ServiceNow documentation for this workflow.
- Limitations and uncertainty
- Boundary: this record covers only the Triage and categorize ITSM incidents agentic workflow. The Investigate and resolve ITSM incidents workflow, the Wrap-up and resolve incident workflow, Incident assist, Generate post incident reviews and Major Incident Management capabilities are separate and are not covered here. Not established: outbound actions to external systems; the exact runtime role set of the ITSM Worker AI Agent user; whether any documented human approval step gates the field writes; model or provider; licensing SKU; and whether a formal preview or general-availability designation applies.
Evidence
- IT Service Management AI agent collection: Triage and categorize ITSM incidents agentic workflow (Australia)
Supports: Function · Data access · Actions · Human confirmation · Permission basis · Admin controls · Default state · Availability · Limitations · Primary source
Names the three AI agents and their execution order and roles.
Documents the incident fields each agent updates and the short description used as input.
States that the workflow autonomously assigns categories, service, service offering and CI, and links major incidents or problems.
States all executions are autonomous and the AI agent does not need user inputs during execution.
Documents the Run as AI user (ITSM Worker AI Agent), the itil trigger user, and the itil role added by default for access.
Documents the trigger Active flag, agent Status, Run as selection, display roles, plugin requirement and duplication.
Requires the trigger to be activated and each agent status enabled before autonomous execution.
Release version Australia, updated 12 March 2026.
Notes the Major Incident Management plugin requirement and semantic indexing requirement for the Problem table.
- Use agentic AI in ServiceNow Otto for IT Service Management (ITSM) (Australia)
Supports: General · Availability · Primary source
Lists Triage and categorize ITSM incidents among the ITSM application agentic workflows.
Australia release listing of available agentic workflows.
- Agentic AI in Incident Management (Australia)
Supports: Availability · Default state · Limitations · Primary source
Requires the ServiceNow Otto for ITSM (sn_itsm_gen_ai) plugin and the Incident Management application.
Prerequisite applications must be installed before the agentic workflow is accessible.
Shows Wrap-up and resolve incident as a separate Incident Management workflow.
- Investigate and resolve ITSM incidents agentic workflow (Australia)
Supports: Limitations · Primary source
Establishes investigation and resolution recommendations as a distinct workflow outside this boundary.
- ACLs, role masking, and user identities in AI Agent Studio
Supports: Permission basis · Primary source
Describes user identities, role masking and what ACLs do and do not govern at runtime.
- Implement access control in AI agents
Supports: Permission basis · Admin controls · Primary source
ACLs must be configured for each agentic workflow, AI agent and certain tools.
Access control configuration responsibilities for administrators.
- Deny-by-default ACL configuration for AI agentic types
Supports: Default state · Primary source
Deny-by-default ACL posture for agentic types without individual ACLs.
- Triage and categorize ITSM incidents agentic workflow (ServiceNow documentation content endpoint, Australia)
Supports: Function · Primary source
Server-readable copy of the primary workflow documentation used for weekly monitoring.