> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Inbox Overview

> Review signals, decisions, pull requests, topics, tickets, and other work before they become projects

Inbox is BuildBetter's unified product-ops review workspace. It replaces the older Triage experience and gives teams one place to review signals, decisions, pull requests, topics, tickets, and other work before deciding what should become a project.

<Info>
  Older `/triage` links continue to work, but the in-app navigation now refers to this workspace as **Inbox**.
</Info>

Inbox combines saved views, mixed queues, embedded details, and shareable URLs so teammates can organize work, revisit the same queue state, and make routing decisions without losing context.

## What's in a Tracked Item

A **tracked item** is the unit of work in Triage. It's a de-duped, enriched version of one or more raw signals. When `in_triage: true`, it shows up in the Signals tab. Each item has:

* A **title** (auto-generated or user-entered)
* A **type** (Bug, Feature Request, Decision, etc.) — fully customizable per workspace
* A **status** (Open, In Progress, Done, etc.) — also customizable
* An **urgency** level (1–5)
* A **triage reason** (why it landed here — high urgency, auto-flagged, manual)
* Linked **signals** (the evidence)

When you promote a tracked item, it gets `in_triage: false` and `status: in_progress` and shows up in [Projects](../Projects/overview).

## Inbox Views

Inbox includes focused views for the main inbound streams, plus saved and mixed queues for cross-stream review.

<CardGroup cols={2}>
  <Card title="Signals" icon="inbox" href="/pages/Triage/signals">
    Individual tracked items that need a routing decision. Assign, change type/status, merge duplicates, correct misclassifications, push to Linear, or promote to a project.
  </Card>

  <Card title="Decisions" icon="lightbulb" href="/pages/Triage/decisions">
    Project-setup decisions waiting on you — missing scoping, unassigned areas, stale PR reviews, customer asks with no project, unattached calls.
  </Card>

  <Card title="Clusters" icon="layer-group" href="/pages/Triage/clusters">
    Aggregated groups of customer signals from /clusters, embedded here. Promote a whole cluster to a project in one move.
  </Card>

  <Card title="PRs" icon="code-pull-request" href="/pages/Triage/prs">
    Open GitHub PRs routed for human review — especially "only Codex has reviewed" PRs. Detect plan files, sync from GitHub, bulk-promote.
  </Card>

  <Card title="Topics" icon="hashtag" href="/pages/Triage/topics">
    Live, real-time groupings of customer themes from Slack and Intercom. The canonical Topics surface — detail page, manual splits/moves, sources, and the Linear Evidence Tracker all live here.
  </Card>

  <Card title="Tickets" icon="ticket" href="/pages/Triage/tickets">
    Linear issue browser. Search and filter Linear tickets, then bulk-promote them into BuildBetter projects with the ticket auto-attached.
  </Card>
</CardGroup>

### Saved Views and Detail Pane

Use saved views to keep common queues one click away, such as:

* High-priority customer asks
* PRs waiting for evidence
* Tickets ready to promote
* Topic clusters that need review
* Decisions that require a human routing choice

The embedded detail pane lets you inspect an item, review evidence, and take action without leaving the queue. Shareable URLs preserve the selected view, filters, and detail item so a teammate can open the same context.

## Cross-Cutting Actions

These actions work on most tracked items, regardless of the tab they came from.

* **[AI Route](./ai-routing)** — let the AI suggest where the item belongs (attach to existing project or create a new one) with editable fields and confidence score.
* **[Promote](./promote-and-merge)** — move the item from triage to `/projects` (single or bulk).
* **[Merge Duplicate](./promote-and-merge#merge-duplicates)** — find similar items and merge the current one into a target.
* **Correct classification** — tell BuildBetter the item was mislabeled. The system learns.
* **Push to Linear** — create a Linear issue from the tracked item, with markdown description built from the item + linked signals.
* **Launch investigation** — kick off a Signals Background Agent run to auto-analyze and suggest actions.

## How Items Enter Inbox

* **Auto** — BuildBetter detects high-urgency / high-relevance signals and creates a tracked item with `in_triage: true`.
* **Manual** — click **New item** in the title bar to create a tracked item from scratch.
* **Routed** — clusters, PRs, and Linear tickets can be brought into the Inbox flow via their respective views.

## How Items Leave Inbox

* **Promote** to a project — most common path.
* **Merge** into an existing item.
* **Correct → Skip** — mark as "should not be tracked"; learns the classifier.

<Tip>
  You can deep-link to a view using `?tab=signals|decisions|clusters|prs|topics|tickets`. Combine with item IDs to share an Inbox view with a teammate.
</Tip>