What real-time chat at events tells you about your audience
Three months into Feedr, a church pastor in Liverpool ran a Sunday service with our live comment stream active. Within five minutes, he had sixty comments. He wasn't preaching to a room; he was overhearing thoughts he'd never have heard otherwise. That's when I realised we'd built something that works differently than most event tools.
The noise isn't noise, it's data you can actually use
Most event hosts get feedback two ways: a survey they send afterwards that three people fill out, or overhearing conversations in the hallway. Both are incomplete. Real-time chat during an event is different. It's unguarded. People comment as they think, not hours later when they've had time to sanitise their response.
That pastor in Liverpool saw something shift in his Sunday service. Normally, he'd finish a point and wonder if it landed. With comments flowing in, he saw which ideas made people lean in. One comment got upvoted seventeen times. It wasn't agreement, exactly. It was recognition. The audience was telling him, in real-time, what mattered to them in that moment. He adjusted his approach for the second service that day based on what he'd read.
This isn't surveillance. It's a conversation happening at speed and scale simultaneously. A conference speaker can see which line resonated. A lecturer can spot confusion before half the room checks out. A podcaster can tell what question their audience actually wants answered, not the one they guessed.
You learn more from upvotes than you do from impressions
Anyone can post a comment. Most won't. But if a comment gets upvoted, someone else thought it was worth amplifying. That's a signal. When Feedr launched to beta, I watched the Creator plan users obsessively. They'd use the upvote system to filter signal from noise. One tech conference host noticed that questions about implementation details were getting three, four, five upvotes each, while theoretical questions barely moved. The speaker wasn't chasing what interested her; the audience was showing her what they actually needed.
We built upvoting into the free tier for a reason. It costs us nothing, but it gives every host a filter. You don't have to read fifty comments to find the one that matters. The audience votes for you.
What's strange is how often the upvoted comments surprise the host. They assumed their audience cared about one thing. The chat showed them another. That gap between assumption and reality is where you improve.
Moderation changes what people say, and that's useful too
We added a comment moderation queue to Creator and Pro plans because early hosts asked for it. Some wanted to catch spam. Others wanted to prevent bad behaviour. But something else happened. Hosts using moderation started to see patterns in what they needed to catch and what they could let through.
One lecturer realised that after she added moderation, the tone in chat improved. Not because she was deleting everything critical, but because people knew someone was paying attention. The stream became more thoughtful. She told me it felt like the difference between a crowded pub with no one watching and a crowded pub where the landlord is behind the bar.
You learn something from that too. Are your audience members respectful when they know they're being read? What language do they use when they think no one's moderating? If you turn moderation on, you often don't have to moderate much. The awareness changes behaviour.
The size of the room changes what people say
Feedr scales from your first hundred attendees up to unlimited on the Pro plan. We watch different behaviours at different scales. A twenty-person workshop generates comments that feel intimate, almost like sidebar conversations. At a hundred, the chat becomes more performative. At five hundred or more, it fragments into clusters of thought.
This matters. A host who moved from a Creator plan (500 audience cap) to Pro (unlimited) told me that the chat felt completely different at a thousand people. Before, key comments rose to the top because the full audience could see and vote on them. At a thousand, the sheer volume meant comments disappeared in seconds. She had to learn to read faster, or accept that some voices would be lost.
That's not a criticism of the platform. It's insight. How do you run an event where everyone feels heard? The chat doesn't solve that. But it makes the constraint visible. And visibility is the first step to solving something.
What people don't say is sometimes louder
I spent launch week watching sessions across industries. A corporate training host ran a two-hour session with ninety attendees and got seven comments total. Worried, she cut her next session to forty minutes and got thirteen comments from thirty people. The shorter format wasn't better because of the content; it was better because people felt like they could actually be heard.
The silence tells you as much as the chat. If a room isn't commenting, you're not dealing with a shy audience. You're probably dealing with a room that doesn't think you're listening. Or they're exhausted. Or they don't feel safe. Some sessions generate comment streams that rival what you'd get from a panel discussion. Others feel like broadcasting into a void.
The hosts who get the most value from Feedr aren't trying to maximize comment volume. They're trying to understand their audience's actual state. Are they engaged? Confused? Bored? The chat is a heartbeat monitor. You're learning whether your event is alive.
If you hosted an event and could see every thought that passed through your audience's mind for ninety minutes, what would surprise you most about what they were actually thinking?
Ready to try Feedr by MRVL?
One tap to download. No sign-up wall.