diff --git a/docs/sources/configure/escalation-chains-and-routes/index.md b/docs/sources/configure/escalation-chains-and-routes/index.md
index 8db2359fa8..1b497b3a04 100644
--- a/docs/sources/configure/escalation-chains-and-routes/index.md
+++ b/docs/sources/configure/escalation-chains-and-routes/index.md
@@ -83,7 +83,7 @@ from an on-call schedule.
 * `Notify all users from a team` - send a notification to all users in a team.
 * `Resolve incident automatically` - resolve the alert group right now with status
 `Resolved automatically`.
-* `Notify whole slack channel` - send a notification to the users in the slack channel. These users will be notified
+* `Escalate to all Slack channel members` - send a notification to the users in the slack channel. These users will be notified
 via the method configured in their user profile.
 * `Notify Slack User Group` - send a notification to each member of a slack user group. These users will be notified
 via the method configured in their user profile.
@@ -97,7 +97,7 @@ Useful when you want to get escalation only during working hours
 passes some threshold
 * `Repeat escalation from beginning (5 times max)` - loop the escalation chain
 
-> **Note:** Both "**Notify whole Slack channel**" and "**Notify Slack User Group**" will filter OnCall registered users
+> **Note:** Both "**Escalate to all Slack channel members**" and "**Notify Slack User Group**" will filter OnCall registered users
 matching the users in the Slack channel or Slack User Group with their profiles linked to their Slack accounts (ie. users
 should have linked their Slack and OnCall users). In both cases, the filtered users satisfying the criteria above are
 notified following their respective notification policies. However, to avoid **spamming** the Slack channel/thread,
diff --git a/docs/sources/manage/notify/slack/index.md b/docs/sources/manage/notify/slack/index.md
index 4213582d35..1f6285d3e5 100644
--- a/docs/sources/manage/notify/slack/index.md
+++ b/docs/sources/manage/notify/slack/index.md
@@ -135,7 +135,7 @@ and users:
 Once your Slack integration is configured you can configure Escalation Chains to notify via Slack messages for alerts
 in Grafana OnCall.
 
-There are two Slack notification options that you can configure into escalation chains, notify whole Slack channel and
+There are two Slack notification options that you can configure into escalation chains, escalate to all Slack channel members and
 notify Slack user group:
 
 1. In Grafana OnCall, navigate to the **Escalation Chains** tab then select an existing escalation chain or
diff --git a/engine/apps/alerts/models/escalation_policy.py b/engine/apps/alerts/models/escalation_policy.py
index e5544b544c..0c10e31f1c 100644
--- a/engine/apps/alerts/models/escalation_policy.py
+++ b/engine/apps/alerts/models/escalation_policy.py
@@ -128,7 +128,10 @@ class EscalationPolicy(OrderedModel):
         ),
         STEP_FINAL_RESOLVE: ("Resolve alert group automatically", "Resolve alert group automatically"),
         # Slack
-        STEP_FINAL_NOTIFYALL: ("Notify whole Slack channel", "Notify whole Slack channel"),
+        STEP_FINAL_NOTIFYALL: (
+            "Escalate to all Slack channel members (use with caution)",
+            "Escalate to all Slack channel members (use with caution)",
+        ),
         STEP_NOTIFY_GROUP: (
             "Start {{importance}} notification for everyone from Slack User Group {{slack_user_group}}",
             "Notify Slack User Group",