SharklyTriage

Incoming work waits hereuntil someone decides

Triage is a dedicated queue, not a saved View. Open an item, decide, and move on: Accept it into the workflow, Decline it, mark it as a duplicate, or Snooze it until later.

Sharkly Triage queue with Accept, Decline, Mark duplicate, and Snooze

Used by teams at

  • Amazon
  • Intuit
  • Markel
  • AT&T
  • Veeam
  • Maersk

Queue, type, assign

Intake is a decision, not a pile

New work should not land on the board until someone accepts it. Triage holds that decision in one place.

Work the queue one item at a time

See the pending count, open the next item, and choose Accept, Decline, Mark duplicate, or Snooze without rebuilding a filter.

Type the work before it spreads

A request, a bug, and a ticket should not share a form. Space-owned types give each item the fields and statuses it needs after it leaves Triage.

Hand accepted work to people or Agents

After Accept, a person stays responsible. An Agent or Crew can take the execution slot. The history remains on the same Task.

From incoming to assigned

Decide first. Then let the workflow run.

Triage sits in front of the board. Slack, Jira, and manual creation can feed it. Public forms and email intake are not part of this product today.

01Queue

Give incoming work a dedicated queue

Triage is built for deciding. It is not a saved View you reconstruct every morning. Items in the triage status stay here until someone acts.

  • See the pending count and work through items one by one
  • Accept, Decline, Mark duplicate, or Snooze from the same detail
  • Keep owner, status, and history on the Task after it leaves the queue
Triage queue with decision actions on an incoming item
02Types

Accept into the right process

When an item is accepted, its type already knows which fields and Workflow apply. Intake stays structured without becoming a generic list.

  • Add types such as Request, Ticket, Issue, or Bug
  • Bind the statuses and custom fields that type actually needs
  • Keep labels for tags; use types for real process differences
Task types used after an item leaves Triage
03Assign

Route accepted work to a person or Agent

A person remains accountable. An Agent or Crew executes the well-specified follow-up. Comments and Inbox keep the decision on the same item.

  • Assign people, a Crew, or an Agent after Accept
  • Keep the owner visible while an Agent does the repeating work
  • Return blockers and review to Inbox instead of a private chat
Accepted Triage item assigned to a person and an Agent
04From chat

Start intake from Slack or a conversation

Create a Task from Slack, or turn an Agent Chat into tracked work. If the Space has Triage enabled, new items in the triage status wait in the queue.

  • Create Tasks from Slack shortcuts and slash commands
  • Turn a Chat exploration into a Task when it needs an owner
  • Do not expect public forms or email intake in this product today
Creating tracked work from chat that can land in Triage

The intake system

What Triage is, and what it is not

Triage is a queue with decisions. It is not a View, not a form builder, and not a replacement for the Task after Accept.

Triage queue

Items in the triage status, waiting for Accept, Decline, duplicate, or Snooze.

Task types

The process each accepted item enters, with its own fields and Workflow.

Inbox

Attention for replies, review, and failed runs after work leaves the queue.

Slack

A shipped source for creating Tasks that can land in Triage.

Jira

Synced or imported issues can enter the Space and wait in Triage when configured.

Agents

Execution after a person has accepted the item — not a substitute for the decision.

Meet intake where it starts

Slack, Jira, and the queue you already run

Bring requests in from chat or a connected tracker. Keep the decision in Triage. Let Agents run only after someone accepts the work.

JiraGitHubSlack

Connected features

Triage is the front door, not the whole house

Accepted work becomes a Task on the plan. Repeating follow-up belongs in Automations.

Quality of life, built in

The details that keep the queue honest

Ops only works if incoming work cannot skip the decision.

Accept, Decline, Mark duplicate, and Snooze
Pending count for the current queue
Space-owned types waiting after Accept
Snooze without losing the original item
History that survives leaving Triage
Inbox for what needs a person after the decision

Stop letting incoming work land on the board unread

Turn on Triage, decide item by item, and assign people or Agents only after the work is accepted.

Start

Turn on Triage in three steps

Enable the queue, give incoming work a type, then accept the first item and assign it.

01

Enable Triage on a Space

Incoming items in the triage status wait here until someone Accepts, Declines, or Snoozes them.

02

Set the types you actually run

Add Request, Ticket, Issue, or Bug so accepted work enters the right Workflow.

03

Accept and assign

Decide on the first item, then put a person and optionally an Agent on the Task.

FAQ

Triage, without inventing a form product

What is the difference between Triage and a saved View?

+

A View is a saved way to inspect Tasks. Triage is a dedicated intake queue for items in the triage status. It is built for deciding: Accept, Decline, mark as a duplicate, or Snooze.

How do requests get into Triage?

+

People can create Tasks in the Space, Slack can create a Task, Jira can sync or import work, and an Agent Chat can become a Task. If the Space has Triage enabled, items in the triage status appear in the queue. Public forms and email intake are not shipped.

Does Accept create a new Task?

+

No. The incoming item is already a Task. Accept moves it into the type’s Workflow. Decline, duplicate, and Snooze also act on that same Task.

Can an Agent empty the Triage queue?

+

People remain responsible for the decision. An Agent can execute after the item is accepted, or run a recurring check as an Automation. Do not treat the Agent as a replacement for Accept.

What happens when I Snooze?

+

The item leaves the current queue until later without being accepted or declined. It remains the same Task, with its history intact.

Is Triage only for operations teams?

+

No. Any Space that needs a decision before work hits the board can use it — product intake, bugs, internal requests. The Operations solution page shows one way Sharkly teams run it.