Using the Mobile App


New to the Mobile App?

The mobile app is available on both Google Play and the Apple Store. (to put download links here)

The mobile app will allow you to trigger, acknowledge, and resolve incidents. You can add responders and run response plays, as well as reassign incidents and add notes. With schedules, you can easily create overrides and view your upcoming on call shifts. You can customize your ringtones and set behavior for high and low urgency incidents all from your settings page.

Supported Operating Systems

The app is supported on iOS 10 and up, and Android 4.4 and up.

Mobile App Walkthrough

Below is a walkthrough of our mobile app. You can download the app from the App Store for iOS or Google Play for Android. Screenshots are from our Android app, and the iOS app is very similar.

The first time you open the PagerDuty app, you will be prompted to enter your email address/password or subdomain to login.

After logging in, you should see a similar screen as follows:

The All tab shows all triggered and acknowledged incidents in the account.

Push notifications will look similar to the one below. You can acknowledge an incident directly from the notification. PagerDuty push notifications provide the incident number, service, and incident description.

If a triggered incident is assigned to you, the banner at the top will turn red. Your incidents will be under the Mine tab on the Open Incidents screen. Once you acknowledge the incident, the banner will turn yellow.

Snooze an incident by swiping left on an acknowledged incident.

Tap an incident to enter the incident detail screen. The incident detail screen contains incident info and timeline.

You also have other options such as running a response play, changing or adding priority, adding responders and more from the Incident detail page.

You will also see Ack and Resolve buttons when selecting a triggered incident. After an incident is acknowledged, the Ack button becomes a Snooze button.

To resolve, swipe left. You can customize your swipe actions within the Settings menu. You can still add notes even after an incident has been resolved.

You can also go to the Resolved Incidents view to see all previously resolved incidents.

The Escalation Policies view shows your escalation policies as well as your teams' and all of your organization’s escalation policies.

Selecting an escalation policy will show who is on-call at each level. Select a user to see their contact info and schedule details.

The Users view lists users and their login email address. Selecting a user will show their contact methods and escalation policies where they are on-call. You can email, call, or SMS a user from your device by tapping on a user's email address or phone number.

From the Settings screen, you can select a custom push notification sound, as well as sounds for high and low-urgency notifications. You can also change your notification behavior, configure your own swipe actions, contact support, or check for critical PagerDuty-related issues by tapping System Status.

You can also change how PagerDuty notifications are displayed on your device (i.e. how many notifications to show at once, whether or not you want notifications to be shown when your device is locked, etc.) by launching the Settings app and going to Notifications → PagerDuty.

Responding to Incidents in the Mobile App

You can use the mobile app to trigger, acknowledge, snooze, and reassign incidents. For more information on using the mobile app, you can check out the mobile app walkthrough.

Trigger an Incident

To trigger an incident in the mobile app, open the app, view the Open Incidents screen, and tap the More icon in the upper right corner.

You can optionally choose to assign an incident to an escalation policy other than the service's default escalation policy. This overrides who the incident is assigned to.

Acknowledge or Snooze an incident

There are 2 ways to acknowledge an incident in the mobile app. On the Open Incidents screen:

  1. Swipe left on an incident to acknowledge the incident.
  2. Tap an incident and then ACK at the bottom of the screen.

Once you acknowledge the incident you will also see the option to Snooze the incident for a period of time.

Resolve an Incident

There are 2 ways to resolve an incident in the mobile app. On the Open Incidents screen:

  • Swipe right to resolve the incident.
  • Tap the name of the incident and then RESOLVE at the bottom of the screen.

Other Actions

You can also add responders, reassign, add priority, and add notes to incidents in the mobile app. These option are available from the MORE menu at the bottom of the screen.

Live Updating

With live updating of incidents, incident pages and detail screens will stay up-to-date with the latest information and incident statuses, eliminating the need to manually refresh these pages in order to get updates.

While on an incident list, when new incidents come in, a button will appear near the top of the screen indicating how many new incidents are ready to be shuffled into the list. After pressing that button, new incidents will be shuffled in and the view will move to the latest, highest priority incident. Alternatively the user can invoke a scroll, where the button will disappear and the new incidents will be shuffled in, but the view will not change.

Live updating is on by default. In order to disable Live Updating:

  1. Navigate to the Settings tab of the mobile app
  2. Under the Performance section, toggle Live Updating off


While on screens with liveness, push notifications will not show up in the app as to not distract users from triaging incidents. The push notifications will still be logged in your notifications list and in the incident’s timeline.

Scheduling Overrides

To schedule an override from the mobile app, navigate to ☰ > Schedules and select the schedule.

Then click on the shift you would like to edit.

Then click the pencil icon, adjust the user and the time as required, and click Override.

Using the Mobile App

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.