Your Inbox Belongs to Machines: Only 13% of Email Is Written by Humans

Long before chat apps arrived, the inbox had quietly become a notification channel. Today most of it is written by machines.

Illustration: An inbox tray overflowing with automated notification cards and a single personal message

Open your work inbox and count the messages a person actually wrote. Task updates, comment alerts, calendar changes, sign-in warnings, digests: a large share comes from tools, not people. Machine-generated email is now the majority of what most of us receive, and it is changing what the inbox is for.

13%Of emails written by humans, in a billion-email sample
90%+Of non-spam webmail traffic is machine-generated
63%Of US workers check email outside working hours

The inbox already belongs to machines

Yahoo researchers studying the company's webmail found that machine-generated messages make up more than 90% of non-spam traffic, and that most of that traffic is never read (WSDM 2018). A more recent study points the same way. When Hostinger analysed around a billion emails received by its customers in January 2026, only 13% were written by humans, and business tools were among the most automated senders (Hostinger).

Free ebookThe Language of InterruptionThe research behind every notification you get at work: where they came from, what they cost and what to do about them. 131 pages, free PDF.Get it free →

Why tools email you

Think of the café loyalty card that sends a reminder just as you were about to forget it. Work tools do the same with email: every notification email is a small knock on the door, asking you to step back inside the app. Some knocks are genuinely useful. Email reaches you when you are away; Asana's 2022 research found 63% of US workers check email outside working hours (CIO Dive). It reaches clients and occasional users who never open the tool. And it leaves a record you can forward or save for an audit.

Many of the rest arrive for a plainer reason: they were switched on from the start. Asana enables email notifications for new users, and Jira attaches a default notification scheme to every new project (Atlassian). Like a newspaper subscription that began as a free trial, they keep arriving because nobody cancelled them.

When a tool absolutely must reach you, it does not rely on its own app. It chooses your inbox.

The echo problem

Follow one client onboarding. The signed contract arrives in Gmail, as you would expect. But so does the kickoff invite, copied from the calendar, and so does every comment on the Asana project. The engineering team connected Jira to Slack, so every comment on the setup ticket lands in a channel too. By the end of week one, seven notifications at the source have become thirteen.

Those echoes carry real costs: duplicates of the same event, delay when bundles arrive late, lost context when a copy shows one message without its thread, split replies when someone answers from the wrong place, and pressure. In the same Asana research, 62% of US workers said they feel the need to respond to emails immediately.

Calculator · Inbox echo

How much of your inbox is an echo?

Estimate the copies your tools send to your inbox each week, and the time they take to clear.

This interactive part needs JavaScript.

Where email notifications are heading

Inbox providers are raising the bar. Since February 2024, Gmail and Yahoo have required large senders to authenticate their mail, offer one-click unsubscribe and keep spam complaints under 0.3%, and Outlook followed in 2025 (Mailsuite). They are also sorting on the reader's behalf: Gmail's tabs send most tool notifications to Updates, and Outlook's Focused Inbox filters automated mail into Other. When Google tested Priority Inbox internally, people spent 6% less time reading email overall and 13% less on unimportant email (Google). Useful, but sorting makes the inbox calmer to look at. It does not reduce how much arrives.

The likely direction: email narrows from an alarm for every event to the channel for what you missed, what you must keep, and people outside the tool. Chat becomes the live feed, email the archive. Neither is where the work lives. For practical steps, see how to stop context switching between Slack, Gmail and Asana.

Frequently asked questions

How much email is written by humans?

In Hostinger's analysis of about a billion emails received in January 2026, only 13% were written by humans. Earlier Yahoo research found machine-generated mail made up over 90% of non-spam traffic.

Why do work tools send so many emails?

Email reaches people when they are away, reaches people outside the tool, and creates a record. Many tools also switch email notifications on by default, so they keep arriving until someone changes the setting.

Should I turn off email notifications from Slack, Asana or Jira?

Turn off the copies of things you already see in the app, and keep email for what you missed while away, for records, and for people outside the tool.

Sources

  1. Unsubscription: a simple way to ease overload in email, WSDM 2018
  2. Our one-billion-email analysis, Hostinger (2026)
  3. Notification fatigue is tanking productivity, report says (Asana 2022), CIO Dive
  4. Configure notification schemes, Atlassian Support
  5. 2024 Google sender guidelines, Mailsuite
  6. Aberdeen, Pacovsky and Slater, The learning behind Gmail Priority Inbox, Google (2010)

Email is not disappearing. It is narrowing: from the alarm for every event to the archive of what you must keep.

MMWritten byMarina MaksimovicFounder of Noticue and author of The Language of Interruption. She writes about how work notifications shape our attention, and builds the app that digests them.
One inbox for Slack, Gmail, Outlook and Asana.Noticue reads every notification, tells you what is urgent and plans your day. Free for the first 200 members.Get early access
Free for the first 200 members

Your unified notification inbox for Slack, Gmail, Outlook and Asana.

Every alert understood, prioritised, and ready to act on. We don’t manage your work. We digest it for you.

No credit card needed