Request for product: AI-powered customer feedback tool

@fle_x Fm, the need is more often than not -- sorely misunderstood.

While many request 'AI-powered customer feedback tool' they are not saying the explicit pains they wish to eliminate.

• From a feedback perspective, the pains are not the same across contexts.
• Triage is king for inbound requests, where the volume has reached overwhelmed.
• Some only need a data gathering tool (email or video snippet to transaction). Transaction being the desired FR tool used.
• For example: Apple's feedback tool (a distinct app) really showed this too after using it across my ipad mini, iphone and macbook. Three distinct experiences, for various apps or osx upgrades.
• the best inbound feedback tools I have seen show state-of-play on a dashboard, so all feedback-ers can come up to speed quickly (at-a-glance) on age of issues, counts, impacts, scope breadth and vertical. The dashboard is needed as the volume of FR is often extensive. There is a side benefit when dev take this approach. Their users (including prospects) learn aspects the app they did not consider. Many times I have voted saying, yes that is a good idea, and had not thought of it. FR are correlated ot the context in which in the app is used AND the maturity of the business using the app. When feedback and ideation is crowd sourced, with transparency, experience has shown me a more robust and greater alignment about any particular issue, occurs.
• The best capture point of the issue at hand is right there on screen, like google does Except it would be even better if I could click a button to say record.. and shows what I was doing and can voice over to explain. Often when a user goes to email issue, some important specifics are lost. Then an AI model video to text is needed to record as transaction.

AI that ingested all these sources then gave me the top ones

Definition of 'top ones' actually will evolve over time in most app launches.

with counts of how many users requested each

Using counts is rarely going to guide the most impactful requested features. I have seen apps that use counts, and launch those features and discover later they missed the mark. This is because often the first feature request is articulated from one perspective, versus a person's who understands the full app. We would often curate and join feature requests. A role of any good product manager.

AI or even simple tags, could certainly. map 'similar' FR with similar', then offer a thread like conversation to the developer/product manager.

Cool. I recently found kraftful.com which purports to do something similar.

I mean, I do read every request but it's hard for me to categorize and keep track of the counts. I do that process in my head but it's very vague and could do with some precision. That's why I believe I would like categories with counts and also links to the actual request to verify that the AI categorized correctly and get more details.