How to use AI to manage your email inbox

Using AI to manage your email inbox works, with one condition: it triages and drafts, you decide and send. Hand it the reading and the first version. Never hand it the judgment about what matters or the send button.

Three jobs it does well. Sorting the overnight pile into what needs you today and what does not. Compressing a forty-message thread into the decision and the open question. Producing the first version of a reply you were always going to write anyway.

The part that actually eats the time

Nobody loses an hour to typing. The hour goes on re-reading: opening the same thread three times because the first two readings did not stick, scrolling back to check whether the deadline moved, reconstructing who agreed to what before you can answer a one-line question.

That reconstruction is exactly what a model is good at, because the whole thread is right there and it has no ego about reading it twice.

The inbox does not cost you an hour because you type slowly. It costs you an hour because you read everything twice.

Where AI to manage your email inbox actually helps

Start with the thread summary, because the send button stays with you. It still needs checking. Take the worst thread in your inbox, the one with fourteen replies and two people who top-post, and ask for the decision reached, what is still open, and who owes whom what by when. You have a working handover without giving the tool authority to answer for you. For a worked prompt and a checkable example, see the email thread summary guide.

Then triage. Copilot in Outlook can prioritise incoming mail, though availability and exclusions depend on the account and setup. Once a day, not continuously: ask for the overnight mail grouped into needs a reply today, needs a decision from someone else, and read later. Review that grouping before acting on it. A low-priority label is a suggestion, not permission to miss a deadline.

Drafting is third, and it is where people start, which is why they get disappointed. A first draft from a model is a serviceable shape with your judgment missing. It is worth having when the reply is administrative and worth skipping when the reply is delicate, which in practice means the ones you were dreading are still yours.

The habit that makes drafting work is giving it your rules once rather than your instructions every time. How long your replies run, whether you open with pleasantries, that you never commit to a date without checking, that a client in Cantonese gets a different register than a counterparty in London. That standing brief is the difference between a draft you edit and a draft you delete, and the ones worth copying are in the free prompt library.

The rules that keep it out of trouble

Keep sending manual. An auto-reply with the wrong tone, number or recipient can undo the time you saved. Review the recipient, attachments, figures and commitments before you press Send.

Watch what leaves the building. Your inbox is the densest concentration of client names, fees and unannounced deals you own. A tool inside your firm's own tenancy may have stronger controls, but its configuration and your policy still matter. If you are pasting a thread into a separate website, the data question needs answering before the habit sets.

And read the summary as an analyst, not a proofreader. The failure mode is not invention, it is omission: the conditional that made the yes a maybe, the one line where someone objected politely. The same trap runs through AI note-taking for meetings, and it is worth knowing how to check AI for errors before a summary becomes your record of what was agreed.

A local caveat

Some decisions in a Hong Kong week are not in the inbox at all. They are on WhatsApp, and no mail tool sees them, so a tidy inbox can leave you confidently out of date. Bilingual threads are the second gap: a message that switches into Chinese for a sensitive clause may come back thinner in the summary, and thinner reads like agreement.

Neither of those makes the habit not worth having. They mean the inbox is one surface, not the whole record.

What to do with the hour

The honest limit here is that email is a symptom. Automating replies to a badly run process makes the process faster, not better, and some of what is in there should not be answered at all.

Still, the inbox is a useful first workflow to rebuild when re-reading and drafting are swallowing the day. If you want yours rebuilt around the way you actually work rather than a generic set of filters, start here.