> ## Documentation Index
> Fetch the complete documentation index at: https://docs.resolve.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Started with Primary On-Call

> Connect a paging tool, turn on auto-investigations for paging alerts, review ResolveAI's escalation decisions, then put Resolve on the pager.

This guide takes a team from a connected paging tool to ResolveAI on the pager.

## Prerequisites

* **A Resolve role that can change the team's settings**: org admin, or team admin for the team being set up.
* **A supported paging tool**, and an admin in that tool who can create the API key, user, and webhook Resolve needs.
* **Alerts that page through that tool.** Resolve makes escalation decisions only on alerts that page through a connected paging tool.
* **An alert channel in Slack or MS Teams** (recommended), so decisions show up in the alert thread. See [App for Slack](https://docs.resolve.ai/app-for-slack.md) or [App for MS Teams](https://docs.resolve.ai/app-for-ms-teams).

## Set up Primary On-Call

**1. Connect the paging tool**

Follow the Primary On-Call section for the team's paging tool. Each one lists the prerequisites, the permissions and why each is needed, and the setup steps:

* [Datadog On-Call](https://docs.resolve.ai/datadog.md#primary-on-call)
* [incident.io](https://docs.resolve.ai/incident-io.md)
* [PagerDuty](https://docs.resolve.ai/pagerduty.md#primary-on-call)
* [Rootly](https://docs.resolve.ai/rootly.md)
* [Splunk On-Call](https://docs.resolve.ai/splunk-on-call.md#primary-on-call)

Finish by sending a test event where the paging tool supports one, and check that the connection's health checks pass on the **Integrations** page.

**2. Turn on auto-investigations for paging alerts**

Open the team, then go to **Settings** > **On-call and Investigations** > **Alerts**. Click **Add filter**, add conditions that match alerts that page through the paging tool, and set the filter to **Investigate**.

See [Choose which alerts Resolve handles](#choose-which-alerts-resolve-handles) for how to make sure the filter covers them.

**3. Review escalation decisions during trust building**

Leave the filter on **Investigate**. The on-call engineer is still paged as usual, and Resolve records **Would close** or **Would escalate** on each of those alerts.

* Review the decisions in the alert thread, the daily digest, or the **On-call & Investigations** page. See [Where escalation decisions appear](https://docs.resolve.ai/where-escalation-decisions-appear.md).
* Leave feedback on each decision, especially the ones the team disagrees with.
* Tune the escalation criteria until the decisions match what the team expects. See [Escalation Decisions and Criteria](https://docs.resolve.ai/escalation-decisions-and-criteria.md).

Expect a high share of **Would escalate** at first. The default criteria are general, and escalating is the safe default.

> [!WARNING]
>
> Do not set a filter to **Handle pages** before reviewing the decisions Resolve makes on it. Move a filter only when the team has reviewed those decisions and is confident in them.

**4. Put Resolve on the pager**

When the team has reviewed the decisions on a filter and is confident in them, change that filter from **Investigate** to **Handle pages**. The change is listed as pending, and paging keeps working as it does now.

Click **Review and apply**. Resolve shows the changes it will make in the paging tool, or the changes to make by hand. Once they are applied, pages for that filter go to Resolve first, and the on-call engineer is paged only if Resolve escalates.

**5. Keep reviewing decisions**

Watch the first days of **Closed** and **Escalated** decisions and keep leaving feedback. Review the decisions on any other filter the same way before setting it to **Handle pages**.

> [!TIP]
>
> A filter that is handling pages shows that every page it matches goes to Resolve first, and its activity line counts the pages handled, closed, and escalated in the last 30 days.

## Choose which alerts Resolve handles

Escalation decisions appear only on paging alerts that Resolve can identify and investigates. If decisions are missing for an alert, check three things:

1. **The alert pages through a connected paging tool.** An alert that reaches Resolve only from a monitoring tool, and never pages, has no escalation decision.
2. **An alert filter covers it.** The alert must match a filter set to **Investigate** or **Handle pages**.
3. **The filter uses labels the paging tool sends.** A filter can route pages only when the paging tool sends every label the filter names. Filter on labels the paging tool sends directly, not on labels that exist only in the monitoring tool.

Each integration page lists the labels that tool sends:

* [Datadog On-Call labels](https://docs.resolve.ai/datadog.md#labels-for-alert-filters)
* [incident.io labels](https://docs.resolve.ai/incident-io.md#labels-for-alert-filters)
* [PagerDuty labels](https://docs.resolve.ai/pagerduty.md#labels-for-alert-filters)
* [Rootly labels](https://docs.resolve.ai/rootly.md#labels-for-alert-filters)
* [Splunk On-Call labels](https://docs.resolve.ai/splunk-on-call.md#labels-for-alert-filters)

When a filter cannot route pages, Resolve says why on the filter. Common reasons are that the paging tool has sent no matching alerts in the last 30 days, or that the tool does not send one of the labels the filter uses.

## What's next

* [Safety and control](https://docs.resolve.ai/primary-on-call-safety-and-control.md): when Resolve always escalates, the fallback timeout, and taking Resolve off the pager.
* [Limits](https://docs.resolve.ai/limits.md#pages-handled-by-resolve): how pages Resolve handles count toward usage.
