Using the Mobile App

New to the Mobile App?

The mobile app is available on the Apple Store and Google Play:

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

Supported Operating Systems and Configuration

The app is supported on iOS 11.0 and up, and Android 5 and up. We do not support rooted devices.

Mobile App Walkthrough

The walkthrough screenshots below are from our Android app, and the iOS app is very similar.

Open Incidents Screen

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

After login, you should see the Open Incidents screen, similar to the following:

The Mine tab shows all triggered and acknowledged incidents assigned to you. The All tab shows all triggered and acknowledged incidents in the account. If you have a Responder role or higher, you will also see the My Teams tab, which will show all incidents assigned to your teams.

Using the Mobile App During an Incident

During an incident, you will be able to see all activity on the Open Incidents screen ( Open Incidents).

Acknowledging Incidents

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. You can acknowledge an incident by swiping left and tapping Ack, tapping the incident and tapping the Ack button on the incident details page, or you can acknowledge directly from a push notification. Push notifications will look similar to the one below. PagerDuty push notifications provide the incident number, service, and incident description.

Once you acknowledge the incident, the banner will turn yellow.

Snoozing Incidents

You will see Ack and Resolve buttons on the incident details page of a triggered incident. After an incident is acknowledged, the Ack button becomes a Snooze button. You can also snooze an incident by swiping left on an acknowledged incident.

Incident Details and Other Actions

Tap an incident to enter the incident details screen. The incident detail screen contains incident information, timeline and a status updates section.

Resolving Incidents

To resolve, tap the Resolve button or swipe right. You can customize your swipe actions within the Settings menu. You can still add notes even after an incident has been resolved. To view resolved incidents, navigate to Resolved Incidents.

Trigger an Incident

To trigger an incident, open the app, navigate to Open Incidents screen, tap the icon and select New Incident.

Enter the following:

  • Name: A meaningful name for the incident.
  • Description (optional): A meaningful description of the incident.
  • Service: Select the affected service.
  • Assign to (optional): You may select an escalation policy or user other than the service's default escalation policy. This overrides who the incident is assigned to.
  • Priority (optional): You may add a priority if necessary.

Tap Create to trigger the incident.

Escalation Policies Screen

The Escalation Policies screen ( Escalation Policies) 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.

Users Screen

The Users screen ( Users) 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.

Settings Screen

From the Settings screen ( Settings), 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 PagerDuty System Status. For more information on notification configuration options, check out our Mobile Notification Settings article.

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.





Live Updating

With incident live updating, 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, you can pull the screen down to refresh, 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. If you would like to to disable Live Updating, navigate to the Settings tab of the mobile app. Under the Performance section, toggle Live Updating off.


While on live screens, 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 your desired schedule.

Click on the shift you would like to override.

Adjust the user and the time constraints as necessary, and tap 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.