-[Communications Manager on-call (CMOC)](/handbook/support/workflows/cmoc_workflows) - in which Support Engineers drive public communication in the incident management process during GitLab.com operational emergencies.
-[Customer Emergencies on-call (CEOC)](/handbook/support/workflows/customer_emergencies_workflows)- in which Support Engineers respond to and coordinate the resolution of emergency reports from Self-managed and GitLab.com customers
-[US Government Emergencies](/handbook/support/workflows/usgovernment_oncall) - which is similar to Customer Emergencies, but has different hours and a US Citizen requirement to participate in
-[Support Leader on the Hook (SLOTH)](/handbook/support/workflows/support-leader-on-the-hook) - in which Support Managers are an escalation point for issues raised by Support Engineers and GitLab team members and missed PagerDuty notifications
-[Customer Emergencies on-call (CEOC)](/handbook/support/workflows/customer_emergencies_workflows)- in which Support Engineers respond to and coordinate the resolution of emergency reports from Self-managed and GitLab.com customers.
-[US Government Emergencies](/handbook/support/workflows/usgovernment_oncall) - an on-call rotation for US Government support customers, with distinct coverage hours and eligibility requirements. The rotation is primarily staffed by the US Government Support team.
-[Support Leader on the Hook (SLOTH)](/handbook/support/workflows/support-leader-on-the-hook) - in which Support Managers are an escalation point for issues raised by Support Engineers and GitLab team members and missed PagerDuty notifications.
For customers that have [Priority Support](https://about.gitlab.com/support/#priority-support), the Support Engineering Team is on-call in these capacities and available to assist with emergencies. What constitutes an emergency is defined in our [definitions of support impact](https://about.gitlab.com/support/definitions/#definitions-of-support-impact).
