The Inbox is the cockpit’s load-bearing surface. Every agent-drafted proposal — across every brand, every channel, every domain — lands here. There are no per-agent queues. There are no per-channel inboxes. One queue, filterable.Documentation Index
Fetch the complete documentation index at: https://docs.meshpilot.app/llms.txt
Use this file to discover all available pages before exploring further.
The KPI strip
Pending now
Approved today
Rejected today
Expiring soon
How a proposal looks
Each row tells you:- From — the agent that drafted it (Ads, Sales, Social, Creative, Voice, or SEO), as an attribution badge.
- Brand — which brand it touches.
- What it proposes — a one-line summary plus a payload preview.
- Why — the agent’s reasoning, citing the data it acted on.
- Predicted impact — where applicable (e.g. “saves ~₹12k/day at current spend”).
- Three actions — Approve, Edit, Reject.
Filters
Slice the queue by brand, source agent, domain (Ads / Sales / Social / Creative / Voice / SEO), and urgency. Filters persist across sessions per operator.Batch actions
Select multiple rows and approve, reject, or expire them in one move. Useful when several low-risk proposals have stacked up (e.g. ten ad-set budget tweaks of the same shape).What happens after you decide
- Approve → the orchestration engine writes the change back to the source-of-truth tool. The row moves to History.
- Edit → tweak the payload (budget number, copy text, target list) before approving.
- Reject → the row moves to History with your decision noted. The relevant agent reads the rejection signal back into the Brain so it adjusts future proposals.
- Expire → proposals that have a window (e.g. time-sensitive bid changes) auto-expire if untouched. Expired rows appear in History as well.
Inbox is not where you go to inspect work that’s already running. For that, head to the relevant Work surface (Ads, Sales, etc.) or the History audit timeline.
Open Inbox
Go triage.