Managing requests

Requests arrive from the widget on your site. Each one lands in your backlog with a status of Needs action, waiting for you to decide what to do with it.

The backlog view

Your project's main view shows all public requests (the Request category), sorted by vote count and cumulative MRR. Each card shows:

• The request title
• Vote count and subscriber count
• Current status
• Cumulative MRR from users who submitted or upvoted it (Pro and Scale plans)

Private submissions (Error, Feedback, and Question categories) appear in the Inbox, not the public backlog.

The status pipeline

Each request moves through three statuses.

Needs action

The request has arrived but no decision has been made. This is the default for every new submission.

From Needs action you can:

• Move it to In progress when you decide to work on it.
• Move it to Completed to close it directly. For example, if it is a duplicate, already shipped, or out of scope.

In progress

Work is underway. Subscribers receive a notification when a request moves to In progress (requires email configuration on your project).

Completed

The request is resolved. Subscribers receive a completion notification.

Completed requests remain visible in the backlog with a resolved badge. They can be reopened (moved back to In progress or Needs action) if the issue resurfaces or the scope changes.

Changing a status

1. 1

   Open the request

   Open any request from the backlog.

2. 2

   Pick the new status

   Use the status selector in the request header to pick the new status.

3. 3

   Confirm

   The change saves immediately and triggers any subscriber notifications.

Internal notes

Each request has an internal note: a free-form text field visible only to dashboard users. Notes never appear in the widget or to end users. Use them for:

• Triage reasoning ("Deferring to Q4: affects 3 enterprise customers")
• Engineering context ("Needs a DB schema change, blocked on migration")
• Links to related issues or PRs

Internal notes are available on every plan, including Free.

Request categories

The widget opens with a five-way choice, chosen by the user before they write anything. Only one lands on the public backlog; the other four are private.

Only Request submissions appear on the public-facing backlog where other users can upvote them. Error, Feedback, and Question submissions go directly to your private inbox and are only visible to dashboard users. Other users cannot see them or their vote counts.

For the full breakdown of all five widget flows, see Request categories.

Revenue weighting

With identity configured, the backlog sorts by cumulative MRR from all users who submitted or upvoted each request, not by raw vote count. A request from three $500/mo customers ranks above one with ten free-tier votes. Pro +

MRR is displayed per-request on the backlog card. It is sourced from the mrr or amount/interval fields in the identity token minted by your server.

Searching and filtering

Use the search bar at the top of the backlog to filter by title. You can also filter by status or category using the controls above the list. Filters are not persisted between sessions.