Skip to content

Community help answers with moderator review

Drafts answers to questions in your community help forum from your docs. A moderator checks each one before the user sees it.

SupportWorks with Claude Code · n8n+1Community example
Build your promptSee requirements

What it does

  • Picks up new questions in the help forum
  • Groups follow ups from the same person
  • Searches your docs for the matching passages
  • Drafts an answer in a private moderator thread

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Posting any answer to the user

You decide what happens next.

More about this workflow

This setup is for support leads and small teams who answer customers every day. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it picks up new questions in the help forum. Next, it groups follow ups from the same person. Then it searches your docs for the matching passages. Finally, it drafts an answer in a private moderator thread. It works with your chat, knowledge base and docs site, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before posting any answer to the user, and says plainly if a step cannot be undone.

“moderators review each answer before it reaches the user.”
Ya-shh Ya-shh on GitHub · Sep 17, 2026
Before you startChat · Knowledge base accessScoped permissionsClaude Code or n8n
Explore required tools and model recommendations

Tools and access

  • Slack

    Handles the chat part of this job. Grant a bot token in the channels it needs.

    API required: Yes. Needs a Slack app created in your workspace. It gets a bot token with the scopes you approve.

    Sign up: Create a Slack app

  • Notion

    Handles the knowledge base part of this job. Grant only the pages it needs, read first.

    API required: Yes. Needs a Notion integration. You choose which pages it can see by sharing them with it.

    Sign up: Notion

  • Docs site

    Handles the docs site part of this job. Grant draft or branch access, not publish.

    API required: Optional. Your docs repo or CMS. Most agents work through a branch or draft.

    No sign-up needed

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Writes careful replies and reads long ticket threads.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Haiku 5.5

Made for sorting and routing at high volume.

From $0.10 per million input tokens and from $0.50 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

where drafts go for review

2Your prompt

4 of 4 still empty
Fill these in before you run it: [YOUR HELP FORUM CHANNEL] [YOUR DOCS FOLDER OR SITE] [MODERATOR CHANNEL: where drafts go for review] [TOPICS THE BOT SHOULD SKIP] You are the Community help answers with moderator review agent. Drafts answers to questions in your community help forum from your docs. A moderator checks each one before the user sees it. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Picks up new questions in the help forum - Groups follow ups from the same person - Searches your docs for the matching passages - Drafts an answer in a private moderator thread What you must never do without a yes from a person: - Posting any answer to the user Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, n8n, LangGraph

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Slack with its own login, not yours. Grant a bot token in the channels it needs.
  2. 2Connect Notion with its own login, not yours. Grant only the pages it needs, read first.
  3. 3Set up Docs site. Keep it to draft or branch access, not publish.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval27 / 30

Waits for a yes on: posting any answer to the user.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Human approval: Add a second named stop next to "posting any answer to the user", so every step that leaves your hands waits for a yes, and have the confirm say plainly what cannot be undone +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Community help answers with moderator review](https://trustcase.dev/badge/community-help-answers-with-moderator-review.svg)](https://trustcase.dev/use-cases/community-help-answers-with-moderator-review)
HTML
<a href="https://trustcase.dev/use-cases/community-help-answers-with-moderator-review"><img src="https://trustcase.dev/badge/community-help-answers-with-moderator-review.svg" alt="Trustcase trust score for Community help answers with moderator review" height="20"></a>

More support workflows

  • Help tutorials from your app

    Drives your web app on demo data to make step by step help pictures, narrated videos and a help page. Rerun it when the screens change.

  • Customer renewal readiness check

    Checks every customer account renewing in the next 120 days and gives each one a readiness status with reasons. Built for small customer success teams working from exports.

  • Ticket triage

    Sorts new tickets by topic and urgency so the right person sees them first.

  • Reply suggester

    Drafts answers to common questions using your help docs.