Tasks

One per detected intent (§31). 11 from 8 messages.

Open

unresolved tasks

At risk

approaching SLA

Overdue

past SLA

Resolved today

closed by agent or human

Unassigned

nobody owns these

All tasks 11 Open 11 Unassigned 11 Agent 0

Record update

task_em_0-1-RECORD_UPDATE_REQUEST

Assignee: unassigned
Mode: HUMAN_REQUIRED
Intent: RECORD_UPDATE_REQUEST
Shipment: —
Held for: CLAIM
SLA: ON_TRACK

What has to happen

Asks to change payment details (Routing number 987654321, Account number 35456575, Bank Main Street Bank & Trust) - verify out of band

Payment details change requested

The sender is asking to change where payments are sent. Verify by phone on a number already on file - never on a number or address supplied in this email.

Routing number: 987654321
Account number: 35456575
Bank: Main Street Bank & Trust

Draft may be incomplete

This draft may be incomplete - the original email also asks about invoice request and shipment status. Handled on the linked tasks.

Source message

john@acme-test.com

Invoice INV-1001

This message produced 3 tasks — INVOICE_REQUEST, RECORD_UPDATE_REQUEST, SHIPMENT_STATUS. §31: each one gets its own decision, its own owner and its own audit record, so they can resolve independently.

Open in review View message

Closing is two decisions, not one: whether the work is finished, and what happens to the drafted reply. The task is the work — a record update is completed by somebody updating the record, which is why nothing the agent does can close it.

Both buttons need the task table applied. Tasks are derived per request today, so state does not persist between page loads.