--- title: Auto Triage slug: neurons-for-itsm/admin-user-help/enu/latest/auto-triage docTags: createdAt: 2026-07-14T19:16:50.630Z --- **Role**: Administrators. **Platform**: SaaS only. **Minimum Version**: Ivanti Neurons for ITSM 2026.3. **Feature Eligibility**: Ivanti's AITSM capabilities are available to customers who have subscribed to Premium or Enterprise Premium license. To know your eligibility, reach out to your Ivanti Account Manager. **Prerequisites**: - Raise an IT ticket to Ivanti Operations to set the *ITSMTCPredictions* feature flag in ConfigDB to **Unconditionally On**. By default, it is in Disable state. For further help, contact [Ivanti support](https://www.ivanti.com/support). - *ITSMTCPredictions* in **Unconditionally On** state - The Auto Triage feature functions through ITSM AI services. - *ITSMTCPredictions* in **Disable** state - The Auto Triage feature functions through Ivanti Neurons. Auto Triage is an AI-powered ticket classification feature that automatically predicts and populates Incident fields such as **Category**, **Subcategory**, **Service**, and **Team** based on the information entered in the incident ticket. It uses a multilingual AI model and can process tickets submitted in any supported language. Auto Triage includes the following key processes: **Training (configured by the administrator)**: Select the Input Fields, Output Fields, and a historical training data range. The system uses previously classified incident records to train the AI model and learn how to classify tickets. After training is complete, deploy the model to start predicting values for new tickets. **Prediction (for new and updated tickets)**: When a ticket is created or updated by an analyst, a self-service user, or through email, the model analyzes the values entered in the configured Input Fields (in any supported language) and predicts the values for the configured Output Fields. If the prediction confidence meets the configured threshold, the application automatically populates the predicted values and displays an *AI Recommended *label. Analysts can review and modify the predicted values before saving the ticket. You can control prediction behavior by configuring confidence thresholds, stop words, and whitelisted keywords. Analysts can also override AI-recommended values when needed. :::hint{type="info"} - At least 10,000 records must remain after preprocessing, which removes incomplete or low-quality records and rare labels with fewer than approximately 200 examples per class. To help meet this requirement, start with approximately 15,000 to 20,000 resolved or closed incidents and include additional records for categories with limited data. - Auto Triage learns from your historical tickets and predicts and pre-populates classification fields for new tickets in any supported language, while confidence thresholds and analyst override options help you maintain control over the predictions. ::: To learn more about Auto Triage use cases, refer to the [Using Auto Triage](docId\:KUxyKGtN4RucvSb4nXwZK). ## Enable Auto Triage 1. Log in to Neurons for ITSM as an Administrator. 2. Open the Configuration console > **Build** > **AI Configuration Hub > AI & ML**. 3. Use the toggle to set **Auto Triage** to **Active**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/I6ZrD-JFRbSY3u-Tg7MAm_auto-triage-enable.png" position="flex-start" size="80" width="1202" height="747" githubPath="Admin-User/Content/AITSM/images/ticket-classification-active.png" darkWidth="1202" darkHeight="747" showCaption="true" caption="Enable Auto Triage toggle" indent="1"} ## Configure Auto Triage 1. Log in to Neurons for ITSM as an Administrator. 2. Open the Configuration console > **Build** > **AI Configuration Hub > AI & ML**. 3. Select the **Configure** option beside the toggle button. 4. Select **Add Model**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/U6zFNJFeqbtL5TkKGMV4e_auto-triage-add-model.png" position="flex-start" size="80" width="1538" height="1026" githubPath="Admin-User/Content/AITSM/images/ticket-classification-creating-model.png" darkWidth="1538" darkHeight="1026" showCaption="true" caption="Add model in Auto Triage " indent="1"} 5. Enter the **Name**, **Description**, and choose a **Language**. :::hint{type="info" indent="1"} The selected language is used for model identification only. The model is multilingual, so it can process all supported languages, regardless of the language selected in this field. ::: 6. Set the **Threshold Percentile** value to determine how confident the model must be before it accepts a predicted value for an Output Field. :::Paragraph{indent="1"} You can choose a value between 10% and 90%, in increments of 10%. Setting a lower value makes the model recommend Output Field values more frequently, although some recommendations may have lower confidence. A higher value makes the model recommend Output Field values only when it is more confident that the prediction is correct. ::: :::Paragraph{indent="1"} This setting is configured separately for each Output Field and can be changed at any time without retraining the model. ::: 7. Set the **Historical training data** range so that the ML model is trained using records from the specified date range. :::Paragraph{indent="1"} The selected date range determines which historical records are exported to the training dataset. The model does not apply any additional date-based filtering during training because no date cutoff exists in the training process. ::: :::Paragraph{indent="1"} Model training requires sufficient historical incident data. At least 10,000 records must remain after preprocessing, which removes incomplete or low-quality records and rare labels with fewer than approximately 200 examples per class. To help meet this requirement, start with approximately 15,000 to 20,000 resolved or closed incidents and include additional records for categories with limited data. ::: :::Paragraph{indent="1"} Your raw incident count does not need to be exactly 10,000. Before training, the system cleans each ticket's text by removing HTML, links, ticket numbers, and punctuation, leaving only meaningful words. A ticket that contains only placeholder text, such as Resolved with an empty description, might be reduced to a single word and excluded because it does not provide enough information for the model to learn from. ::: :::Paragraph{indent="1"} Because many tickets are reduced or removed during preprocessing, plan your raw dataset to be well above 10,000 records, typically 15,000 to 20,000 resolved or closed incidents. ::: :::Paragraph{indent="1"} Example: *\

