@@ -36,6 +36,8 @@ Before your scheduled on-call shift begins, check [the Customer Events calendar]
**Note:** the Customer Events calendar is also linked at the top of the [#support_self-managed](https://gitlab.enterprise.slack.com/archives/C4Y5DRKLK) Slack channel for quick reference.
If you've recently switched to a new phone, see the `[guidance on switching phones](#keeping-the-pagerduty-contact-up-to-date)` in the PagerDuty contact section below to ensure your notifications are properly configured before your shift starts.
### Communicate
**Involve relevant stakeholders**: whether it's the e-group, a CSM, an [ASE (Assigned Support Engineer)](enhanced-support-offerings/offering-assigned-support-engineer/emergencies.md), subject matter experts or Support leadership, customer and operational emergencies should be known. See your rotation specific workflow for more detailed notes.
@@ -359,3 +361,5 @@ We understand you may have plans outside of your normal workspace while you're o
PagerDuty phone and SMS notifications can come from a variety of different phone numbers and as such, it is important to stay up to date with this to avoid missed pages. You should use [this PagerDuty documentation page](https://support.pagerduty.com/main/docs/notification-phone-numbers) to download the most recent vCard or setup an automatically updated PagerDuty contact on your device.
If you use a "do not disturb" mode on your device, you should also allow the PagerDuty contact to bypass this.
**When switching phones:** If you change to a new phone, log out of the PagerDuty app on your old device and thoroughly test notifications (both app alerts and calls) on your new device before your shift starts. Ensure the app is fully set up and receiving alerts correctly.
