Only the infrastructure team should be posting updates on @GitLabStatus. There is a defined process for this describing who should do this, how and what channels should be alerted.
When a tweet mentions more than one handle described above, always reply from the main @GitLab handle, unless it's about GitLab availability status
If a wrong handle is used in a response, take note and respond from the correct one in the follow-up (if there is one)
All Twitter responses should be sent from Zendesk.
Reply to almost all tweets, following the social media guidelines, regardless of whether the tweet is of a technical nature or not.
Follow up with the support team if the issue is too complex to handle.
When resolving Twitter tickets in Zendesk you should:
Use Play mode in the Twitter view. The default Twitter view will sort tickets by created date (ascending).
Not skip any tickets
Assign the ticket to yourself or ask in the appropriate chat channel if you don't know how to answer it
Not cross assign tickets
Tweets use short links which require you to visit that link to make sure you understand the context.
Clarify if the request refers to GitLab.com or an externally hosted GitLab instance as we can only handle requests for GitLab.com.
Usage of Likes
Use "Likes" on Twitter for promoting positive feedback about our product, since we direct users there when we want to show that people really love the product. Avoid using it for anything else.
Advocates shouldn't retweet anything from the official GitLab Twitter accounts. If you see something that should be retweeted, paste the tweet in the #twitter Slack channel, or mention Emily von Hoffmann - she has these permissions.
We have direct messages disabled in our Twitter accounts, but they can be used if we first send a direct message to a user. This should only be used when the user needs to communicate with us privately (e.g. to give a mailing address).
Tweets that mention @GitLab, or @GitLabStatus will create a ticket in Zendesk, and show up in the "Twitter" view.
If a tweet is responded to from TweetDeck, this risks duplicate responses. Responding from Zendesk also enables us to track our response times vs. our internal SLA.