If you spend half an hour a day sorting mail, that's over two hours a week spent moving messages into folders a computer could have handled. Filters do that work before you ever open the app.
This guide covers seven automations worth building, in the order worth building them, plus the setup mistakes that make rules misfire and the ones that quietly hide messages you needed.
Build these seven: high-volume sender sorting, subject-line routing for automated reports, VIP alerts, attachment handling, follow-up flagging, newsletter routing, and auto-archiving. Run them server-side so they work on every device, put the VIP rule first, and test every new rule in label-only mode before letting it move anything.
Before You Start
Find your top senders. Sort the last week by sender. A handful of automated sources usually account for most of the volume, and those are your biggest wins.
Keep the folder structure small. Five or six is plenty: Action Required, Waiting On, Newsletters, Receipts, Notifications, Archive. Elaborate hierarchies create decisions, which is the thing you're trying to eliminate.
Check whether your rules run server-side. This is the single most important setting (see below).
Clear out old rules first. Overlapping rules created years apart are the main cause of "where did that email go?" Export them if you can, then start clean.
Server-side vs client-side matters more than anything else here. Server-side rules run on the mail server the moment a message arrives, so your phone, laptop, and webmail all show the same sorted inbox. Client-side rules only run when that particular app is open, which means your phone shows an unsorted inbox all day and the sorting happens whenever you next open your desktop client. If your provider supports server-side filters, use them.
1. Sort High-Volume Automated Senders
Condition: From contains @notifications.yourtool.com
Actions: Move to Notifications, mark as read
Notification mail from project tools, ticketing systems, and CI pipelines is the easiest category to automate, because you almost never need to act on individual messages. Moving them out and marking them read turns a hundred interruptions into one folder you check when you choose to.
Do this for your top few automated senders and most of your inbox noise disappears.
Pro tip: Match on the domain rather than the full address. One rule for
@slack.comcatches every notification variant, where address-specific rules need constant maintenance.
2. Route Recurring Reports and Invoices by Subject
Condition: Subject contains invoice AND has attachment
Actions: Move to Receipts, apply label
Automated reports arrive with predictable subject lines. Adding a second condition sharply improves accuracy: without "has attachment," a rule for "invoice" also catches every conversation where someone mentions an invoice, including the client asking why theirs is wrong.
A word on OR logic: syntax varies a lot. Gmail supports invoice OR receipt OR payment and curly-brace syntax, while many clients require a separate rule per term and some support no OR at all. Check your provider's documentation rather than assuming the pipe character works.
Think twice before auto-archiving invoices and receipts out of sight. They're often records you need to retain; see email retention policies.
3. Make VIP Messages Impossible to Miss
Condition: From is [your three to eight most important senders]
Actions: Never send to spam, star, keep in inbox, notify
Your biggest client, your manager, and your co-founder should never land in a folder you check on Fridays. Put this rule first in the list, because in clients that stop processing after a match, a VIP rule running after an archive rule never fires at all.
Keep the list short. A VIP list of twenty people isn't a priority signal, it's a second inbox, and the alerts stop meaning anything.
Pro tip: Add a companion rule for subjects containing "urgent" or "ASAP" from inside your own domain, so escalations from people not on the list still surface.
4. Handle Attachments Deliberately
Condition: Has attachment AND size greater than 5 MB
Actions: Move to "To File," apply label
Large attachments are what fill mailboxes. A rule that gathers them into one folder lets you file them in a single batch instead of interrupting yourself each time one arrives.
One correction to advice you'll see elsewhere: mail rules generally cannot push attachments into cloud storage. Some services give you a dedicated upload address you can forward to, and some integrations handle it, but a plain filter can't. The batching approach above works everywhere.
The better long-term fix is sending fewer attachments in the first place; see our guide to sharing files with clients.
5. Flag Things That Need Follow-Up
Condition: Subject contains deadline, due, by EOD, expires, or renewal
Actions: Flag for follow-up, move to Action Required
Deadlines hide in email bodies, and a flag at the moment of arrival beats remembering later.
An important limitation: most filters only run when a message arrives, so a rule like "escalate anything in Action Required older than three days" isn't something standard filters can do. Handle the time dimension with a saved search sorted by date, a recurring calendar reminder to review the folder, or a task tool. Don't build a system that depends on an automation your client can't run.
6. Route Newsletters to a Read-Later Folder
Condition: List-Unsubscribe header exists, or From contains known newsletter senders
Actions: Move to Newsletters, mark as read
Bulk mail nearly always carries an unsubscribe header, which makes it easy to identify where your provider lets you filter on headers. Failing that, add senders as you go.
Then actually read the folder weekly, or unsubscribe. A read-later folder you never open is just a slower delete.
7. Auto-Archive Low-Value Mail
Condition: From contains [sender] AND older than [period], where supported
Actions: Move to Archive
Archiving keeps the working inbox small. Two rules, though: never set a filter to permanently delete, because you'll eventually delete something you needed, and don't archive anything that's a business record. Archive means "out of sight, still searchable."
Example: A 14-Person Agency
The following is an illustrative scenario.
An agency owner spends most of her first hour each morning sorting mail. Her inbox is dominated by six sources: a project tool, two client workspaces, a billing system, a newsletter platform, and the team's shared address.
In one sitting she builds the seven rules above. Project notifications and newsletters leave the inbox entirely. Invoices land in Receipts with their attachments. Her five key clients are starred and stay visible. Large design files collect in "To File" for a single daily pass. Deadline keywords get flagged.
What changes isn't just the time spent sorting. It's that the first thing she sees each morning is a short list of messages that genuinely need a human reply, instead of a hundred items she has to triage before she can think.
Which Rules to Build First
Under 50 messages a day: start with sender sorting, VIP alerts, and newsletter routing. That's most of the benefit for fifteen minutes of setup.
Sales and client services: VIP alerts and follow-up flagging first. Missing a client message costs more than a cluttered folder.
Operations and finance: attachment handling and receipt routing, with retention in mind.
Team leads: agree a shared convention for the team's shared inbox so everyone sees the same labels and statuses, rather than each person inventing their own.
Test any new rule for a week before relying on it. Watch what it catches and what it catches wrongly.
Why Automation Helps More Than It Looks
The saving isn't just the seconds spent dragging messages. Email triage is interruption work, and research by Gloria Mark at UC Irvine found that people took an average of about 23 minutes to return to a task after being interrupted. Filters remove the interruption for whole categories of mail: you never see the notification, so there's nothing to recover from.
Rules also make your inbox predictable, which is what lets you trust it. An inbox you trust gets processed in batches at times you choose. An inbox you don't trust gets checked constantly, which is the actual time sink.
Common Mistakes
Rules that are too broad. Moving everything from a whole consumer domain will bury something important. Pair a broad condition with a narrowing one.
Wrong rule order. Many clients process top to bottom and some stop at the first match. Put VIP and exception rules above sweeping ones, and check whether your client has a "stop processing further rules" option.
Deploying untested. Run new rules in label-only mode for a week, applying a label without moving anything, so you can see exactly what they'd have caught.
Building ten at once. Ten new rules means ten new ways to lose an email. Add one, verify, then add the next.
Never reviewing the folders. Automation sorts; it doesn't judge. Scan Notifications and Archive weekly for anything that needed you.
Auto-deleting. Route to Archive instead. Deleted is unrecoverable once your provider's window passes; see our guide to business email backup.
Leaving rules behind when people leave. Forwarding rules in a departing employee's mailbox are both a continuity and a security problem; see what to do with an employee's email when they leave.
FAQ
How many rules should I have?
Start with three to five and grow slowly. Past a dozen, conflicts and maintenance usually outweigh the benefit.
Do filters work on my phone?
If they run server-side, yes, because sorting happens before the message reaches any device. Client-side rules only run in the app where you created them.
What happens when two rules match?
It depends on the client. Some apply every matching rule; others stop at the first match or at a rule marked "stop processing." Order rules from most specific to least, and test.
Can filters send automatic replies?
Some clients can trigger auto-replies on conditions. Keep these to confirmations and absence notices; generic auto-replies to real people read as dismissive.
Can a rule act on old messages?
Most filters only run on arrival, though some clients can apply a filter retroactively to existing mail as a one-off. Time-based escalation generally needs a saved search or a reminder instead.
Do filters break search or compliance?
No, as long as you move rather than delete. Filtered mail stays searchable. Never auto-delete anything you might need as a record.
How often should I review my rules?
Monthly, and after any role change. Delete rules that haven't matched anything in a month.
Should the whole team use the same rules?
Agree conventions for shared addresses so the team sees consistent labels. Personal inboxes are better left to personal preference.
Run Your Rules on Email You Control
NevTan Mail gives your team secure, ad-free email on your own domain, with a calendar, meetings, and notes alongside the inbox, mailboxes, aliases and groups managed from one console, guided SPF, DKIM, DMARC and Autodiscover setup, and two-factor authentication with security key support. Up to 10 mailboxes are free forever, with paid storage from $2 per mailbox per year.
Related reading: A beginner's guide to shared team inboxes · How many business email accounts do you need? · All articles
