Review Channel Community

For a review channel: a request queue with visible position, verdict discussion by category and a disclosure channel.

  • 4 categories
  • 14 channels
  • 6 roles
  • Small
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

THE CHANNEL

  • server-rules

    Disagree with the verdict, not the person.

  • disclosure

    How things are sourced, what is accepted, how paid pieces are labelled.

  • new-reviews

    Posted automatically.

  • general

    Everything else.

REQUESTS

  • request-queue

    One request per post. Votes matter.

  • queue-status

    Next, in progress, and declined with a reason.

VERDICTS

  • category-one

    Rename to a category the channel covers.

  • category-two

    Rename to a second category.

  • category-three

    Rename to a third category.

  • disagree-with-the-review

    A real channel, not a complaint box. Bring your reasoning.

  • ranking-list

    Everything reviewed, in order. Edited, not reposted.

THE AUDIENCE

  • your-own-reviews

    Yours. Same standard, please.

  • buying-advice

    The question a video cannot answer for one person.

  • Review Room

Roles

  • ReviewerAdministrator
  • ModeratorModerator
  • Viewer
  • Review Ping
  • Muted

Overview

Review audiences behave differently from other channel audiences: they arrive with a specific thing they want covered, they argue about verdicts, and they are unusually alert to whether the reviewer was paid. This layout answers all three. #request-queue is where viewers ask for something to be reviewed, and #queue-status is the read-only companion showing what is next, what is in progress and what has been declined with a reason — which is what stops the same request arriving weekly forever. #disclosure is the channel that earns a review channel its audience: a permanent statement of how the reviewer sources what they cover, what is accepted for free, and how a sponsored piece is labelled. It is read-only, short, and does more for credibility than any amount of insisting. Verdicts splits discussion by category so an argument about one product is not buried under another, with #disagree-with-the-review kept as a real channel rather than something moderators discourage, because a review audience that cannot argue leaves. #ranking-list holds the channel's running order of everything reviewed, which is the most-referenced thing a review channel produces. #your-own-reviews lets the audience post theirs, and #buying-advice is where viewers help each other with the question the videos cannot answer individually.

When to use it

Review channels get the same request forty times because nobody can see the queue, verdict arguments spill across every channel, and the audience's questions about sponsorship go unanswered until they become an accusation. This layout publishes a queue with status, keeps a permanent disclosure statement, splits verdict discussion by category, and gives disagreement a channel of its own rather than treating it as trouble.

What makes it different

  • A read-only queue status showing what is next, in progress or declined and why.
  • A permanent disclosure channel, which does more for credibility than any statement in a video.
  • Disagreement gets a real channel, because a review audience that cannot argue leaves.
  • A running ranking list, which is the most-referenced thing a review channel produces.

Recommended Vetox setup

  • Suggestions

    Run Suggestions on #request-queue so the queue is ordered by what the audience voted for rather than who asked loudest.

  • Embed Messages

    Use Embed Messages for #ranking-list so the running order is edited in place instead of reposted every month.

  • Notifications

    Point Notifications at the channel feed so #new-reviews fills the moment a video publishes.

  • Starboard

    Point Starboard at #your-own-reviews so the audience's best writing becomes part of what the server offers.

Questions

Why publish declined requests?

Because a silent decline reads as being ignored, and the request comes back. A one-line reason — outside what the channel covers, already reviewed, cannot get access — closes it permanently and is usually accepted without complaint. It also gives the audience an accurate picture of what the channel is for, which reduces the off-topic requests over time.

How detailed should the disclosure channel be?

Specific enough to be checkable: whether review units are kept or returned, whether anything is accepted on condition of coverage, how a paid piece is labelled, and what the channel will not do. Vague assurances of independence are read as evasive. A short, concrete statement that a viewer can hold you to is the version that actually builds trust.

Common mistakes

  • Taking requests with no visible queue, which guarantees the same request arrives every week.
  • Handling sponsorship questions case by case, so the answer is never findable and doubt accumulates.
  • Discouraging disagreement, which removes the reason a review audience joins a server at all.

Consider instead

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages