Moderator Handoff Notes for Paid TTS and Upload Corner

Moderator consistency is part of the product

Paid TTS and viewer uploads feel unfair when moderation changes every hour. One mod approves a joke, another rejects the same kind of joke, a third does not know sponsor-safe mode is active, and the streamer has to settle disputes live. The viewer sees inconsistency. The streamer loses focus. The mod team gets blamed for rules that were never written.

A handoff note fixes the most common gap: context. It tells the next moderator what kind of stream is happening, which paid features are open, which rules are strict tonight, what has already gone wrong, and who makes the final call.

StreamableBot features such as AI TTS, Upload Corner, tipping, alerts, overlays, and chat commands are strongest when moderators operate them predictably. The tool can provide controls, but the team still needs shared judgment.

Write the mode at the top

The first line should say the current mode. Casual, focused, sponsor-safe, event, charity, late-night, members-first, or paused. That one word changes approval decisions. A message that is fine during a casual game may be wrong during a sponsor read or public IRL segment.

Mode also affects speed. During a casual stream, fast approvals may matter more than perfect curation. During sponsor-safe mode, stricter review wins. During a charity stream, disclosure and donor intent may matter. During an IRL stream, privacy may override comedy.

Do not bury mode in a long document. Put it where the next moderator sees it before touching the queue.

• Current mode: casual, focused, sponsor-safe, event, charity, IRL, or paused.
• Paid features open: TTS, Upload Corner, tips, alerts, commands, sponsor prompts.
• Queue speed: fast, normal, slow, manual-only, or held.
• Streamer preference: playful, strict, low-distraction, no personal topics, no sponsor jokes.
• Segment timing: when normal rules return.

List approval and rejection rules

Approval rules should be specific enough for a tired mod. Approve short clean jokes. Hold anything that mentions private locations. Reject hate, slurs, doxxing, sexual content involving real people, unverified claims, sponsor confusion, and images with unreadable small text. Your exact rules may differ, but the handoff should remove guesswork.

Twitch chat docs, YouTube moderation docs, and Kick moderation surfaces all make clear that platform chat needs its own controls. Paid production queues add another layer because approved content reaches OBS as audio or visuals. A message that would merely be annoying in chat can become much worse when read aloud by TTS.

Use category names, not arguments. Mods should not need to debate whether a viewer meant harm. The rule can be off-topic for current segment, private information, unsafe image, too long, or sponsor-confusing.

• Approve: short, safe, on-topic, readable, and timed well.
• Hold: unclear context, possible private info, sponsor-adjacent joke, or needs streamer call.
• Reject: harassment, slurs, doxxing, explicit content, unapproved brand claim, unsafe image, or scam link.
• Edit if allowed: trim length, remove repeated characters, or crop an image safely.
• Escalate: anything involving safety, legal claims, sponsor conflict, minors, threats, or payment disputes.

Name queue priority

When the stream is busy, moderators need to know what gets handled first. A high-value paid TTS message is not automatically more important than an unsafe Upload Corner submission. A sponsor prompt may outrank a normal joke. A privacy report may outrank everything.

Write the order. For example: emergency pause, privacy reports, sponsor queue, paid TTS, Upload Corner, tips with messages, normal command questions, logs. The order can change by stream mode, but it should be explicit.

Queue priority protects moderators from chat pressure. If viewers ask why something is delayed, the mod can follow the written order instead of making a personal judgment every time.

• Emergency pause and privacy reports always come first.
• Sponsor or event prompts come before casual paid jokes during that segment.
• Paid TTS with audio risk gets reviewed before low-risk visual alerts.
• Upload Corner images with unclear content get held until a second mod checks.
• Refund or credit questions go to payment support, not live chat debate.

Include exact controls

A handoff note should say where the controls are. Pause TTS here. Hide Upload Corner here. Replay failed alert here. Reject with reason here. Switch OBS browser source off here. Message producer here. If a moderator has to search for the button during a bad moment, the handoff failed.

Use roles. Chat mod, production mod, payment support, producer, and streamer may be different people. A chat mod should not need full payment access. A production mod may need overlay pause but not account billing. Keep permissions narrow and practical.

Also name the emergency phrase. If anyone says pause paid queue, all paid browser-source moments stop until the producer or streamer reopens them. Shared language is faster than a long explanation.

• Pause TTS: where the button is and who can use it.
• Pause Upload Corner: where the button is and what viewers see.
• Emergency hide: how to remove browser sources from OBS fast.
• Replay or credit: who decides after a playback failure.
• Escalation path: which Discord, call, or chat to use.
• Final call: who overrides a disputed approval.

Track what changed during the shift

The outgoing moderator should leave notes for the incoming moderator. Not a long essay. Just changes that affect decisions: streamer is tired, sponsor segment starts in twenty minutes, TTS voice three caused problems, Upload Corner is paused, viewer X is arguing about a rejection, queue is twenty minutes behind, refund issue sent to support.

This matters because paid moments have memory. A viewer whose message was rejected may submit again. A repeated joke may become unsafe after the streamer asks for it to stop. A sponsor segment may require stricter approvals only for a short window.

The note should be factual and calm. Avoid insults or speculation. The goal is continuity, not a mod diary.

• Current queue length.
• Features paused or reopened.
• Repeated rejection categories.
• Specific viewer support cases that need follow-up.
• Streamer instructions given during the shift.
• Sponsor, charity, or event timing changes.
• Technical issues with browser sources, audio, or playback.

Viewer-facing copy should match the handoff

If the handoff says TTS is manual-only but the command says messages play right away, viewers will blame moderators. If Upload Corner is paused but the payment link still invites uploads, viewers will feel misled. Internal rules and public copy have to match.

Update commands when the mode changes. A short line is enough: TTS is open with mod review, Upload Corner is paused during the sponsor segment, or paid messages are held until the interview ends. Clear status prevents many refund and rejection arguments.

Do not overexplain. Viewers need the practical state, not the full moderation policy. Put detailed rules on the payment or submission page and keep chat copy short.

• !tts says whether review is required.
• !upload says whether images are open, paused, or sponsor-safe.
• !rules links to full paid-message rules.
• Queue status explains delays without promising exact times.
• Rejection copy uses the same categories moderators use internally.

After-stream review

After the stream, review handoff notes against what actually happened. Did mods disagree? Did viewers misunderstand a rule? Did the streamer override a rejection? Did one control take too long to find? Did a sponsor-safe rule need clearer copy?

Improve the template before the next stream. Remove stale rules. Add missing rejection reasons. Shorten control instructions. Create a separate sponsor-safe version if the normal note is too broad.

The best handoff is boring to use. It should make the next moderator faster, calmer, and more consistent than they would be from memory alone.

• Find one rule that caused confusion.
• Find one control that took too long.
• Find one command that did not match reality.
• Find one repeated rejection reason worth adding to public rules.
• Update the handoff template before the next paid stream.

Other resources

Use these references to align platform chat moderation, production moderation, and StreamableBot paid moment controls.

• Twitch Developers: Chat and Chatbots.
• YouTube Help: Moderate live chat.
• Kick Dev Docs: Chat and moderation APIs.
• StreamableBot features.
• OBS Studio: Browser Source.