Caixa de entrada dos funcionários digitais

NEED YOU: the agent has stopped and will not continue without a decision from you — and while it waits, that work does not happen. CONFIRM FIRST: it has already prepared what it would do and only needs your yes; nothing has been done yet. FOR YOUR INFORMATION: there is nothing to decide, and ignoring it is a legitimate answer. The separation exists because a single list of "pending items" makes the urgent look like the informational, and people end up opening neither.

Because it gathers, it does not grant. Each item leads to the screen that resolves it — the reconciliation in the Reconciler, the purchase in the Buyer, the month item in the Closing, the decision in the Trail — and that is where permission and action already live. Reimplementing six approval flows here would create a copy, and the first time the copy diverged from the original nobody would notice.

Each item carries the subject's screen, and whoever does not have access to that screen does not receive the item in the inbox. Proposal and reconciliation amounts come out masked for those who cannot View Values — masked, not removed: knowing that a money decision is waiting is different from seeing the number.

The inbox reads the real state of each subject every time it opens; it does not keep a copy. An item disappears when someone resolved it on the source screen, when its deadline passed, or when the agent itself completed the step it had stopped at. There is no "mark as read" here on purpose: it would allow clearing the inbox without having done anything, and the number would go back to lying.

Items that the source screen resolves with a YES appear with a checkbox: proposed reconciliation, purchase above the approval limit, decision awaiting review and monitoring finding. Resolving from here calls exactly the same method that the button on that screen calls — there is no second approval rule, and that's why nothing diverges when the first one changes. Whatever requires a decision that is not a yes still only leads to the screen: an agent step waiting for data, a closing item that needs a note. The reason is simple: copying those flows into the inbox would make the two diverge without anyone seeing.

It's the inbox thermometer. Three items from yesterday are healthy: the agents worked and stopped where they should stop. Three items from forty days ago mean that someone raised the agents to "confirm first" and never came back — the brake exists, the queue grows, and the work that should happen doesn't. When this becomes routine, the way forward is to raise the autonomy of the steps you already trust, on the Agent autonomy screen.