Social Media
Community management and engagement
A community that gets replies stays. We manage the daily conversation around your brand: comments, messages and mentions on social, plus dedicated communities on Discord and Telegram where you run them.
Who it is for: Brands with an active audience nobody has time to answer, and projects running Discord or Telegram communities.
Everything in this service
- Comment and message replies within agreed response times
- Discord and Telegram server management and moderation
- Community guidelines and escalation rules
- Engagement prompts, events and conversation starters
- Monthly community health reporting
What to expect
- An audience that feels heard instead of ignored
- A safe, active community that grows by word of mouth
- Product and content insight straight from your audience
How community management actually works
Managing a feed is not the same as building a community
Social media management is about what you publish. Community management is about what happens between the people who show up. They overlap, but the goals are different and confusing them is why so many brands have large followings and no community at all.
A feed is a broadcast with a comment box attached. Success is measured in reach and engagement on your posts. A community is a place where members talk to each other, where conversations continue without you starting them, and where people arrive for reasons that have nothing to do with your latest announcement. The measure of a community is whether it would still be active if the brand went quiet for a fortnight. For most brand social accounts, the honest answer is no, and that is fine as long as nobody is claiming otherwise.
The practical difference is where the effort goes. Feed management puts most of its hours into producing content. Community management puts most of its hours into responding, connecting people, asking questions, surfacing member contributions and dealing with problems. A dedicated space such as a Discord or Telegram server, or a private group, changes the job again, because the space is always on and members expect someone to be present rather than someone to post.
- Feed: you talk, they respond. Community: they talk to each other
- Community effort goes into responding, not publishing
- Test question: would it stay active if you went quiet for two weeks
- A dedicated space is always on, and that changes the staffing
- Do not sell a community when what exists is an audience
Response standards, tone and the reply that helps
Response standards make the difference between a community that feels attended and one that feels abandoned. They should be written down, agreed and actually achievable, because a published standard that is regularly missed is worse than none.
The standards cover time and substance. Time means a target for first response by channel and by type, with a shorter target for anything that looks like a complaint or a safety issue, and a stated position on evenings and weekends rather than a pretence of constant coverage. Substance means a reply that moves things forward. A question gets an answer or a route to one. A thank you gets a sentence, not an emoji. An unanswerable question gets an honest we do not know yet, with a commitment to come back, which is far better received than silence.
Tone is where most guidance is too vague to use. Adjectives like friendly and professional do not help someone writing at speed. What helps is a set of worked examples: the same awkward message answered well and answered badly, side by side. Add a short list of approved answers for the questions that come up weekly, so the routine work is fast and consistent, and the time saved goes into the replies that need real thought. Keep the approved answers as starting points rather than scripts, because a copy-pasted reply is recognisable and it reads as a brush-off.
- Published response targets by channel and message type
- State your real coverage hours instead of implying constant presence
- Worked examples beat adjectives in a tone guide
- Approved answers for weekly questions, edited before sending, never pasted raw
- An honest we do not know yet beats silence
Escalation: what a community manager must never decide alone
A community manager is often the first person to see a serious problem, and giving them clear escalation rules protects both them and the business. Without rules, someone junior ends up improvising a response to a legal threat at nine on a Friday evening.
The rules should name categories rather than rely on judgement. Anything alleging harm from a product or service. Anything mentioning lawyers, regulators or the press. Anything involving a safety concern or a person in distress, which needs a defined humane response and a route to actual help rather than a support macro. Any claim about pricing, contracts or guarantees where the answer has to be exact. Anything touching a live incident or outage. Any accusation of discrimination or misconduct. And anything from a journalist, which goes to whoever handles press, always.
For each category, three things get written down in advance: who it goes to, how fast, and what the community manager says in the meantime. That holding line matters. It is usually a short acknowledgement that the message has been seen and is being looked at properly, which buys the time the business needs without going silent in public. The rest is simply a matter of the escalation contact being reachable, which is a management commitment rather than a process detail.
- Escalate by category, not by how bad it feels
- Legal, press, safety, regulatory and incident issues always escalate
- Name the person, the deadline and the holding line for each category
- Never let a community manager improvise on liability
- The escalation contact has to actually be reachable
Moderation that keeps a space worth being in
A community without moderation degrades quickly. The people who make a space valuable are the first to leave when it stops feeling safe, and they do not announce that they are going.
Moderation starts with published guidelines: what the space is for, what is not welcome, and what happens if someone crosses the line. Written before there is a problem, they turn an argument about fairness into a reference to a rule everyone agreed to. Enforcement then needs to be consistent and proportionate, usually a warning, then a temporary restriction, then removal, with the exception that scams, impersonation, harassment and doxxing get immediate removal with no warning at all.
Two specific threats deserve naming. Crypto and support scams target brand communities constantly, and the pattern is predictable: a fake admin account with your logo direct messaging members within seconds of them posting a question. Countermeasures are practical, including a pinned notice that staff never message first, verified role badges, restrictions on new accounts sending links, and fast removal. The second threat is the opposite mistake, which is over-moderation. Deleting honest criticism, or every mildly negative comment, teaches everyone else that the space is managed rather than real, and it is usually what turns a complaint into a wider story. Criticism stays. Abuse goes.
- Publish guidelines before you need to enforce them
- Warn, restrict, then remove, consistently and visibly
- Immediate removal for scams, impersonation, harassment and doxxing
- Pin a notice that staff never direct message first
- Leave honest criticism up and answer it in public
Turning members into advocates
The point of a community is not attention, it is that some members become people who recommend you without being asked. That happens through recognition and access, not through a points scheme.
The mechanics are ordinary. Notice the people who consistently help others and say so publicly. Ask them for their opinion on something real before it is decided, which is the strongest signal of respect you can send. Give them early sight of what is coming, or a genuine say in it. Feature their work, their questions and their answers in your own content, with credit and permission. Bring them into direct contact with the people who build the product, since a founder or engineer answering a question personally is worth more than any campaign.
What does not work is transactional. Discount codes for reviews, incentives for positive comments, or anything that pays for endorsement changes the nature of the relationship and, where reviews are involved, creates real legal exposure. We do not buy followers, engagement or reviews, and we do not run schemes that manufacture the appearance of enthusiasm. Advocacy that was purchased is visible to everyone except the brand that bought it. The slower route is the only one that produces people who will defend you when something goes wrong, which is the moment advocacy actually matters.
- Recognise helpful members publicly and by name, with permission
- Ask for opinions before decisions, not after
- Give early access and real input rather than badges
- Put members in direct contact with the people who build the thing
- Never pay for reviews, engagement or manufactured enthusiasm
Measuring community health
Member count tells you almost nothing. A community of two thousand where forty people talk is healthier than one of fifty thousand where nobody does. The measures that matter are about activity, distribution and feeling.
Five are worth tracking. Active participation, which is the share of members who posted or replied in the period rather than the share who merely logged in. Member to member conversation, which is the proportion of threads not started by staff, and the clearest single indicator of whether a community exists at all. Retention, meaning whether people who joined three months ago are still around. Response coverage, meaning the share of questions that got an answer and how fast. And sentiment, read by a human across a sample rather than trusted from a tool, because automated sentiment scoring misreads sarcasm, industry shorthand and complaints phrased politely.
The most useful output is not a chart. It is the recurring themes: the questions asked repeatedly, which usually point at a gap in your documentation or your product, the feature requests, the friction points and the reasons people give for leaving. Routed back to the content team, the product team and support, that is where community management stops being a cost line and starts being the cheapest research the business has.
- Share of members active, not total members
- Proportion of threads started by members rather than staff
- Cohort retention: are three month old joiners still here
- Percentage of questions answered, and how quickly
- Route recurring themes back into content, product and support
A clear path, step by step
- 01
Set the rules
We agree tone, response times, guidelines and what escalates to your team before we reply to anyone.
- 02
Engage daily
Comments, messages and community channels covered every working day, in your voice.
- 03
Moderate and protect
Spam, scams and bad actors removed quickly, so the space stays worth being in.
- 04
Report and improve
Monthly reporting on activity, sentiment and the questions your audience keeps asking.
Why choose us for this
Real people replying in your voice, with clear escalation rules
Experience running Discord and Telegram, not just comment sections
The questions we hear feed back into your content plan
Common questions
How do you reply in our brand voice?
We build a tone guide with approved answers for common questions, and your team reviews early replies closely. Anything sensitive or unusual escalates to you before we respond.
Can you run our Discord or Telegram community?
Yes. Setup, channel structure, moderation, bots and daily engagement are all in scope, whether we build the server or take over an existing one.
Explore related work
Want this for your business?
Book a free visibility call and I will tell you honestly whether I can help.
How this is delivered
One person leads every project. Where a job genuinely needs a specialist, I bring in people I have worked with before and manage them, so you get one point of contact and one invoice rather than three suppliers blaming each other.
- You talk to the person responsible for the work, not an account manager
- Specialists are briefed and managed by me, and their work is checked before it reaches you
- One contract, one invoice, one place to chase