Skip to main content
Primary On-Call is built so that a page is never lost. ResolveAI closes a page only when the evidence shows no one needs to respond. In every other case, the page reaches the on-call engineer. The root causes Resolve identifies are tracked as Issues, including for the pages it closes.

When Resolve always escalates

Resolve escalates the page to the on-call engineer when:
  • It is unsure. A reasonable investigation leaves material uncertainty about the impact, the blast radius, or the action needed.
  • It cannot support a close with evidence. Every close must cite evidence. A close that cannot be confirmed becomes an escalation.
  • A close fails in the paging tool. If the paging tool rejects the close, Resolve escalates instead.
  • The escalation criteria changed during the investigation. Resolve does not close a page on criteria that are no longer current.
  • A credit limit has been reached. Resolve escalates the page immediately, without investigating it. See Billing and Credit Controls.

Fallbacks and failed escalations

Resolve is added to the existing escalation policy, ahead of the on-call rotation. Keep the timeout on that policy. It is the fallback for everything Resolve cannot do:
  • Resolve does not decide in time. The timeout expires and the page moves to the next level as usual.
  • The investigation fails or cannot start. Resolve writes nothing to the page, and the timeout moves it on.
  • Resolve cannot reach the paging tool to escalate. The timeout is still running and moves the page on.
Resolve does not override a person. If someone has already acknowledged, resolved, or reassigned the page, Resolve leaves it as it is.

Approvals

Handling pages does not change what Resolve is allowed to do in production.
  • Escalation decisions are automatic. Closing, acknowledging, and escalating a page happen without approval. That is the purpose of Primary On-Call.
  • Mitigation actions stay human-approved. When an investigation proposes a mitigation action, such as silencing a noisy alert, a person must approve it before anything runs. This holds even when Resolve holds the pager.

How Resolve closes a page

Each team chooses what a close does in the paging tool. Open the team’s Settings > On-call and Investigations > Integration & Notifications and find How Resolve responds:
  • Resolve alert group (default): Resolve closes the page.
  • Acknowledge only: Resolve acknowledges the page and leaves it open for the on-call rotation to resolve.

Take Resolve off the pager

Resolve can be taken off the pager at any time, one alert filter at a time.
1

Open the team's alert filters

Open the team, then go to Settings > On-call and Investigations > Alerts.
2

Change the filter's level

Change the filter from Handle pages to Investigate to keep the investigations, or to Off to stop them. The change is listed as pending, and paging keeps working as it does now.
3

Apply the change

Click Review and apply. Resolve removes itself from the paging path for that filter, and pages go straight to the on-call rotation again.
Deleting a filter that handles pages follows the same path: Resolve moves the filter to Off as a pending change first, and the filter can be deleted once the change is applied.

Who can change these settings

  • Org admins can change Primary On-Call settings for every team.
  • Team admins can change them for the teams they administer.
This covers alert filters, escalation criteria, the fallback timeout, how Resolve closes a page, and notifications.