Why is user feedback still handled through 90s-style forums instead of AI-assisted aggregation?

I genuinely don’t understand why feedback and feature requests are still handled through traditional forum threads.

From a user perspective, this model is broken. There are countless duplicate threads, endless “this was already discussed” replies, and an unrealistic expectation that users should spend time searching through hundreds of posts before expressing their own experience. Most users won’t do that — they just want to describe their issue or idea and move on.

What feels especially strange is that this is an AI company. Instead of forcing feedback into fragmented threads, why not allow users to simply write or dictate their thoughts into a shared pool, where AI aggregates, clusters, summarizes, and surfaces the real signals? Patterns, recurring pain points, and high-impact ideas could emerge naturally — without users policing each other over duplicate topics.

Right now, the forum structure seems optimized for moderation and noise control, not for real dialogue or understanding user needs. It spreads responsibility thinly and makes it easy to ignore feedback because it’s scattered everywhere.

An AI-assisted feedback system — even a simple one — would be a massive step forward:

  • No need to search endlessly

  • No duplicate-policing culture

  • Clear aggregation of what users are actually saying

  • Better signal for product teams

It feels ironic that a company building world-class tools for synthesis and context is still relying on outdated forum mechanics for user feedback.

Curious if others feel the same, and whether this has been discussed internally.

2 Likes

I genuinely don’t understand why feedback and feature requests are still handled through traditional forum threads.

Please show an example of a traditional forum

An AI-assisted feedback system — even a simple one — would be a massive step forward

I don’t agree.

Curious if others feel the same

Nope

1 Like

agreed, nuke this place.

it was great during the slack days.

fire everyone that works on this forum and create something you’d expect out of oai

2 Likes

Hi, and thanks for the points-to-ponder, but realize the forum is a “forum”, based on the Discourse web forum software, and that software’s pattern somewhat guides how user-to-user interactions happen here. This forum doesn’t have regular interactions with OpenAI staff in the manner of a customer support helpline. It’s primarily for discussion with your peers.

What you describe is the way people are going to act anyway just because the developer forum is here - post their unrealistic idea (“dating in ChatGPT please”) without search work or reading (and usually posting ignorable text written by AI) and then leave, never really engaging.

If OpenAI is mining the forum for ideas, they aren’t saying “thanks”. Particularly the ChatGPT (consumer web chatbot) feedback category is muted by default, and ideas go there to die.

The forum focus is on coding API and codex products, developer chat. This particular forum topic you’ve selected, “forum feedback”, is Feedback on how to make this developer forum better for you! " - not how to re-engineer reaching OpenAI.

For this forum, search can be powered by AI:


If you want aggregated feedback, press the downvote button in ChatGPT, and add your comments.

That is pinned with the AI generation that was unsatisfactory. Similar can also be done when in the API developer playground if enabling feedback thumbs up/down there for training.


If you want AI answers to your problems or feedback in private, you can send messages via help.openai.com with the chat there. Expect that for even escalations, it is an outsourced contractor resolving issues and making statistics.

2 Likes

Follow-up: Core usability pain points from a long-term user perspective

To continue from my earlier point about the limitations of a traditional, 90s-style forum model, I want to clarify my concrete usability pains as a ChatGPT user.

Voice interactions and conversation fragmentation
A core issue is that voice interactions always start a new conversation instead of continuing the active one. This fragments context across multiple threads. What is logically a single discussion ends up split into several conversations, each missing parts of the reasoning and background. This makes it difficult to maintain continuity, revisit decisions, or understand prior context.

Conversation growth and management overhead
Because of this fragmentation, the total number of conversations grows rapidly. Managing them becomes increasingly time-consuming, especially since the current UI is very basic and slow. There are no bulk actions, and conversations cannot be selected or managed efficiently at scale.

Ideally, conversations should be manageable in a structured way, similar to a file system or table view, for example:

  • sorting by name, creation date, last activity date, or conversation length

  • folders and/or tags (labels, hashtags) to group related discussions

  • bulk actions such as archive, delete, or move

Projects help somewhat, but they feel like a partial solution layered on top of a limited underlying system.

Lack of customization and user control
Users currently have almost no ability to customize the UI or UX to fit their workflows. Features and behaviors change frequently, good workflows disappear, and there is no way to opt in, opt out, or preserve preferred usage patterns. Development feels driven by rapid experimentation, while users have no control over stability or continuity.

This makes it difficult to build reliable long-term workflows, because usability depends entirely on what happens to be released next.

Transparency and communication
Another major issue is the lack of communication around changes. New features and behavioral changes often arrive without explanation or advance notice. Users are left guessing why changes were made, what problem they solve, or what the long-term vision is.

Even high-level explanations would help users adapt and evaluate changes more constructively.

User perspective and broader direction
Finally, it’s concerning that the user perspective is not clearly reflected in the company’s stated mission or values. Given how central ChatGPT has become to people’s daily work and thinking, this absence is noticeable.

I’ve also sent similar feedback via the Help Center chat (https://help.openai.com/en), but the core frustration remains: users have lost the ability to adapt the tool to their needs.

For me personally, my productivity system built around ChatGPT was significantly disrupted by recent changes—especially voice creating new conversations and the lack of scalable conversation management. The UI is visually clean, but functionally too limited and slow for advanced, high-volume use.

This feedback comes from appreciation for the product’s potential. ChatGPT is powerful, but the current lack of continuity, control, and predictability makes serious long-term use unnecessarily difficult.