diff --git a/docs/Contributing/Releasing-Fleet.md b/docs/Contributing/Releasing-Fleet.md
index 7889034a11..3dc971e5ac 100644
--- a/docs/Contributing/Releasing-Fleet.md
+++ b/docs/Contributing/Releasing-Fleet.md
@@ -93,7 +93,7 @@ Note: Please prefix versions with `fleet-v` (e.g., `fleet-v4.0.0`) in git tags,
 
 5. Deploy the new version to Fleet's internal dogfood instance: https://fleetdm.com/handbook/engineering#deploying-to-dogfood.
 
-6. In the #g-infrastructure Slack channel, notify the @sandbox-oncall of the release. This way, the @sandbox-oncall individual can deploy the new version.
+6. In the #g-customer-experience Slack channel, notify the @infrastructure-oncall of the release. This way, the @infrastructure-oncall individual can deploy the new version.
 
 7. Announce the release in the #fleet channel of [osquery
    Slack](https://fleetdm.com/slack) and
diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md
index e6b800956f..377dc3bdb1 100644
--- a/handbook/engineering/README.md
+++ b/handbook/engineering/README.md
@@ -889,7 +889,7 @@ Escalations (in order):
 
 - Zach Wasserman
 
-The first responder oncall will take ownership of the @sandbox-oncall alias in Slack for ease first thing Monday morning.
+The first responder oncall will take ownership of the @infrastructure-oncall alias in Slack for ease first thing Monday morning.
 
 Expected response times: during business hours, 1 hour. Outside of business hours 4 hours.
 
@@ -899,7 +899,7 @@ We should collect both the email for the customer and information for the error.
 
 Escalation of issues will be done by hand for the moment.
 
-All infrastructure alarms will go to #g-infrastructure.
+All infrastructure alarms will go to #help-p1.
 
 The information needed to evaluate and potentially fix any issues is documented in the [runbook](https://github.com/fleetdm/fleet/blob/main/infrastructure/sandbox/readme.md).