Customer support communities

A support community that keeps useful answers in reach.

Bring customer questions, team replies, and community knowledge into one searchable forum. Add AI assistance when you need it, with explicit permissions, reviewable proposals, and an audit trail.

Create your communityRead the scope reference
5
grantable scopes
none
standing access
human
approval required
100%
actions traced
From question to reusable knowledge

A useful answer should not end with one conversation.

  1. Ask

    A customer asks a product question.

    Give setup questions, troubleshooting, and product discussions a home in organised topics instead of starting each conversation from scratch.

  2. Answer

    Your team and community reply.

    Keep answers alongside the original question. Customers can search existing discussions and learn from the context your team and other members share.

  3. Assist

    An agent helps with routine work.

    Connect an agent only when you need one. Grant access to search or summarise discussions, prepare reply drafts, and propose tags without handing over every permission.

  4. Review

    Your team reviews proposed changes.

    Review reply drafts and tag suggestions before applying them. Moderation actions require confirmation, and the audit ledger records the actor, scope, trace, and time.

An AI suggestion, ready for review
acme.pubroo.linkIllustrative ledger entry
#getting-started

How should we welcome new members?

MKRAJDTS
Illustrative thread · not usage data
AgentAgent Moderator 7agent:moderator-7

Proposed adding a pinned setup checklist to this topic.

Currentpinned: nonesetup_guide: none
Proposedpinned: setup-checklistsetup_guide: "5 steps to first agent"
scope:community:write · trace:7f3a…c1 · 14:22 GMT
ApproveEditReject
Permissions, in detail

Choose what your agent can do.

There is no catch-all permission and no implicit escalation. An agent holding community:read cannot reach a community:write tool, and the refusal is recorded like any other action.

  1. community:identity

    Read who the connected agent is acting as. Nothing about the forum itself.

  2. community:read

    Search topics, open threads, and summarize discussions. No writes of any kind.

  3. community:write

    Draft replies, propose tags, and flag content. Each one arrives as a proposal, not a change.

  4. community:moderate

    Read the moderation queue and triage review items. Destructive triage waits for confirmation.

  5. community:admin

    List members, change roles, create invitations, and update community settings.

Every tool and the scope it needs is listed in the MCP reference.

The essentials for day-to-day support.

FORUM

A forum people actually want to use

Categories, tags, threaded topics, search, member profiles, invitations, and email notifications. The AI is additive, not a replacement for a working forum.

QUEUE

A moderation queue with a review trail

Flagged content collects in one queue. Every triage decision, human or agent, is a review item with a visible outcome.

LEDGER

An immutable audit ledger

Filter by actor, action, or target type. Team and above keep full audit ledger history for your own records.

BRAND

Your brand, your domain

Start free on a pubroo.link subdomain with your own logo and brand colour. Custom domains are available on Team and Scale.

As of .

Start with the questions your customers already ask.

Start free on a Pubroo subdomain. No credit card required.

Create your community