In this guide
Which alert solution do I need?
Follows and subscriptions, sound memes, chat TTS, and channel point actions are different jobs. This overview page points you to the right dedicated guide and keeps several services from needlessly doing the same thing.
1. The main alert types
- Classic alerts: follow, sub, gift sub, bits, raid, and donation.
- Sound alerts: sounds, memes, and videos triggered by viewers.
- TTS: reading chat messages or event texts aloud.
- Channel points: OBS actions, clips, screenshots, a prize wheel, or camera switching.
- Production messages: bitrate, connection status, and technical warnings. You need those more in monitoring on the go than in viewer alerts.
2. Comparing solutions
| Solution | Focus | Guide |
|---|---|---|
| StreamerHub | TTS, alerts, sounds, community actions, OBS Remote, and IRL Map | StreamerHub |
| Streamer.bot | Local automation, channel points, and OBS | Streamer.bot |
| Alert services | Follows, subs, bits, and donations | Stream alerts |
| Sound Alerts/Blerp | Community sounds and videos | Sound alerts |
| SpeechChat/TTS | Reading chat aloud | TTS |
Three questions first
- You only want to show follows, subs, or donations? Then an alert service is enough.
- Viewers should trigger sounds or videos, or chat should be read aloud? Then add Sound Alerts or TTS, each on its own.
- Channel points should start OBS actions? Then you need automation, for example Streamer.bot.
3. Hearing alerts on the go
If a Bluetooth speaker is playing, the phone mic usually picks the alert up. In that case the source stays muted in OBS. With headphones, OBS has to output the browser source, or viewers won't hear the alert. The whole audio path is explained in audio in an IRL stream. The step-by-step setup is in the Stream alerts guide.
4. Channel points and automation
Streamer.bot can use reward redemptions as triggers for prepared actions. That gives you clips, screenshots, markers, prize wheel actions, or OBS switches. Critical actions need cooldowns, a role check, and a manual off switch.
5. Moderation, rights, and costs
- Treat browser sources and tokens like passwords.
- Limit volume, cooldowns, and spending.
- Only use media you have enough usage rights for.
- Moderate TTS and uploads.
- Test each function on its own before you combine services.
6. Common questions about alerts in an IRL stream
Do I have to combine several alert services?
No. One service per job is usually enough. Two services doing the same thing give you doubled alerts and audio chaos. Set up one function completely and test it on its own. Only then move on to the next.
What is the difference between classic alerts and sound alerts?
Classic alerts fire when something happens on the platform: a follow, sub, bits, raid, or donation. Sound alerts are triggered by viewers themselves, for example with sounds, memes, or videos. Each has its own guide: Stream alerts and Sound alerts.
Streamer.bot or StreamerHub: which fits me?
Streamer.bot is local automation for channel points, OBS actions, and your own workflows on the production PC. StreamerHub bundles TTS, alerts, sounds, community actions, OBS Remote, and IRL Map. Which fits better depends on your setup. Both guides show what each one contains.
Do I hear alerts automatically while I'm out?
Not on its own. OBS often runs somewhere else, so you need your own return path to your phone, for example through a Bluetooth speaker or headphones. How to build that is covered in the Stream alerts guide.
Can I use any sounds and images in alerts?
Only use media you have the usage rights for. That applies especially to music, memes, and videos that viewers can trigger. This page is not legal advice. If you're unsure, leave the material out.
Setup service & consulting
If you want help with your setup or with troubleshooting, reach out in the IRL4YOU Discord.