Feedback Workflow
How to triage feedback and turn validated requests into actionable Ideas on your roadmap
From raw feedback to roadmap
SeggWat uses a two-tier system to help you process user input efficiently:
- Feedback — Raw input from your users (bugs, feature requests, questions, praise)
- Ideas — Validated, curated items on your product roadmap
The feedback inbox is where everything lands. Your job is to triage it quickly and promote the valuable signals into Ideas that drive your product forward.
Feedback statuses
Every feedback item moves through a status pipeline. Use the Kanban board view in your dashboard to visualize and drag items between columns.
| Status | Purpose | When to use |
|---|---|---|
| New | Unreviewed inbox | Automatically assigned when feedback is submitted |
| Active | Under review | You've read it and are evaluating it |
| Assigned | Delegated to a team member | Someone owns the response or investigation |
| Hold | Parked intentionally | Waiting for more info, deprioritized, or blocked |
| Resolved | Addressed successfully | Bug fixed, question answered, or promoted to an Idea |
| Closed | Not actionable | Duplicate, out of scope, or won't fix |
Focus on triage velocity — move items out of "New" quickly. A fast response loop builds trust with your users.
The triage flow
Review incoming feedback
New feedback appears in the New column. Read the message, check the page path and screenshot (if attached), and decide on next steps.
Categorize and assign
Move the item to Active if you're handling it yourself, or Assigned if you're delegating. Use feedback types (Bug, Feature, Improvement, etc.) to organize.
Resolve or promote to an Idea
- Quick wins: Fix the bug or answer the question, then mark as Resolved
- Feature requests: If the request is valid and worth tracking, create an Idea from it and link the feedback. Mark the feedback as Resolved
- Duplicates or out of scope: Mark as Closed
Feedback to Ideas pipeline
When you spot a pattern — multiple users asking for the same thing — that's a signal to create an Idea.
Ideas represent validated feature requests on your product roadmap. They differ from raw feedback in key ways:
| Feedback | Ideas | |
|---|---|---|
| Source | Users submit directly | Your team curates from feedback |
| Volume | High — everything comes in | Low — only validated requests |
| Purpose | Capture raw input | Plan and prioritize work |
| Lifecycle | Triage quickly | Track to implementation |
Multiple feedback items can link to the same Idea, giving you a natural "votes" signal — the more feedback pointing to an Idea, the higher the demand.
When you link feedback to an Idea, the feedback item is marked as Resolved automatically. This keeps your triage inbox clean.