--- schema_version: "1" id: defe3f39dd43173a723bb6377f7468f8e70a1669244dfc93d127fc7bcc39bc39 title: Create and Validate an Automated Incident Triage collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/it_srvcs_agentforce_use_inctriage.md canonical_url: https://help.salesforce.com/s/articleView?id=service.it_srvcs_agentforce_use_inctriage.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: aac0a883c34f2ff09be01c62127426282502c906d448362053ec0e8fdc9d598b description: Agentforce automatically triages new incidents by verifying information completeness, detecting duplicates, and notifying employees about active major incidents. products: - Service Cloud - Agentforce IT Service release: "264" --- # Create and Validate an Automated Incident Triage Agentforce automatically triages new incidents by verifying information completeness, detecting duplicates, and notifying employees about active major incidents. ### Required Editions If you want to modify the input parameters or update the output for this action, edit the Incident Triage prompt template. For instructions, see [Revise a Prompt Template](https://help.salesforce.com/s/articleView?id=ai.prompt_builder_revise_template.htm&type=5&language=en_US).
Available in: Lightning Experience
Available in: Enterprise, and Unlimited Editions with Agentforce IT Service.
1. From the App Launcher, find and select **Agentic IT Service Desk**. Employees can create incidents from Slack as well. 2. Click the **Incidents** tab. 3. Click **New**. 4. In the New Incident form, complete the required fields: 1. Enter a descriptive value in the Subject field. 2. Set the Impact and Urgency values. 5. Save your changes. The incident record is created and the incident triage flow runs automatically in the background. 6. On the incident record, click the **Feed** tab. The automated process posts a triage summary to the feed. Depending on the incident data, the summary can include: - A list of similar open incidents, with a recommendation to review and close the current incident to avoid duplication. - Whether the incident was identified as a major incident. - A note if no relevant knowledge articles were found to help resolve the issue. 7. Review the triage results and take appropriate action, such as associating the incident with an existing record or escalating it as a major incident. ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-it_service-264-0-0-production-enus/0a574a10-4c7a-4681-aacf-0767f8beaad4/images/icon_example.png) Example **Scenario 1:** **Check Incident Completeness** When an incident is created, Agentforce reviews the structured fields and free-text description, then cross-references the incident with past similar incidents to identify information gaps that were critical for earlier resolutions. For example, when an employee reports a VPN issue, Agentforce recognizes from past incidents that the VPN client name and version are required for effective troubleshooting. Agentforce automatically contacts the employee through Slack or email to request the missing details. Agentforce consults the following data sources to determine what information is needed: - Current incident details - Past similar incidents, including the incident feed, resolution notes, and descriptions - Knowledge articles **Scenario 2:** **Notify Employees During Major Incidents** When an employee submits an incident related to an active major incident, Agentforce immediately notifies them and asks them to consider closing their individual incident. Resolving the major incident also resolves the related issue, which reduces incident volume and allows support teams to focus on the root cause. For example, if multiple employees report email access issues during an active server outage investigation, each new submission triggers an automatic notification informing the employee of the ongoing major incident and requesting that they close their individual incident. **Scenario 3:** **Identify and Manage Duplicate Incidents** When an employee submits a new incident, Agentforce checks their open incident history for duplicates. If a match is found, Agentforce notifies the employee with the existing incident number and asks them to close the new incident and update the original record. This keeps the incident queue accurate and ensures cleaner reporting on issue frequency and resolution times. For example, if an employee submits two incidents for the same printer connectivity problem, Agentforce detects the match, provides the existing incident number, and asks the employee to consolidate their updates into the original record.