Native Twitch · Shoutouts

Send shoutouts and welcome raids

Recommend another live channel now, or prepare one automatic welcome for each qualifying incoming raid.

BlokeBot Shoutouts page showing the manual target and automatic raid shoutout settings. BlokeBot Shoutouts page on a phone showing a Twitch channel name field and the Send shoutout action.
Manual shoutouts, automatic incoming-raid settings and recent outcomes stay on one task page.

Send a shoutout now

If BlokeBot asks for the bot account to be reconnected, restore that account's moderator role first, then reconnect it from Channel setup.

  1. Open Shoutouts, enter the other channel's Twitch name and select Send shoutout.
  2. Wait for the result before trying again. The target must be live with viewers.
  3. Use the displayed cooldown and Recent shoutouts to decide when another send is available.

Welcome incoming raids automatically

  1. Automatic raid shoutouts are off by default. Open the section and turn them on when you are ready.
  2. Set the minimum viewer count, then choose either a Native Twitch shoutout or a Chat message.
  3. For a chat message, choose Regular, Pinned or Announcement. A pinned message can use a duration from 30 to 1,800 seconds or stay pinned until stream end; an announcement also needs a colour.
  4. Write the message, check its preview and readiness note, then select Save automatic shoutouts.
  • Message tokens include {twitch_handle}, {display_name}, {channel_url}, {viewer_count}, {last_game|fallback} and {stream_title|fallback}.
  • Last game and stream title need an inline fallback because Twitch may not provide them.
  • BlokeBot handles each eligible raid once. A failed native shoutout is not replaced with a chat message, and a failed announcement is not replaced with a regular message.

Check an automatic outcome

  • Automatic shoutout outcomes shows the newest raid results and why a send was skipped or incomplete.
  • Native shoutouts can be skipped while Twitch's cooldown is active.
  • A pinned message can be sent even when Twitch cannot pin it afterwards; the outcome states both parts.
  • Fix the connection or permission named by the outcome before the next raid. There is no retry or fallback action for an earlier raid.