Community Building and Management SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as community-building/SKILL.md.

---
name: community-building
description: "Build and run brand communities on and around social: member-first purpose, comment communities, groups, Discord and Slack spaces, forums, live events and ambassador programmes, response standards for questions, messages and complaints, guidelines, programming, member roles, fair moderation, feedback loops and metrics such as member-to-member answers. Use whenever someone asks about community management, building a brand community, responding to comments and messages, Discord or Slack communities, Facebook or LinkedIn groups, moderation policies or turning followers into a community."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/social-media/community-building/
  category: marketing
  subcategory: social-media
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Community Building and Management

Audiences watch; communities talk to each other. A brand community (comments that become conversations, a group where customers help each other, a Discord or Slack space, live events, a forum) creates loyalty, word of mouth, product feedback and support at scale. Communities also take time, rules and care: unmoderated spaces turn toxic, ignored members leave and communities built only to sell feel hollow.

This skill builds and runs communities and community management on social: purpose, platform choice, engagement and response standards, programming, member roles, moderation, crisis handling, feedback loops and measurement.

## Operating principles
1. **Purpose for members first.** People join to learn, connect, get help or belong, not to be sold to.
2. **Respond like a person.** Fast, warm, specific replies build trust.
3. **Members talking to members.** The goal is connection between members, not just with the brand.
4. **Clear rules, fair moderation.** Safety and respect make participation possible.
5. **Close the loop.** Show members how their feedback changed things.

## Community types
| Type | Where | Good for |
|---|---|---|
| Comment communities | Brand and expert posts on social | Everyday engagement and relationships |
| Groups | Facebook Groups, LinkedIn Groups | Peer discussion around a topic |
| Chat communities | Discord, Slack, WhatsApp, Telegram | Real-time help, product communities, creators |
| Forums | Discourse, Circle, own website | Searchable knowledge, support |
| Live events | Lives, Spaces, webinars, meetups | Connection and trust |
| Ambassador programmes | Mixed | Advocates who lead and create |

## Engagement and response standards
| Situation | Standard |
|---|---|
| Questions in comments | Reply within a working day, ideally within hours |
| Direct messages | Reply within hours during business hours |
| Complaints | Acknowledge publicly, move details to private messages, follow up publicly when resolved |
| Praise | Thank and, where appropriate, ask permission to share |
| Misinformation | Correct politely with sources |
| Abuse or harassment | Hide or remove, block if needed, follow moderation policy |

## When to use, and when not to
Use it when building engagement on social, launching a customer or creator community, handling growing comment and message volume, improving support on social and building advocacy.

Don't use it for one-off campaigns without long-term commitment, or for support desk operations in depth (customer support teams and tools).

## Inputs to ask for, in one message
1. Goals for community (retention, support, advocacy, feedback, acquisition).
2. Current social engagement and volume of comments and messages.
3. Audience and what they would value from a community.
4. Team capacity for moderation and programming.
5. Existing groups, forums or chat spaces.
6. Escalation contacts (support, legal, communications).

## Workflow

### Step 1. Define purpose
What members get, in one sentence: "A place for finance managers to share month-end tips and get answers fast."

### Step 2. Choose the space
Start where members already are; build owned spaces when you need depth, search or control.

### Step 3. Write guidelines
What the community is for, expected behaviour, what's not allowed, how moderation works.

### Step 4. Set response standards
Times, tone, escalation paths and saved replies for common questions.

### Step 5. Seed and programme
Welcome posts, recurring threads (weekly wins, questions, show your setup), events and expert sessions.

### Step 6. Grow member roles
Recognise helpful members; invite moderators and ambassadors.

### Step 7. Moderate
Clear actions for spam, abuse and off-topic posts; consistent and fair.

### Step 8. Create feedback loops
Share themes with product and support; tell members what changed.

### Step 9. Measure
Active members, posts and replies, member-to-member answers, response times, sentiment, retention and business outcomes.

## Community guidelines template
```
What this community is for:
Who it's for:
Be helpful and respectful: ...
Not allowed: spam, self-promotion without permission, harassment, sharing private information
How we moderate: warnings, removals, bans
How to get help from the team:
Privacy and data notes:
```

## Saved reply examples
| Situation | Reply |
|---|---|
| How-to question | Great question, [name]. Here's how: [steps or link]. Let us know if that works. |
| Complaint | Sorry about this, [name]. We'd like to fix it; could you send us a message with your account email? |
| Feature request | Thanks for the idea. We've shared it with the product team and will update this thread if it's planned. |
| Praise | Thank you, that means a lot to the team. Mind if we share your comment? |
Personalise every saved reply; templates speed things up but should never read like a bot.

## Programming ideas
- Weekly wins thread where members share progress.
- Monthly expert Q&A or office hours.
- Member spotlight posts.
- Challenges with a start and end date.
- Early access groups for new features.
- Local meetups or virtual networking sessions.

## Escalation path
| Issue | Escalate to | Timing |
|---|---|---|
| Account or billing problems | Support | Same day |
| Security or data concerns | Security team | Immediately |
| Legal threats or regulatory issues | Legal | Immediately |
| Viral complaints or crisis signs | Communications lead | Immediately |
| Product bugs | Product team via support | Same day |

## Community metrics
| Metric | Why |
|---|---|
| Active members (weekly, monthly) | Health |
| Share of questions answered by members | Self-sustaining community |
| Median response time | Service quality |
| Sentiment trends | Mood and risks |
| Retention and expansion of members versus non-members | Business value |
| Feedback items shipped | Loop closed |

## Welcoming new members
Greet new members personally or with a pinned welcome post, point them to the guidelines and best resources, and ask them to introduce themselves with a simple prompt. The first week decides whether people return, so make sure their first question gets a quick, helpful answer.

Review guidelines and programming every quarter as the community grows.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Low activity | Seed questions, invite engaged customers personally, run regular events |
| Angry pile-ons | Respond calmly once, move to private channels, escalate if needed |
| Competitors posting | Apply rules consistently |
| Sensitive topics | Clear policy; trained moderators |
| Community grows fast | Recruit volunteer moderators; tooling for moderation |

## Handoffs to related skills
- Strategy: `social-media-strategy`
- Listening: `social-listening`
- Advocates and creators: `creator-employee-advocacy`
- Reporting: `social-media-reporting`
- Retention and lifecycle: the CRM and Lifecycle skills
- Referral programmes: the Growth Marketing `referral-programmes` skill

## Worked example
A project management software company had thousands of followers but comments went unanswered and customers asked support questions publicly with no reply. The team set a same-day response standard, used saved replies, and launched a customer community on a forum with weekly "show your workflow" threads, monthly expert sessions and recognition for helpful members. Within a year, a large share of community questions were answered by other members, support tickets for common issues fell, and community members renewed at higher rates than non-members.

## Output format
```
# Community plan: <brand>, <date>
## Purpose and goals
## Space and platform choice
## Guidelines
## Response standards and escalation
## Programming calendar
## Member roles
## Moderation policy
## Feedback loop
## Metrics
```

## Common mistakes
- Communities built only to promote.
- Slow or absent responses.
- No guidelines or inconsistent moderation.
- Brand doing all the talking.
- Feedback collected but never acted on.

## Questions to ask before you build
- What would members get that they can't get elsewhere?
- Who will respond and moderate every day?
- How will feedback reach product and support?

## Self-check before you answer
- Is the purpose member-first?
- Are response standards and escalation defined?
- Are guidelines and moderation clear?
- Is member-to-member activity measured?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/social-media/community-building/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.