username-removed-423915
--- a/howto/tweeting-guidelines.md
+++ b/howto/tweeting-guidelines.md
 Closing tweets should be as detailed as possible, for example: 'we have a failing database migration of a column name'
 instead of 'there is a problem with the database'

+[Cog]: https://gitlab.com/gitlab-com/runbooks/blob/master/howto/manage-cog.md
+
+## How to tweet
+
+The one who commands `@marvin` on Slack should get a Cog user. Then we send
+a message begins with `!tweet` on **#production** channel in order to tell
+`@marvin` to tweet, like:
+
+    !tweet "We will be deploying GitLab EE 9.1.2 shortly, no downtime is expected"
+
+We could also use `!broadcast` to broadcast on GitLab.com, like:
+
+    !broadcast "We will be deploying GitLab EE 9.1.2 shortly, no downtime is expected"