diff --git a/source/handbook/marketing/developer-relations/developer-advocacy/index.html.md b/source/handbook/marketing/developer-relations/developer-advocacy/index.html.md
index 9f1219ac51b84e22a82c9d53c70b94f6c48c6536..f5ed09ac301beaaadd467f1dfeb32a575aae78ab 100644
--- a/source/handbook/marketing/developer-relations/developer-advocacy/index.html.md
+++ b/source/handbook/marketing/developer-relations/developer-advocacy/index.html.md
@@ -270,6 +270,10 @@ About using the tools
 
 -   Use Tweetdeck to find GitLab mentions without the # or @.
 
+Ignore tweets that are negative about competitors
+
+-   From time-to-time, we also receive tweets that mention competitors in a negative way or about negative events related to them. Don't acknowledge these tweets, since that would violate our "Be friendly" policy.
+
 Use English
 
 - [GitLab communicates in English](https://about.gitlab.com/handbook/#internal-communication) so please tweet in English.
diff --git a/source/handbook/support/index.html.md b/source/handbook/support/index.html.md
index 7a827a2b54fcb8347488ec1d3f6677a15486d10b..0b7fff4a1cb7b8e783977942b8eb26651b8d9f8b 100644
--- a/source/handbook/support/index.html.md
+++ b/source/handbook/support/index.html.md
@@ -308,7 +308,17 @@ from ZenDesk also enables us to track our response times vs. our internal [SLA](
 
 Our Developer Advocates also have access to tweets through ZenDesk, and often
 participate in responding to questions. The support team does not retweet or favorite
-any tweets; that is handled by the marketing team.
+any tweets; that is handled by the marketing team. Our support team _does_ reply
+to almost all tweets, following the [social media guidelines](https://about.gitlab.com/handbook/social-media-guidelines/), regardless of whether
+the tweet is of a technical nature or not. The marketing team's decision to favorite
+and/or retweet is independent of the reply provided by the support team; so a tweet
+may be responded to from ZenDesk, and separately favorited from TweetDeck, as an
+example.
+ 
+From time-to-time, we also receive tweets that mention competitors or negative events 
+related to them. In principle, we don't acknowledge these tweets as also described in
+the [developer advocacy](https://about.gitlab.com/handbook/marketing/developer-relations/developer-advocacy/#representing-gitlab-on-twitter) 
+section.
 
 The @GitLabStatus account should only be used to give updates on the availability
 of GitLab.com and to follow up on users reporting that GitLab.com is unavailable.