Which networks are actually read, how to reply to a viewer from the studio, and what the panel deliberately does not do.
When you broadcast to several networks at once your audience is split across them. The Chat tab on the broadcast page gathers the comments into one place, so you are not keeping three browser tabs open while talking to a camera.
This is where precision matters, because it is an easy promise to break:
That is the whole list. Twitch, Instagram, TikTok, X, LinkedIn and Kick are not read. There is no chat ingestion for them, which is why they do not appear as a filter either. If you are streaming to Twitch and the audience there is writing, those comments will not reach this panel and you will need the network's own window.
The chat lives on the live broadcast page. The chat inside the podcast studio is a different thing entirely — it is between host and guests and never touches the networks.
YouTube is read every few seconds, at the rate YouTube itself dictates. Facebook is read roughly every six seconds and slows itself down when nothing is happening, so a quiet broadcast does not burn through request allowances. In practice a message appears within a few seconds rather than instantly.
Above the message box is a picker that decides where your message is sent from. You can reply to one specific channel or send to all active destinations at once. A message is limited to 500 characters, and it is posted to the network itself — meaning viewers there see it too, not only you.
Sent replies come back into the list marked as yours, so the conversation reads in order.
Replying works for YouTube and Facebook only. An attempt to send anywhere else returns an explicit message saying sending is not supported there, rather than disappearing silently.
Every message carries Reply and Quote, which fill the message box with a reference to the commenter.
Better to know this in advance than to hunt for a button mid-broadcast:
If a Facebook Page's permissions are insufficient, comment reading for that Page stops and a message is written into the list explaining that Facebook needs reconnecting. This usually follows a permissions change on Facebook's side rather than anything about the broadcast itself.
History is stored and remains available after the broadcast. When you return to the room the most recent messages are reloaded so you do not come back to an empty screen. Chat text is deleted after about thirty days — that is a requirement of YouTube's developer policy rather than a choice of ours. The broadcast's own figures are kept and are not removed with it.
Viewers on the public player are rate-limited on how often and how much they can write, so the list cannot be flooded.
Because there is no Twitch chat ingestion. The list reads YouTube and Facebook, plus viewers on our own player. For Twitch you need the network's own window.
Yes. A message sent from here is posted into YouTube's live chat or Facebook's comments, not only into your own panel.
Not from here. The unified chat has no moderation tools. Deleting, muting or banning is done in the interface of the network where the comment was written.
No. The graphics layers are driven by text you type, and there is no path that puts a viewer's comment into the picture.