Skip to main content

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.

The Triage settings page (Settings → Features → Triage) is where you configure how the system creates, classifies, and prioritizes tracked items. It covers three areas: routing config (what gets routed to triage), item types (what categories exist), and the ARR source field shared with Projects.
The /settings/features/tracked-items URL redirects here. The Triage and Tracked Items configurations are the same surface.

Routing Configuration

Controls whether new signals are automatically routed into triage and what rules the AI follows.

Enable automatic routing

A toggle. When on, new extractions are auto-classified against your item types and routed into triage if they match a routing rule. When off, items only enter triage through manual creation or via the AI Route action on individual signals.

Routing Instructions

A free-text prompt that tells the AI what kinds of extractions should become triage items. Sent alongside the list of your item types when the classifier runs. Example prompt:
Route into triage if the extraction describes: a bug report, feature request, customer commitment, sales objection, or churn risk. Skip general observations and positive feedback.
The more specific your prompt, the fewer false positives you’ll see in the inbox.

Similarity Threshold

Numeric value, default 0.85. Controls how similar a new extraction must be to an existing tracked item before the system merges it into the existing item instead of creating a new one. Higher = fewer merges (more standalone items); lower = more merges. Tune this based on whether you find yourself manually merging duplicates often (lower it) or seeing items merged that shouldn’t be (raise it).

Item Types

The categories that classify every tracked item. Each type carries a name, slug, description, color, and an optional triage rule prompt.

Seed Defaults

If your workspace has no types yet, the Seed Defaults button populates six standard types:
TypeColorDefault Triage Rule
BugRedPut in triage immediately when created.
Feature RequestPurplePut in triage when there are 10+ extractions attached, or when a company with significant revenue mentions this.
CommitmentAmberPut in triage immediately when created.
ObjectionPinkPut in triage immediately when created.
Churn RiskRedPut in triage immediately when created.
IdeaCyan(No auto-triage rule)
You can edit any default and add your own.

Adding a Custom Type

Click Add Type and provide:
  • Name — display label (e.g., “Compliance Request”)
  • Slug — URL-safe identifier
  • Description — what this type represents
  • Color — hex color for the badge
  • Triage rule prompt — natural-language rule for when items of this type should enter triage

Triage Rule Prompts

Each type can have its own rule prompt that fires when the routing classifier considers an item. Useful for:
  • Volume-gated types“Put in triage only when there are 10 or more extractions attached, or when a Tier 1 customer mentions this.”
  • Always-triage types“Put in triage immediately when created.”
  • Never-triage types — leave blank to skip auto-triage for this type (still classifiable manually)
The classifier reads each type’s rule plus your global routing prompt to decide.

Editing & Deleting

Click any row to edit. Click the trash icon to delete — be careful, deleting a type orphans its tracked items (they keep the items but lose the type label).

ARR Source Field

A single setting shared between Triage and Projects: which company metadata field stores each customer’s ARR. This drives:

Choosing the Right Field

The settings UI lists every company metadata field in your workspace, sorted by how many companies have a populated value. Pick the field with the most coverage — empty fields make the rollups look broken. A green check next to a field name marks the currently selected source. Click another field to switch; takes effect immediately.

When Companies Don’t Have ARR

If a linked company has no value in the configured ARR field, it’s treated as 0 in rollups. No error, no warning — just a quieter contribution to the totals.

How These Settings Connect

  • Routing config decides what shows up in Triage Signals.
  • Item types drive the Type dropdown in detail panes and the chips on every row.
  • ARR source is the single source of truth for revenue numbers across Triage, Projects, and Topics.
If your inbox feels noisy, the first lever is the Routing Instructions prompt — tighten it before changing the similarity threshold. The threshold affects merging; the prompt affects whether items ever land in triage in the first place.