Split Inbox
Consequence first, chronology never
Threads that change a decision sit at the top. Receipts, digests and newsletters are filed while you sleep.
Everything Dispatch does, and what it will not do
Three surfaces, one instruction language, and a log of every decision. Nothing here guesses quietly: if Dispatch is not sure, it leaves the message alone and tells you why.
Gmail, Google Workspace, Microsoft 365 and Exchange Online. About four minutes to connect.
Inbox
It has already read everything you have not
Every thread arrives summarised, sorted by what it changes rather than when it landed, and stripped of the two hundred messages that only needed filing. Nothing is deleted and nothing is hidden — the filing is a list you can open.
Four things that happen before you sit down
None of them need a rule builder, and all of them are reversible for thirty days.
Auto-drafts
Written the way you write
Your length, your sign-off, your habit of using first names. Facts pulled in and cited.
Follow-ups
Nobody gets forgotten
Dispatch counts the days since you asked, and chases in your voice when it has been too many.
Briefs
When a thread should stop being a thread
Fourteen replies become one document with the decisions at the top, the open questions in the middle, and everyone who argued still in the room.
Agents
Write the instruction once. It runs on Sunday too.
An agent is a sentence, not a flowchart. Dispatch reads it, tells you what it intends to do, and then does that — on our servers, whether or not the tab is open.
- Plain English, not a rule builder
- Chase anyone who has not replied to a quote in four days, politely. That is the whole configuration.
- It tells you before it acts
- Every new instruction is played back as a plan you approve once. After that it just runs.
- A log you can argue with
- Each action is written down with the reason behind it, and every one of them can be undone for thirty days.
Follow-ups
Ran 06:40 · 9 actions
- Chased Ambient on the quote
- Chased Meridian on the quote
- Skipped Northbeam — they replied
- Held Talia — out of office until Monday
Every action reversible until 27 September
Briefs
The thread ends. The decision does not.
When a thread has said everything it is going to say, Dispatch turns it into a document: what was decided at the top, what is still open in the middle, and every person who argued still in the room.
See how briefs workRenewal — Northbeam
From 14 replies · 3 people
Decided
- Three-year term at the 2025 rate
- Legal sign-off on the liability cap
Still open
- Who owns the migration window
- Whether the pilot seats roll over
In the room — Rowan, Marisa and Dev, with the original thread attached
Approved by the security team, not tolerated by them
Dispatch is a client in front of your provider, not a second copy of your mail. Nothing is used to train a shared model, every automated decision is written down before it happens, and the keys can be yours.
- SOC 2 Type II
- ISO 27001
- HIPAA BAA
- EU data residency
Audit log
Exported hourly to your SIEM
- Filed · Invoice 4471
- Matched instruction: file paid invoices
- Escalated · Customs hold, DE
- No instruction matched. Routed to a person.
- Reversed · Weekly digest
- Undone by r.vasquez, 08:12, within 30 days
- 4.2h
- given back per person, per week
- 94%
- of routine threads never reach a human
- 11min
- median first response, down from 6 hours
- 0
- messages used to train a shared model
Try it on one mailbox first
Connect a single address, leave the rest alone, and see what a week looks like.