Problem
ChatGPT currently lacks a clearly identifiable, consistently accessible mechanism for submitting product-level feedback, user-interface improvements, and feature requests.
Users seeking to suggest application enhancements may be directed to the thumbs-down feedback control associated with individual assistant responses.
This presents several usability problems:
-
Incorrect feedback association: Product enhancement requests are treated similarly to feedback about an individual assistant response, even when that response is accurate and helpful.
-
Inconsistent availability: Feedback controls may not be visible or accessible in every ChatGPT interface or platform.
-
Unclear submission process: Users may need to contact Support simply to discover how to submit a feature suggestion.
-
Limited acknowledgment: Users may receive no unique reference number or confirmation that their suggestion has entered a product feedback process.
-
No transparent tracking: Users cannot readily determine whether a suggestion has been received, reviewed, accepted, declined, or implemented.
For example, a user attempting to submit a navigation enhancement through the official support channel may be repeatedly directed to use a thumbs-down control that is not available in their current browser interface.
Although Support may document the suggestion, this does not necessarily establish a formal, trackable product enhancement request.
Proposed Enhancement
Introduce a dedicated Feedback & Suggestions interface, accessible directly from ChatGPT’s Help menu and consistently available across supported platforms.
1. Dedicated Feedback Entry Point
Provide a clearly labeled option such as:
Help → Feedback & Suggestions
This should be separate from the controls used to evaluate individual assistant responses.
2. Structured Submission Categories
Allow users to classify their submissions as:
-
Feature Request
-
User Interface / User Experience Improvement
-
Bug Report
-
Accessibility Improvement
-
General Product Feedback
Each category could offer relevant optional fields without making the submission process unnecessarily complicated.
3. Submission Confirmation and Tracking
Upon successful submission, provide:
-
Confirmation that the feedback was received.
-
A unique submission reference number.
-
A visible submission history.
-
A clearly defined status.
Suggested statuses include:
Submitted → Under Review → Planned → Implemented
Additional statuses could include Needs More Information, Declined, and Closed.
Status changes should reflect actual product-team decisions rather than implying that every submission will receive individual review.
4. Cross-Platform Consistency
Ensure the feature is accessible through supported ChatGPT interfaces, including:
-
Web browsers
-
Windows desktop
-
macOS desktop
-
Android
-
iOS
The location and basic behavior of the feedback interface should remain consistent across platforms.
5. Privacy and Security Controls
The submission process should not automatically include private conversation content, Project names, conversation titles, or other potentially sensitive information.
Users should explicitly authorize the inclusion of:
-
Screenshots
-
Conversation excerpts
-
Project-related context
-
Diagnostic information
A preview should clearly show what information will be submitted.
6. Optional Feedback Lifecycle Notifications
Allow users to opt into notifications when:
-
Additional information is requested.
-
A suggestion changes status.
-
A proposed enhancement becomes available.
-
A reported issue is resolved.
Notifications should be optional and configurable.
7. Duplicate Detection and Community Participation
Consider allowing users to discover existing suggestions before creating new ones.
Where appropriate, users could support or subscribe to existing proposals rather than creating duplicates.
This could help OpenAI identify frequently requested improvements while reducing redundant submissions.
Expected Benefits
For users:
-
A clear, accessible method for suggesting product improvements.
-
Greater confidence that feedback has been received.
-
Reduced confusion between response-quality ratings and application feedback.
-
Better visibility into the status of submitted suggestions.
-
Less reliance on Support for routine product feedback.
For OpenAI:
-
More structured, actionable product feedback.
-
Improved identification of recurring usability issues.
-
Reduced duplicate feature requests.
-
Better insight into user priorities.
-
Reduced support interactions concerning feedback submission procedures.
Implementation Considerations
This enhancement could be introduced incrementally.
An initial release could provide a dedicated submission interface, structured categories, privacy controls, and confirmation numbers.
Submission history, status tracking, duplicate detection, and optional notifications could follow in later releases.
The interface should not promise individual review or implementation unless those processes are actually supported.
Summary
A dedicated product feedback system would establish a clear distinction between evaluating an assistant’s response and proposing improvements to the ChatGPT application itself.
It would provide users with a consistent, transparent, privacy-conscious way to contribute suggestions while giving OpenAI more structured information for product development.
Requested outcome: Consider implementing a dedicated, cross-platform Feedback & Suggestions mechanism within ChatGPT, with submission acknowledgment and an extensible framework for tracking product enhancement requests.