Chat bot
Post live, BRB, and back alerts to your chat, and answer commands like !bitrate.
The VISP chat bot writes to Twitch, Kick, and YouTube chat on two occasions: when your stream changes state, and when someone types a command. It runs on VISP's servers — the relay reports that your source appeared or vanished, and the app host posts the message — so it works with your computer off and keeps working while your phone is in your pocket.
On Twitch, messages are posted by the VISP bot by default. Eligible accounts can instead choose My Twitch account in the dashboard. Kick and YouTube messages are always posted as your own linked account.
What it can say
| Alert | Fires when | Default wording |
|---|---|---|
| Live | A publishing device starts sending | Now live. |
| Signal dropped | The source disappears and BRB holds the broadcast | Signal dropped — the stream is held on the BRB card, back shortly. |
| Back | The source returns after a drop | Back — the signal recovered after {downtime}. |
| Stream ended | The source disappears and the outputs are torn down | Stream ended after {uptime}. Thanks for watching! |
"Signal dropped" and "Stream ended" are different events. Which one you get depends on whether Never drop again (dashboard BRB tab) is holding the broadcast open: if it is, chat hears that you are on the BRB card; if it is not, chat hears that the stream is over.
Each alert fires once per device per transition, no matter how many times the relay reports it.
Turn it on
The chat bot is optional and off by default.
- Open the dashboard Chat tab and find Chat bot.
- Switch on Let VISP post in my chat.
- Choose the platforms to post on. Anything not authorized yet shows Authorize posting — that re-opens the provider's consent screen.
- Press Send test next to a platform to prove delivery end to end.
VISP asks for every permission you had already granted at the same time, so authorizing the bot never switches off chat reading, Direct, or title editing.
Permissions each platform needs
| Platform | Permission | Usually already granted? |
|---|---|---|
| Twitch with VISP bot | channel:bot | No — one extra consent |
| Twitch with your account | user:write:chat | No — one extra consent |
| Kick | chat:write | No — one extra consent |
| YouTube | youtube.force-ssl | Yes, if you use Direct or edit titles from VISP |
AI moderator (Plus)
With Plus, the VISP bot also moderates your Twitch chat. It reads chat while you are on air, removes messages that break your rules, times out repeat offenders, answers viewers who mention it, and can make a Twitch clip when someone asks. It never bans: anything permanent stays with you and your moderators.
It is on by default for Plus accounts and switched off from the AI
moderator section of the Chat bot card. To let it act, type /mod and
the bot's name (shown on the card, usually vispstream) in your Twitch chat
once. Twitch chat must be connected and Authorize posting done for the
VISP bot, as for alerts. No other permission is asked from you: the bot acts
with its own account.
What it does, and what you can change:
- House rules. A short free-text description of what to remove, what to allow, and how to sound. Twitch's own rules always apply on top.
- Longest timeout. The cap on any timeout it hands out (10 minutes by default). It never acts on you or your moderators, and never times out the same viewer twice within five minutes.
- Mentions.
@vispstream how long have you been live?gets an answer with the real uptime, viewers, title, and link health.@vispstream clip thatposts a clip link; the clip takes a few seconds to appear on Twitch. Only you and your moderators can ask it to delete or time someone out. - Unprompted lines, each on its own switch: welcoming raids, thanking gifted subs and cheers, a heads-up when your upload link is congested (before the BRB card takes over), and answering stream questions nobody picked up (off by default, as it is the chatty one).
It reads chat in small batches every few seconds, so a message can be up to about five seconds old when it is removed. Replies are one line, in the language chat uses. Usage counts against the Plus token quota shown under Plan and usage; when the quota is used up the moderator goes quiet until the month resets.
Commands
By default, anyone in chat can use commands. The prefix is !.
| Command | Who | Answers with |
|---|---|---|
!bitrate | Anyone | Live bitrate, round-trip time, and packet loss |
!uptime | Anyone | How long the current stream has been up |
!viewers | Anyone | Viewer counts from each linked platform |
!commands | Anyone | The list of public commands |
!title <text> | You and your moderators | Updates the title on every platform that allows it |
Custom commands are plain text replies: add them under Wording and commands
on the dashboard card. A custom command with the same name as a built-in wins,
so !uptime can be replaced with your own answer.
The bot replies on the platform the question came from. It does not repeat one viewer's answer across all three chats.
Limits, on purpose
- One line, 200 characters. Longer replies are truncated.
- 20 messages a minute per platform, and at least 1.5 seconds between them. A bot that loops is what gets an account timed out.
- Viewers wait out a cooldown on custom commands (10 seconds by default). You and your moderators do not.
- The bot only listens while a device is publishing or while the BRB card is holding the broadcast. It is not connected to your chat when you are offline.
Placeholders
Alert wording accepts {device} (the publishing device's label), {uptime},
and {downtime}. Leave a field empty to use the default wording.
Troubleshooting
"Authorize posting" keeps coming back. The consent screen was closed before finishing, or the platform dropped the permission. Re-run it and confirm the chat permission is ticked.
Nothing is posted on YouTube. YouTube chat only exists while a broadcast is live, and live chat must be enabled for that broadcast. Check Direct output first: if VISP did not create a broadcast, there is no chat to write to.
Commands are ignored. Check that Answer chat commands is on, that chat is enabled for that platform under Chat connections on the Chat tab, and that a device is actually publishing.
Alerts are missing but the stream did drop. Alerts are suppressed for a minute after the same event on the same device, so a link that flaps twice in quick succession only says so once.