--- title: Pages description: Datadog, the leading service for cloud-scale monitoring. breadcrumbs: Docs > Incident Response > On-Call > Pages --- # Pages {% callout %} # Important note for users on the following Datadog sites: app.ddog-gov.com {% alert level="danger" %} This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). (). {% /alert %} {% /callout %} A Page is an alert that requires an on-call responder's attention. Pages move through the following life cycle: - **Triggered**: The Page has been sent, but no one has taken ownership. The escalation policy runs according to its configuration, notifying additional responders if no one responds within the defined time frame. - **Acknowledged**: A responder has claimed the Page. Escalation notifications stop, and the responder begins working on the issue. - **Resolved**: The underlying issue has been addressed, and the Page is closed. This guide explains how to trigger, acknowledge, reassign, and resolve Pages. ## Trigger a Page{% #trigger-a-page %} A Page is sent to a Team and routed through its escalation policies and schedules. After your Team is [onboarded to Datadog On-Call](https://docs.datadoghq.com/incident_response/on-call/teams.md), you can start paging it. ### Trigger Pages from monitors{% #trigger-pages-from-monitors %} Send a Page by mentioning a Team's handle with `oncall-` prepended. For example, to send a Page to the Checkout Operations Team (`@checkout-operations`), mention `@oncall-checkout-operations`. {% image source="https://docs.dd-static.net/images/service_management/oncall/notification_page.daa7e914865641789d565bd04bf92a24.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/service_management/oncall/notification_page.daa7e914865641789d565bd04bf92a24.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Notification that mentions an On-Call Team." /%} You can send Pages to On-Call Teams anywhere @-handles are supported, including monitors, Incident Management, security detection rules, and Event Management. #### Resolving Pages automatically{% #resolving-pages-automatically %} When a monitor recovers, any Page it triggered is automatically set to `Resolved` if the recovery notification includes the On-Call Team mention (for example, `@oncall-payments`). If the mention appears only in the alert template (for example, within `{{#is_alert}} ... {{/is_alert}}`) and not in the recovery message, the Page does not auto-resolve. #### Monitors and dynamic urgencies{% #monitors-and-dynamic-urgencies %} If you send a Page through a monitor alert and the Team's routing rule uses dynamic urgencies: - If the WARN threshold is crossed, the Page urgency is set to `low`. - If the ALERT threshold is crossed, the Page urgency is set to `high`. ### Trigger Pages through email{% #trigger-pages-through-email %} Generate a unique email address to trigger a Page directly to a Team's on-call responders. Emails sent to this address follow the Team's configured routing and escalation policies. Some teams embed this address in a human-readable distribution list (for example, `page-network@company.com`) to make it more recognizable. To page a Team through email: 1. Go to the Team's page and scroll to **Custom Triggering Sources**. 1. Under the email trigger section, click **Generate**. ### Trigger Pages through incidents{% #trigger-pages-through-incidents %} Trigger a Page directly from an active incident to escalate and involve additional responders without leaving the workflow. See [Trigger a Page from an incident](https://docs.datadoghq.com/incident_response/incident_management/notification.md#trigger-a-page-from-an-incident) for detailed instructions. ### Trigger Pages through calls{% #trigger-pages-through-calls %} Trigger a Page through [Live Call Routing](https://docs.datadoghq.com/incident_response/on-call/pages/live_call_routing.md) by calling a dedicated phone number. ### Trigger Pages manually{% #trigger-pages-manually %} Send a Page from the Datadog platform, or through a tool like Slack or Microsoft Teams. This lets you alert a Team or individual directly, even if they are not On-Call. #### Through Datadog{% #through-datadog %} 1. Go to [**On-Call** > **Teams**](https://app.datadoghq.com/on-call/teams). 1. Find the Team you want to page. Select **Page**. {% image source="https://docs.dd-static.net/images/service_management/oncall/manual_page.af92d0e564847090f38d22be6bfd35a1.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/service_management/oncall/manual_page.af92d0e564847090f38d22be6bfd35a1.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The list of On-Call Teams, showing the Checkout Operations Team. Three buttons are displayed: Schedules, Escalation Policies, Page." /%} 1. Enter a **Page title** and add more context in the **Description** field. Select **Page**. Pages sent manually through Datadog are always `high` urgency. #### Through Slack{% #through-slack %} 1. Install the Datadog Slack app. 1. Enter `/datadog page` or `/dd page`. 1. Select a Team to send a Page to. Pages sent from Slack are always `high` urgency. To receive Page notifications in Slack, see [Routing Rules](https://docs.datadoghq.com/incident_response/on-call/routing_rules.md#send-pages-to-slack-or-microsoft-teams). ## Respond to a Page{% #respond-to-a-page %} Go to [**On-Call** > **Pages**](https://app.datadoghq.com/on-call/pages) to view all active and historical Pages. Click a Page to open its side panel and take action, or select the checkbox next to one or more Pages to bulk-edit them. {% image source="https://docs.dd-static.net/images/service_management/oncall/on-call-pages-list.be974905ef3375898d2b16d2ff0ac3ee.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/service_management/oncall/on-call-pages-list.be974905ef3375898d2b16d2ff0ac3ee.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The On-Call Pages list view with sub-tabs for Active, Triggered, Acknowledged, Resolved, and All, and a table showing each Page's name, status, Team, responders, and creation date" /%} ### Acknowledge a Page{% #acknowledge-a-page %} Acknowledging a Page signals that you're actively working on it and stops the escalation policy from notifying the next tier of responders. If you do not acknowledge the Page, escalation continues and additional responders may be paged. To acknowledge a Page: 1. Click the Page to open its side panel. 1. Under **Next Steps**, select **Acknowledge**. The Page status changes to `Acknowledged`. {% image source="https://docs.dd-static.net/images/service_management/oncall/on-call-page-side-panel.55c68abae3266382db9f05d69a9f6a1f.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/service_management/oncall/on-call-page-side-panel.55c68abae3266382db9f05d69a9f6a1f.png?auto=format&fit=max&w=850&dpr=2 2x" alt="An On-Call Page side panel showing the Page status, urgency, responder, and service, with Next Steps buttons to Acknowledge, Reassign, Resolve, or Declare Incident" /%} ### Reassign a Page{% #reassign-a-page %} Reassign a Page if it was routed to the wrong person or Team, or if you need to transfer ownership to someone better positioned to respond. When you reassign a Page, the Page history remains intact. To reassign a Page: 1. Click the Page to open its side panel. 1. Under **Next Steps**, select **Reassign**. This opens a **Reassign Page** modal. {% image source="https://docs.dd-static.net/images/service_management/oncall/on-call-reassign-page.7b277cc06742683cc87d2460accece69.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/service_management/oncall/on-call-reassign-page.7b277cc06742683cc87d2460accece69.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The Reassign Page modal with a toggle to reassign to a Team or User, a team selection dropdown, and an optional comment field" /%} 1. Select the user or Team to reassign to. 1. Optionally, add a comment explaining the handoff. 1. Click **Reassign**. The new recipient is notified immediately. **Note**: You can only reassign Pages with a `Triggered` or `Acknowledged` status. ### Resolve a Page{% #resolve-a-page %} Resolve a Page when the underlying issue is addressed. This closes the Page and sets its status to `Resolved`. To resolve a Page: 1. Click the Page to open its side panel. 1. Under **Next Steps**, select **Resolve**. If the Page was triggered by a monitor, it resolves automatically when the monitor recovers—provided the recovery notification includes the On-Call Team mention. See Trigger a Page for details. ### Declare an incident from a Page{% #declare-an-incident-from-a-page %} If a Page requires cross-team coordination, stakeholder communication, or formal tracking, promote it to an incident. This creates an incident in [Incident Management](https://docs.datadoghq.com/incident_response/incident_management.md) with the Page context pre-filled. To declare an incident: 1. Click the Page to open its side panel. 1. Under **Next Steps**, select **Declare Incident**. 1. Review and adjust the pre-filled details as needed. {% image source="https://docs.dd-static.net/images/service_management/oncall/on-call-declare-incident-demo.285dd7ff335e5e71ced703b716136590.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/service_management/oncall/on-call-declare-incident-demo.285dd7ff335e5e71ced703b716136590.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The Declare Incident modal pre-filled with the Page title and summary, with fields for incident type, severity level, incident commander, and team" /%} 1. Select **Declare Incident** to confirm. For guidance on incident severity levels and responder roles, see [Incident Management](https://docs.datadoghq.com/incident_response/incident_management.md). ### Add a comment{% #add-a-comment %} The Page timeline is an activity log that records when the Page was triggered, who was notified, and how escalation progressed. You can add your own comments to provide context for other responders. {% image source="https://docs.dd-static.net/images/service_management/oncall/on-call-timeline-demo.0dd6ce85a26352223e600a66d40bdae4.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/service_management/oncall/on-call-timeline-demo.0dd6ce85a26352223e600a66d40bdae4.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The Timeline section of an On-Call Page showing a comment input field and a chronological log of events including the Page trigger, notifications sent, and acknowledgment" /%} Use comments to: - Document what you've already investigated or ruled out - Provide context when handing off to another responder - Record external factors that affected your response To add a comment, open the Page and enter your text in the **Timeline** section. ## Further Reading{% #further-reading %} - [Datadog On-Call](https://docs.datadoghq.com/incident_response/on-call.md) - [Incident Management](https://docs.datadoghq.com/incident_response/incident_management.md)