Skip to main content
FeedBlox

Support / Inbox

Feedback Inbox

Every widget submission lands in a per-site inbox. Read comments, inspect client debug, filter by sentiment, and export when you need a spreadsheet - on every plan.

Open the Inbox

  1. Pick a site

    From the dashboard, open Sites and choose the property you want to review.

  2. Open Feedback

    Click Feedback in the site menu. New reports appear at the top with sentiment, comment text, page URL, and submit time.

  3. Open a report

    Click a row to read the full comment, extra field answer, element-trail repro summary, and client debug bundle (console, network, JS errors, optional metadata).

Filter and Search

Use sentiment filters to focus on negative, neutral, or positive reports. When triage is enabled, filter by Open, In Review, or Done. Search matches comment text and metadata where configured.

  • Sentiment chips map from faces, stars, thumbs, NPS, or scale input modes
  • Status filters appear when Feedback Triage is enabled for the site
  • Bulk select rows for archive, export, or status updates when triage is on

Inbox Without Triage

Triage is optional per site. When triage is off, the inbox stays a simple list. You can still archive or delete reports in bulk, and switch to an Archived tab to review closed items.

Export CSV

Export selected reports or the filtered list to CSV for spreadsheets, incident reviews, or sharing with stakeholders outside FeedBlox.

Client Debug on Every Plan

Each report can include recent console lines, failed fetch and XHR calls, uncaught JS errors, and optional metadata from FeedBlox.setMetadata. Pro and Max add screenshots, recordings, and AI summaries when enabled.

  • Element trail shows a structural repro summary without storing page text
  • Network URLs are path-only; query strings are stripped before storage
  • See Widget Data and GDPR for the full capture list to disclose to visitors

Examples

  • Bug report with console and network context

    Scenario: A visitor submits negative feedback on /checkout with the comment "Pay button does nothing." Your site already logged a failed POST to /api/billing/charge in the browser console.

    Outcome: The inbox row shows negative sentiment, the comment, page URL, and client debug with the failed network call and any console errors captured at submit time. Engineering opens one report instead of asking for a screen share.

  • Monday triage on negative reports only

    Scenario: Your SaaS gets a mix of praise and bug reports over the weekend. Support starts the week by opening Feedback and clicking the Negative sentiment filter.

    Outcome: Only negative rows remain visible. You work through urgent items first, then clear the filter to review neutral feature requests and positive testimonials.

  • Export after a release

    Scenario: You shipped a fix for the checkout flow and want to share every related report with product leadership in a spreadsheet.

    Outcome: Filter or search for checkout-related comments, select the matching rows, and export CSV. The file includes sentiment, comment text, page URL, and submit time for each row.

  • Simple inbox without triage

    Scenario: A small marketing site gets a handful of comments per month. You do not need Open, In Review, and Done columns.

    Outcome: Leave Feedback Triage off in Site Settings. The inbox stays a flat list. Archive handled items in bulk and use the Archived tab when you want to review what you already closed.

Related Docs