Why Use User Feedback
Improve Response Quality
Identify patterns in poorly-rated responses to refine prompts and model selection
Catch Regressions Early
Monitor feedback trends to detect when changes negatively impact user experience
Build Training Datasets
Use highly-rated responses as examples for fine-tuning or few-shot prompting
Understand Real Usage
Learn what users actually find helpful, not just what scores well in evaluations
Quick Start
Make a request and capture the ID
Make your LLM request through Helicone with a custom request ID:
Alternative: Getting request ID from response
Alternative: Getting request ID from response
You can also try to get the Helicone ID from response headers, though this may not always be available:
API Format
Request Structure
The feedback API expects this simple format:Parameters
| Parameter | Type | Description | Example | |-----------|------|-------------|---------|| |rating | boolean | User’s feedback on the response | true (positive) or false (negative) |
| requestId | string | Helicone request ID (in URL path) | f47ac10b-58cc-4372-a567-0e02b2c3d479 |
Feedback Types
Explicit Feedback
Direct user ratings through UI interactions:- Thumbs Up/Down
- Star Ratings
- Follow-up Question
Implicit Feedback
Implicit feedback is often more valuable than explicit ratings because it reflects actual user behavior, not just their stated opinion. Most users don’t click feedback buttons, but their actions reveal satisfaction.- Code Acceptance (like Cursor)
- Engagement Patterns
- Search/Recommendation Clicks
- Task Completion
Integration Patterns
Chat Application
Collect feedback in conversational interfaces:Support Bot
Automate feedback collection based on ticket resolution:Batch Feedback Submission
Submit multiple feedback ratings efficiently:Analyzing Feedback
Using Feedback to Build Datasets
Create training datasets from highly-rated responses:Combining Feedback with Scores
Get comprehensive quality signals:Best Practices
Make It Easy
Place feedback buttons prominently and make them simple to use (one click)
Prefer Implicit
Implicit signals (acceptance, engagement) are more reliable than explicit ratings
Don't Over-Ask
Don’t prompt for feedback on every response—only when it matters
Close the Loop
Show users that their feedback leads to improvements
Combine Signals
Use both feedback AND automated scores for comprehensive quality assessment
Act on Negatives
Immediately investigate and fix patterns in negative feedback
API Reference
Key Endpoints
| Endpoint | Method | Description |
|---|---|---|
/v1/request/{requestId}/feedback | POST | Submit user feedback rating |
/v1/session/{sessionId}/feedback | POST | Submit feedback for entire session |
Related Features
Datasets
Build training datasets from highly-rated responses
Scores
Combine automated scores with user feedback for comprehensive quality assessment
Custom Properties
Segment feedback by feature, user type, or experiment
User Metrics
Track feedback trends per user or user segment
User feedback provides real-world validation of LLM response quality. Start with simple thumbs up/down, then expand to implicit signals that reflect actual user satisfaction.
