Peer support works because the person replying has been there too. They are not a clinician and they are not a crisis service, and the strength of the format depends on everyone, including you, being clear about that. A mental health peer community is a place to say “me too” at two in the morning, and to find out that what feels unspeakable is something other people have also lived with.
This guide covers the site side of running one on WordPress: who gets in, how spaces are shaped, what moderators can do, and how to point people to real help. It is not clinical guidance. Nothing on your site should tell a member what to take, stop or do about their own health, and members should be told to consult a qualified professional about their own situation. None of the plugins below provides compliance with any health-privacy rule, and none of them can monitor a person’s safety.
The tools are BuddyNext for the community and Jetonomy for slower, threaded discussion. Free and Pro scope is labelled where it matters.
Write the promise before you build anything
Start with a plain statement of what the community is and is not. Everything else, including settings, follows from it.
| This community is | This community is not |
|---|---|
| A place for people to share their own experience | A substitute for care from a qualified professional |
| Run by trained or briefed volunteers and staff | A crisis line or an emergency service |
| Moderated, with written rules | Monitored around the clock, unless you truly staff it |
| Private to members who ask to join | A place to diagnose or advise other members |
Be honest about the second column. If nobody reads the site at night, say so in the places people will see it. A member who writes something alarming while nobody is watching needs to have already been told where to go.
If your organisation is led by clinicians who want to publish education alongside a community, the setup is different. See patient education communities, which separates expert content from peer talk with different tools.
A front door, not an open window
For most peer support communities, public sign-up with an open feed is the wrong default. Think about the entrance in three layers.
Registration
BuddyNext supports four registration modes: open, invite only, admin approval and closed. Admin approval holds each new account until someone on your team approves it, and the member cannot sign in until then. That slows down raids and gives you a moment to read what a new person wrote in the form. Email verification is also available. Both are in the free plugin, as is two-factor authentication for members who want it.
Ask for the minimum. A display name and an email address are enough. Do not add profile fields for diagnoses, medication or treatment, and let people pick a name that is not their legal name.
The space itself
BuddyNext spaces are Open, Private or Secret. For support, the usual choice is Private. The space is listed, so people can find it, but a join click becomes a request that an owner or moderator approves, and the feed is locked until they do. A visitor can still read the About tab, which holds the description, the house rules and the list of moderators. That is where your promise table and your signposting notice belong, because people read them before deciding whether to ask in.
Secret spaces do not appear in any list and are reachable by invitation only. They suit a small group run alongside a professional service, where you already know who belongs.
If you also use Jetonomy for discussion boards, its private spaces work similarly and ask for an optional message with the join request.
The first hour
BuddyNext’s welcome wizard walks new members through a profile, space choices and notification preferences. Use it. A person who lands in an empty feed in a bad moment is likely to leave. Give them one obvious first stop, such as an Introductions space, with a short welcome message from a named moderator.
Spaces that match what people need
Most support sites do well with few spaces. Each should have a purpose that people can describe in a sentence.
| Space | Visibility | Who can post | Purpose |
|---|---|---|---|
| Introductions | Private, request to join | Members | Say hello, find out how things work |
| Check-ins | Private | Members | Short updates on how the week is going |
| Good days | Private | Members | Things that went well, kept apart from heavy posts |
| Longer discussions | Jetonomy private space | Members | Threaded conversation that is worth coming back to |
| Resources | Open or private | Moderators only | Links and notices curated by the team |
The Resources space shows a useful setting. In BuddyNext, set Who can post to moderators and owner only and the space becomes a curated channel where members read and react but only the team posts. Jetonomy offers the same through Who can post and Who can reply.
Keep voting off where you can. In a Jetonomy forum space, voting can be switched off per space, which removes the vote buttons and scores. Q&A and ideas spaces always keep voting, so use the forum type for support threads. Whether a reply gets more upvotes than another should not matter to someone describing a bad week.
Moderators are the product
On a support site, the quality of moderation is the product. Plan for it as you would a staff rota.
Roles
BuddyNext has three community roles: member, moderator and admin, and every space has its own owner, moderator and member roles on top. A moderator can review the report queue, remove posts and comments, issue warnings and strikes, and suspend a member for a set number of days. Only an admin can suspend with no end date and decide appeals. Space moderators handle join requests and bans for their own space.
Appoint a few moderators rather than one, so nobody carries the whole queue, and agree who is responsible at what times. Be realistic about what volunteers can carry. Burnout is a risk in this kind of work, so arrange a way for moderators to step back without guilt and a named person they can talk to. That arrangement belongs to your organisation, and a qualified person should help you design it.
Tools in the free BuddyNext plugin
- Reports. Members can report posts, comments, direct messages, media and profiles. Reports on the same item merge into one row, with Dismiss, Remove, Resolve and Escalate actions.
- Content safeguards. Banned words and phrases (site-wide, or set per space), blocked link domains, a post rate limit and a new-member gate that publishes a first post but flags it for review.
- Content warnings. A moderator can blur a post behind a label until the reader chooses to reveal it. The available labels are NSFW, Spoilers, Violence and Strong language. They are a tool for you to use when a post is allowed but may not suit every reader in a feed, and they are not a clinical classification.
- A graduated ladder. Warn, then strike, then suspend, with an appeals route so a suspended member can ask for a second look. Predictable consequences are kinder to people who made a mistake in a hard moment.
- Space bans. A ban affects one space and leaves the rest of the account alone.
Tools in Jetonomy
Jetonomy has its own moderation queue, covering flags, pending posts and replies, and held content, plus a Require Post Approval setting per space. New accounts start at a trust level with daily caps on topics, replies and votes, which lifts as members take part. Pro adds advanced auto-moderation.
For a longer treatment of moderation as a practice, see the community moderation guide, and for the wording of rules, the community guidelines template.
Keep a record
BuddyNext records moderation actions in a moderation log, with the action, the moderator, the target and any note. Use it. When a member disputes a decision, or a new moderator takes over a space, a written history is what makes the response consistent. Add your own handover notes for anything the log cannot hold, such as the reasoning behind a house rule.
Members also control their own data. BuddyNext lets a member download a copy of their data or delete their account from their settings, and the owner can switch those controls on or off. Leave them on for a support community: a person who wants to leave should be able to leave cleanly. This is a control for members and not a statement that your site meets any legal standard.
Crisis signposting as standing practice
Every peer support site needs a plan for the post that says someone may be in danger. The plan should be written before launch, with input from a qualified professional, and it should be visible to members from the start.
The general practice is simple: direct people to local emergency services and crisis lines. Your notice should do three things. It should state that the community is not an emergency or crisis service. It should tell people to contact local emergency services if they or someone else is in immediate danger. And it should point to crisis lines that operate where your members live.
We do not list numbers here. Crisis lines differ by country and change, and a wrong or outdated number is worse than none. Look up the services for each region you serve, confirm them against the official source, and give someone the job of re-checking them on a schedule.
Where the notice lives
Put it in more than one place, because any single place can be missed.
- The About tab of every space, where it is read before joining.
- A footer or sidebar element on every community page.
- The pinned or announcement position in each space. BuddyNext announcements pin to the top of the feed, but they can be dismissed and can be set to expire, so they are a reminder and not the only copy.
- The welcome message sent to every new member.
- A short template reply that moderators can paste under any alarming post.
The moderator procedure
Write down, for moderators, what to do when a post raises concern. This should be agreed with a qualified professional, and it will usually include replying with the signposting message, telling a named lead, and recording what happened. Moderators are not counsellors and should not be asked to act as one. Do not leave the response to individual judgment in the moment.
One-to-one messages: decide on purpose
BuddyNext direct messages run through WPMediaVerse, which must be installed with Messages on. A member can control who is allowed to message them, including no one. Reported messages are handled so that a moderator can act without reading the private exchange.
That last point is the catch: private messages are private, which means they sit outside your visible moderation. On a support site, consider leaving direct messages off at launch and turning them on once you have the moderators and the rules to handle what comes with them. If you do enable them, set expectations in your rules about contacting people who have not asked to be contacted.
Names, anonymity and points
Some people can only speak freely under a different name. BuddyNext has no anonymous posting, but members can use a display name of their choosing. Jetonomy Pro adds anonymous posting, where other members see “Anonymous” and only a site administrator can reveal the real author, with every reveal logged. Tell members this plainly if you switch it on, because administrators can see who wrote a post.
Do not lock names on this kind of site. Jetonomy has a setting that stops members changing their names for communities that need verified real names, and a support community generally wants the opposite.
Leave points, badges and leaderboards out. They suit communities where people compete to contribute, and they sit awkwardly beside someone posting about a hard week. If you want recognition, a short thank-you from a moderator does the job and costs nothing.
Free and Pro for a support site
| You want | Plan |
|---|---|
| Spaces, join requests, reports, safeguards, content warnings, strikes, suspensions, appeals, space bans | BuddyNext free |
| Admin approval and email verification at registration | BuddyNext free |
| Discussion boards with moderation queue, post approval and private spaces | Jetonomy free |
| Anonymous posting; advanced auto-moderation | Jetonomy Pro |
| Member labels such as Moderator or Staff next to names | BuddyNext Pro |
| Auto and bulk moderation tools | BuddyNext Pro |
The free versus Pro page lays out every plugin in the stack.
A calm, consistent look
Reign is built to work with BuddyNext and every Wbcom plugin, so the whole site shares one design. For a support community that means a calm, consistent look across the community pages and the discussion boards, without a patchwork of themes. Read what Reign is, or try the demos. If you are still deciding how open to be, private versus public community walks through the trade-offs.
Frequently asked questions
Can a peer support community give advice or treatment?
No. Members share their own experience, and the site should say that nothing in it is professional advice. Members should consult a qualified professional about their own situation.
What should I tell members about emergencies?
Tell them the community is not an emergency or crisis service, and direct them to local emergency services and crisis lines in their own country. Look up current contact details from official sources for each region you serve. We do not list numbers in this guide.
Can members post anonymously?
BuddyNext does not offer anonymous posting, though members can choose a display name. Jetonomy Pro does, with the real author stored and visible only to site administrators. Explain this to members if you enable it.
Should I turn on direct messages?
It is a decision, not a default. Direct messages are private, so they sit outside visible moderation. Many support communities start without them and add them once moderation is ready.
Does using BuddyNext or Jetonomy make my site compliant with privacy or health regulations?
No. The plugins give you controls, and compliance depends on what you collect and where you operate. Get qualified advice for your situation.
How many moderators do I need?
Enough that nobody carries the whole queue. Start with a small group, agree coverage times honestly, and publish those times so members know when someone is watching.