In order to communicate and respond to our community effectively, management of responses and conversations is a shared effort between Social Media, Community Operations, Developer Evangelists, various experts, and our Support Teams. The two key teams in our processes are the Social and Community Operations teams. Both act as either the final point of contact or the responsible party to forward messages to the other teams.
non-executive, non-evangelist, non-brand personality team members
GitLab brand channels provide additional impressions/view, comments, and clicks when engaging with team member social posts. It will be more common for the brand social profile to like or comment on a team member post, because this does not interfere with the editorial calendar, while still provding an amplification. We also leave a small amount of space to retweet/quote retweet users (including Team Members) on Twitter, as this is appropriate for the channel and still aids in our editorial efforts. Shares on Facebook or LinkedIn are highly unlikely, due to the low volume of appropriate content available to be calendared on these channels.
Team member social posts that would considered for likes or comments from the brand channel include:
Team member social posts that would be considered for retweeting or sharing include:
It is important to note that team member social posts are considered the same pool of content as the greater community. Who's post gets shared is a subjective response from the social team and does not have a specific or repeatable formula, due to the nature of every day social media activity.
While our team will see every post where the brand handle is tagged, the volume creates a delay. Consider sharing the link to your post in the #social_media_action channel for the brand team to engage.
Also, consider sharing the link to your post in #content_updates or #social_media_posts for additional awareness, increasing the possibility for other team members to engage with your post.
This escalation workflow dictates predetermined actions and DRIs for Twitter, Facebook, LinkedIn, and Instagram
|If…||Then…||Who owns the response to the community member?|
|A user tags GitLab in a question or comment that does not require a SME / seems generic or benign||The social team decides whether or not to engage directly on the social channel. This work will usually be done in Sprout, but can be done natively on-channel.||The social team|
|A user doesn't tag GitLab in a question or comment but mentions "GitLab" in plain text||The social team does not engage because we have not been invited to respond with an @ mention||No one - we weren't invited to respond with an @ mention|
|A user tags GitLab in a question or comment that does require a product-related SME||Community Operations responds with directions to the forum||Community Operations|
|A user tags GitLab in a question or comment that does require a non-product-related SME (think employer brand, remote, etc.)||The social team decides whether or not to engage directly on the social channel and works with the non-product-related SME to craft a response. This work would usually be done in Slack||A response may come from brand channel (the social team) or from an SME in the space (e.g., we tag Darren in response to a question), but the social team owns the responsibility to find a response|
|A user identifies themselves as a free and open source user and tags GitLab in a question or comment that would require assistance||Community Operations responds with directions to the forum||Community Operations|
|A user identifies themselves as a paying customer of GitLab and tags GitLab in a question or comment that would require support||Community Operations forwards to support||Support Team|
|A user doesn't identify themselves at all and tags GitLab in a question or comment that would require assistance||Community Operations responds with directions to the forum||Community Operations|
|We recieve a message that breaks our code of conduct or that of the social channel||The reciever reviews the message reports the message via the native tools to the specific social channel as spam, a troll, etc.||Whoever the reciever is|
This chart defines who owns what channels, sources, and how often they are reviewed.
|Channel||Source||Tool||Who Reviews?||Review Cycles||Justification||Note|
|Twitter @GitLab||Mentions, DMs, Retweets, Quote Tweets, New Followers||Sprout Social, Tweetdeck, Twitter App, Zapier||Social Team, Community Operations||More than 3 times a day during business; periodically over the weekend||Twitter is for live and recent changes/news. Requires more engagement and community management than other channels.||-|
|Wall Posts, Comments, Ad Comments, Private Messages||Sprout Social, Facebook App, Zapier||Social Team, Community Operations||1-2 times during business; no weekend requirements||Facebook does not receive many comments and users shouldn't expect immediate responses.||Reviewing items in Sprout doesn't remove the native Facebook notifications, so we'll need one SSOT (likely Sprout)|
|Comments||Sprout Social, LinkedIn App||Social Team||1-2 times during business; no weekend requirements||While LinkedIn works 7 days a week, our engagement isn't necessary. Most comments are not questions, and users don't have an expectation on a response time for LinkedIn.||responding directly to a user comment doesn't allow for tagging the user in Sprout (could be a LinkedIn API limitation)|
|Shares, Mentions||LinkedIn App (not available through a 3rd Party tool)||Social Team||2-3 times a week||This activity helps with reviewing how GitLab is percieved on the channel, and engagement aids in impressions. However, this is not a high priority activity.||Requires a manual check several times a week for engagement and awareness factors|
|Comments, Ad Comments, Mentions, and Media Tags||Sprout Social, Instagram App||Social Team||1-2 times during business; no weekend requirements||Instagram does not receive many comments and users shouldn't expect immediate responses.||-|
|DMs||Instagram App||Social Team||1-2 times a day||While we don't receive many messages, what we do get is mentions of being in a user story. With only a 24 hour lifecyle, if we want to engage with users who tag us, we'll need to look at least once a day.||Not available through a 3rd party tool|
|HackerNews||Mentions||Zapier + Slack||Community Operations, Developer Evangelism, Team Member Experts||via notification in Slack||no cycle is necessary because notifications happen live||notifications in #hn-mentions channel, requires a personal account to respond|
|Mentions||Zapier + ZenDesk||Community Operations, Developer Evangelism, Team Member Experts||via notification in Slack||no cycle is necessary because notifications happen live||requires a personal account to respond|
|StackOverflow||Mentions||Zapier + ZenDesk||Community Operations, Developer Evangelism, Team Member Experts||via notification in Slack||no cycle is necessary because notifications happen live||requires a personal account to respond|
|GitLab Forum||New User Posts||Zapier + Slack||Community Operations, Developer Evangelism, Team Member Experts||via notification in Slack||no cycle is necessary because notifications happen live||notifications to the #gitlab-forum channel|
|YouTube (both channels)||Comments on our videos||YouTube App||We need to identify who owns these channels, whether or not we want comments on, and how often they need to be checked. This has been a crack in our workflows for many teams.||-||-||there is no community management function available in 3rd parties|
It is worth calling out platform specifics for Instagram in our handbook because the channel does not operate like any other Brand Social Channel. Since Instagram is a visual first platform, we take an editorial approach that prioritizes brand awareness, and 1:1 conversation. This is GitLab's opportunity to share real team member stories, and express our values.
One of the challenges we face as an all-remote organization on Instagram, is that we typically have lower quality images. We have to depend on team members and their cell phone photos. So our approach to each post is to be authentic. Don't filter the image. These are photos of real offices or experiences, and portray actual team members.