Build an approval workflow for recurring YouTube FAQs

Repeated questions are a good automation candidate only after you know what a correct answer looks like. This recipe turns a frequently asked question into an approval-first workflow, so you can inspect wording, find edge cases, and decide whether a narrow part of the answer is safe to automate.

Automation recipe · approval workflow

Best for

Channels with recurring questions about an upload schedule, recipe, resource, process, product, or other fact that the creator can verify and maintain.

Recommended action

AI-generated reply

Start in approval mode so you can inspect real matches before anything posts.

The rule boundary

Match one job, leave nearby comments out

Describe the question in plain language rather than listing every synonym. The rule should match intent, then let approval mode expose questions that only look similar.

Match typeAI intent matching
Starter conditionthe commenter is asking the recurring FAQ described by the creator, and the question can be answered from the supplied facts without account-specific context
Action modeAI-generated reply · Needs approval

Make it yours

Edit the facts, then preview the reply

Approval recommended

The fields below are placeholders for your channel. The preview updates as you type; nothing is posted or saved by this page.

Write the shortest complete answer you are comfortable publishing.
Link to a page or video that adds context to this answer.
Example comment

When do you usually publish the next part?

Suggested public reply
The short answer is: [approved answer] If you need the full context, start here: [supporting URL]
Open unsaved draft

Add your own values for Approved answer, Supporting link to enable the draft handoff.

The draft opens in CommentShark's Comment Assistant. Review the rule, accept the product disclaimer, and save it under your own account when it fits your channel.

The draft uses this instruction to guide a fresh reply; the public example above is a starting point you can copy or adapt.

Use real comments to calibrate

What should match and what should not

Examples are guardrails, not a promise that every comment will be classified correctly. Review your own channel language before enabling a rule.

Good matches

  • Is there a new tutorial every Tuesday?The viewer asks the recurring publishing FAQ.
  • When will you upload part two?This is a version of the same schedule question.
  • Where can I find the full written recipe?If this is the chosen FAQ, the supplied link can answer it directly.

Keep out

  • Can you make a tutorial about color grading next?That is a content suggestion, not the existing FAQ.
  • I never received the download email.This is an account or delivery issue that needs a human.
  • Will you upload every day forever?The question exceeds the facts the creator supplied.

Why this structure works

A useful answer needs a useful boundary

  • It defines the answer before the automation is enabled, giving reviewers a stable standard.
  • It makes approval the default so the rule can teach you how viewers actually phrase the question.
  • It separates a reusable fact from personal support or requests that should not be automated.

Setup path

Configure it in three deliberate passes

The recipe page is a planning and preview tool. CommentShark does not post or save anything until you open the editor, review the draft, and save it under your own account.

  1. 1

    Pick one FAQ

    Do not combine several unrelated questions in one intent. Start with a question that has a short, stable, publicly verifiable answer.

  2. 2

    Review a real sample

    Use approval mode to inspect matches, edit false positives, and expand the intent description only when the new phrasing still means the same thing.

  3. 3

    Graduate narrowly

    If the answer stays correct across a representative sample, consider autonomous execution for this FAQ while leaving adjacent topics in approval mode.

Open Comment Assistant rulesYou can also use the preview above to open this recipe as an unsaved draft.

Before you enable it

Quick safety checks

  • Keep the answer current; a schedule or policy can become wrong without a code change.
  • Exclude personal account, payment, access, safety, and medical or legal advice requests from a general FAQ rule.
  • Do not add a link just because one is available; it should help answer the question.

Questions creators ask

Frequently asked questions

How many questions should one FAQ rule cover?

One recurring intent is easier to review than a bundle of loosely related questions. Create separate rules when the answer, risk, or supporting link changes.

Why start in approval mode?

Approval mode shows which real comments match and gives you a chance to refine the boundary before anything posts automatically. It is especially useful for natural-language FAQ matching.

Can an FAQ rule post an answer with no link?

Yes. A concise factual answer is often enough. Only include a supporting link when it helps the viewer complete the task.

Keep exploring