diff --git a/docs/sources/escalation-chains-and-routes/_index.md b/docs/sources/escalation-chains-and-routes/_index.md
index 2c9a255f..036ea6d0 100644
--- a/docs/sources/escalation-chains-and-routes/_index.md
+++ b/docs/sources/escalation-chains-and-routes/_index.md
@@ -56,9 +56,8 @@ need a larger time interval, use multiple wait steps in a row.
 from an on-call schedule.
 * `Resolve incident automatically` - resolve the alert group right now with status
 `Resolved automatically`.
-* `Notify whole slack channel` - send a notification to a slack channel (not recommended
-to use as it will spam the channel).
-* `Notify Slack User Group` - send a notification to a slack user group.
+* `Notify whole slack channel` - send a notification to the users in the slack channel.
+* `Notify Slack User Group` - send a notification to each member of a slack user group.
 * `Trigger outgoing webhook` - trigger an [outgoing webhook][outgoing-webhooks].
 * `Notify users one by one (round robin)` - each notification will be sent to a group of
 users one by one, in sequential order in [round robin fashion](https://en.wikipedia.org/wiki/Round-robin_item_allocation).
@@ -69,6 +68,14 @@ 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
+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,
+users **won't be notified** in the alert group Slack **thread** (this is how the feature is currently implemented)
+but instead notify them using their **other defined** options in
+their [respective policies]([url](https://grafana.com/docs/oncall/latest/notify/#configure-user-notification-policies)).
+
 ### Notification types
 
 Each escalation step that notifies a user, does so by triggering their personal notification steps. These are configured in the Grafana
diff --git a/helm/oncall/Chart.yaml b/helm/oncall/Chart.yaml
index ed4d6ec6..12eb4b2d 100644
--- a/helm/oncall/Chart.yaml
+++ b/helm/oncall/Chart.yaml
@@ -2,8 +2,8 @@ apiVersion: v2
 name: oncall
 description: Developer-friendly incident response with brilliant Slack integration
 type: application
-version: 1.3.50
-appVersion: v1.3.50
+version: 1.3.55
+appVersion: v1.3.55
 dependencies:
   - name: cert-manager
     version: v1.8.0