Operator console
Ticket queue
Requests Maya filed through the agent, with the agent's own summary. Triage actions are shown disabled: this build is read-only and says so rather than pretending to save.
- Rows
- 3
- Open
- 1
- Unassigned
- 2
- Source
- example fixture
Ticket writes are not wired in this build: no live API. The contract defines PATCH /ops/tickets/:id, and this console calls nothing.
| Ticket | Status | Intent | Priority | Assignee | Filed | Agent summary | Triage |
|---|---|---|---|---|---|---|---|
| Request: move Thursday's shootExampletk_1 | IN_PROGRESS | SCHEDULING | HIGH | elena | 2026-10-01 02:19Z | Wants the confirmed production moved. Conflicts with a shooting day already booked. | |
| Question: payment date for the last campaignExampletk_2 | TRIAGED | MONEY | NORMAL | Unassigned | 2026-09-30 02:19Z | Needs the invoice and payment status. No amount quoted by the agent. | |
| Idea: autumn content seriesExampletk_3 | OPEN | CONTENT | LOW | Unassigned | 2026-09-29 02:19Z | Content proposal with no brand attached yet. |
3 tickets listed. Triage controls render disabled: a read-only console states what it cannot do instead of offering a button that fails.