Inbox

The Inbox is where your agents reach you. When an agent needs an answer, hits a blocker, finishes something worth showing, or wants to recommend a connection, it sends a message here instead of failing silently — questions arrive as Urgent; updates, results, and blockers arrive at the priority the agent judges right.

This is the other half of delegation. Handing work to agents only saves time if you don’t have to babysit the runs, and you can stop babysitting only if the moments that genuinely need you reliably surface. The Inbox is that contract: an agent that needs a decision, a credential, or a review sends the item here with a priority instead of stalling quietly — including assignment runs that hit a blocker on a morning nobody was watching.

What arrives, and at which priority

Example items, one per priority:

• Urgent — a question the agent needs answered: “The export has two revenue columns, booked and recognized — which should the pipeline report use?” The agent is waiting on you, so questions always arrive Urgent.
• Important — a blocker on scheduled work that isn’t racing a clock: “The CRM credentials have expired; Monday’s pipeline report can’t run until the integration is reconnected.” Worth your attention today, not this minute.
• Normal — routine updates and ambient context: “Weekly competitor sweep finished — two rows updated, no pricing changes.” Skim it now or let it wait.

Triage

Tabs slice the list by priority — All, Urgent (“needs your attention soon”), Important (“worth your attention but not time-sensitive”), and Normal (“routine updates and ambient context”) — with a separate view for items you’ve marked Done. Mark items read, move them between priorities, or Snooze them (later today, tomorrow, later this week, this weekend, next week, or a date you pick).

The agent’s priority is a starting point, and you can override it: if a Normal update turns out to matter, move it up; if an Important item can wait for Friday’s review, snooze it to later this week. Snoozing to the time you’ll actually act keeps the queue honest — “this weekend” for reading, “next week” for a decision that’s waiting on something else.

Acting on an item

Open an item and it’s a thread: reply to answer the agent in place, forward it to another agent, or jump to the originating session for the full context. Integration recommendations come with one-click Connect (or Don’t ask again). Attached work products open right from the thread.

Reply covers the common case — the revenue-column question above needs one sentence (“use recognized”), typed right in the thread. Forward covers the question that reached the wrong desk: an agent asks you about data another agent owns, and forwarding puts the question where the answer is. And when a one-line item isn’t enough context to decide, the jump to the originating session shows exactly what the agent was doing when it wrote to you. A recommendation works the same way in miniature: an agent that keeps needing data from a system you haven’t connected can suggest the integration, and Connect acts on it from the thread — or Don’t ask again closes the subject.

Note

An Urgent question usually means an agent is waiting on you, so the work it was doing can’t move until you answer. That’s the case for treating Urgent items the way you’d treat a teammate standing at your desk, and Normal ones the way you’d treat a status channel.

Clear the queue and the Inbox says so: “You’re all caught up! Your agents are handling the rest.”