# Service Dependencies

Use Service Dependencies to define relationships between technical and business services.

[Service dependency](/incident-management/services/service-profile#service-dependencies-tab) data provides a broader understanding of the environment surrounding their incident, allowing you to identify the root cause more efficiently. When a service is experiencing an incident and has defined dependencies, relevant service dependency data is available on the incident details page. If the service does not yet have dependencies defined or is missing possible dependencies, you can view suggested dependencies and easily add them. 

## View Technical Service Dependencies in an Incident

To view the impacted service’s **Technical Service Dependencies**, click an incident’s **Title** to view the incident details page. You will see the **Technical Service Dependencies** section on the right, below **Notes** section.

![A screenshot of the PagerDuty web app showing technical service dependencies](/images/kb/20056a16538624db662fadef0ace462c695e802dd168d6de16a0c64dda1e7294-technical-service-dependencies-incident.webp)
*Technical service dependencies*

Each dependency includes the following details:

- **Service Name**
- **Status**: **Open Incidents** or **Operational** (no open incidents).

If you click the dependency’s **Service Name**, you can view more granular details:

- **On Call Now**: Responder(s) currently on call for the service.
- **Open Incidents**: A list of current open incidents on the service.

## Suggested Technical Service Dependencies in an Incident

If incidents on your service tend to be followed by incidents on another service, or vice versa, suggested technical service dependencies will also be provided. If available, they appear under a **Suggested** header with  next to the service's name:

![Suggested Technical Service Dependencies section with a lightning bolt icon next to a recommended service name](/images/kb/2dd7a833810344a2a067875bbe99111f0cb0a0fc4a77d72f67c3ddb804854318-technical-service-dependencies-suggested.webp)
*Suggested service*

To add a **Suggested Service Dependency**, click the **service name**  →  **Add**, next to **Add this service as a dependency?**.

![A screenshot of the PagerDuty web app showing how to add a service as a dependency](/images/kb/c6ed7b5a32f6502a7b5586987516aa1c099f72d445cf3a1482f731606bc00101-technical-service-dependencies-add-suggested.webp)
*Add service as a dependency*

## Add Technical Service Dependencies From an Incident

1. Click an incident’s **Title** to view the incident details page. 
2. View the **Technical Service Dependencies** section on the right, below **Notes**.
3. Click **Add Service Dependency**.  
   You will be directed to the service’s [Service Dependencies](/incident-management/services/service-profile#service-dependencies-tab) page. There are two sections to this page: other services that this service **uses** or is **used by**. 
4. Click **Edit Services** to add the appropriate dependency. 
5. On the **Edit Services** screen, search by service name, or select one of the **Business Services** or **Technical Services** tabs. 
6. Click  to add the desired services; you may add multiple business and technical services.
7. (_Optional_) Create a new business or technical service on this screen by clicking **Create a new business service** or **Create a new technical service** from the corresponding tabs. This launches the [Business Service](/incident-management/services/business-services#create-a-business-service) or [Technical Service](/incident-management/services/services-and-integrations#create-a-service) configuration screen in a new tab.
8. Click **Save Changes**.