Skip to main content
FeedBlox

Support / Feedback Triage

Feedback Triage

An inbox full of reports is not a workflow. Triage gives each submission a status, tags, and internal notes so your team knows what is new, what is being investigated, and what shipped.

Triage is available on all plans. Collaborators on Pro and Max can triage without sharing the owner login.

Enable Triage for a Site

  1. Open Site Settings

    From the site menu, open Settings and scroll to Features.

  2. Turn on Feedback Triage

    Check Feedback Triage and click Save Features. The Triage page and inbox status columns appear for that site.

  3. Disable when you want a simple inbox

    Turn triage off anytime. The triage board hides and the inbox returns to a flat list with archive and delete bulk actions.

Statuses

Each report moves through three statuses:

  • Open - new or not yet picked up
  • In Review - someone is investigating or building a fix
  • Done - resolved, shipped, or no action needed

Tags and Internal Notes

Add manual tags such as billing, onboarding, or mobile. Internal notes stay inside FeedBlox; visitors only see their original comment. Tags show as chips on inbox rows and in report details.

Bulk Updates

Select multiple reports in the inbox and change status in one action after a release or incident. Useful when a deploy fixes a batch of related negative reports.

Triage Board

Open Triage in the site menu for a board view of Open, In Review, and Done columns. Triage presets help apply common tag combinations quickly during review sessions.

Examples

  • New bug report lands as Open

    Scenario: A visitor leaves negative feedback: "Export CSV downloads an empty file." Triage is enabled for the site.

    Outcome: The report appears in the inbox and on the Triage board under Open. No one has picked it up yet, so the team can see at a glance what still needs a first look.

  • Engineering picks up the investigation

    Scenario: A developer opens the report, reproduces the issue using the element trail and client debug, and starts a fix branch.

    Outcome: They change status to In Review and add an internal note: "Repro on Chrome 124, export endpoint returns 500 for accounts over 10k rows." The visitor never sees that note.

  • Tag and route by area

    Scenario: Product sees a neutral comment asking for dark mode. Support adds the tag feature-request and leaves the report Open for the weekly product review.

    Outcome: The tag chip shows on the inbox row. During product planning, filter or scan for feature-request tagged items instead of re-reading every comment.

  • Bulk close after a deploy

    Scenario: You ship a patch that fixes five related negative reports about the same login error.

    Outcome: Select all five rows in the inbox, set status to Done in one bulk action, and optionally add a shared internal note that release 2.14 resolved the auth redirect bug.

Related Docs