@@ -200,12 +200,19 @@ When raising a GitLab Dedicated incident, you must complete all three steps:
1.[Declare a Dedicated incident through Slack](../../engineering/infrastructure-platforms/incident-management/_index.md#reporting-an-incident).
- Provide the `internal_reference` and `tenant_id` (also known as identifier) of the customer by referring to [Dedicated Switchboard](dedicated_switchboard.md#accessing-switchboard).
1. In the incident channel that is automatically created on Slack, provide a summary of the current state.
1. Escalate the incident to the GitLab Dedicated Engineer On-Call (SRE) to page them. Dedicated incidents declared do not automatically page EOCs, unlike for GitLab.com. Do so by selecting **dedicated EOC** as the **On-Call Teams** when you:
- Click on the button **📟 Escalate to someone** in the Slack channel, or
- Type `/inc escalate` into the Slack channel.
1. Dedicated incidents declared do not automatically page EOCs, unlike for GitLab.com. Proceed to [escalate the incident to the GitLab Dedicated Engineer On-Call](#escalate-to-gitlab-dedicated-engineer-on-call).
You are now done raising the incident!
#### Escalate to GitLab Dedicated Engineer On-Call
Sometimes, you may need to escalate to the GitLab Dedicated Engineer On-Call (GDEOC), which is a GitLab Dedicated SRE, to get their immediate attention on an urgent Dedicated issue or an incident.
Escalate to the GDEOC by paging them. Select **dedicated EOC** as the **On-Call Teams** when you:
- Click on the button **📟 Escalate to someone** in the Slack channel, or
- Type `/inc escalate` into the Slack channel.
#### Engaging the GitLab Dedicated CMOC
If the nature of the emergency reaches the point where we only need to provide async status updates
