Feature requests and enhancement ideas
Forward to: Product team
"It would be amazing if you added dark mode"
Product decisions should not depend on who read the right channel
It is roadmap planning season. Your product lead asks: 'what are users asking for?' You know dark mode comes up a lot. You remember someone complaining about the export feature. But how many users? Is the export issue a bug or UX confusion?
Feature requests are scattered across #general, #feedback, and #help. The same request is phrased twelve different ways. Bug reports are worse: users say 'the download thing stopped working,' not 'bug in the export function.' These signals hit community chat weeks before your bug tracker, and most never make it there at all.
89%
Of feature requests in chat never captured in product tools
12
Average different phrasings for the same feature request
3 weeks
How early community bug reports appear before formal tickets
15%
Of support questions about features that already exist (doc gaps)
Product intelligence from the conversations already happening
1
Capture every product signal
Intent classification identifies feature requests, bug reports, competitive mentions, and feature confusion, no matter how users phrase them.
2
Deliver to the teams that own them
Feature requests land with Product. Bugs reach Engineering. Competitive mentions go to Strategy. Confusion about existing features flags a documentation gap.
3
Rank by momentum, not recency
Weekly product briefs show feature request momentum with unique user counts and week-over-week growth. Data for roadmap planning, not anecdotes.
Routes in action
Each route pairs a condition with a destination. When a message matches, it gets forwarded automatically.
Bug reports and broken functionality
Forward to: Engineering
"The export button doesn't work since the last update"
Competitive mentions and comparisons
Forward to: Strategy
"[Competitor] just added this. When are you?"
Confusion about existing features
Forward to: Documentation
"I can't find where to change notification settings"
What your team gets
Momentum ranking
Features ranked by data
Every feature request is grouped by meaning and ranked by unique user count and week-over-week growth
3 weeks earlier
Bug detection
Community bug signals surface weeks before formal tickets. Engineering gets early warning while issues are still small.
Competitive intel
From organic conversation
When users mention competitors or compare features, those signals are captured and included in the product brief.
Doc gap analysis
From confusion signals
When help questions are about a feature that already exists, the brief flags it as a documentation gap