An inbox where replies are already written

A hundred decisions before lunch

Investor updates, vendor threads, introductions, a customer question forwarded by the team, three people trying to find a meeting time. Every one of them needs a decision, and every decision arrives wrapped in a paragraph somebody has to write.

The old shape of that day is familiar: the inbox becomes a list of small debts, the important reply gets drafted at eleven at night, and the fast answers go out first while the ones that matter wait.

Now, by the time he opens a message, the reply is already underneath it: his phrasing, the thread taken into account, and what the workspace knows about the sender folded in.

Where the drafts come from

Each draft is built from the thread and from the record around it: the calendar, the files, what was agreed the last time this person wrote. It answers the way he would, because it has read the way he answers.

The voice is the part people notice. Short where he is short, warm where he is warm, and firm in the places he has always been firm. Colleagues cannot tell which sentences he typed, because increasingly the honest answer is none of them.

Sometimes the draft carries an answer he did not have yet: a delivery date pulled from a thread he had not read, a figure from a document he had not opened. He approves his own mail and learns something from it.

Approval is the interface

Nothing sends itself. The tap is the decision, and the decision is the part of the job that actually needs him, which is why it is the only part left.

When a draft is wrong he edits it, and the edit is not wasted: the next draft on that subject comes back closer. The assistant is not replacing his judgement; it is memorising it.

What a day of mail costs now

The inbox went from an evening of typing to a pass between meetings: read, adjust the odd sentence, approve. The replies go out the same day in his own voice, and the pile that used to follow him home stays empty.