Skip to content

Commit 3742d06

Browse files
authored
Merge pull request #5655 from alphagov/ChrisBAshton-patch-1
Update escalation process for Technical On-Call support
2 parents 47e29a7 + 8b12a8e commit 3742d06

1 file changed

Lines changed: 12 additions & 1 deletion

File tree

source/manual/ask-for-help.html.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,18 @@ There are channels for each area of GOV.UK:
2424
- `#govuk-publishing-service-support`
2525
- `#govuk-web-support`
2626

27-
In addition, there's a `#govuk-technical-on-call` channel that can be used to communicate with the on-call engineers in a public forum. However, bear in mind that Slack does not page their phones, so whereas in-hours you may be able to `@` the on-call engineer, out-of-hours you'll need to contact via PagerDuty.
27+
## Escalate to Technical On-Call
28+
29+
There's a `#govuk-technical-on-call` channel that can be used to communicate with the on-call engineers in a public forum, in-hours only.
30+
31+
Out of hours, or if you need to escalate urgently in-hours, create an incident in PagerDuty:
32+
33+
- Impacted Service: "GOV.UK"
34+
- Urgency" "High"
35+
- Assignee: “GOV.UK Regular Coverage”)
36+
- Fill out the incident detail and create the incident
37+
38+
This causes the engineer(s) to be paged by PagerDuty.
2839

2940
## Ask the developer communities
3041

0 commit comments

Comments
 (0)