Triage and prioritization

This workflow helps a workspace admin keep conversation and request decisions fast, consistent, and evidence-based.

Quick actions

1. Prepare the queue

1. Open Inbox for your workspace.
2. Use Waiting for answer or a custom view when you need a narrower queue. Search ignores the selected view.
3. Group obviously related conversations before deep review.

2. Judge actionability

For each conversation, determine:

• Is the problem statement clear?
• Is user impact stated or inferable?
• Is the request in scope for your product roadmap?

Use an internal note for follow-up. Do not turn unclear text into a request yet.

3. Link or create requests and issues

1. Review AI proposals from the conversation or selected messages. Accept, edit, or remove each one.
2. Create a sourced request manually when you already know the ask. Manual requests default public, with a preview when the source is private.
3. Keep provenance on every request so you can return to the message, capture, or internal note that produced it.
4. Create an issue independently, or from one or more sourced requests.

4. Prioritize

Prioritize using:

• paying conversations and longest waiting, when using Priority ordering
• user impact severity
• number of related requests
• strategic relevance for the current roadmap window

5. Assign and operationalize

1. Assign the conversation, snooze it, or mark it done.
2. Sync linked issues to Linear when execution should begin.
3. Track issue status until resolution.

Expected result

• Every actionable ask is a sourced request with live provenance.
• Duplicate demand strengthens existing issues instead of creating noise.
• The team can explain why each top-priority issue was chosen.

Common failure patterns

• Creating new issues for duplicate requests.
• Prioritizing without conversation evidence.
• Leaving unclear conversations unresolved in Inbox.
• Delaying integration troubleshooting while triage quality drops.