Workflow
Workflow
Follow a piece of feedback from inbox to shipped in Feedjolt: submitted, triaged, discussed, built, and shipped. Plus habits that keep your queue healthy.
The journey of a single piece of feedback, in five steps:
- Submitted - by a customer (portal or widget) or a teammate (dashboard).
- Triaged - moved to the right status, tagged, occasionally merged with a duplicate.
- Discussed - public comments with the customer, internal notes among the team.
- Built - status moves to "In progress", optionally synced to your project tracker via Linear or webhook.
- Shipped - status flips to "Shipped". The customer gets a notification. Optionally promoted to a changelog entry.
The pages
- Triage - your daily routine for the inbox.
- Merging duplicates - how to combine two posts cleanly.
- Internal notes - private team threads.
- Notifications - what triggers email/Slack pings.
Habit ideas
- Triage on a schedule. Every Monday morning. Daily for high-volume products. Inbox zero is overrated; inbox-not-six-months-old is the goal.
- Merge aggressively. Two posts saying the same thing kill momentum. Pick the better-worded one and merge.
- Update statuses early. "Planned" tells customers you heard them. Don't wait to be 100% certain.
- Always reply to "Shipped". A short comment ("This is live in v2.4 - thanks for filing!") closes the loop.
Roles & permissions
Feedjolt has three workspace roles, OWNER, ADMIN, and CONTRIBUTOR, plus end users. See the full permission matrix covering posts, voting, billing, and more.
Triage
Your daily Feedjolt triage routine: read the inbox, tag posts, set statuses, and merge duplicates. Includes bulk actions, filters, saved views, and backlog tips.