By DLVX · 7 min read · Updated 12 October 2026

AI for email: clear the work, not just the inbox

  • Use built-in AI first when the job is summarising threads or improving drafts.
  • Consider a specialist inbox when search, triage and repeat replies dominate your day.
  • Build a custom flow only when the enquiry needs current business records, clear handoffs and evidence of completion.
On this page

Which inbox problem are we solving?

An empty inbox can hide unfinished work. A message may be archived while its quote, refund decision or customer follow-up is still waiting. We start by naming the work behind the email: understand it, find a fact, decide who owns it, prepare a reply or complete a business action.

Separate personal productivity from a shared service process. A founder may need help finding a promise buried in a long thread. A team answering enquiries may need ownership, escalation and a current price source. Faster prose helps both, but it does not settle responsibility.

For a first trial, choose one mailbox and one message category. Use historical examples with unnecessary personal data removed. Keep the original thread available so the reviewer can check what the assistant omitted.

Which route fits your team?

RouteGood first fitMain tradeoff
Gemini in GmailA Google Workspace team drafting and finding information in existing mailEligibility, language and feature access need checking.
Copilot in OutlookA Microsoft team summarising threads and drafting inside OutlookMailbox type and the specific Copilot experience matter.
Superhuman MailPeople who spend much of their day navigating and replying to mailAnother paid interface and another service with data access.
ShortwaveGmail teams wanting AI search, summaries and inbox organisationMicrosoft 365 and Exchange are not currently supported.
Custom workflowAn enquiry must consult approved records, prepare work and route an exceptionYou own the rules, monitoring, recovery and ongoing maintenance.

These are trial recommendations, not measured claims that one product saves more time. The right result is a correctly completed enquiry with less human effort.

When are Gmail and Outlook enough?

Gemini in Gmail

Google documents thread summaries, suggested replies, drafting and finding information in email and Drive. Access requires an eligible plan, and availability varies by feature and language. That makes it a sensible first trial when the source already lives in Workspace. The advantage is working beside the message. The limitation is that finding a passage does not prove it is your current approved policy. Gemini in Gmail help.

Ask for the commitment, date, unresolved question and source message before asking for a reply. Check the result against the actual thread. For Thai enquiries, test the feature you intend to use with realistic mixed-language messages instead of assuming every AI feature shares the same language coverage.

Copilot in Outlook

Microsoft documents summarising, drafting and coaching. Shared mailbox support needs particular care: the general FAQ and the newer shared-mailbox article describe different boundaries. The latter supports summary and draft in Copilot Chat, while listing direct actions as unavailable in those mailboxes. Test your exact client and account. Outlook FAQ and shared mailbox guidance.

Our practical recommendation is to try built-in assistance before replacing a familiar inbox. Keep it if the job ends with a reviewed draft and the extra system would add more administration than value.

When do Superhuman and Shortwave earn a place?

Superhuman Mail

Superhuman lists shared conversations, team comments and AI features on Starter. Business adds Auto Drafts, Ask AI and Custom Auto Labels. As of October 2026, the official help page lists Starter at $30 monthly or $300 yearly, and Business at $40 monthly or $396 yearly. Enterprise is quoted. These are US dollar references; verify the exact Mail or suite package at checkout. Superhuman Mail plans.

We would trial it for a person who repeatedly searches, sorts and replies throughout the day. The upside is a focused inbox workflow. The downside is paying for another interface before knowing whether the friction is email handling or an unresolved business process. An auto-draft cannot decide a discount policy for you.

Shortwave

Shortwave lists AI search, summaries, attachment analysis and AI filters. Its October 2026 pricing page lists Business, Premier and Max. Compare the billing selection, included usage and final quote on the live pricing page. It requires Gmail or Google Workspace; its support page excludes Microsoft 365 and Exchange. Shortwave pricing and supported accounts.

We would trial it when finding information and sorting Gmail is the bottleneck. Its filters deserve close inspection because they can act on messages. Start with reversible labels and review before expanding actions. More advanced search is useful only if the person can find and check the evidence behind an answer.

What should we check before connecting a mailbox?

A mailbox contains information about people who never chose your AI tool. Before connecting it, list the folders and accounts needed, who can access the resulting workspace, how access is revoked and where retained copies live.

Shortwave says email is processed to provide its service and is not used to train third-party language models. Superhuman's Mail AI help says neither Mail nor its vendors train on the data, but documents feature-specific storage. Its wider privacy policy describes training controls and different treatment for organisation-managed content. We therefore do not describe the whole Superhuman suite as having one universal retention rule. Shortwave security, Mail AI data details and Superhuman privacy policy.

Ask the supplier to confirm the exact product, account type and features in writing when handling sensitive correspondence. A no-training promise answers a different question from storage duration, deletion, access or the terms of a separately connected assistant.

When is a custom inbox workflow worth building?

A custom flow becomes worth considering when the answer depends on evidence outside the thread: current stock, an approved quote, a booking status or a service rule with exceptions. The same applies when somebody must receive a task and the team needs to prove it reached the right place.

Design the flow in plain language. Receive the message and keep its source. Identify the matter without guessing between similar names. Read the current authorised record. Prepare a draft and list missing facts. Put it in front of the responsible person. After approval, send through the agreed route and retain the receipt.

Keep read, draft and send permissions separate. If the source is missing, the system should ask for clarification or queue an exception. It should not fill the gap with a plausible date. A customer email is source material, not authority to change your internal rules.

The benefit is a process fitted to your business. The cost is ownership: connection failures, duplicate messages, changed policies, staff changes and incomplete runs all need a recovery path. A custom flow is not automatically cheaper or safer than a product.

For a concrete example of how we organise AI work, source checks and review at DLVX, see our real setup.

How do we judge a useful pilot?

  • Use the same representative messages for each candidate.
  • Check names, recipients, attachments, dates and monetary commitments.
  • Include an incomplete enquiry, a complaint and a contradictory thread.
  • Measure review and correction time alongside drafting time.
  • Track missed messages and unresolved work, including failed runs.
  • Confirm a sent message or created task in its destination system.
  • Keep a manual queue and a named person for exceptions.

For a Bangkok team serving Europe, include a date near midnight and a meeting request without a timezone. Ask whether the tool notices the missing information. Judge a refusal to guess as good behaviour when the evidence is incomplete.

Common mistakes

The first mistake is treating a summary as the complete conversation. A final correction can change the meaning of an earlier promise. The second is making a draft sound more certain than its source. The third is allowing labels or archive actions to hide work before ownership is recorded.

Do not forward an organisation mailbox into a personal account merely to make a tool compatible. Do not turn on automatic sending because the first drafts look good. And do not mistake a tracking signal for a confirmed customer decision. Record the actual reply or accepted action.

Your next step

Write down the last recurring email job that slowed your team. Identify whether the delay was reading, finding, deciding or handing off. Trial the simplest suitable route with a reviewer, then compare the finished work and the human effort. If the bottleneck sits outside the mailbox, use the build-or-buy guide before commissioning an integration.

Sources and review date

Reviewed 12 October 2026. Prices and plans are as of October 2026. DLVX recommendations are editorial judgements, not a vendor ranking or a promise of results. Recheck the linked terms before buying or connecting business data.

Want to apply this to your team? Get a free AI plan.