Back to app
Intake and triage

Intake and triage

Triage incoming task requests — accept one into a task or decline it with a reason.

Reviewed OperatorVertiqa 1.54+

The intake queue at /pm/intake is where incoming requests land before they become real tasks. Reach it from the Intake button in the Projects page header. Each request waits in the queue until someone triages it — accepting it into a task or declining it with a reason.

Where requests come from

Each request carries a source badge so you know how it arrived:

  • Manual — entered by a person.
  • Form — submitted through a public or embedded form.
  • Email — created from an inbound email.
  • API — pushed in by an integration.
  • Agent — raised by an AI agent.

The queue

Requests are split across three tabs:

  • Pending — waiting for triage. This is your work list.
  • Accepted — turned into tasks. Each one links to View task.
  • Declined — closed out, with the reason kept on record.

Triaging a request

On a Pending request you have two actions:

  • Accept — opens the Accept request dialog. Pick a Status (the task's starting status) and a Priority (Low, Normal, High, Urgent), then click Create task. Accepting creates a task — it's a real record from that point on, so triage deliberately.
  • Decline — opens the Decline request dialog. Add an optional Reason and click Decline. The reason stays on the declined record for accountability.

Tips

  • Work the Pending tab to zero daily. A clear intake queue is the point — No pending requests — the queue is clear. is the goal state.
  • Use the Reason field when declining even though it's optional. Future-you (and whoever submitted the request) will want to know why.
  • Set a real Priority at accept time. It's easier than re-triaging the task later.

Permissions

Accepting and declining requests requires task edit permission. Anyone who can view PM can read the queue.

Was this helpful?