User cannot log in to VPN\

* becomes *user cannot log in vpn* and is retained for training. In contrast, a ticket containing only *Resolved* becomes *resolved*, which provides insufficient information and might be excluded from the training dataset. ::: :::hint{type="warning" indent="1"} - If training fails due to insufficient data, increase the **Historical training data** range and retrain the model. - If increasing the date range does not help, consider consolidating rarely used categories into broader categories, where appropriate. Categories with very few examples (typically fewer than 200) are removed along with their associated tickets during preprocessing. Merging several low-volume categories into a broader category can help retain more data for training. ::: 8. The **Incident** business object is selected by default in the **Select the Business Object** dropdown. 9. Under **Input Fields**, select the relevant fields to train the ML model. :::Paragraph{indent="1"} When a Service Desk Analyst or Self Service User enters values in the selected Input Fields of an Incident record, the system predicts and populates the fields defined under **Output Fields**. ::: :::hint{type="info" indent="1"} - You can add up to four entries. - A field cannot be configured as both an Input Field and an Output Field. - Use short-to-medium text or categorical fields, such as **Summary** and **Description**, as Input Fields. Avoid using lengthy or unstructured fields, such as **Notes**, **Journal entries**, **HTML content**, or **attachment content**, as they might affect model training. ::: 10. Under **Output Fields**, specify the fields that you want the ML model to predict and populate. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/B7zneGNWgfttl0IoxWiSP_auto-triage-input-output.png" size="90" isUploading="false" position="flex-start" caption="Field Selection in Auto Triage" width="1039" height="364" darkWidth="1039" darkHeight="364" showCaption="true"} :::hint{type="info"} - Before training the ML model, ensure that the name of the fields selected under **Input Fields** and **Output Fields** matches your Incident business object field names. Some organizations might have customized field names in their Incident business object. For example, Sub-Category instead of Subcategory field. In such cases, you must create a field mapping so that the ML model can correctly recognize and use the custom field. For more information on field name mapping, refer to [Viewing Fields](docId\:dRawml4f1ib3LOySPaMcu). - You can configure up to four Output Fields. Supported Output Fields are **Category**, **Subcategory**, **Service**, and **Team**. ::: 11. Turn on **Enable Whitelist & stopwords** **filtering **to enable it. 12. Under **Stop words**, enter words or phrases that you want to exclude from the training data. 13. Under **Whitelisted keywords**, enter the imported words to prioritize during classification. :::hint{type="info" indent="1"} - You can use a maximum of 20 keywords to both Stop words and Whitelisted keywords. - Words separated by a space or comma are treated as separate keywords. ::: 14. Click **Save** to save the model as draft or click **Save and train** to train the model instantly. 15. Click the Deploy icon :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/eIDlSIbOnZQcE_DlJsXHi_ticket-classification-deploy-icon.png" alt caption size="10" width="16" height="15"} to deploy the trained model once the model status change to **Trained**. :::hint{type="info" indent="1"} The model learns the fixed set of values available in its training data. Whenever you add, rename, or delete a picklist value used as an Output Field — Category, Service, Subcategory, or Team — you must retrain and redeploy the model. Until then, newly added values will not be predicted, and renamed or deleted values might still be recommended. ::: ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/F9PLG1rWA2Cf1G1iF3u8v_auto-triage-model-deploy.png" position="flex-start" size="90" width="1402" height="720" githubPath="Admin-User/Content/AITSM/images/ticket-classification-deploy-model-icon.png" darkWidth="1402" darkHeight="720" showCaption="true" caption="Model actions in Auto Triage" indent="1"} :::Paragraph{indent="1"} You can have multiple AI models with **Trained** and **Draft** status, whereas four models can be in the **Deployed** status simultaneously, one for each Output Field: **Service**, **Category**, **Subcategory**, and **Team**. For example, if you deploy another model with the **Service **field configured as an Output Field, the previously deployed model for the **Service **Output Field changes its status to **Trained**. ::: :::hint{type="info" indent="1"} Steps 16 to 20 are applicable only if you are configuring the feature for Self Service Users. These steps are not required for Service Desk Analyst role as the AI prediction works automatically for Service Desk Analyst role. ::: 16. Go to the Configuration console > **Build** > **Business Objects**, and open **Incident**. 17. Click **Quick Actions** tab, and then click **Graphical Action Designer**. 18. Create a Quick Action using the **AI Prediction Notification** block. For more information, refer to [AI Prediction Notification](docId\:ZZY_CYSw6uN5EYI_Njkmk). :::Paragraph{indent="1"} This quick action enables the ML model to predict and populate the values for the Output Fields that you configured in the AI Configuration Hub. ::: 19. After saving the Quick Action, go to the **Business Rules **tab and expand **Triggered Actions**. 20. Ensure the **Auto Triage action **toggle is ON. :::hint{type="info" indent="1"} - For out-of-the-box customers, this toggle is ON by default. The Upgraded Customers must create this toggle using the **+ Add Trigger **option. For more information, refer to [Creating a Triggered Action for a Business Object](docId:22z0oXtQ_ZEPBEmDkSzNs). - The feature predicts output field values even when incident records are created through email. ::: ## Configure the label When Service Desk Analyst or Self Service User has auto-populated the Output Fields, the application displays recommended field values in the mapped fields Output Fields and a green-colored label indicating that the recommendations have been applied. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/ZRIg7qoXRJUp5gAF0OCyk_auto-triage-label.png" size="90" caption="Configure label in Auto Triage" isUploading="false" width="1043" height="720" darkWidth="1043" darkHeight="720" showCaption="true" position="flex-start"} To display the label, do the following: 1. Log in to Ivanti Neurons for ITSM as an Administrator. 2. Open the Configuration console > **Build **> **AI Configuration Hub > Incident **business object. 3. Click **Forms **tab and select the relevant form. :::Paragraph{indent="1"} For example, *Incident.CustomerOwnershipForm* or any other form you use. ::: 4. Modify the form with the following expression: :::Paragraph{indent="1"} `$("AI Recommended Category "+RecommendedCategory) and $("AI Recommended Service "+RecommendedService)` ::: :::Paragraph{indent="1"} For more information on modifying the form, refer to [Using Forms](docId:5dD6Rlsb123v5tlqc9Wfn). ::: ## Frequently Asked Questions :::ExpandableHeading ### How many incidents are required to train the model? A minimum of 10,000 filtered and pre-processed records is required. For best results, use approximately 15,000 to 20,000 resolved or closed incidents before training. ::: :::ExpandableHeading ### Can new customers use Auto Triage without historical ITSM data? No. Auto Triage requires historical incident data to train the model. A new tenant should have approximately 15,000 to 20,000 resolved or closed incidents before training. ::: :::ExpandableHeading ### Does Auto Triage use only resolved incidents or also closed incidents for training? Auto Triage can use both resolved and closed incidents for training. ::: :::ExpandableHeading ### Why did training fail even though I have more than 10,000 incidents? The minimum requirement of 10,000 records applies after preprocessing. During preprocessing, the system cleans ticket text, removes records with insufficient content (for example, a ticket containing only *Resolved *text with an empty description), and excludes categories with too few examples. As a result, the number of records available for training can be significantly lower than the original incident count. If training fails, increase the **Historical training data** range and, where appropriate, consolidate low-volume categories into broader categories before retraining. :::