|TWITTER HANDLE||RESPOND FROM||GUIDELINES|
|@GitLabStatus||Zendesk||Post service updates|
|@GitLab||Zendesk||Respond to mentions and questions|
Community Operations uses Zendesk via Zapier to pull in all mentions of GitLab on Twitter. When resolving Twitter tickets in Zendesk you should:
Check if we're experiencing any issues with our system on GitLab System Status page or if there were any official updates on our Twitter GitLab.com Status profile. If you find anything that might be related, please follow up with the user forwarding that link and asking if they are still experiencing issues.
Often, users will tweet their support related questions to the main @gitlab account. Solving support related questions via twitter is not the preferred method, as the character limit is difficult to work with, and resolutions could be lost for future use.
Instead, please direct users to post their question on the GitLab Forum.
Try to find a related topic in the forum (preferably one that is solved!) and share a direct link. If no similar topic exists, share the link to the most appropriate forum category.
Consider using language like this in your tweet to best encourage forum use:
Posting in the forum allows the GitLab team and the wider community to help find solutions for your needs, create issues for long-term solutions, and update our documentation.
In order to troubleshoot your issue, please post your question in our forum at https://forum.gitlab.com! This way you'll have the whole power of the community to help.
It's likely these community experts will be able to help: (link to forum topic) since they have worked through something similar before. Post your question and we'll check in on it!
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.
Tweetdeck can be used to delete tweets if something is sent accidentally from Zendesk. If you send an accidental tweet from the @GitLab handle, please notify the Social Media team asap via the #social_media_action slack channel.