Tasks
One per detected intent (§31). 11 from 8 messages.
Open
11
unresolved tasks
At risk
0
approaching SLA
Overdue
0
past SLA
Resolved today
0
closed by agent or human
Unassigned
11
nobody owns these
- newurgentdue in 2h
Invoice request
Acme Manufacturing · unassigned
- newurgentdue in 2h
Record update
Acme Manufacturing · unassigned
- newurgentdue in 2h
Shipment status
Acme Manufacturing · unassigned
- newmediumdue in 8h
POD request
Acme Manufacturing · 84721 · unassigned
- newmediumdue in 8h
Shipment status
Acme Manufacturing · 84721 · unassigned
- newmediumdue in 8h
Shipment status
unmatched · unassigned
- newmediumdue in 8h
POD request
Acme Manufacturing · 1002 · unassigned
- newmediumdue in 8h
Shipment status
Acme Manufacturing · unassigned
- newmediumdue in 8h
Shipment status
Globex Distribution · 1003 · unassigned
- newmediumdue in 8h
Rate request
Acme Manufacturing · unassigned
- newmediumdue in 8h
Shipment status
Acme Manufacturing · unassigned
Shipment status
task_em_2-0-SHIPMENT_STATUS
- Assignee
- unassigned
- Mode
- COLLABORATIVE
- Intent
- SHIPMENT_STATUS
- Shipment
- —
- Held for
- POLICY_COLLABORATIVE
- SLA
- ON_TRACK
What has to happen
Disclosure refused — sender not verified for this data
Source message
random@gmail.com
quick question
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.