---
title: "On-call and paging — FireFight"
description: "Pull in a teammate and know they are coming, page whoever is on call through PagerDuty or Opsgenie, and let Halon take the first look when an alert fires at night."
canonical: https://firefight.app/product/on-call
---

# On-call and paging

**Wake the right person, and tell them why**

Pull in a teammate and know they are coming, or page whoever is on call through PagerDuty or Opsgenie. Halon takes the first look before anyone is awake.

[Sign in with Slack](https://app.firefight.app/)

## Escalations in Slack, pages in your on-call tool

Your rotations stay in PagerDuty or Opsgenie. Firefight knows who is on call and keeps the incident and the page in step.

### Escalate

**Pull someone in, and know they are coming.** They get a direct message to acknowledge, and a reminder if they don't. The channel sees the moment they join.

- From Slack or the dashboard
- Acknowledge in one click
- A reminder if nobody answers
- Every escalation on the timeline

### Page

**Page through PagerDuty or Opsgenie.** Your schedules stay where they are, and the page and the incident stay in step both ways.

- PagerDuty and Opsgenie
- Who is on call, read live
- Acknowledgements flow both ways
- Every page on the incident

### Halon on call

**Halon takes the first look at 3am.** It reads the logs, deploys and metrics, and the person paged wakes up to the likely cause and a proposed fix.

- Off until you turn it on
- A spending limit you set
- The answer travels with the page

## What happens before and after someone is woken

### Schedules stay put

Keep your rotations in PagerDuty or Opsgenie, with one schedule to maintain.

### One page, kept in step

Resolve the incident and the page resolves, and whatever happens in your tool shows on the timeline.

### The person on call can approve the fix

Let whoever was woken approve the change they were woken for, without waiting on anyone else.

### Agreed fixes run on their own

Decide ahead which rollbacks and restarts Halon may make alone, and it tells you what it did and how to undo it.

### Page from a workflow

Wake whoever is on call as one step of a workflow, even with no on-call tool connected.

### Page from a chat or your agents

Ask Halon to page whoever is on call, or let your own agents do it, under the same approval rules.

## Documentation

- [Halon on call](https://firefight.app/docs/ai/on-call.md): Let Halon take the first look, page through your on-call tool, and agree fixes ahead.
- [Slack command reference](https://firefight.app/docs/incidents/slack-commands.md): Escalate and everything else you can do from an incident channel.
- [Connect PagerDuty](https://firefight.app/docs/alerts/pagerduty.md): Bring PagerDuty incidents in as alerts, and keep pages in step.
- [Connect Opsgenie](https://firefight.app/docs/alerts/opsgenie.md): Bring Opsgenie alerts in, and keep pages in step.
- [Approvals](https://firefight.app/docs/gateway/approvals.md): Hold a change for approval, and let the person on call approve it.
- [Workflows](https://firefight.app/docs/ai/workflows.md): Page on call, and everything else a workflow can do.

## Wake the right person, with the answer

Connect Slack, then PagerDuty or Opsgenie. Your schedules stay where they are. [Sign in with Slack](https://app.firefight.app/).