diff --git a/handbook/company/communications.md b/handbook/company/communications.md
index fda18e407..43d1bd61d 100644
--- a/handbook/company/communications.md
+++ b/handbook/company/communications.md
@@ -175,6 +175,7 @@ We use these prefixes to organize the Fleet Slack:
  * ***2023-***: for temporary channels _(Note: specify the relevant year in four digits, like "YYYY-`)_
 
 ### Slack communications and best practices
+- We use [channels over DMs](https://fleetdm.com/handbook/company/why-this-way#why-group-slack-channels).
 - We use threads in Slack as much as possible. Threads help limit noise for other people following the channel and reduce notification overload.
 - We configure our [working hours in Slack](https://slack.com/help/articles/360025054173-Set-up-Slack-for-work-hours-) to make sure everyone knows when they can get in touch with others.
 - In consideration of our team, Fleet avoids using global tags in channels (i.e. @here, @channel, etc.) (What about polls? Good question, Fleeties are asked to post their poll in the channel and @mention the teammates they would like to hear from.)