Operational work queue
Operations Memory
Review AI-maintained follow-up tasks, client operational state, and source events from email, calls, SMS, and synced workflows.
Needs attention first
Visible event rows
Operational state engine
What Needs Attention
Start with these open operational tasks, then use the queue below to clear or assign work.
Run an intake or review the event timeline if you expected follow-up items. Cleared tasks stay in memory without cluttering the active queue.
Review Queue
Search the visible tasks, client state, and event timeline. Use bulk actions only after confirming the rows are safe to clear.
Auto-Generated Tasks
Tasks are outputs from events. Duplicate calendar/update emails can be collapsed here without deleting the source timeline.
| Priority | Task | Client | Type | Due | Action | |
|---|---|---|---|---|---|---|
| No open operational tasks yet. Run a Gmail intake to start building memory. | ||||||
Client Operational State
Clients with watch or needs-review status based on recent operational signals.
| Client | Status | Urgency | Summary | Next Action | Updated |
|---|---|---|---|---|---|
| No client state snapshots yet. | |||||
Operational Event Timeline
Source evidence behind the task queue. Use details/source links before teaching a new intake rule.
| Type | Event | Client | When | Source |
|---|---|---|---|---|
| No operational events stored yet. | ||||