AI email assistant: what it can and cannot do for your inbox in 2026

Every mail client now has an AI button. The interesting question is not whether it can write an email, it obviously can, but which parts of inbox work it should own, and which parts you should never hand over.

What it does well

• First drafts. Given the thread, a good assistant writes a reply in your voice that needs editing, not rewriting. The saved time is the blank page.
• Triage. Newsletters, receipts and notifications are easy to classify; threads that need a human reply are easy to surface.
• Follow-ups on a schedule. The mechanical persistence that humans are worst at, with stopping rules that machines are best at.
• Summaries. A forty-message thread in five lines, when you have been away.

What it does badly

• Judgement about whether to reply at all. The most valuable inbox decision is the one to ignore something, and the assistant cannot know your priorities.
• Tone under pressure. Apologies, bad news and negotiation need a human hand on the draft; the assistant's default is smoother than the situation deserves.
• Relationships. An assistant can maintain a thread; it cannot know that this person hates being chased.

What to demand from one

Your voice, not a house style. Your keys, sent per request and never stored, if it uses a model provider on your behalf. A visible line between what the machine wrote and what you wrote. Send controls that cannot fire twice. And an off switch per contact, because the person who hates being chased exists in every address book.

How PeakLook draws the line

PeakLook drafts, triages, sequences and summarises; you read, decide and send. Anything the AI wrote or will send is gold in the interface so you always know who wrote what. Your Claude, OpenAI or Gemini key travels with each request and is never stored, and a shared send lock with two ledgers means a follow-up cannot go out twice.