# Email Notifications See sample subject lines and body content PagerDuty sends by email for incident triggers, responses, and status updates. PagerDuty can notify users via email when various incident lifecycle events occur. This article details what such notifications may look like, though the exact content may vary. PagerDuty sends email notifications from `no-reply@pagerduty.com`. > **Contact Information and Notification Rules:** For more information about adding contact methods and configuring notification rules, see [Contact Information](/account-admin/user-profile/contact-information) and [Notification Rules](/account-admin/user-profile/notification-rules) in the [User Profile](/account-admin/user-profile) article. ## Email Notification Content | PagerDuty Action | Subject Line | Body | | --- | --- | --- | | An incident triggers and notifies the on-call user | **One incident assigned:** "\[PagerDuty Alert] You have 1 TRIGGERED Incidents (`[4cb96]`)" **If you are assigned multiple incidents, PagerDuty will bundle incident notifications into one email:** "\[PagerDuty Alert] You have `[3]` TRIGGERED Incidents (`[db97d]`)" | **HTML Email:** "Hello `[User Name]`, you have `[#]` open incident(s) assigned to you: `[Incident Number]`, `[Incident Title]`, `[View Incident Link]`, `[Details]`, `[Meeting URL]`, `[Dial-In Number]`, `[Status]`, `[Urgency]`, `[Assigned To]`, `[Opened On]`, `[Service]`, `[Escalation Policy]`" **Plain Text Email:** "Hello `[User Name]`, You are assigned `[#]` triggered incident in PagerDuty. Please visit the following URL to manage this incident: `https://[subdomain].pagerduty.com/incidents`. `[Incident Number]`, `[Opened On]`, `[Service]`, `[Description]`, `[Incident Link]`, `[Escalation Policy]`, `[Meeting URL]`, `[Dial-In Number]`, `[Details]`. You can disable these messages by adjusting your notification methods: `https://[subdomain].pagerduty.com/users/PXXXXXX`" \* _If applicable_ | | A user is added as a [responder](/incident-management/incidents/add-responders) upon incident trigger | "PagerDuty response requested" | "Your response is requested: Please help with "\[#`[Incident Number]`] `[Incident Title]`" `https://[subdomain].pagerduty.com/incidents/XXXXXXXXXX`" | | A user is added as a [responder](/incident-management/incidents/add-responders) to an _existing_ incident | "PagerDuty response requested" | "Your response is requested: Please help with "`[Incident Title]`" `https://[subdomain].pagerduty.com/incidents/XXXXXXXXXX` `[Meeting URL]`\* `[Dial-In Number]`_"_ _If applicable_ | | A user receives a [Status Update](/incident-management/communicate/communicate-with-stakeholders) to an incident they are assigned or subscribed to | "\[PagerDuty Status] `[incident status]`: `[incident name]`" | "`[user]` updated: `[incident number]`, `[incident title]`, `[trigger date and time]`, `[service name]`, `[user(s) assigned to the incident]`, `[View Incident link]`, `[incident status]`, `[status update]`, `[View Status Page link]`" | | A user is about to go on call ([On-Call Handoff Notification](/incident-management/schedules/escalation-policies)) | "\[PagerDuty] `[user name]` is going on call for `[escalation policy]` (Level `[X]` - `[schedule name]`)" | "`[user name]` is going on call for the following escalation policy in 1 hour: Escalation Policy: `[escalation policy]` (used by X services) Level 1 (`[schedule name]`) `[date and time]` Override here: `https://subdomain.pagerduty.com/schedules/PXXXXXX`" | ### HTML Email Notifications Users can choose whether they’d like to receive HTML notifications in their web app user profile: 1. Go to **User Icon** → **My Profile** → **Contact Information** tab. 2. In the **Email** section, click to edit your desired email address, _or_ **Add Email Address** if you would like to add a new one. 3. Check the **Send HTML Emails** checkbox. - If this option is unselected, PagerDuty will send email notifications in plain text. ![Send HTML Emails checkbox in the Contact Information tab of the user profile](/images/kb/de732a6b9d1a75725fe65a7fe7fc69506d1c5313e76346d87f48c770925dd264-html_emails.webp) *Enable or disable HTML emails* 4. Click **Save**. Here is an example of a PagerDuty HTML email notification: ![Formatted HTML email with incident number, title, status, urgency, and a View Incident button](/images/kb/689df706e45b9290ae633affb7a1c1ac260ae37938462bd74fd4ab6d080c568b-notification-content-bx-html-email.webp) *HTML email notification* Here is an example of a PagerDuty plain text email notification: ![Unformatted plain text email listing incident number, service, and a link to manage the incident](/images/kb/cc8f41e1536da393e1cfc2fd0c4fdb8d3ec9dcceaf352f2c7ba3c773e633658c-notification-content-bx-text-email.webp) *Plain text email notification* ## Email Truncation and Attachments When you receive a PagerDuty email notification, the incident’s **Details** section will be truncated after 500 characters. You can include clickable links in this truncated message. The rest of the email body is accessible either in the web app on the incident’s details page, or in the [mobile app](/get-started/mobile-app#mobile-app-walkthrough). PagerDuty removes attachments from email notifications and incident logs. To view the original attachment, please refer to the system that sent the original attachment. ## Email Digests PagerDuty adds a digest to the end of email notification subject lines so that related messages are grouped together in your inbox, for example: `[PagerDuty Alert] You have 2 TRIGGERED Incidents (4bc68)`. This digest is not displayed in the PagerDuty web app, however it will help your email client know that subsequent messages are related to a specific incident.