What “AI” means in Bloopbot
A handful of Bloopbot features can ask an AI judge a plain-English question about a chat message — never to generate a reply, only to answer with a probability, a pick from a short list you define, or a position on a scale you define. Nothing it decides is shown to viewers as AI-written text; it only steers which path your flow takes, or whether something gets through.
| Feature | What it does |
|---|---|
| Judge & route nodes | Three flow-canvas nodes: ask a yes/no question, pick one of several labelled branches, or pick a song title/username/game name/number out of a message — all by what it means. |
| Intent trigger | Wakes a flow when chat means something, instead of when it matches an exact word. |
| Smarter song matching | A Find a song step that picks the track a viewer actually meant out of several Spotify results, and hands you the runner-up for “wrong song”. |
| Song policy | A step that screens out troll/meme uploads and checks a track against a song policy you write in plain English. |
| AI moderation filter | A step that judges what a message means — harassment, hate speech, sexual content, scam/spam, or your own rule — rather than which exact words it contains. |
| Text screening | A step that checks viewer-written text before it is saved or shown. |
| Flow builder | Powers the Describe it instead button: type what you want a flow to do, in your own words, and get the closest ready-made template filled in — see the guide. |
Check what your channel has
Open Flows and press Your plan near + New flow. The AI capabilities are the AI judgments group there: it says whether your channel currently includes each one, why, and how many AI requests your channel has used this month for it — read-only, nothing to buy or configure. What your plan includes walks through the whole panel, including the groups that have nothing to do with AI.
What “locked” looks like
A feature your channel doesn’t currently include shows up wherever it would normally appear, dimmed, with a small lock badge reading Not included in your plan and a short explanation on hover:
- On the flow canvas, a locked node (an AI judge/route node, or the intent trigger) appears in the node library, in ⌘K search, when you drag a new connection, and in the sidebar’s suggestions — always visible, never addable. Clicking or dragging it in just explains why instead of adding it.
- A flow someone built before a feature became locked keeps working. The node stays fully editable and deletable, and the flow still runs — the AI step just always takes its “didn’t answer” path (unsure, or the branch built for that), so nothing breaks and nothing crashes.
- Every AI capability is a step on the canvas, so this is the only shape “locked” takes — there is no AI settings page or filter card anywhere that can be locked separately.
This is intentionally boring: an expired or missing entitlement should feel like “this AI step didn’t run today”, never like a broken flow or a channel-wide problem.
If your channel doesn’t have a feature at all
Nothing changes for you. Every AI feature is additive — it sits in front of behaviour Bloopbot already had, and hands control straight back the moment it isn’t available. A channel with no AI features included is indistinguishable from Bloopbot before any of this existed: the same commands, the same moderation filters, the same song requests.
The same is true moment-to-moment even on a channel that does include a feature: if the AI judge times out, is rate-limited, or has not been switched on for this channel, every AI feature falls back to its ordinary, non-AI behaviour rather than blocking chat or failing a flow run. For a suggestion-only command such as !findsong, that means asking for a clearer clue rather than guessing a track — see find a song from a description.
If a feature isn’t available yet
Some AI steps are not available on every channel yet, and there’s no self-serve switch or checkout today. When a step isn’t available, it still appears in the library with a Not included in your plan badge so you can see what it would do — you just can’t add it to a flow, and a flow that already uses it keeps running. Everything else in your channel works exactly as before, and none of these steps is required to run Bloopbot. What your plan includes lists what your channel holds; for what each one does when it is available, see the smart song requests guide, the AI moderation guide, the flow AI guide and the describe-a-flow guide.
Was this guide helpful?
Thanks. Your answer helps us decide which guides to improve.