Listening vs acting
Community and sentiment tools are good at what they do: spotting emerging issues across Discord, forums, reviews, support queues, and social feeds. Iridae doesn't replace that. It ingests it.
The hard part starts after the alert. Players are upset about the patch -- now what? Who owns the response? What's safe to say? Sentiment tools tell you the temperature. Iridae connects that signal to a decision and tracks whether the response landed.
After the alert
- Different communities form different narratives. No single picture.
- Ownership of the "what now?" call is unclear. Decisions drag or fork.
- Patch work, support policy, and public comms move out of sync.
- Promises get made without a record of assumptions or tradeoffs.
- Weeks later, nobody can trace what shipped versus what was said.
Without a loop from signal to response to follow-up, teams stay reactive.
What Iridae adds
- Consolidate sentiment and support themes into one decision view.
- Frame the moment: what players expect, what's broken, what constraints apply.
- Draft response actions across product, support, and comms, then route for approval.
- Track follow-through so the next response starts smarter.
You keep editorial control. Iridae coordinates the loop but never posts unilaterally.
Comparison at a glance
| Dimension | Sentiment tools | Iridae |
|---|---|---|
| Core question | "What are players saying?" | "What should we do about it?" |
| Typical outputs | Alerts, themes, dashboards, moderation queues | Decision briefs, approved actions, traced outcomes |
| Best for | Monitoring sentiment and surfacing issues early | Coordinating response, follow-through, and learning |
| Together | Listening tools detect and summarize | Iridae runs the response loop and closes it |