Mailex.ai
Log inStart with Gmail
All posts
OpsJul 8, 2026 · 6 min read

The workflow that gets dispatch teams to inbox zero

Reply-and-close, snooze-to-pickup-date, and the one rule that keeps Unassigned empty.

PA
Priya Anand
Ops research

Inbox zero for a dispatch team is not about answering everything. It is about making sure no email is sitting in a state where nobody knows whether it is handled. The queue is honest when every open thread has an owner and a reason to still be open.

Reply and close, not reply and leave

The default habit in most inboxes is to reply and move on, which leaves a thread technically open forever. Flip it. Send and close in one keystroke. If the broker writes back, the thread reopens and lands back in the queue on its own. You are not losing anything by closing; you are just refusing to count finished work as unfinished.

Snooze to the moment you actually need it

A rate con you cannot action until pickup on Thursday does not belong in your live queue on Monday. Snooze it to Thursday morning. It disappears and comes back exactly when it is useful. Teams that snooze aggressively run a queue that reflects today, not the whole week piled on top of itself.

The one rule: Unassigned must trend to empty

Pick a single number and defend it. Unassigned should be empty by the end of every shift. Not "mostly handled", empty. When a thread has no owner, nobody is accountable for it, and that is where SLAs quietly die. Round-robin assignment on arrival gets you most of the way; a lead sweeping the Unassigned view at end of shift closes the gap.

The teams that hold this get something better than a clean screen. They get a queue they can trust at a glance, which is the whole point of working out of a shared inbox instead of forwarding email around.