You are here:
How Service Management Records Work Together in IT Services
Agentforce IT Service management records are interconnected and work together for service stability and efficiency. While incidents and service requests capture employees needs, problems, change requests, and releases help IT teams implement long-term fixes and planned updates.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with Agentforce IT Service. |
The Journey from Disruption to Resolution
The IT service management process is a continuous loop that begins with an incident and can lead to a formal release.
This table summarizes how each record is used in IT services and what it helps IT teams achieve.
| RECORD TYPE | USAGE | GOAL |
|---|---|---|
| Incident | Unplanned disruption | Restore service quickly |
| Service Request | Standard request or preapproved change request | Fulfill efficiently through defined steps |
| Problem | Recurring or complex issues | Identify root cause and prevent recurrence |
| Change Request | Controlled modification | Implement a long-term fix safely |
| Release | Deploy approved change request | Coordinate rollout with minimal impact |
Service requests track standard requests and preapproved change requests. If a request is logged as an incident, IT teams can create a service request from the incident to complete fulfillment efficiently. For more information, see Create Service Requests from Incidents.
This interconnected workflow leads a reported incident to a long-term, proactive solution. It moves the IT team from a reactive, firefighting mode to a strategic approach that improves service quality and operational performance over time.
With service maps that show affected and impacted configuration items for an issue in a visual and interactive graph, and AI actions that help IT fulfillers react to the smallest of updates during the entire IT service lifecycle, the records in Agentforce IT Service helps IT teams work cohesively towards faster and effective resolution.
| Record | Purpose | Example |
|---|---|---|
| Incident | The issue is an unplanned disruption and the goal of the IT team is to restore service quickly. | An employee reports that their company laptop suddenly lost Wi-Fi connectivity. The IT team creates a high-priority incident to immediately troubleshoot the issue and get the user back online. |
| Problem | The issue is recurring and needs root cause analysis to prevent repeat incidents. | The IT team notices that multiple employees have been reporting Wi-Fi connectivity issues in the same building. They create a problem record to investigate if there's a hardware fault with a specific network router that is causing the recurring incidents. |
| Change Request | The issue requires a controlled update to the IT environment that must be reviewed and approved. | The problem investigation reveals a faulty router. A change request is created to schedule the replacement of the router during a maintenance window. The request is sent for approval to ensure all stakeholders are aligned. |
| Release | The issue involves deploying an approved change into the live environment and validating rollout. | After the change request for the new router is approved, it is tied to a release record. The release team uses this record to track the deployment of the new hardware and verify that the fix is successfully implemented for all affected employees. |
| Service Request | The issue is a standard request for something new and follows a defined fulfillment process. | An employee requests VPN access for a new project. The IT team creates a service request to track the request and complete the standard fulfillment steps. |
