How it works
Resolve follows the team’s escalation criteria and records the reason and the evidence behind each decision. The deep investigation runs in full whichever way the decision goes, whatever investigation mode the alert had before, and the root cause it identifies is tracked as an Issue. If Resolve does not decide in time, the timeout on the escalation policy moves the page to the on-call engineer as usual. See Safety and control.What Resolve does not do
- It does not replace the escalation policy. The on-call rotation stays on the policy, behind Resolve.
- It does not close a page when unsure. Material uncertainty about impact or the action needed is an escalation.
- It does not override a person. A page that someone has already acknowledged, resolved, or reassigned is left alone.
- It does not run mitigation actions on its own. Mitigation actions still need human approval.
- It does not handle alerts that do not page. Escalation decisions apply only to alerts that page through a connected paging tool.
Trust building
Before putting Resolve on the pager, review the escalation decisions it would make. During trust building the on-call engineer is paged as usual, and Resolve records Would close or Would escalate on each paging alert it investigates. Nothing changes in the paging tool. Use this period to check decisions against what the team expects, leave feedback, and tune the escalation criteria. Do not set an alert filter to Handle pages until the team has reviewed the decisions on it and is confident in them.What’s next
Get started
Go from a connected paging tool to Resolve on the pager.
Escalation decisions and criteria
Read a decision, write good criteria, and give feedback.
Where escalation decisions appear
Alert threads, the daily digest, and the On-call & Investigations page.
Safety and control
When Resolve always escalates, the fallback timeout, and taking Resolve off the pager.

