3. The SSOT for who is the current EOC is the [GitLab.com Production EOC](https://app.incident.io/gitlab/on-call/schedules/01K5YWAGZ7YCQGAG7ATQ9XQWHW) schedule in incident.io.
1. SREs are responsible for arranging coverage if they will be unavailable for a scheduled shift. To make a request, send a message indicating the days and times for which coverage is requested to the `#eoc-general` Slack channel. Alternatively, use incident.io "request cover" feature. If you are unable to find coverage reach out to the [EOC coordinator](/handbook/engineering/infrastructure/incident-management/#engineer-on-call-coordinator) for assistance.
4. Alerts that are routed to incident.io require acknowledgment within 15 minutes, otherwise they will be escalated to the oncall Incident Manager.
1. Alerts that page incident.io will automatically create a triage incident in [`#incidents-dotcom-triage`](https://gitlab.slack.com/archives/alerts).
1. Alerts that create an escalation in incident.io will automatically create a triage incident in [`#incidents-dotcom-triage`](https://gitlab.slack.com/archives/alerts).
1. If it is determined to be a true incident, the triage incident should be accepted by joining the channel and choosing "Accept it".
1. If there are multiple pages/triage incidents created for the same incident, merge them into the primary incident. However, resolving the incident takes precedence. It is fine if a related triage incident auto-closes instead of getting merged while you're working an incident.
1. The triage incident will automatically declined if no action is taken and the generating alert clears.
Sarah Walker <swalker@gitlab.com>