From 3f201f799c1ab9972b0c87e4629e9c0f3822e451 Mon Sep 17 00:00:00 2001
From: Charlie Chance <100798688+CharlotteChance@users.noreply.github.com>
Date: Mon, 29 Aug 2022 14:17:40 -0600
Subject: [PATCH] Handbook: Slack communications best practices (#7434)

---
 handbook/people/README.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/handbook/people/README.md b/handbook/people/README.md
index 74fc6d82dc..4a3d54cb10 100644
--- a/handbook/people/README.md
+++ b/handbook/people/README.md
@@ -200,6 +200,11 @@ We use these prefixes to organize the Fleet Slack:
  * ***help-***: for asking for help on specific topics.
  * ***at*** or ***fleet-at***: for customer channels.
 
+### Slack communications and best practices
+
+In consideration of our team, Fleet avoids using global tags in channels (i.e. @here, @channel, etc). 
+      1. 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. 
+      2. Why does this matter? Great question! The Fleet [culture](https://fleetdm.com/handbook/company#culture) is pretty simple: think of others, and remember the company [Values](https://fleetdm.com/handbook/company#values).
 
 ## Performance feedback
 At Fleet, performance feedback is a continuous process. We give feedback (particularly negative) as soon as possible. Most feedback will happen during 1:1 meetings, if not sooner.
@@ -547,4 +552,4 @@ Please see [Digital Experience > Slack channels](https://fleetdm.com/handbook/di
 
 
 <meta name="maintainedBy" value="charlottechance">
-<meta name="title" value="🧑‍🚀 People">
\ No newline at end of file
+<meta name="title" value="🧑‍🚀 People">