Approval Inbox
An approval inbox is a queue of high-stakes agent decisions — spend, sends, deploys — that the human owner explicitly approves or rejects before execution.
In plain English
An approval inbox is where the agent pauses before doing anything expensive or irreversible and asks the owner for a yes. Each item in the inbox is a structured card: the proposed action, the reason, the cost, the evidence. The owner clicks approve, reject, or edit. Reject sends feedback back to the agent; edit lets them tweak and approve in one motion.
The pattern exists because high autonomy does not mean zero supervision — it means supervising at the right altitude. Instead of watching every tool call, the owner only sees the decisions that matter. The inbox becomes a short, meaningful list rather than a flood of micro-events.
Why it matters for Black Box
Black Box's Approval Inbox is the primary place owners interact with the system. The product is UI-driven, not chat-first: the agent surfaces cards, and the owner clicks. Spend-over-threshold, public-sends, production-deploys, and custom-flagged actions all land here by default.
Examples
- A cold-email batch of 20 drafts awaiting one-click approval.
- A proposed $150 ad-budget increase with expected-return rationale.
- A landing-page deploy ready to go live once approved.